ingo: that's the way the Ubuntu release process works, I'm sorry that this is a surprise to you
On Mon, Jan 24, 2011 at 1:00 PM, ingo <672...@bugs.launchpad.net> wrote: > @Zippo, > > it is really a sad story with LTS-Lucid. I really don't understand how > such a buggy release could pass QC (if there is any?). I.e. today there > came in an update of openSSH in Lucid, and still the old bug in the > upstart-script '/etc/init/ssh.conf' (stop on runlevel S) is not fixed. > Set it to (stop on runlevel [!2345]) - a hint from Clint. > > In fact Scott has left behind a half done upstart - not only in Lucid. > And Clint has taken the ungreatful challenge to clean up the biggest > issues. Shutdown process had been neglected to a great part. > Unfortunately Canonical is mainly focussing on Natty while Lucid just > gets the fixes for the worst. > > -- > You received this bug notification because you are a member of Upstart > Developers, which is subscribed to upstart . > https://bugs.launchpad.net/bugs/672177 > > Title: > libc6 upgrade causes umount to fail on shutdown because init cannot be > restarted > > Status in Upstart: > Invalid > Status in “eglibc” package in Ubuntu: > Fix Released > Status in “sysvinit” package in Ubuntu: > New > Status in “upstart” package in Ubuntu: > In Progress > Status in “eglibc” source package in Lucid: > Fix Committed > Status in “sysvinit” source package in Lucid: > New > Status in “upstart” source package in Lucid: > Fix Committed > Status in “eglibc” source package in Maverick: > Fix Committed > Status in “sysvinit” source package in Maverick: > New > Status in “upstart” source package in Maverick: > Fix Committed > Status in “eglibc” source package in Natty: > Fix Released > Status in “sysvinit” source package in Natty: > New > Status in “upstart” source package in Natty: > In Progress > > Bug description: > On a clean install of Ubuntu 10.04.1, after upgrading the offer libc6 > upgrade, on the next reboot the root fs can't be properly unmounted > (mount: / is busy). This causes fsck to run on boot and of course some > minor issues with the filesystem. This might not be a problem with > libc6 itself, but a side effect of upgrading in combination with some > other package (I suspect the init process, so I guess upstart). > > The fsck run, and the orphaned inodes it finds are holding me back > from installing this on a new server - especially since this already > happens on a clean install of 10.04.1! > > paul@ubuntu:~$ lsb_release -rd > Description: Ubuntu 10.04.1 LTS > Release: 10.04 > > ii libc6 2.11.1-0ubuntu7.2 > Embedded GNU C Library: Shared libraries > > ProblemType: Bug > DistroRelease: Ubuntu 10.04 > Package: libc6 2.11.1-0ubuntu7.2 > ProcVersionSignature: Ubuntu 2.6.32-24.39-server 2.6.32.15+drm33.5 > Uname: Linux 2.6.32-24-server x86_64 > Architecture: amd64 > Date: Sun Nov 7 16:17:07 2010 > InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 > (20100816.2) > ProcEnviron: > PATH=(custom, no user) > LANG=en_US.UTF-8 > SHELL=/bin/bash > SourcePackage: eglibc > > > -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
