On Fri, 30 Mar 2012, Roger Leigh wrote: > We currently treat any key which isn't settable as "unknown". > Maybe we should report it as "invalid" instead? Or we could > have a list of known and deprecated keys, and tailor the > warning appropriately. In this specific case, without the > union-type setting, the chroot most likely isn't a source > chroot, and hence there is not means to set that key on that > particular chroot instance (it entirely lacks the logic, the > chroot_facet_source_clonable facet), so is completely > unaware that it's valid in other contexts.
At the very least the error message should hint that it can be either invalid or not appropriate for this specific "facet". But the more specific you can be, the better. Cheers, -- Raphaël Hertzog ◈ Debian Developer Pre-order a copy of the Debian Administrator's Handbook and help liberate it: http://debian-handbook.info/liberation/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
