Latest upstart update unresolvable dependency

[Fraoch]

Is anyone else seeing this with the update today from upstart 0.6.6-3 to 0.6.6-4?

upstart:
  Breaks: libc6 (<2.12.1-0ubuntu10.2) but 2.12.1-0ubuntu10.1 is to be installed

Should I force this or is it a universal issue and should I wait for it to be resolved?

[jimmyjones]

Wondering the same.

You're not the only one.

[chesterman]

same here

[imbjr]

Well I avoided upgrading upstart, but then I saw this:

Installing new version of config file /etc/init/portmap.conf ...
portmap start/running, process 2900
There are RPC services which were registered with the portmapper
before the configuration was changed.
You need to manually restart them in order for the changes to take effect.
Current registered services:
------------------------------------------------
    100021    1   udp  50441  nlockmgr
    100021    3   udp  50441  nlockmgr
    100021    4   udp  50441  nlockmgr
    100021    1   tcp  41635  nlockmgr
    100021    3   tcp  41635  nlockmgr
    100021    4   tcp  41635  nlockmgr
    100024    1   udp  43803  status
    100024    1   tcp  49823  status
------------------------------------------------

I can't seem to find any information on how to restart those services, without resorting to a reboot.

[Bob63]

I've got it too. I wouldn't force it as yet; wait for some more knowledgeable input.

It's odd that it wants to regress libc6.

[Fraoch]

Thanks for the advice everyone.

I've got it too. I wouldn't force it as yet; wait for some more knowledgeable input.

It's odd that it wants to regress libc6.

Yes, I'll leave it for now.

libc6 is a very important package, doesn't all code written in C depend on it? I wouldn't want to mess with it.

Kind of looks like just a typo, that the older version of libc6 was specified. libc6 was upgraded fairly recently (Jan. 12), could it be possible that 2.12.1-0ubuntu10.1 was the most current version at the time the developer(s) worked on upstart?

I've seen things like this happen from time to time - they usually get resolved in a day or two.

[w0jrl]

I'm glad I'm not the only one! I honestly thought I broke something.

Thanks,
Jeremy

[daniel.kullmann]

The libc6 version 2.12.1-0ubuntu10.2 is available from the maverick-proposed repository. This repository is by default deactivated.

$ apt-cache policy libc6
libc6:
  Installed: 2.12.1-0ubuntu10.2
  Candidate: 2.12.1-0ubuntu10.2
  Version table:
 *** 2.12.1-0ubuntu10.2 0
        500 http://dk.archive.ubuntu.com/ubuntu/ maverick-proposed/main i386 Packages
        100 /var/lib/dpkg/status
     2.12.1-0ubuntu10.1 0
        500 http://dk.archive.ubuntu.com/ubuntu/ maverick-updates/main i386 Packages
        500 http://security.ubuntu.com/ubuntu/ maverick-security/main i386 Packages
     2.12.1-0ubuntu6 0
        500 http://dk.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages

Update:
I just updated to the latest version, and restarted the computer. Everything seems to work fine...

I guess the dependence on the libc6 version was an oversight by the person who created the upstart package.

[bichopro]

same problem here

ubuntu 64 with unity

[hanzgroove]

+1 on this issue. I'm waiting to see if the package is updated to resolve the problem.