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

Bug#844315: marked as done (updates appear in wheezy-security before jessie)

Your message dated Mon, 27 Jul 2020 17:53:33 +0200
with message-id <7f0c15310ef08be0e48fd99526820a04d8adab58.camel@43-1.org>
and subject line Re: Bug#844315: tzdata version breaks dist-upgrade leaving version from oldstable security installed
has caused the Debian Bug report #844315,
regarding updates appear in wheezy-security before jessie
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
844315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844315
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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:

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

<petn-randall> 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.

<petn-randall> 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.

--- End Message ---
--- Begin Message --- 
On Mon, 14 Nov 2016 22:42:09 +0100 Aurelien Jarno wrote:
> On 2016-11-14 12:54, Marcel Meckel wrote:
> > 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'.
> 
> Nothing can be done at the tzdata level, except maybe stopping providing
> updates to wheezy users. I am therefore reassigning the bug to the
> "general" package. Also there are probably more than tzdata affected.
> 
> Note however that you are supposed to use jessie-updates on a jessie
> system. This is actually enabled by default in debian-installer.

I don't think there is really anything to do here as I don't see a
problem with having to use *-updates.  Given nobody else said anything
in the last 3 1/2 years, I'll close the report.

Ansgar

--- End Message ---
Reply to: