Bug#1035522: bullseye-pu: package debian-security-support/1:11+2023.05.04
Control: tags -1 + confirmed
On Fri, 2023-05-12 at 08:50 +0000, Holger Levsen wrote:
> hi,
>
> friendly ping on this.
>
It's only been a week, and one of the SRMs has been on a publicised
(fvo publicised being relevant to DDs) week away. It's a little soon to
be chasing. :-(
> On Thu, May 04, 2023 at 07:50:37PM +0200, Holger Levsen wrote:
> > this is a pre-approval request, I have not uploaded this yet
> > (except to
> > unstable).
>
> the package has migrated to bookworm now.
>
> > [ Reason ]
> >
> > unfortunatly debian-security-support in both bullseye and bookworm
> > are affected by - #1034077
> > "debian-security-support: Lots of noise about DEBIAN_VERSION 12
> > being
> > invalid when upgrading bullseye→bookworm"
> [...]
>
> > [ Other info ]
> > As there will be no more bullseye point releases before the
> > bookworm
> > release, this probably needs to go in via bullseye-updates. Is
> > d/changelog
> > correct for this like it is?
>
> I'm not quoting the full bug report but the above is reason why this
> should
> go into *bullseye* before the bookworm release...
I'm a bit confused here. Your own text above indicates that you're
aware that there won't be any more point releases before the release,
and that therefore the package *cannot* be in bullseye before the
release. Point releases are the mechanism by which packages get updated
in stable.
In any case, please go ahead.
Regards,
Adam
Reply to: