Syncing a repository with a Packages directory results many duplicate symlinks
I noticed this when investigating #1654 and I didn't look into it too much, but when we sync repositories with a Packages directory, it seems we recreate the Packages directory complete with symlinks to every piece of content. However, we also publish the packages to the root of the repository, and the metadata in `repodata` seems to refer exclusively to these. We're creating a lot of extra symlinks that we don't need to be making.
1. sync /content/dist/rhel/server/7/7Server/x86_64/kickstart/ from the CDN or some mirror
2. inspect the published repository and note the Packages/ directory with its many symlinks.
#4 Updated by email@example.com over 5 years ago
- Status changed from ASSIGNED to NEW
- Assignee deleted (
Upon long investigation, this appears to intentional behavior and only occurs when syncing a repository that contains a "Distribution". I'm going to unassign this for now and will re-evaluate it as part of the distribution-related story I am about to write.
#7 Updated by firstname.lastname@example.org over 5 years ago
- Triaged changed from No to Yes
I believe the solution to this is to correctly handle treeinfo files. They have a concept of a repository in them (either in the variant section or in the deprecated general section) that may or may not be 'Packages'. We do some things to try and make this work, but I don't think we do a good job of it. A possible solution (I am not sure if it is the right one) is to not always symlink the rpms to the root of a the repository and instead use the distribution to decide the layout.
#9 Updated by bmbouter over 2 years ago
- Status changed from NEW to CLOSED - WONTFIX
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.
Please register to edit this issue