Your message dated Sat, 9 Jun 2012 12:24:57 +0300
with message-id
<CAPZXPQeUvJ14Z4x7rraU0X3RKTaQu=hoytvkjaiwsi0qetn...@mail.gmail.com>
and subject line Re: Bug#672829: upgrade-system: please bump dependency on
deborphan to 1.7.28.7 after it has reached unstable
has caused the Debian Bug report #672829,
regarding upgrade-system: please bump dependency on deborphan to 1.7.28.7 after
it has reached unstable
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 [email protected]
immediately.)
--
672829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672829
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: upgrade-system
Severity: wishlist
Hi,
as discussed, please bump dependency on deborphan to 1.7.28.7 to prevent
endless loops in Ubuntu Q… and in weird cases in Debian.
The multiarch aware deborphan release 1.7.28.7 has been uploaded to the
delayed queue and will reach unstable on 2012-05-21.
Source: deborphan
Binary: deborphan
Version: 1.7.28.7
Distribution: unstable
Delayed-Until: 2012-05-21 22:46:33
Carsten
--- End Message ---
--- Begin Message ---
2012/5/14 Carsten Hey <[email protected]>:
> * Martin-Éric Racine [2012-05-14 09:24 +0300]:
>> 2012/5/14 Carsten Hey <[email protected]>:
>> > as discussed, please bump dependency on deborphan to 1.7.28.7 to prevent
>> > endless loops in Ubuntu Q… and in weird cases in Debian.
>> >
>> > The multiarch aware deborphan release 1.7.28.7 has been uploaded to the
>> > delayed queue and will reach unstable on 2012-05-21.
>> >
>> > Source: deborphan
>> > Binary: deborphan
>> > Version: 1.7.28.7
>> > Distribution: unstable
>> > Delayed-Until: 2012-05-21 22:46:33
>>
>> Actually, I was wondering if it wouldn't make more sense for the
>> multiarch-aware deborphan to depend upon multarch-aware dpkg or more
>> recent?
>
> Since it does not require a multiarch-aware dpkg, I don't think it
> should depend on a multiarch-aware dpkg. It's upgrade-systems that
> enters an endless loop if it is run with deborphan 1.7.28.6 or earlier
> on multiarch enabled systems (which of course requires a recent dpkg).
It only enters into a loop when the components below it are
mismatched. In this case, it was deborphan that wasn't able to produce
multiarch-aware output that APT could use. deborphan was broken, not
upgrade-system. I'm closing this bug.
--- End Message ---
