Hi, Quoting Adam Borowski (2015-12-09 14:31:10) > As per apt's defaults, whenever a package that's a part of the sbuild chroot > gains a new Recommends:, that recommendation will be installed. This > default makes sense for regular apt uses outside of sbuild, but in sbuild's > context, it goes against the aim of a minimal chroot. It'll allow missing > build-dependencies to sneak through unnoticed, and makes fresh chroots > differ from updated ones. > > Thus, please make sbuild-update pass --no-install-recommends to apt.
This is entirely reasonable and should be done that way but can you give me a way how to reproduce this problem? I never experienced the problem myself and looking at the code in ResolverBase.pm it seems that sbuild already calls apt with a custom configuration file /var/lib/sbuild/apt.conf which contains APT::Install-Recommends false; So I don't understand how you got apt as used by sbuild installing Recommends. Thanks! cheers, josch
signature.asc
Description: signature
