On Wed, 2017-08-30 at 10:21 -0500, Jimmy Berry wrote:
It appears that in order to workaround the
emitted by repo_checker a number of patterns have been whitelisted.
aside, during my requests for feedback about issues and manual
previous repo_checker nothing was really mentioned although we have
across several cases that would have been present previously as well.
this case of working around an issue it would be preferred if a
started rather than me having to stumble across such workarounds.
Currently whitelisted patterns:
Most can probably disappear already again - as they were temporarily
needed (as an alternative to rebase a whole staging).
Maybe we can have this kind of 'staging based, temporary ignores' as
part of the project meta data the checker would take into account?
Would be better than having a whitelist which I will keep forgetting to
This is certainly less than ideal as it means that any
ignored. In fact one of the oldest issues in against the repo_checker
regards to packages reference by patterns being removed without any
I tried to only add stuff which I understood when I saw them in staging
(pattern-kde for example got updated, telepathy dropped, which meant
the stuff in the existing stagings were no longer happy)
repo_checker acts like an extension of OBS in that OBS
BuildRequires can all be met before attempting to build while
ensures the Requires can be met. Currently, anything added to the
have all of the build dependencies present. This has led to packages
split and all sort of fun stuff to avoid bringing in too many
the end of the day, packages in rings are only passed because all
dependencies are also available in the rings.
I don't think every package in a ring has to be installable inside the
I can easily create a source package in ring0 that produces a FOO-doc
package that has a Requires: texlive - yet, I certainly do not EVER
want texlive in ring0. And as long as FOO has no build deps on texlive,
there is no need to do so.
Contrast that to patterns which while having their
present do not have there install-time dependencies present. That
with the exact version Requires causes the repo_checker to correctly
they are not installable from the letter staging. Not having the
requirements met within the staging seems like a short-cut rather
idealistically correct setup. If patterns are of enough importance to
the rings, their install-time requirements ought to be as well.
would seem logical to remove them from the rings since they really
being checked as the primary purpose of a pattern is to pull in other
which cannot be confirmed.
We care for SOME patterns - and the not for others.. the ones we care
for are referenced by the testdvd creation script - and the kiwi file
gets invalidated if the pattern is not installable.
Alternatively, not having the hard version
requirements would remove
repo_checker errors, but still fail if packages required by the
removed. Either way, from what I can tell this should really be a
change rather than either special-casing in repo_checker or
hide the problem.
Most of the issues I'd seen around patterns in stagings is that things
change in oS:F - and if the patterns are the only thing holding off
repo-checker from passing it, I'm certainly not willing to rebase a
staging and have it build a couple hours again.
Hence back to the proposal: can we have the repo_checker exception for
a staging project as part of the staging project directly instead of a
global config ?