On Mon, 2011-02-21 at 14:10 +0000, Stephan Adig wrote: > @All: > > Did anyone tried to install now nfs-common (in lucid with the latest sru > bugfix) in a chroot environment? > > If so, did nobody see nfs-common failing in nfs-common.postinst? > > Normally, in a chroot, starting services is disabled and/or not allowed (or > in some cases the startup mechanism is somehow diverted to /bin/true or > /bin/false whatever). > But now, nfs-common.postinst does an invoke.rc statd and this failes in a > chroot environment which means, that the package in question is not > configured properly. > > The upstart dependency (started portmap ON_BOOT= or (local-filesystems > and started portmap ON_BOOT=y)) doesn't apply inside a chroot. > > One thing that needs to be done is, to not start the services during > installation (which means removing all blind magic of dh_installinit) or > whatever it takes to come back with the old behaviour. >
Hi Stephan, thanks for the feedback. First off, services are always started/stopped with invoke-rc.d on upgrade in Debian packages and, thusly, have always been started and stopped in Ubuntu. This is a known issue in upstart which is under active development. Basically upstart doesn't know anything about the chroot environment, so it doesn't read the /etc/init from the chroot. Take a look at bug #430224 for more information. A simple workaround to get the postinst to succeed is to edit the postinst in /var/lib/dpkg/info/nfs-common.postinst and remove the calls to invoke-rc.d -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/525154 Title: mountall for /var races with rpc.statd -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
