Bug#844315: tzdata version breaks dist-upgrade leaving version from oldstable security installed

2016-11-14 Thread Marcel Meckel

I like my systems to have packages from stable and stable security only.
So when I do a dist-upgrade and remove old/outdated/not needed packages
I expect to have all remaining packages to be from stable.

tzdata - although with a newer version - being stuck on oldstable,
is not expected.

It doesn't break anything in terms of "something doesn't work" but more
in terms of "it simply shouldn't be this way".

So, I'm with you - "critical" might not be the appropriate severity 
here.


Marcel



Bug#844315: tzdata version breaks dist-upgrade leaving version from oldstable security installed

2016-11-14 Thread Marcel Meckel

Package: tzdata
Version: 2016i-0+deb7u1
Severity: critical

Upgrading a fully updated wheezy system (incl. security repo) to
jessie (incl. security repo) results in tzdata not being updated
because the version in wheezy-security is newer than in jessie.

Package tzdata on amd64

  wheezy:  2016d-0+deb7u1
  wheezy-security: 2016i-0+deb7u1

  jessie:  2016f-0+deb8u1
  jessie-updates:  2016i-0+deb8u1
  jessie-proposed-updates: 2016i-0+deb8u1

Using only the main repo + security repo results in tzdata not being
updates since wheezy-securities '2016i-0+deb7u1' is higher than
jessies '2016f-0+deb8u1'.

Comment from IRC:

 That's indeed unfortunate. You can work around the
problem by adding jessie-updates, though.

 I think it's because wheezy didn't have a wheezy-updates,
so all updates must go through wheezy-security, whereas in jessie all
non-critical updates go through jessie-updates, and get wrapped up in
point releases every few months.

 It's still a bug though, I'd report it on the tzdata
package. Might warrant a RC severity, since it breaks automatic upgrades
and is easy to fix.