It's common for Ubuntu packages to be present in multiple repositories. For example, updates to a package in xenial might go to xenial-security and xenial-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 on linux-headers-4.4.0-75-generic in xenial-security and on linux-headers-4.4.0-77-generic in xenial-updates. If I have xenial-security listed first, then bcfg2 wants to see version 75, but apt installs 77.
My workaround for this is to rearrange the sources as necessary, but that won't work in every case.
It's common for Ubuntu packages to be present in multiple repositories. For example, updates to a package in
xenialmight go toxenial-securityandxenial-updatesat different times. In the absence of priorities,aptdeals 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-genericcurrently depends onlinux-headers-4.4.0-75-genericinxenial-securityand onlinux-headers-4.4.0-77-genericinxenial-updates. If I havexenial-securitylisted first, then bcfg2 wants to see version 75, butaptinstalls 77.My workaround for this is to rearrange the sources as necessary, but that won't work in every case.