Hi Petter, On Fri, Feb 23, 2018 at 10:56:08AM +0100, Petter Reinholdtsen wrote: > > IMO this is a regression; it worked some time ago, right? > > As far as I know, this has never behaved differently. I am not aware of > blends-dev every looking at main/contrib status, only if the package > exists.
Petter, if I might refresh your mind ;-): blends-dev has pulled Packages.gz as per /etc/blends/sources.list.* (by default /etc/blends/sources.list.testing since this will be our target release). If you provide a different sources.list file with -s option or if you change your local configuration by adding other resources, than you can tweak this behaviour. Blends-dev has checked, whether a package exists there (by default testing/main). Everything that did not existed there (may it be in contrib/non-free/somewhere-else) was put to Suggests. This is how it worked and how it should work to create policy conform packages. > In my view, it is the responsibility of the people writing the tasks to > decide if a package in contrib should use recommends or suggest, not the > blends build system. No. Recommends need to reside in main (per policy). Kind regards Andreas. -- http://fam-tille.de