Relax strict version constraints for DEB package dependencies. #17681
+13
−13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Outside of a few cases involving eBPF, we don’t actually need to have an exact match between individual package component versions. Removing this constraint significantly simplifies our dependency graph, and should both speed up updates, and also make them much more reliable. This will also simplify consolidation of dependency handling across package types, because our package names are identical between DEB and RPM packages.
github-actions
bot
added
the
area/packaging
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Outside of a few cases involving eBPF, we don’t actually need to have an exact match between individual package component versions.
Removing this constraint significantly simplifies our dependency graph, and should both speed up updates, and also make them much more reliable.
This will also simplify consolidation of dependency handling across package types, because our package names are identical between DEB and RPM packages.
Test Plan
Requires manually checking that the package dependencies are updated correctly.