Bug 826621
| Summary: | Unable to update fc17 after Upgrading from FC16 to FC17 using DVD_64 bits | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Majid <m.rafiee2007> |
| Component: | yum | Assignee: | Fedora Packaging Toolset Team <packaging-team> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | ffesti, jzeleny, maxamillion, mike_parlett, m.rafiee2007, packaging-team, smfaall, tim.lauridsen, urilabob, zpavlas |
| 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: | 2013-05-22 13:14:05 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
Majid
2012-05-30 15:48:42 UTC
Hi Had a very similar problem loads of broken dependency and duplicates I accepted F17 is bleeding edge and so did the following: package-cleanup --problems this will be large but shows the problems Then #yum clean all #yum clean packages #yum clean headers #yum clean oldheaders #package-cleanup --cleandupes #package-cleanup --problems Remove obvious dupes still there by hand #yum remove name of old package #yum update if this fails then repeat #package-cleanup --problems Remove obvious dupes still there by hand #yum remove name of old package Got there eventauly and probaly cleaned up loads of old stuff i got away with at the the f15 and F16 update :-) the pureist would probaly say use yum to update not a DVD but with a BT drip feed internet that would be too painfull as any failure would be another 3 hour re-try for me good luck Thank you for your fast response. I worked. I'm so grateful for your help. * I worked= It worked Good stuff glad to be of help mike I encountered similar problems, with hundreds of duplicate and orphan packages. What worked for me was: yum --skip-broken distro-sync (broke the back of the orphan and duplicate packages, reducing it down to 20 or so) followed by package-cleanup --orphans > orphs package-cleanup --dupes > dupes then editing the orphs and dupes files by hand to construct 'yum remove' commands. Some gotchas with this: .In the orphs list, you will get backup kernels and also any packages you installed by hand. You probably _don't_ want to remove these. .Be very careful in editing the dupes list that you only remove the older package of each pair of duplicates. When you go to run the command, if you see lots of dependent packages listed to be removed, it almost certainly means that you are about to remove the _new_ version of the package. ABORT THE COMMAND and check again carefully. Oh, I forgot to mention that even yum --skip-broken distro-sync may abort with errors about specific packages (I hit these problems with some sane backends and cups libraries). To get it to work, I had to manually 'yum remove' those specific packages, remember them, go through the whole cleanup process, then manually reinstall. > To get it to work, I had to manually
> 'yum remove' those specific packages, remember them, go through the whole
> cleanup process, then manually reinstall.
This is the right thing to do. Yum doesn't remove packages during the upgrade. Therefore if there are some packages that can't be updated for any reason and they are holding back the update of other packages, yum will fail to do the update altogether.
|