Do not validate_duplicate_content for APT repositories #632
Labels
.bugfix
CHANGES/<issue_number>.bugfix
Comments
quba42
added a commit
to ATIX-AG/pulp_deb
that referenced
this issue
Aug 31, 2022
closes pulp#632 Using validate_duplicate_content prevents successfull synchronization when multiple package indices contain references to the same package. However, this is an entirely legitimate situation for separate distributions/releases within a single APT repo. Further more, the so created duplicate package content, does not cause any adverse effects, since it is actually identical and only one of each duplicate will be saved.
quba42
added a commit
to ATIX-AG/pulp_deb
that referenced
this issue
Aug 31, 2022
closes pulp#632 Using validate_duplicate_content prevents successfull synchronization when multiple package indices contain references to the same package. However, this is an entirely legitimate situation for separate distributions/releases within a single APT repo. Further more, the so created duplicate package content, does not cause any adverse effects, since it is actually identical and only one of each duplicate will be saved. Note that this issue was masked prior to the introduction of the optimize sync feature, since we were inadvertently using the Repository class from pulpcore instead of the AptRepository class from pulp_deb.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using validate_duplicate_content prevents successful synchronization when multiple package indices contain references to the same package. However, this is an entirely legitimate situation for separate distributions/releases within a single APT repo. Further more, the so created duplicate package content, does not cause any adverse effects, since it is actually identical and only one of each duplicate will be saved.
Note, that this bug was masked until the optimize feature was added, because we were using
Repositoryinstead ofAptRepositoryduring sync, inadvertently skipping the problematic check.The text was updated successfully, but these errors were encountered: