[fixed] upstart 0.6.6-4 - cannot install new update

[han9k]

Binary package hint: upstart

After updating ubuntu 10.10 32bit today(2011-02-02 GMT +9 hrs),
I found out that "upstart" (ver 0.6.6-4) is still on the recommended update but, "Install" button is grayed out.

I went to "synaptic package manager" to check the further problem and found out that the new version of "upstart" is trying to install "libc6(2.12.1-ubuntu10.1)" when "libc6 (2.12.1-ubuntu10.2)" is already installed.
Synaptic package manager will not allow user to install this new update, "upstart 0.6.6-4", when "libc6 (2.12.1-ubuntu10.2)" is already installed with "upstart 0.6.6-3".

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: upstart 0.6.6-3
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
Uname: Linux 2.6.35-25-generic i686
Architecture: i386
Date: Wed Feb 2 10:09:03 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
 LANG=ko_KR.utf8
 SHELL=/bin/bash
SourcePackage: upstart

[Tero Tilus (tero-tilus)]

The upstart package says it breaks all libc6 versions that are available for Maveric. Prolly for a reason. :-) Good question is why was it released before it actually could be installed. It is bound to confuse people.

Package: upstart
...
Version: 0.6.6-3
...
Breaks: libc6 (<< 2.12.1-0ubuntu10.2)

[Tero Tilus (tero-tilus)]

Could the "Breaks:" be due to bug #672177 ?

[yamo (stephane-gregoire)]

Hi,
I have this same bug :

apt-get install upstart
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Certains paquets ne peuvent être installés. Ceci peut signifier
que vous avez demandé l'impossible, ou bien, si vous utilisez
la distribution unstable, que certains paquets n'ont pas encore
été créés ou ne sont pas sortis d'Incoming.
L'information suivante devrait vous aider à résoudre la situation :

Les paquets suivants contiennent des dépendances non satisfaites :
 libasound2 : Dépend: libpython2.6 (>= 2.6) mais ne sera pas installé
 libc6 : Dépend: libgcc1 mais ne sera pas installé
         Dépend: tzdata mais ne sera pas installé
         Dépend: findutils (>= 4.4.0-2ubuntu2) mais ne sera pas installé
 libpulse0 : Dépend: libdbus-1-3 (>= 1.1.1) mais ne sera pas installé
             Dépend: libice6 (>= 1:1.0.0) mais ne sera pas installé
             Dépend: libsm6 mais ne sera pas installé
             Dépend: libsndfile1 (>= 1.0.20) mais ne sera pas installé
             Dépend: libwrap0 (>= 7.6-4~) mais ne sera pas installé
             Dépend: libx11-xcb1 mais ne sera pas installé
             Dépend: libxcb-atom1 (>= 0.3.6) mais ne sera pas installé
             Dépend: libxcb1 mais ne sera pas installé
             Dépend: libxtst6 mais ne sera pas installé
 libschroedinger-1.0-0 : Dépend: libgcc1 (>= 1:4.1.1) mais ne sera pas installé
 libtheora0 : Dépend: libogg0 (>= 1.1.0) mais ne sera pas installé
 libvorbis0a : Dépend: libogg0 (>= 1.1.0) mais ne sera pas installé
 libvorbisenc2 : Dépend: libogg0 (>= 1.0rc3) mais ne sera pas installé
 libx11-6 : Dépend: libxcb1 (>= 1.2) mais ne sera pas installé
 upstart : Dépend: libdbus-1-3 (>= 1.2.16) mais ne sera pas installé
           Dépend: libnih-dbus1 (>= 1.0.0) mais ne sera pas installé
           Dépend: libnih1 (>= 1.0.0) mais ne sera pas installé
           Dépend: libudev0 (>= 151) mais ne sera pas installé
           Dépend: sysvinit-utils mais ne sera pas installé
           Dépend: sysv-rc mais ne sera pas installé
           Dépend: initscripts mais ne sera pas installé
           Dépend: mountall mais ne sera pas installé
           Dépend: ifupdown (>= 0.6.8ubuntu29)
           Casse: libc6 (< 2.12.1-0ubuntu10.2) mais 2.12.1-0ubuntu10.1 devra être installé
E: Paquets défectueux

[al.cadd9 (al.cadd9)]

libc-bin 2.12.1-0ubuntu10.2 was moved from proposed to updates https://launchpad.net/ubuntu/maverick/i386/libc-bin/ .
It's only a question of time, now, before it hits all the mirrors.

[al.cadd9 (al.cadd9)]

obviously I meant https://launchpad.net/ubuntu/maverick/amd64/libc6/ :)

[James Hunt (jamesodhunt)]

Thank you for taking the time to report this bug and and helping to make Ubuntu better.

The problem appears to have been caused by a delay in the required libc6 update moving from maverick-proposed to maverick-updates. This issue has been resolved, so please retry the upgrade to ensure it works as expected for you.

[Daniel Dietrich (shaddowy2)]

Thank you, it works for me now. I mark the bug as solved.

[han9k (hjyoo)]

Thank you, updating "upstart" to version 0.6.6-4 works now.

[Ray Nichols (ray-rdnichols)]

I don't see libc-bin 2.12.1-0ubuntu10.2 yet on my amd 64 system and can't upgrade upstart.

nicholsr@ubuntu01:~$ uname -a
Linux ubuntu01 2.6.35-25-generic #44-Ubuntu SMP Fri Jan 21 17:40:44 UTC 2011 x86_64 GNU/Linux

nicholsr@ubuntu01:~$ dpkg -l upstart libc-bin
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-===========================================-===========================================-======================================================================================================
ii libc-bin 2.12.1-0ubuntu10.1 Embedded GNU C Library: Binaries
ii upstart 0.6.6-3 event-based init daemon

nicholsr@ubuntu01:~$ sudo apt-get update
< ... snip ...>
nicholsr@ubuntu01:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
  upstart
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

[Tero Tilus (tero-tilus)]

Ray,

Could your mirror be lagging behind?

[Ray Nichols (ray-rdnichols)]

Is anyone, who is using x86_64 and downloading maverick-security/main from a UK server, able to get this update?
In Synaptic, Repositories, I tried changing my UK sever but it hasn't made a difference.

[Geronimo Orozco (gorozco)]

I am running x86_64 not able to get this update the bug is still there for x86_64, could someone push the update to x86_64 maverik please

[Ray Nichols (ray-rdnichols)]

It remains a problem. Is there anything I should do?

nicholsr@ubuntu01:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
  upstart
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

nicholsr@ubuntu01:~$ sudo apt-get install upstart
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.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
 upstart : Breaks: libc6 (< 2.12.1-0ubuntu10.2) but 2.12.1-0ubuntu10.1 is to be installed
E: Broken packages

[Jochen Fahrner (jofa)]

I still get the message

"upstart:
  Stört: libc6 (<2.12.1-0ubuntu10.2), aber es wird 2.12.1-0ubuntu10.1 installiert"

libc6-2.12.1-0ubuntu10.2 depends on libc-bin-0ubuntu10.2, which depends on many other packes. I think there is something broken in apt dependencies.

[muhkuh (markus-henschel)]

Same here on x86_64:
upstart:
  Stört: libc6 (<2.12.1-0ubuntu10.2), aber es wird 2.12.1-0ubuntu10.1 installiert

[Martin Kalén (martin-kalen)]

For the ones still having problems, check if you have any apt pinning that prevents the libc6 update. For example, you can use "apt-cache policy libc6" to check which version you have installed (marked with "***") and what priority the maverick-updates/main repository is given.

Personally, I had the updates and security repositories set to the same priority through /etc/apt/preferences and ended up getting libc6 stuck at the 2.12.1-0ubuntu10.1 level from the security repository. Commenting out apt pinning preferences for maverick-security and maverick-updates in /etc/apt/preferences (i.e. going back to default priority of 500) and doing aptitude update + aptitude dist-upgrade fixed this problem.

Before:
apt-cache policy libc6
     2.12.1-0ubuntu10.2 0
        900 http://ftp.hosteurope.de/mirror/archive.ubuntu.com/ maverick-updates/main amd64 Packages
 *** 2.12.1-0ubuntu10.1 0
        990 http://ftp.hosteurope.de/mirror/archive.ubuntu.com/ maverick-security/main amd64 Packages
        100 /var/lib/dpkg/status
     2.12.1-0ubuntu6 0
        500 http://ftp.hosteurope.de/mirror/archive.ubuntu.com/ maverick/main amd64 Packages

After:
apt-cache policy libc6
 *** 2.12.1-0ubuntu10.2 0
        500 http://ftp.hosteurope.de/mirror/archive.ubuntu.com/ maverick-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     2.12.1-0ubuntu10.1 0
        500 http://ftp.hosteurope.de/mirror/archive.ubuntu.com/ maverick-security/main amd64 Packages
     2.12.1-0ubuntu6 0
        500 http://ftp.hosteurope.de/mirror/archive.ubuntu.com/ maverick/main amd64 Packages

[Ray Nichols (ray-rdnichols)]

Hi Martin,

I had originally enabled proposed as per
https://wiki.ubuntu.com/Testing/EnableProposed
for Bug #525154.

I hadn't realised this would stop the updates.

I stoped using proposed by
- taking it out of my repositories list
- moving my preferences file out of the way:
nicholsr@ubuntu01:/etc/apt$ sudo mv preferences preferences_do_not_use

and updated fine after that.

Thanks a lot for the information.

Ray.

[Jochen Fahrner (jofa)]

The same thing happened to me. I had enabled proposed for Bug #672873 and that introduced a conflict for this update package.