SCIENTIFIC-LINUX-USERS Archives

March 2008

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Akemi Yagi <[log in to unmask]>
Reply To:
Akemi Yagi <[log in to unmask]>
Date:
Wed, 19 Mar 2008 08:56:20 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
On Wed, Mar 19, 2008 at 8:42 AM, Chris Payne <[log in to unmask]> wrote:

>  > >>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?
>
>  > >
>  > >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:

Isn't it possible to give a slightly highre e.v.r. to the new/current
rpm in such a way that the next version still installs as newer?

Akemi

>  Or did I miss something?

ATOM RSS1 RSS2