Control: severity -1 important
Control: tag -1 + confirmed pending
Hi Diederik,
Diederik de Haas wrote:
> I have recently created a Jessie VM and noticed that there was (quite) a
> difference between the kernel I expected and the one that I had.
> I just learned that those are uploaded to security.debian.org, so I
> enabled the security repo lines in /etc/apt/sources.list. But when doing
> 'aptitude update', it reported that it couldn't find the repo.
> Turns out that it uses 'jessie-security', what the section has become
> since Bullseye, but it should be 'jessie/updates'. After changing that,
> it could find the repo and I had quite some updates.
>
> 'Strangely' enough, in my recently created Stretch VM, it did have
> 'stretch/updates' in /e/a/sources.list, which is correct.
Yep, indeed. This is a bug introduced in commit
eab2940bf6d56538159808acb174bbda6271d343 when I rewrote the
differentiation between pre-bullseye and bullseye + later
because my first solution wasn't backward compatible:
There's a missing "|" in a regexp in hooks/debian/20-setup-apt. Small
mistake, big effect.
It affects Wheezy as well btw. as the regexp uselessly matches
"wheezyjessie" instead of "wheezy|jessie".
Fix committed locally. Will prepare a upstream minor bugfix release as
well as a Debian upload to unstable at least.
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
