upstart fails to upgrade from hardy to lucid (--configure)

[Rolf Leggewie]

Binary package hint: upstart

I updated my vserver the other day from hardy to lucid, but the upgrade process came to a premature halt. See the attached aptitude console log.

[Rolf Leggewie (r0lf)]

looks a lot like Bug #454783 which is supposedly fixed

[Clint Byrum (clint-fewbar)]

Rolf, I would agree that this looks very similar. Marking as duplicate and nominating for Hardy.

[Rolf Leggewie (r0lf)]

Unduping for further analysis.

Clint, the other bug report is against update-manager, I used plain aptitude. Furthermore the other ticket is supposedly fixed since karmic, no need to backport a fix to lucid.

[Rolf Leggewie (r0lf)]

You nominated for hardy. That of course may make sense, depending on the situation. Not sure if any changes in the update-manager package would have prevented this situation, though.

[Rolf Leggewie (r0lf)]

I think lucid upstart does not work in a vserver or chroot, period. That's my current understanding. That would be a shame.

http://blog.opperschaap.net/2009/11/16/chroot-with-upstart/

[Rolf Leggewie (r0lf)]

some more helpful links I found

http://wiki.raceme.org/dokuwiki/tof:computer:vserver:upstart_ubuntu_lucid
http://linux-vserver.org/Upstart_issues