> This violates the policy in the generated blends tasks packages;
> therefore the severity.
> 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
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. I would thus classify this as a wishlist issue,
and recommend against changing the current default, as changing this
would make it impossible to use blends-dev to create a task where the
developer want to recommend a package in contrib or non-free. In short,
I do not agree that this 'violates the policy' to do what the task
writer intends. It might be useful to emit a warning if the build
system detect a recommend from main to contrib or non-free, but it
should not prohibit task writers from creating such tasks.