Bug 974333
Summary: | Fedora 19 Beta Fresh install, yum update failures | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Christina <chu4> |
Component: | distribution | Assignee: | Radek Vokál <rvokal> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Radek Vokál <rvokal> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | dennis, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, vpavlin |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-08-04 14:30:11 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Christina
2013-06-14 02:11:36 UTC
This doesn't look like a kernel problem at all. Please attach your yum.log file from /var/log/ Hi, I did a fresh install so I could try to figure out what could have possibly branched to cause this error. After completely fresh installing Fedora 19 Beta (3.9.2-301.fc19.x86_64), I tried to run a yum update. Here is the error message that is generated the FIRST time when I ran a yum update (fresh install, no updates done): Error: Package: pymongo-gridfs-2.1.1-3.fc19.x86_64 (@anaconda) Requires: pymongo = 2.1.1-3.fc19 Removing: pymongo-2.1.1-3.fc19 Removing: pymongo-2.1.1-3.fc19.x86_64 (@anaconda) pymongo = 2.1.1-3.fc19 Obsoleted By: python-pymongo-2.5.2-1.fc19.x86_64 (updates-testing) pymongo = 2.5.2-1.fc19 Available: python-pymongo-2.5-4.fc19.x86_64 (fedora) pymongo = 2.5-4.fc19 You could try using --skip-broken to work around the problem You could try running rpm -Va --nofiles --nodigest After running: rpm --rebuilddb rpm -va yum clean metadata I was still unsuccessful performing a yum update. I ran into the same error. I will try to do the update and see what happens from there. As we are far away from F19 Beta, I guess your issue is solved. Feel free to reopen if it still persists for F20/Rawhide |