Re: yum-completed-transactions...
Tim Lauridsen <[email protected]>
| Newsgroups | gmane.linux.rpm.yum |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Feb 18, 2010 at 12:44 AM, Robert G. Brown <[email protected]> wrote: > Dear yumsters, > > OK, yum was interrupted (probably by an urgent powerout shutdown) on a > small notebook computer I'm installing and had "uncompleted > transactions". I ran yum-complete-transactions and it announced that > what it wanted to do was remove 193 odd packages from the system, all of > them critical to system functionality at first glance. > > Safe or not safe? yum update is otherwise clean -- are these old > packages that yum needs to remove, or did yum get caught in a bizarre > state where it is getting ready to trash my system by removing enough > core that I'd have to reinstall (a major PITA)? > > rgb > > Robert G. Brown http://www.phy.duke.edu/~rgb/<http://www.phy.duke.edu/%7Ergb/> > Duke University Dept. of Physics, Box 90305 > Durham, N.C. 27708-0305 > Phone: 1-919-660-2567 Fax: 919-660-2525 email:[email protected]<email%[email protected]> > > > _______________________________________________ > Yum mailing list > [email protected] > http://lists.baseurl.org/mailman/listinfo/yum > It should be safe. This is because updating foo-1.0 to foo-2.0 is a 2 step process. 1. install foo-2.0 2. cleaup after foo-1.0 ( files not overwritten by foo-2.0 is erased) If the process is aborted between 1 and 2, then all the cleanup has not been executed and when you run yum-complete-transactions then yum will continue where it was aborted by doing all the cleanup and removing the old package versions. package-cleanup --dupes will show you a lot of duplicate packages because the old versions is still in the rpm db. after running yum-complete-transactions then then dupes should be gone. Tim _______________________________________________ Yum mailing list [email protected] http://lists.baseurl.org/mailman/listinfo/yum