[Yum] Duplicated packages.

[Shlomi Levi]

10x to you all,
'rpm -e ' did solve it all. Now how can I debug and see what went wrong with
the %post/%postun scripts (or even direct yum to be more verbose during the
update - since I understood that the failure was during update not cleanup)?

10x,
Shlomi

> -----Original Message-----
> From: yum-bounces at lists.dulug.duke.edu 
> [mailto:yum-bounces at lists.dulug.duke.edu] On Behalf Of Panu Matilainen
> Sent: Tuesday, June 13, 2006 10:29 PM
> To: Yellowdog Updater, Modified
> Subject: Re: [Yum] Duplicated packages.
> 
> 
> On Tue, 2006-06-13 at 16:05 -0400, Luke Macken wrote:
> > On Tue, Jun 13, 2006 at 09:36:32PM +0300, Panu Matilainen wrote:
> > > On Tue, 2006-06-13 at 21:20 +0200, Shlomi Levi wrote:
> > > > Hi,
> > > > Somehow I got to the situation that yum reports both glibc.i686 
> > > > 2.4-4 glibc.i686 2.4-8
> > > > As installed on my system. How do I remove the specific 
> 2.4-4 from my
> > > > system?
> > > > Not that important to remove the package as to fix 
> yum's repository.
> > > 
> > > Broken %post/%postun scripts can lead to such situations, 
> eg it's a 
> > > packaging problem typically. 'rpm -e glibc-2.4-4' to fix.
> > 
> > If the %post/%postun scripts are busted, then running `rpm -e 
> > glibc-2.4-4` will execute them and fail again.  You will need to do 
> > `rpm --noscripts -e glibc-2.4-4` to make sure that any of 
> the broken 
> > scripts aren't run.
> 
> Yup, to be sure you'll need --noscripts. OTOH quite often in 
> these cases it's the upgrade that's broken, not the remove 
> case. And if you need --noscripts it's usually a good idea to 
> look at the scripts to see what was *supposed* to happen on 
> the upgrade and what part of it possibly didn't happen 
> because of the failure.
> 
> 	- Panu -
> 
> _______________________________________________
> Yum mailing list
> Yum at lists.dulug.duke.edu 
> https://lists.dulug.duke.edu/mailman/listinfo/yum
>