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

Bug#503303: marked as done (etch -> lenny minimal chrrot upgrade fails due to Conflicts/Pre-Depends loop)

Your message dated Sun, 10 Oct 2010 13:08:20 +0200
with message-id <20101010110820.GA16553@radis.liafa.jussieu.fr>
and subject line Re: Bug#503303: Bug#503712: etch->lenny upgrade left the system in broken state
has caused the Debian Bug report #503303,
regarding etch -> lenny minimal chrrot upgrade fails due to Conflicts/Pre-Depends loop
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.)


-- 
503303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503303
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: upgrade-reports
Severity: serious

Upgrading a clean minimal etch chroot to lenny fails with

  E: This installation run will require temporarily removing the essential package tzdata due to a Conflicts/Pre-Depends loop. This is often bad, but if you really want to do it, activate the APT::Force-LoopBreak option.
  E: Internal Error, Could not early remove tzdata

This is reproducible with piuparts.

This is on i386.

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here.

--- End Message ---
--- Begin Message --- 
On Mon, Oct 27, 2008 at 22:42:24 +0200, Holger Levsen wrote:

> Hi,
> 
> I'm pretty sure this bug is a duplicate of 503303, which look like duplicates 
> of #464559 (merged with #466027, #466695, #467059, #475530).
> 
> "Unfortunatly" those bugs are closed in sid/lenny, but thats exactly the 
> problem here (as we cannot upgrade apt in an etch pointrelease as upgrades 
> need to work whithout applying all pointreleases), which then leads to the 
> solution: apt has to be upgraded to lenny before the rest and this needs to 
> be documented in the release-notes.
> 
> So, forcemerge and reassign?!
> 
Etch->lenny upgrade bug, probably not going to be fixed now if it hasn't
been before, so closing.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: