It's possible that OBS says that A provides cap required by B, but for B
it does not show that cap is required or that cap is even provided by A.
Detect and handle that explicitly.
e52d4180361d8aab02eb8a2c0bae7d985f11d8d8 removed the exit 1 with adi
checker in mind (where one failed adi is not reason to be red on
dashboard). But for letter stagings we want to stop the pipeline
if installcheck failed (and not calculcate package lists or enable
images repo)
For openSUSE:Factory:Staging:adi:*, i586 is only enabled when necessary and so
the check is not set as required. Currently x86_64 is handled first (due to
target_archs), which means that for oS:F, i586 comes last and so the ugly hack
results in x86_64 getting a fake success and the actual status is set for i586
only, which gets ignored.
SLE service packs are just too complex to check delete requests sanely,
so better disable it. For next SLE we would enable it though
Fixes#2221 and ##2282
This is a too big hammer and doesn't motivate to fix things. This was
required for leaky ring projects, but with that problem gone, we can
require adi projects to fix issues.
A rather small reviewbot just made for one thing: check maintenance
release requests. They are much easier to handle: they are only created
on locked projects, so there is no waiting required. Just checking
and if it's broken, the request can be declined.
Extract the writing of the susetags content into a new script that
also creates a yaml file which package comes from what directory.
This information is used in repochecks.py to run findfileconflicts
and installcheck as repo_checker.pl used to
Implement a new command that takes a target project and one of its
staging projects and will run the checks against that project (including
delete requests) and if all is fine approves all reviews selected in
that staging.
This is to be used as part of the staging pipeline (and has been tested
with Factory's staging projects)
