apt::backports pins the wrong suite #1187
Labels
Comments
kenyon
added a commit
to kenyon/puppetlabs-apt
that referenced
this issue
Jun 10, 2024
Debian 11 bullseye and Debian 12 bookworm backports release files look like this: https://deb.debian.org/debian/dists/bullseye-backports/InRelease: Suite: bullseye-backports Codename: bullseye-backports https://deb.debian.org/debian/dists/bookworm-backports/InRelease: Suite: stable-backports Codename: bookworm-backports Using "release" (aka Suite in the InRelease file) causes our pin to not match for bookworm because they changed it to stable-backports instead of $codename-backports. We can use codename to support both for this pin. Fixes puppetlabs#1187.
|
#1188 should fix this. |
kenyon
added a commit
to kenyon/puppetlabs-apt
that referenced
this issue
Jun 10, 2024
Debian 11 bullseye and Debian 12 bookworm backports release files look like this: https://deb.debian.org/debian/dists/bullseye-backports/InRelease: Suite: bullseye-backports Codename: bullseye-backports https://deb.debian.org/debian/dists/bookworm-backports/InRelease: Suite: stable-backports Codename: bookworm-backports Using "release" (aka Suite in the InRelease file) causes our pin to not match for bookworm because they changed it to stable-backports instead of $codename-backports. We can use codename to support both for this pin. Fixes puppetlabs#1187.
kenyon
added a commit
to kenyon/puppetlabs-apt
that referenced
this issue
Jun 10, 2024
Debian 11 bullseye and Debian 12 bookworm backports release files look like this: https://deb.debian.org/debian/dists/bullseye-backports/InRelease: Suite: bullseye-backports Codename: bullseye-backports https://deb.debian.org/debian/dists/bookworm-backports/InRelease: Suite: stable-backports Codename: bookworm-backports Using "release" (aka Suite in the InRelease file) causes our pin to not match for bookworm because they changed it to stable-backports instead of $codename-backports. We can use codename to support both for this pin. Fixes puppetlabs#1187.
kenyon
added a commit
to kenyon/puppetlabs-apt
that referenced
this issue
Jun 15, 2024
Debian 11 bullseye and Debian 12 bookworm backports release files look like this: https://deb.debian.org/debian/dists/bullseye-backports/InRelease: Suite: bullseye-backports Codename: bullseye-backports https://deb.debian.org/debian/dists/bookworm-backports/InRelease: Suite: stable-backports Codename: bookworm-backports Using "release" (aka Suite in the InRelease file) causes our pin to not match for bookworm because they changed it to stable-backports instead of $codename-backports. We can use codename to support both for this pin. Fixes puppetlabs#1187.
kenyon
added a commit
to kenyon/puppetlabs-apt
that referenced
this issue
Oct 4, 2024
Debian 11 bullseye and Debian 12 bookworm backports release files look like this: https://deb.debian.org/debian/dists/bullseye-backports/InRelease: Suite: bullseye-backports Codename: bullseye-backports https://deb.debian.org/debian/dists/bookworm-backports/InRelease: Suite: stable-backports Codename: bookworm-backports Using "release" (aka Suite in the InRelease file) causes our pin to not match for bookworm because they changed it to stable-backports instead of $codename-backports. We can use codename to support both for this pin. Fixes puppetlabs#1187.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Bug
include apt::backportspins the wrong repository on Debian bookworm.As we can see, the backports are registered as
a=stable-backports. However the pinning that is used (in file/etc/apt/preferences.d/backports.pref) reads:Manually overriding the release for
apt::backportssolves the problem but I suppose this should rather work out of the box as there is no warning generated anywhere and the mistake is not really obvious to discover.The text was updated successfully, but these errors were encountered: