tags 675189 +pending thanks On Wed, May 30, 2012 at 08:46:43PM +0300, Edward J. Shornock wrote: > I had the same problem. The key word is 'had'. > > The output above shows 'profile=default'. I did not, however, have that > set in my configs. After setting that key/variable, schroot works as > expected, mounting /proc, /sys, etc..
Thanks for that, I think I've found the problem. We were initialising profile to "default" in the constructor, but the function which sets the profile (chroot::set_profile) actually sets a number of other properties (the ones which were missing in Mike's --info output). We just need to add a call to set_profile in the constructor, and we should be OK. I missed this due to either having script-config (which indirectly sets profile for backward compatibility) or profile in by chroot configurations. And the testsuite explicitly sets it. We need to add a test to the testsuite to make sure that the defaults in the absence of settings are sane. Just testing the one line fix now, so you should have a fix for it in unstable in a few hours unless I run into any complications. Thanks, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
