Bug 194197 - should check for dep closure before allowing an update to be pushed
Summary: should check for dep closure before allowing an update to be pushed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora Infrastructure
Classification: Retired
Component: update system
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Luke Macken
QA Contact: Bill Nottingham
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-06-06 01:56 UTC by Jeremy Katz
Modified: 2016-09-20 02:37 UTC (History)
3 users (show)

Fixed In Version: 1.0
Clone Of:
Environment:
Last Closed: 2006-06-22 16:27:34 UTC
Embargoed:


Attachments (Terms of Use)

Description Jeremy Katz 2006-06-06 01:56:52 UTC
Updates being pushed should at check and at least warn about dep closure
problems before pushing so that we can avoid things like bug 194195

Comment 1 Luke Macken 2006-06-06 16:11:09 UTC
Sounds reasonable.

Before a push, I'll have the update system toss the rpms in a testclosure repo,
run createrepo on it, then run `repoclosure -n -r testclosure -r core -r
{updates,updates-testing}`, correct ?

To make this possible, I would have to modify repoclosure to use return values
to actually know if there are broken deps or not.

Once they are found, what should the update system do, just halt the push ?

Comment 2 Jeremy Katz 2006-06-06 16:30:16 UTC
It should probably at least require an override to know that you're pushing
something that may be broken.  Given that multiple updates could be required for
a set, unless the pushing happens as a batch, an override is going to be needed.



Comment 3 Luke Macken 2006-06-22 16:27:34 UTC
There is now a 'Check Dependecies' button next to the 'Push' button in
fedora-updates/push.py.  It seems to be working OK (although I think a
yum{,-util} upgrade on porkchop might speed things up a bit).  I'll work with
Jesse on polishing this feature up.


Note You need to log in before you can comment on or make changes to this bug.