** Description changed: + SRU Justification + + 1. impact of the bug is medium for stable releases, as not being able to + preseed the home tunable is a longstanding bug that was intended to be + fixed in Lucid. + + 2. This was first fixed in Maverick during its development cycle. + + 3. Patch is very small-- it simply removes a chunk of faulty logic from + the preinst. + + 4. TEST CASE: + $ cat /etc/apparmor.d/tunables/home.d/ubuntu | grep '^@' # should return nothing + $ printf 'apparmor\tapparmor/homedirs\tstring\t/myhome/\n' | sudo debconf-set-selections + $ sudo dpkg-reconfigure -p high apparmor + $ cat /etc/apparmor.d/tunables/home.d/ubuntu | grep '^@' + + At this point '/myhome/' should be in + /etc/apparmor.d/tunables/home.d/ubuntu, but it is not. + + 5. The regression potential of the patch is low, as it removes code from + the apparmor preinst to fix a feature introduced in Lucid that never + worked. + + Binary package hint: apparmor This concerns apparmor 2.5-0ubuntu3 in Ubuntu Lucid beta1. I am preseeding the debconf database of an Ubuntu install with a custom value for the apparmor/homedirs selection. When I then go to configure the package, however, the preseeded value is not given as the default answer, as expected---instead, the answer is blank. # printf 'apparmor\tapparmor/homedirs\tstring\t/myhome/\n' | debconf-set-selections # dpkg-reconfigure apparmor What appears to be happening is that the debconf question takes the default value from /etc/apparmor.d/tunables/home.d/ubuntu (the file that is modified as a result of the question) instead of the debconf database. This behavior is at least questionable, and when a blank value overrides a preseeded debconf value, clearly incorrect.
-- Does not use preseeded debconf value for apparmor/homedirs https://bugs.launchpad.net/bugs/561694 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
