Re: How to handle erasing an RPM that contains a mandatory file

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Oct 27, 2006 at 01:17:05PM -0400, Fulko.Hew@xxxxxxxxx wrote:
> I would, but the std tarballs such as (in the case of bash), from
> FSF.org don't come with spec files.  Do you suggest that I hunt
> down Redhat's version of a source?

Hunt down?
ftp://ftp.redhat.com/pub/redhat/linux/enterprise/4/en/os/i386/SRPMS

> Perhaps, but the person who built our package manager manager
> chose to rpm -e followed by rpm -i, whenever a package is upgraded.
> This is probably due to the reason that during the install process
> (because its actually install and not upgrade), we have to be able
> to 'install' older versions of an RPM incase the 'new' rpm failed
> because and embedded application failed within the new rpm,
> or because the customer decided that they wanted to fall-back
> to an older version of the same rpm
> 
> I don't think that rpm allows you to upgrade to an older version.

rpm -U --oldpackage rpm

or, if you must, --force.

> 
> This document is strictly confidential and intended only for use by the addressee unless otherwise stated.  If you are not the intended recipient, please notify the sender immediately and delete it from your system.

You do know the archives for this list are publicly displayed? :)

-- 
lfr
0/0

Attachment: pgp6DXyXXTWc2.pgp
Description: PGP signature

_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list

[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux