[Aptitude-devel] Bug#663134: aptitude: safe-upgrade fails on libgcc1 version skew

[Manuel A. Fernandez Montecelo]

Control: tags -1 + moreinfo


Hi,

2012-03-10 10:00 Sven Joachim:
>> 2. Insert some logic to not mark packages violating the multiarch
>> lockstep requirement, thereby avoiding invoking the resolver and the
>> resulting status messages.
>>
>> Option 2 is easy, but personally I'd like to avoid it because it is an
>> extra layer on top of the native APT implementation of the multiarch
>> spec (i.e. implicit Breaks: self on these packages).  Also, aptitude's
>> behaviour would internally deviate from apt-get's even though the
>> results would appear similar.
>
>There is also the theoretical possibility that the requirement to
>upgrade "M-A:same" packages in lockstep might be lifted some day
>(Guillem proposed this, but was apparently convinced/persuaded not to do
>this).

There are people talking about this from time to time, because it's
annoying at several levels, specially when some arches are at different
binNMU levels than others.

People have pinged the bug lately, I forgot which one it is.


In general, I think that this is a transient problem only affecting
unstable (as far as I can tell) and in the vast majority of cases only
for a few hours until the version becomes available, and that it might
be solved by another means.

So this has been happening for a few years already and maybe it's not
fixed soon, but the lazy person in me still thinks that the best option
is "wait and see" :-)


Cheers.
-- 
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>