-
Notifications
You must be signed in to change notification settings - Fork 78
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
Rework No-Support-for-Architecture-all format sync handling #456
Labels
.misc
CHANGES/<issue_number>.misc
Comments
quba42
added
Triage-Needed
.misc
CHANGES/<issue_number>.misc
and removed
Triage-Needed
labels
Mar 17, 2022
quba42
added a commit
to ATIX-AG/pulp_deb
that referenced
this issue
Mar 17, 2022
Closes pulp#456 pulp#456 When a repo uses "No-Support-for-Architecture-all: Packages" style format, we should not warn about all architecture packages in architecture specific package indices! They are expected to be there! We still skip those packages since there is no need to download them twice! When a mirror mirrors metadata indicating "No-Support-for-Architecture-all: Packages" format, while failing to mirror the binary-all package indices we introduce special handling to ensure we nevertheless sync "Architecture: all" packages.
quba42
added a commit
to ATIX-AG/pulp_deb
that referenced
this issue
Mar 17, 2022
Closes pulp#456 pulp#456 When a repo uses "No-Support-for-Architecture-all: Packages" style format, we should not warn about all architecture packages in architecture specific package indices! They are expected to be there! We still skip those packages since there is no need to download them twice! When a mirror mirrors metadata indicating "No-Support-for-Architecture-all: Packages" format, while failing to mirror the binary-all package indices we introduce special handling to ensure we nevertheless sync "Architecture: all" packages.
quba42
added a commit
to ATIX-AG/pulp_deb
that referenced
this issue
Mar 17, 2022
Closes pulp#456 pulp#456 When a repo uses "No-Support-for-Architecture-all: Packages" style format, we should not warn about all architecture packages in architecture specific package indices! They are expected to be there! We still skip those packages since there is no need to download them twice! When a mirror mirrors metadata indicating "No-Support-for-Architecture-all: Packages" format, while failing to mirror the binary-all package indices we introduce special handling to ensure we nevertheless sync "Architecture: all" packages. For more info, see: https://wiki.debian.org/DebianRepository/Format#No-Support-for-Architecture-all
quba42
added a commit
to ATIX-AG/pulp_deb
that referenced
this issue
Mar 17, 2022
Closes pulp#456 pulp#456 When a repo uses "No-Support-for-Architecture-all: Packages" style format, we should not warn about all architecture packages in architecture specific package indices! They are expected to be there! We still skip those packages since there is no need to download them twice! When a mirror mirrors metadata indicating "No-Support-for-Architecture-all: Packages" format, while failing to mirror the binary-all package indices we introduce special handling to ensure we nevertheless sync "Architecture: all" packages. For more info, see: https://wiki.debian.org/DebianRepository/Format#No-Support-for-Architecture-all
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Many upstream repos declare the
No-Support-for-Architecture-all: Packages
option in their release file. For example, most official Debian bullseye repos.This format results in a number of edge cases requiring special handling.
For example, we should not warn about
Architecture: all
packages in architecture specific indices for such repos.Even more problematically, deb-mirror may mirror the metadata indicating
No-Support-for-Architecture-all: Packages
format, while failing to mirror thebinary-all
package indices (which actually results in "old style repo format" while declaring "mixed style repo format"). This two requires special handling, or theArchitecture: all
packages will either not be synced or cause outright sync failures for such mirrors! (which depends on the value ofignore_missing_package_indices
).The text was updated successfully, but these errors were encountered: