On Tue, 2017-01-17 at 10:59 +0000, Richard Brown wrote:
On 17 January 2017 at 10:23, Olaf Hering
wrote: On Tue, Jan 17, Marcus Meissner wrote:
On Tue, Jan 17, 2017 at 11:04:07AM +0100, Scott Bahling wrote:
I believe this has been worked out with the maintenance team in the meantime?
No.
There is no further action required. One has to override rpmlint-backports-data anyway to build packages which have have subpackages missing.
Olaf
Isn't the whole point of building against Backports to prepare submissions for Packagehub? Doesn't disabling mandatory checks for Backports undermine that purpose?
When you look at something like devel:languages:python, there a lot of packages that can be submitted to Backports and at the same time contains packages that fail the checks because of policies. Just because those other packages are not suitable for Backports doesn't mean they shouldn't be built in the devel project. One options is to override the checks, the other option is to have both SUSE:SLE and openSUSE:Backports build targets in parallel in such projects. Not sure which is better or what the project maintainers would prefer. I'm open to both. In the end the best way to submit any packages from such large projects is to branch the packages first in an isolated project just to determine build and runtime dependencies. In the branched project the mandatory checks would kick in by default. -Scott