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.

Sign up for GitHub

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

Jump to bottom

[Issue] debian package pools are no longer browsable #1633

Closed
skaes opened this issue Aug 30, 2023 · 4 comments
Closed

[Issue] debian package pools are no longer browsable #1633

skaes opened this issue Aug 30, 2023 · 4 comments
Assignees
@riosje
Labels
bug

Comments

@skaes
Copy link

skaes commented Aug 30, 2023

Describe your bug

We have an internal mirror for a subset of the nodejs packages. Once per day we used to sync with upstream by parsing the directory listings like "https://deb.nodesource.com/node_18.x/pool/main/n/nodejs/" to detect packages missing on our mirror and copying them to our internal package server.

But the listings are no longer available and so this doesn't work anymore.

It is my understanding that the packages are still there, it's just that the listing isn't shown anymore. Correct?

We established this rather complicated process because previously only the latest package version for each release branch could be installed and this wasn't acceptable.

Would it be possible to expose the listing again?

If not, is there some other HTTP API endpoint to retrieve the package list?

To Reproduce
Open https://deb.nodesource.com/node_18.x/pool/main/n/nodejs/ in the browser. No directory listing.

Expected behavior
Directory listing shown.
@skaes skaes added the bug label Aug 30, 2023
@riosje riosje self-assigned this Aug 30, 2023
@riosje
Copy link
Contributor

riosje commented Aug 30, 2023

Hi @skaes hope you're doing well today.
As you mentions there is not anymore the option to list the folders, this is because we migrated from a traditional filesystem exposed with Nginx to use an Object Storage.

First thing, I highly suggest you to migrate to our new repo.
How-to-migrate-to-the-new-repository

Second, You don't need anymore download locally some specific version, with our new repository is now possible to install an specific version, follow these instructions.
How-to-select-the-Node.js-version-to-install

Also I understand you may still want to have a mirror of the packages, for this I encourage you to use APTLY to create that mirror.
https://www.aptly.info/doc/aptly/mirror/create/

We have a section in our wiki with this topic, at this moment is only documented for RPM but we're still writing the instructions for DEB, anyway if you follow the APTLY docs you will be ok.
Creating-a-Repository-Mirror

@riosje riosje changed the title [Issue] debian package pools are now longer browsable [Issue] debian package pools are no longer browsable Aug 30, 2023
@skaes
Copy link
Author

skaes commented Aug 30, 2023

Hi @riosje, thx for the quick answer.

We are already using aptly. We'll adapt.

@skaes skaes closed this as completed Aug 30, 2023
@daragonstormshield
Copy link

Hey, is it possible to mirror it using Sonatype Nexus ?

luislavena added a commit to luislavena/hydrofoil-php that referenced this issue Oct 8, 2023
@luislavena
8.x: Switch NodeJS sources to use latest ones
7b34d17 
Nodesource.com changed how repositories are provided and this broke
building the images.

Since this dockerfiles do not install the remote repository, updated the
URL format to the new one and adjusted the SHA256 of each of the
packages.

Ref:
nodesource/distributions#1633
@PlusLake
Copy link

Not an exactly workaround, but you can add the deb repo,
and apt install nodejs --print-uris to get the direct link to the debian packages

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@riosje riosje

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@skaes @PlusLake @riosje @daragonstormshield