On Wed, Mar 19, 2008 at 06:10:00PM +0300, Valery Mitsyn wrote:
> On Wed, 19 Mar 2008, Troy Dawson wrote:
> 
> >[log in to unmask] wrote:
> >>Hi Troy,
> >>
> >>On Wed, 19 Mar 2008, Troy Dawson wrote:
> >>
> >>>Matthias Schroeder wrote:
> >>>>Tullio Macorini wrote:
> >>>>>what is the newest rpm for CUPS in SL 4.5 ?
> >>>>>
> >>>>>cups-1.1.22-0.rc1.9.20.2.el4_6.5.i386.rpm
> >>>>>or
> >>>>>cups-1.1.22-0.rc1.9.20.2.2.i386.rpm
> >>
> >>>>I fear in the case of cups (and probably a few others) the only way out
> >>>>is to build the rpm without the dist tag, so that yum and rpm recognize
> >>>>that the package needs updating...
> >>
> >>>Ugg ... thanks for letting us know.  For SL 4.6 we cleaned all these up 
> >>>(I
> >>>really hope) but that doesn't clean up the errata in the other releases.
> >>>I'll take a shot at cleaning this up, which might involve moving the 
> >>>older
> >>>rpm's into the obsolete area.
> >>
> >>But how to get these updates onto systems where the old packages are
> >>already installed (other than manually, with --force)? Do I have to dig
> >>out my old scripts from the pre yum aera?
> >>
> >>Cheers,
> >>        Stephan
> >>
> >
> >You have a good point.
> >Any ideas anyone?
> 
> Unfortunately, it can be done by hand only.
> One can do:
> rpm -e --nodeps --justdb <old>
> yum -y -d 1 install <new>
> I don't claim it is absolutely safe method.

That seems excessive, what about just:

rpm --oldpackage -Uvh <package>

where, from the man page: 

 --oldpackage
	  Allow  an upgrade to replace a newer package with an older one.

This should allow a seemingly "older" package to replace an installed one:

Or did I miss something?

Cheers
Chris
--
Chris Payne			[log in to unmask]
TRIUMF ATLAS Tier-1 System Administrator - Networking
TRIUMF				+1 604 222 7554
4004 Wesbrook Mall, Vancouver, BC, V6T2A3, CANADA