On Sat, Feb 23, 2013 at 17:35:40 +0100, Sébastien Villemot wrote:

> Le samedi 23 février 2013 à 17:17 +0100, Julien Cristau a écrit :
> > On Sun, Feb 17, 2013 at 13:42:45 +0100, Andreas Beckmann wrote:
> > 
> > > I have now observed this behavior also while upgrading the following
> > > packages from squeeze -> sid (and verified that these upgrades fail on
> > > squeeze -> wheezy(+new numpy) in the same way).
> > > 
> > If this is due to the breaks added in the new numpy, then I'd say let's
> > revert those.  Aborting the upgrade like that seems much worse than
> > possible incompatibilities for partial upgrades.
> 
> Yes the problem is introduced by the new Breaks. However, as noted in my
> previous message to this bug, this is the consequence of a real bug
> somewhere else.
> 
Whether the somewhere else is python-support or python or dpkg, it's
probably not something we'll change before release...

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature

Reply via email to