-
Notifications
You must be signed in to change notification settings - Fork 58
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
Source order affects package dependencies #387
Comments
I have a local patch, that adds priorities to the sources. It should be possible to select the package with the highest version, if multiple sources have the same priority. (Even if it could be really hard to compare debian version numbers.) |
@AlexanderS that could be useful but I guess we achieve the same effect by sorting? What case is covered by having a priority that wouldn't be covered by sorting sources? |
A priority attribute would allow us to define two or more sources with equal priorities. |
To add to this: This would limit the choices for the priority values to apt preference settings, but would reflect the source ordering to clients that run with packages version: any |
It's common for Ubuntu packages to be present in multiple repositories. For example, updates to a package in
xenial
might go toxenial-security
andxenial-updates
at different times. In the absence of priorities,apt
deals with this by installing the latest version from any repository.This works fine with bcfg2 so long as the dependencies are the same across repositories. If they differ, then bcfg2 arbitrarily selects the dependencies from the first repository that has the package (ref).
I've found this to be problematic with kernel packages. For example,
linux-headers-generic
currently depends onlinux-headers-4.4.0-75-generic
inxenial-security
and onlinux-headers-4.4.0-77-generic
inxenial-updates
. If I havexenial-security
listed first, then bcfg2 wants to see version 75, butapt
installs 77.My workaround for this is to rearrange the sources as necessary, but that won't work in every case.
The text was updated successfully, but these errors were encountered: