Re: Coordinated tzdata uploads between wheezy + jessie?

[Emilio Pozuelo Monfort <pochu@debian.org>]

On 12/04/17 15:49, Michael Prokop wrote:
> Hi,
> 
> (explicitly Cc-ing Emilio and Aurelien, who usually take care of tzdata uploads)
> 
> 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:
> 
> ,---- [ wheezy ]
> | % apt-cache policy tzdata tzdata-java
> | tzdata:
> |   Installed: 2017a-0+deb7u1
> |   Candidate: 2017b-0+deb7u1
> |   Version table:
> |      2017b-0+deb7u1 0
> |         500 http://security.debian.org/ wheezy/updates/main amd64 Packages
> | [...]
> `----
> 
> while in stable/jessie we're currently at tzdata=2017a-0+deb8u1:
> 
> ,---- [ jessie ]
> | % ssh coccia.debian.org dak ls -s jessie-updates tzdata
> | tzdata     | 2017a-0+deb8u1 | jessie-updates | source, all
> | % apt-cache policy tzdata tzdata-java
> | tzdata:
> |   Installed: 2017a-0+deb8u1
> |   Candidate: 2017a-0+deb8u1
> |   Version table:
> |  *** 2017a-0+deb8u1 0
> |         500 http://deb.debian.org/debian/ jessie-updates/main amd64 Packages
> |         100 /var/lib/dpkg/status
> | [...]
> `----
> 
> This is causing troubles when having automatic install/update
> procedures, resulting in situations like:
> 
> | tzdata-java : Depends: tzdata (= 2017a-0+deb8u1) but 2017b-0+deb7u1 is to be installed
> | tzdata-java : Depends: tzdata (= 2016i-0+deb8u1) but 2016j-0+deb7u1 is to be installed
> | tzdata-java : Depends: tzdata (= 2016h-0+deb8u1) but 2016i-0+deb7u1 is to be installed
> 
> 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.

Cheers,
Emilio