-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
repo_checker: provide indication of new dependencies for ring0 packages #1039
Comments
Presumably, the new dependencies is not so much the item of interest as much as dependencies from a lower ring (ie ring-1). |
I think on ring1/2 this is not so much of a problem, as those things are actually seen usually, due to the split LETTER/LETTER:DVD The problem with ring0 packages is that they are also in LETTER (in the ring0 enabled stagings), and this simply can consume everything in ring1 - definitively not what we want. Just had a case again today, i.e. rpm update, new dependency on /usr/bin/python (python2-base); python2-base being a ring1 package, this would not cause any extra warning that this rpm package would completely mess up ring0 (luckily, this provoked a couple build fails, which made us catch it) |
Out of curiosity, why is the ring project separation not carried down into stagings? Would seem far more straight forward than tip-toeing around the issue.
That would have been seemingly the most straight forward way to setup stagings in light of rings. Presumably that would also solve the hidden dependency issue as well. |
I don't see why we need this - wouldn't this cause the cycle to grow? @DimStar77 ? |
I don't see why we need this - wouldn't this cause the cycle to grow? @DimStar77 ? One would expect so, yes - but pretty sure the issues mentioned above were somehow not caught by it (or the cycle checker did not really work back then, also a possibility - there are still chances that OBS misses cycles - purely based on feelings) |
Source request: https://progress.opensuse.org/issues/15016:
Likely, a comment on the request and an added review for
factory-maintainers
or similar?The text was updated successfully, but these errors were encountered: