Actions
Bug #38239
openDebian backports priorities
Description
With a Debian machine configured with the regular `debian.sources`, the priorities are as follow:
```- apt-cache policy
Package files:
100 /var/lib/dpkg/status
release a=now
500 mirror+file:/etc/apt/mirrors/debian-security.list bookworm-security/main amd64 Packages
release v=12,o=Debian,a=stable-security,n=bookworm-security,l=Debian-Security,c=main,b=amd64
100 mirror+file:/etc/apt/mirrors/debian.list bookworm-backports/main amd64 Packages
release o=Debian Backports,a=stable-backports,n=bookworm-backports,l=Debian Backports,c=main,b=amd64
500 mirror+file:/etc/apt/mirrors/debian.list bookworm-updates/main amd64 Packages
release v=12-updates,o=Debian,a=stable-updates,n=bookworm-updates,l=Debian,c=main,b=amd64
500 mirror+file:/etc/apt/mirrors/debian.list bookworm/main amd64 Packages
release v=12.9,o=Debian,a=stable,n=bookworm,l=Debian,c=main,b=amd64
500 https://oss.atix.de/Debian12 stable/main amd64 Packages
release a=stable,n=stable,l=stable,c=main,b=amd64
origin oss.atix.de
```
```
- apt-cache policy
Package files:
100 /var/lib/dpkg/status
release a=now
500 katello://kat.xavbac.lab/pulp/content/XavBac_Lab/Dev/CV_debian_base/custom/Atix/Debian_12 stable/main all Packages
release a=stable,n=stable,l=stable,c=main,b=all
origin kat.xavbac.lab
500 katello://kat.xavbac.lab/pulp/content/XavBac_Lab/Dev/CV_debian_base/custom/Atix/Debian_12 stable/main amd64 Packages
release a=stable,n=stable,l=stable,c=main,b=amd64
origin kat.xavbac.lab
500 katello://kat.xavbac.lab/pulp/content/XavBac_Lab/Dev/CV_debian_base/custom/Debian_12/Debian_12_full bookworm/main all Packages
release v=12.9,o=Debian,a=stable,n=bookworm,l=Debian,c=main,b=all
origin kat.xavbac.lab
500 katello://kat.xavbac.lab/pulp/content/XavBac_Lab/Dev/CV_debian_base/custom/Debian_12/Debian_12_full bookworm/main amd64 Packages
release v=12.9,o=Debian,a=stable,n=bookworm,l=Debian,c=main,b=amd64
origin kat.xavbac.lab
500 katello://kat.xavbac.lab/pulp/content/XavBac_Lab/Dev/CV_debian_base/custom/Debian_12/Debian_12_full bookworm-updates/main all Packages
release v=12-updates,o=Debian,a=stable-updates,n=bookworm-updates,l=Debian,c=main,b=all
origin kat.xavbac.lab
500 katello://kat.xavbac.lab/pulp/content/XavBac_Lab/Dev/CV_debian_base/custom/Debian_12/Debian_12_full bookworm-updates/main amd64 Packages
release v=12-updates,o=Debian,a=stable-updates,n=bookworm-updates,l=Debian,c=main,b=amd64
origin kat.xavbac.lab
500 katello://kat.xavbac.lab/pulp/content/XavBac_Lab/Dev/CV_debian_base/custom/Debian_12/Debian_12_full bookworm-backports/main all Packages
release o=Debian Backports,a=stable-backports,n=bookworm-backports,l=Debian Backports,c=main,b=all
origin kat.xavbac.lab
500 katello://kat.xavbac.lab/pulp/content/XavBac_Lab/Dev/CV_debian_base/custom/Debian_12/Debian_12_full bookworm-backports/main amd64 Packages
release o=Debian Backports,a=stable-backports,n=bookworm-backports,l=Debian Backports,c=main,b=amd64
origin kat.xavbac.lab
500 https://oss.atix.de/Debian12 stable/main amd64 Packages
release a=stable,n=stable,l=stable,c=main,b=amd64
origin oss.atix.de
Pinned packages:
```
One can notice the priority for the backports repo is 100 in the regular repos case, while it's 500 with the Katello repos.
As such the apt behaviour will be different, preferring the packages from the backports repo, while one would have expected to have only the packages installed explicitly from the backports repo to be considered.
No data to display
Actions