Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ERROR] Node.js 18+ incorrect control file information #1492

Closed
theofficialgman opened this issue Dec 31, 2022 · 5 comments
Closed

[ERROR] Node.js 18+ incorrect control file information #1492

theofficialgman opened this issue Dec 31, 2022 · 5 comments
Assignees
Labels

Comments

@theofficialgman
Copy link

theofficialgman commented Dec 31, 2022

Describe your bug
This bug has been incorrectly closed months ago (#1392 (comment)) and is still unfixed. the control file is incorrect in nodejs18+

Package: nodejs
Version: 18.9.1-deb-1nodesource1
Architecture: arm64
Maintainer: Ivan Iguaran <ivan@nodesource.com>
Installed-Size: 174931
Depends: libc6 (>= 2.17), libgcc1 (>= 1:4.2), libstdc++6 (>= 5.2), python3-minimal, ca-certificates

nodejs 18 depends on much higher than libc6 2.17, libstdc++6 5.2, etc. please fix your pipeline @igsu
I haven't checked the rpms but I assume they are also similarly broken

Distribution Information:

  • OS: all
@riosje
Copy link
Contributor

riosje commented Mar 9, 2023

This has been fixed a couple of weeks ago.
now the control file shows glibc1.28 as dependency.

@riosje riosje closed this as completed Mar 9, 2023
@theofficialgman
Copy link
Author

@riosje please reopen. the issue is not fully fixed
there should not be a bionic apt repo for nodejs 18/19/+ as the dependencies can not be resolved, yet there still is
https://deb.nodesource.com/node_18.x/dists/bionic/main/binary-arm64/Packages
https://deb.nodesource.com/node_19.x/dists/bionic/main/binary-arm64/Packages

@riosje
Copy link
Contributor

riosje commented Mar 9, 2023

Hi @theofficialgman yes you're right, we're working to remove those packages from non supported distros and this will take an extra time, but at this moment at least the control file will fail the installation because the distro doesn't meet the minimum requirements.

@theofficialgman
Copy link
Author

it has been 2 months and the non-supported distros still have these versions on their repos

@cobalt2727
Copy link
Contributor

Looks like we're coming up on the anniversary of this issue! How time flies. I guess that means it's actually been about a year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants