On Tuesday, 21.06.2022 at 17:29 +0200, gregor herrmann wrote:
> On Tue, 21 Jun 2022 16:21:07 +0100, Dave Ewart wrote:
>
> > This bug has been closed but there is still no update in the oldstable
> > repository as far as I can see.
> >
> > # dpkg -l|grep tzdata
> > ii tzdata 2021a-0+deb10u3
> > all time zone and daylight-saving time data
>
> That's not the repository but your local installation :)
>
> % rmadison tzdata
> tzdata | 2018e-0+deb8u1 | oldoldoldstable | source, all
> tzdata | 2020a-0+deb9u1 | oldoldstable | source, all
> tzdata | 2021a-0+deb10u3 | oldstable | source, all
> tzdata | 2021a-0+deb10u5 | buster-updates | source, all
> tzdata | 2021a-0+deb10u5 | oldstable-proposed-updates | source, all
> tzdata | 2021a-1+deb11u2 | stable | source, all
> tzdata | 2021a-1+deb11u4 | proposed-updates | source, all
> tzdata | 2021a-1+deb11u4 | stable-updates | source, all
> tzdata | 2022a-1 | testing | source, all
> tzdata | 2022a-1 | unstable | source, all
>
> So you have 2021a-0+deb10u3 from oldstable installed, and the fixed
> version 2021a-0+deb10u5 is in buster-updates, which you seem to miss
> in your sources.list.
>
> (I assume it will end up in oldstable proper in the next point
> release but for inbetween updates, {old}stable-updates is needed.) I know that's my version, I was simply trying to demonstrate (perhaps poorly) that the updated version hadn't reached my system. :-) I have never used the 'updates' or 'proposed-updates' for a production stable system because my understanding is that those repositories were not necessary, nor recommended, for a purely 'stable' installation. "Don't add extra repositories" etc. I see the point you're making: will have to make an exception here, I guess. Thanks, Dave. -- Dave Ewart, da...@sungate.co.uk
signature.asc
Description: PGP signature
