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

[Daniel Hartwig]

On 10 March 2012 18:00, Sven Joachim <svenjoac at gmx.de> wrote:
> On 2012-03-10 04:17 +0100, Daniel Hartwig wrote:
>
>>
>> However, the output of the programs does differ.  Aptitude
>> safe-upgrade reports that it can not resolve the dependency problems
>> (correct), and that the user should try using the full resolver (which
>> would remove at least one of the packages; this is a useful option for
>> a user)
>
> Note that this affects unrelated upgradable packages, since "aptitude
> safe-upgrade" does not find a solution, while the full resolver will
> upgrade them.
>

Is that so in some situation?  Your original report only had the two
out-of-sync gcc packages available, which, of course, can not be
upgraded.

In a test situation 'safe-upgrade' works the same as 'apt-get upgrade'
when some packages are upgradable:

# apt-cache policy lockstep-bad lockstep-bad:armel
lockstep-bad:
  Installed: 1.0
  Candidate: 1.0
  Version table:
 *** 1.0 0
        500 file:/home/daniel/repo/multiarch-lockstep/rep-lockstep/
binary-powerpc/ Packages
        100 /home/daniel/repo/multiarch-lockstep//var/lib/dpkg/status
lockstep-bad:armel:
  Installed: 1.0
  Candidate: 2.0
  Version table:
     2.0 0
        500 file:/home/daniel/repo/multiarch-lockstep/rep-lockstep/
binary-armel/ Packages
 *** 1.0 0
        100 /home/daniel/repo/multiarch-lockstep//var/lib/dpkg/status
# apt-cache policy lockstep-good lockstep-good:armel
lockstep-good:
  Installed: 1.0
  Candidate: 2.0
  Version table:
     2.0 0
        500 file:/home/daniel/repo/multiarch-lockstep/rep-lockstep/
binary-powerpc/ Packages
 *** 1.0 0
        100 /home/daniel/repo/multiarch-lockstep//var/lib/dpkg/status
lockstep-good:armel:
  Installed: 1.0
  Candidate: 2.0
  Version table:
     2.0 0
        500 file:/home/daniel/repo/multiarch-lockstep/rep-lockstep/
binary-armel/ Packages
 *** 1.0 0
        100 /home/daniel/repo/multiarch-lockstep//var/lib/dpkg/status
# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
  lockstep-bad:armel
The following packages will be upgraded:
  lockstep-good lockstep-good:armel
2 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
E: The package index files are corrupted. No Filename: field for
package lockstep-good.
# aptitude upgrade
Resolving dependencies...
The following packages will be upgraded:
  lockstep-good lockstep-good:armel
2 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Do you want to continue? [Y/n/?] n
Abort.


But this test only has two packages, available each on two archs.  If
you have a real world scenario where this doesn't work please provide
the details.


Regards