Upgrade to Meteor 2.13 leads to failure on node modules installation

help
26

Any idea how this can be solved, RJ?

27

The team just launched a new version to fix this issue. Can you try again using the 2.13.3 version?

28

I will try to rebuild it again but like I wrote I didn’t install 2.13.1 either so I still don’t understand why it selected that specific version for the Meteor tool.

29

The fix worked @hschmaiske - thanks to the team for such a quick solution

1 Like
30

Glad it worked @a4xrbj1!

31

@a4xbj1, we use a docker based on version 14-bulleye-slim for distribution. @grubba, could you please tell us which distribution you use on which platforms it works?

32

Can you explain what happened and what was done to fix it? “Here’s a fix” is not very instructive to understanding the root cause and the change needed to make it work. Clear summarizations make these threads far more useful for future readers, increases trust, and reduces frustration from both users and those called upon to help.

3 Likes
33

@grubba: with version 2.13.3, which is neither documented nor officially released, it seems to work correctly. Where should we look to be updated on these important changes? We are talking about sites in production with an uncertified version of node. Thank you.

1 Like
34

Hey, there is a changelog for 2.13.3

https://docs.meteor.com/changelog#v213320230908

2 Likes
35

For those of us not working on the codebase, it isn’t so clear what changes were made to fix the release. Based upon reading the changelog, I understand

  1. The ESM Node.js release (v 14.21.4.3) was compiled on a CentOS Linux distro.
  2. The release (v 14.21.4.1) that was creating the error posted above was because it was compiled on a Ubuntu Linux distro.

Do I have that right?

36

Yeah, Alim! You got it. I’ve made this fix while travelling. That is the reason why it is missing some pieces. I’m planning on starting working today on adjusting these edges.

2 Likes
37

Just a heads up @grubba that CentOS 7 will EOL next year. I supposed this is what you are using to get a low version glibc that is still maintained.

Rocky linux looks like a viable option for long term support short of going straight to RHEL. Rocky linux 8 will bump glibc to 2.28.

Ubuntu 20.04 is at 2.31.

2 Likes
38

Thanks! @rjdavid will let the DevOps team know.

39

Thanks for this fix.

I am trying to run the Meteor 3 version (METEOR@3.0-alpha.11) to start testing and being familiar with the next version, and I am running with the same issue mentioned here on my system (using still an older version of Ubuntu 20.04).

Error: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33’ not found

Will you include the fix from 2.13.3 about the glibc in the next Meteor 3 alpha version?

PD: Not blocking my testing actually since I provisioned a WSL Ubuntu 22.04 for the testing.

2 Likes
40

@grubba …also fourseven:scss has a problem after upgrading to 2.13.

41

Hey, what is the error you are receiving? Maybe is related to this issue[solved]?

42

I will check with the team what happened! thanks a lot for pinging and testing the alpha version @nachocodoner

1 Like
43

Hi @grubba, I solved it by rewrite the package to dart-sass (nodsec:scss) instead of using old deprecated node-sass. Still there are a mistakes which I will fix, but It works.

44

…but I have another headache which dependabot, which is creating something like aliases in package-lock.json, which makes a problem with old meteor npm version :frowning:

46

Solved with Meteor 2.13.3 ! Thank you.

2 Likes