[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Coordinated tzdata uploads between wheezy + jessie?



* Emilio Pozuelo Monfort [Wed Apr 12, 2017 at 04:29:36PM +0200]:
> On 12/04/17 15:49, Michael Prokop wrote:

> > According to https://tracker.debian.org/pkg/tzdata we have:

> > [2017-04-07] Accepted tzdata 2017b-0+deb7u1 (source all) into oldstable (Emilio Pozuelo Monfort)
> > [2017-04-08] Accepted tzdata 2017b-0+deb8u1 (source all) into proposed-updates->stable-new, proposed-updates (Aurelien Jarno)

> > So in oldstable/wheezy-security we currently have tzdata=2017b-0+deb7u1 available:
[...]
> > while in stable/jessie we're currently at tzdata=2017a-0+deb8u1:
[...]
> > because the version in jessie is older than the one in wheezy.
> > (I'm aware that the new tzdata package is available in
> > jessie-proposed-updates, but enabling proposed-updates isn't always
> > a viable option.)

> > Is there any chance to synchronize this process/the versions between
> > wheezy and jessie in a better way, so users don't end up in
> > situations like mentioned above or is the only reasonable answer
> > "enable proposed-updates" here?

> > Also I might be mistaken, but IIRC this situation usually resolved
> > itself in <24 hours, so the package from proposed-updates was
> > included in jessie-updates before an upcoming point-release, though
> > current situation seems to be longer already? What's the
> > timeline/process for tzdata handling here?

> I assumed tzdata would go into jessie-updates quickly. Maybe I should have
> waited before doing the upload to wheezy.

Oh, if "that's all" what's needed and if that would work for you
I'd highly appreciate if you could do that in such a way. :)
Thanks! \o/

regards,
-mika-

Attachment: signature.asc
Description: Digital signature


Reply to: