Hi, On Tue, 13 May 2014, Gerfried Fuchs wrote: > This also affects a cowbuilder chroot and ends up in its build logs. > Either it is needed, then it should be a Depends, or not, then it > shouldn't blabber about it and end up in build logs. > > Yes, installing something in a pbuilder/cowbuilder chroot that isn't a > Build-Depends (or Depends of the base system) is a problem in the sense > that it somehow defeats the whole purpose of using a chroot for that in > the first place. :)
FWIW, I agree that we should do something to get rid of that warning. It hurts more than it helps. The build log pollution is very annoying. And we have seen that installing the dependency in the build chroots is also not desirable because it will create problems during a perl transition. Is there a way to detect that NFS is in use ? If yes, then we could make the warning conditional on the usage of NFS. Otherwise we should just silence it and document the limitation when the module is not installed. Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
