FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.

» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > CentOS > CentOS

LinkBack Thread Tools
Old 06-25-2008, 12:37 PM
"Tim Verhoeven"
Default Broken upgrade to 5.2 {solved - I hope}

On Wed, Jun 25, 2008 at 2:27 PM, Ian Blackwell <ian@ikel.id.au> wrote:
> Thanks to all that offered advice to help solve this for me. Here's a round
> up for those that may follow in similarly ill-fated foot-steps.
> 1. Don't update/upgrade remotely without using "screen". Dropping the ssh
> session caused yum to die inelegantly, with duplicate packages in the RPM
> database.
> 2. Analysing the output from
> /bin/rpm -qa --qf '%{name}-%{version}-%{release}.%{arch}.rpm
' | sort
> led me to erase almost 30 new packages that appeared to be duplicates of
> existing packages. This wasn't without problems though, because I used this
> command:-
> yum erase libgcc-4.1.2-42.el5.i386
> to remove the duplication noticed here:-
> libgcc-4.1.2-14.el5.i386.rpm
> libgcc-4.1.2-42.el5.i386.rpm

The best way to remove duplicate package is using rpm itself and the
--justdb switch. This will only remote entries inside the RPM database
and not on the filesytem itself. If you remove the newest version of
the duplicate packages you can run the yum update again and it will
reinstall the newer versions and all should be good.


Tim Verhoeven - tim.verhoeven.be@gmail.com - 0479 / 88 11 83

Hoping the problem magically goes away by ignoring it is the
"microsoft approach to programming" and should never be allowed.
(Linus Torvalds)
CentOS mailing list

Thread Tools

All times are GMT. The time now is 09:44 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org