libc6-i386 dependency not met in gutsy x86_64 after upgrade of libc6

[mamruoc]

Binary package hint: libc6

After upgrade of libc to version 2.6.1-1ubuntu10, libc6-i386 will not install anymore. Probably just an easy minor version requirement bump nedded:

root@sushi:/root# apt-get install ia32-libs
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  ia32-libs: Depends: lib32gcc1 but it is not going to be installed
             Depends: libc6-i386 (>= 2.3.6-2) but it is not going to be installed
             Depends: lib32z1 but it is not going to be installed
             Depends: lib32stdc++6 but it is not going to be installed
             Depends: lib32asound2 but it is not going to be installed
             Depends: lib32ncurses5 but it is not going to be installed
E: Broken packages
root@sushi:/root# apt-get install libc6-i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  libc6-i386: Depends: libc6 (= 2.6.1-1ubuntu9) but 2.6.1-1ubuntu10 is to be installed
E: Broken packages
root@sushi:/root#

[mamruoc (toan)]

Forgot uname -a:

Linux sushi 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 GNU/Linux

[Matthias Klose (doko)]

ia32-libs did move to the universe section of the archive; is this enabled in /etc/apt/sources.list?

[Colin Watson (cjwatson)]

I see no problem here, and I think your problem must be something else. The archive has:

libc6-i386 | 2.6.1-1ubuntu10 | gutsy-updates | amd64

[AleksanderAdamowski (aadamowski)]

I think there's something fishy going on:

* I'm using Gutsy
* lib32gcc1 is available for Gutsy http://packages.ubuntu.com/gutsy/lib32gcc1
* I have all the official repositories I can think of in apt's sources.list:
deb http://pl.archive.ubuntu.com/ubuntu/ gutsy main restricted
deb http://pl.archive.ubuntu.com/ubuntu/ gutsy-updates main restricted
deb http://pl.archive.ubuntu.com/ubuntu/ gutsy universe
deb http://pl.archive.ubuntu.com/ubuntu/ gutsy multiverse
deb http://pl.archive.ubuntu.com/ubuntu/ gutsy-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu gutsy-security main restricted
deb http://security.ubuntu.com/ubuntu gutsy-security universe
deb http://security.ubuntu.com/ubuntu gutsy-security multiverse
* however, I cannot install lib32gcc1 using apt:
# apt-get install lib32gcc1
...
Package lib32gcc1 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package lib32gcc1 has no installation candidate

[AleksanderAdamowski (aadamowski)]

I forgot to mention, I'm on i386. x86_64 isn't involved.

[AleksanderAdamowski (aadamowski)]

Oops, I've realized my mistake, lib32gcc1 only makes sense on amd64... I got mislead by a third party package with a stupid dependency. Sorry for spam.

[Michael Lustfield (michaellustfield)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

If you can confirm that bug bug has been resolved in Intrepid, please let us know if we can set the status to "Fix Released"

Thanks again!