This message was deleted.
# forge-modules
s
This message was deleted.
p
@simonhoenscheid could you tell us the version of apt your using? we will look into this issue…
s
9.2.0, latest release
thankyou 1
k
hmm, that's weird, the default pin of 200 is working for me on Ubuntu 20.04 and 22.04. I wonder if Debian repos are different somehow
I also have Debian 11 machines, and the default pin of 200 is working there too
I think this is why, they changed the Suite format for bookworm:
Copy code
kenyon@beta ~ % curl --no-progress-meter https://deb.debian.org/debian/dists/bullseye-backports/Release | grep -FA1 Suite:
Suite: bullseye-backports
Codename: bullseye-backports

kenyon@beta ~ % curl --no-progress-meter https://deb.debian.org/debian/dists/bookworm-backports/Release | grep -FA1 Suite:
Suite: stable-backports
Codename: bookworm-backports
Suite is
a=...
, Codename is
n=...
(from apt_preferences(5))
👍 1
can't just change it to use Codename, also have to handle Ubuntu, which is slightly different:
Copy code
kenyon@beta ~ % curl --no-progress-meter http://archive.ubuntu.com/ubuntu/dists/jammy-backports/Release | grep -F -e Suite: -e Codename:
Suite: jammy-backports
Codename: jammy

kenyon@beta ~ % curl --no-progress-meter http://archive.ubuntu.com/ubuntu/dists/focal-backports/Release | grep -F -e Suite: -e Codename:
Suite: focal-backports
Codename: focal
s
That’s the reason! I can open an issue and provide a PR if it makes sense to handle this as an exception
k
yes, sounds good to me, thanks
s
@Parvez Malik are you fine with that too?
k
maybe this would be a good use of hiera data in the module
s
Is puppet finally taking Debian 12 support in their metadata.json? I know Debian 12 puppet agents should be there soon, according to the ML.
k
oh I don't know, doesn't hurt to try putting up a PR. I suppose tests won't work in puppetlabs modules until they actually release the agent. I know we are supporting Debian 12 in Vox Pupuli modules.