Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 61766
Summary: | up2date-2.7.60-7.x.2 - solvedeps weirdness | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | James Manning <jmm> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED RAWHIDE | QA Contact: | Jay Turner <jturner> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7.2 | CC: | gafton, mihai.ibanescu, srevivo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-03-26 00:06:18 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
James Manning
2002-03-24 09:50:17 UTC
yeah, that all needs to be written to be sane. The current arg parsing code base is pretty out of hand already. I should be able to fix it for the next major release. How about if if cant find any solutions for those deps it prints: No packages were found that satisfy those dependencies. and exits? Sound like expected behaviour? sounds good to me - could the error line list the deps in the ilst that couldn't get satisfied, though? I think if pushed up to whatprovides() it'd also handle cases where unknown deps are just ignored by --whatprovides jmm@bp6:/home/jmm> sudo up2date --whatprovides=kernelxxx jmm@bp6:/home/jmm> sudo up2date --whatprovides=kernel,kernelxxx,kernel-headers kernel-2.4.9-31 kernel-headers-2.4.9-31 so if whatprovides() can do the required print/log/whatever'ing so that unsolvable deps get spit back to the user, then we're all set (well, solvedeps still needs to act sane, of course :) whatprovides() silently ignoring unsolvable deps is made more obvious with the above barfing on the unsolvable dep (original report here) but as soon as a solvable dep is also in the list, we're "fine" jmm@bp6:/usr/share/rhn/up2date_client> sudo up2date --solvedeps=kernel,kernelx Retrieving list of all available packages... Removing installed packages from list of updates... ######################################## Removing packages with files not specified from list... There are no packages available for update. None of the packages you requested were found, or they are already updated. which makes me think that (aside from notifying of specific unsolvable deps) we may need to just exit if there's nothing coming back from whatprovides --- wrapper.py.orig Mon Mar 25 18:48:16 2002 +++ wrapper.py Mon Mar 25 18:47:51 2002 @@ -374,6 +374,8 @@ extraPackages = whatprovides(argObj.getLong("solvedeps"), 1) if extraPackages: pkgNames = pkgNames + extraPackages + else: + sys.exit(0) if up2date.cfg.readEntry("showChannels"): channels = up2date.loginInfo['X-RHN-Auth-Channels'] but I'm not sure how that affects expected behavior elsewhere The bit of patch is basically exactly what I did. The other more sophisticated logic cases may have to wait for a redesign. Better handling of the many varied cases of "sort of failures" is on the plan for the next major version. It's kind of up there with "generic handling for special cases" the above fix should be in 2.7.63 or so (fixed in cvs already) I'm gonna flag this one as closed with RAWHIDE as the status. The more elaborate behaviour would make a good RFE. |