Bug 632452
| Summary: | RFE: pass the more helpful yum-like error message instead of the non-specific gpk-update-viewer error message? | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | collura |
| Component: | gnome-packagekit | Assignee: | Richard Hughes <rhughes> |
| Status: | NEW --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | collura, rhughes |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 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
collura
2010-09-10 00:37:16 UTC
What was the same error from the yum command line tool in this case? it looked like a mismatched dependency requirement. i referenced that in comment#0: "an example of this is expressed in the 'additional info' section of https://bugzilla.redhat.com/show_bug.cgi?id=632126" which shows: "Additional info: # yum update Loaded plugins: presto, refresh-packagekit Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package firefox.x86_64 0:3.5.12-1.fc12 set to be updated ---> Package xulrunner.x86_64 0:1.9.1.12-1.fc12 set to be updated ---> Package xulrunner-devel.x86_64 0:1.9.1.12-1.fc12 set to be updated --> Processing Dependency: pkgconfig(nspr) >= 4.8.6 for package: xulrunner-devel-1.9.1.12-1.fc12.x86_64 --> Finished Dependency Resolution Error: Package: xulrunner-devel-1.9.1.12-1.fc12.x86_64 (updates) Requires: pkgconfig(nspr) >= 4.8.6 Installed: nspr-devel-4.8.4-2.fc12.x86_64 (@updates) pkgconfig(nspr) = 4.8.4 Available: nspr-devel-4.8.2-1.fc12.i686 (fedora) pkgconfig(nspr) = 4.8.2 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest" hope that helps. This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping dont remember fc13 error to recheck this with lately but changing to fc13 to ping i didnt think to write down the actual error message but this seems to be present in fc15 This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping this is still alive in f16-release in the following way: when a nss update came through f16-gnome-updates-testing that killed yum updates (see https://bugzilla.redhat.com/show_bug.cgi?id=753931) yum gave a nice error message about repomd.xml saying that it couldnt connect but the gpk-update-viewer would run and just say 'no updates available' like all was well. when i downgraded the nss it fixed yum and the gpk-update-viewer so now the gpk-update-viewer found 75 updates that had been piling up for the last week or so unknowingly. it would have been nice to have a 'notice of brokenness' for the week or so instead of a 'no updates available' so i would have know to look for the brokenness. i only noticed the brokenness when i went to install a package and found that couldnt to repo eventhough browswer worked fine. |