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

Bug#670954: [apt] MultiArch: apt-get -f install doesn't see correct dependency of package



Török Edwin <edwin+ml-debian@etorok.net> writes:

> Package: apt
> Version: 0.9.2
> Severity: normal
>
> --- Please enter the report below this line. ---
>
> 'apt-get -f install' won't install libgcc1-dbg 4.7.0-6, although its available.
> For some reason it thinks that it depends on gcc-4.7-base=4.7.0-5, which results in a conflict (gcc-4.7-base is 4.7.0-6 already).
>
> I checked the control file in the .deb, it says gcc-4.7-base=4.7.0-6, so I don't know why its looking for -5.
> Maybe it wants to run the postrm from 4.7.0-5 (but then shouldn't it ignore dependencies for that?).
> Anyway all gcc-related packages seem to have a 4.7.0-6 version now, so 'apt-get -f install' should
> be able to fix whatever the problem is, but it can't (see below).
>
> Version 4.7.0-6 is available for libgcc1-dbg:
> $ apt-cache policy libgcc1-dbg:amd64
> libgcc1-dbg:
>   Installed: 1:4.7.0-5
>   Candidate: 1:4.7.0-6
>   Version table:
>      1:4.7.0-6 0
>         500 http://iota.nren.ro/debian/ unstable/main amd64 Packages
>  *** 1:4.7.0-5 0
>         500 http://ftp.lug.ro/debian/ unstable/main amd64 Packages
>         100 /var/lib/dpkg/status
>      1:4.7.0-3 0
>         500 http://iota.nren.ro/debian/ testing/main amd64 Packages
>
> The :i386 is not installed:
> $ apt-cache policy libgcc1-dbg:i386
> libgcc1-dbg:i386:
>   Installed: (none)
>   Candidate: 1:4.7.0-5
>   Version table:
>      1:4.7.0-5 0
>         500 http://iota.nren.ro/debian/ unstable/main i386 Packages
>         500 http://ftp.lug.ro/debian/ unstable/main i386 Packages
>      1:4.7.0-3 0
>         500 http://iota.nren.ro/debian/ testing/main i386 Packages
>
>
>
> # apt-get install libgcc1-dbg:amd64=1:4.7.0-6
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages were automatically installed and are no longer required:
>   anjuta-common gtkpod-data id3v2 libanjuta-3-0 libgdl-3-2 libgdl-3-common
> Use 'apt-get autoremove' to remove them.
> The following packages will be upgraded:
>   libgcc1-dbg
> 1 upgraded, 0 newly installed, 0 to remove and 62 not upgraded.
> 2 not fully installed or removed.
> Need to get 0 B/101 kB of archives.
> After this operation, 0 B of additional disk space will be used.
> Traceback (most recent call last):
>   File "/usr/bin/apt-listchanges", line 237, in <module>
>     main()
>   File "/usr/bin/apt-listchanges", line 48, in main
>     debs = apt_listchanges.read_apt_pipeline(config)
>   File "/usr/share/apt-listchanges/apt_listchanges.py", line 83, in read_apt_pipeline
>     return map(lambda pkg: filenames[pkg], order)
>   File "/usr/share/apt-listchanges/apt_listchanges.py", line 83, in <lambda>
>     return map(lambda pkg: filenames[pkg], order)
> KeyError: 'libgcc1-dbg'

I think that is your actual problem. Something is broken with (your)
apt-listchanges. Apt-listchanges is a hook run before installing
packages and if any hook fails the installation is aborted. Try removing
that temporary from your apt.conf.

> dpkg: dependency problems prevent configuration of libgcc1-dbg:amd64:
>  libgcc1-dbg:amd64 depends on gcc-4.7-base (= 4.7.0-5); however:
>   Version of gcc-4.7-base:amd64 on system is 4.7.0-6.
>  libgcc1-dbg:amd64 depends on libgcc1 (= 1:4.7.0-5); however:
>   Version of libgcc1:amd64 on system is 1:4.7.0-6.
> dpkg: error processing libgcc1-dbg:amd64 (--configure):
>  dependency problems - leaving unconfigured
> dpkg: dependency problems prevent configuration of libstdc++6-4.7-dbg:amd64:
>  libstdc++6-4.7-dbg:amd64 depends on libgcc1-dbg; however:
>   Package libgcc1-dbg:amd64 is not configured yet.
> dpkg: error processing libstdc++6-4.7-dbg:amd64 (--configure):
>  dependency problems - leaving unconfigured
> Errors were encountered while processing:
>  libgcc1-dbg:amd64
>  libstdc++6-4.7-dbg:amd64
> E: Sub-process /usr/bin/dpkg returned an error code (1)

The installation was aborted but apt-get tries to be nice and configure
the packages that are unconfigured. Unfortunately the versions you do
already have unpacked on your system have the wrong versions so
configuring fails.

MfG
        Goswin



Reply to: