On Mon, Feb 21, 2011 at 02:10:11PM -0000, Stephan Adig wrote: > 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. invoke-rc.d should not fail in a chroot environment. How have you configured your chroot? *Any* of the standard methods for disabling services in a chroot should have the intended effect (i.e., diverting /sbin/initctl to /bin/true, or configuring a policy-rc.d to disallow service starting). If you have /sbin/initctl diverted to /bin/*false*, that is a misconfiguration in your environment. > 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. No, that is not a thing that needs to be done. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs