[Rpm-maint] upgrade/replace multiple packages with custom package

Andy Harrison aharrison at gmail.com
Fri Aug 29 13:14:44 UTC 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I was just wondering the proper way to do this.

I've created a custom version of openldap, tailored for my company's
preferences and configs.  I created the spec from scratch, just
borrowing a few lines from the default centos 5 openldap spec.  It
builds and packages just fine.  I used a different value for %{NAME}
and I used 22.3.43 for the version instead of the actual openldap
version 2.3.43 to make sure my version would be higher.

I then checked the capabilities provided by the existing installed
openldap packages: (rpm -q --provides
openldap-devel-2.3.27-8.el5_2.4.x86_64
openldap-2.3.27-8.el5_2.4.x86_64
openldap-clients-2.3.27-8.el5_2.4.x86_64) and made sure that my spec
file had appropriate Provides declarations, then double checked it for
accuracy (rpm -qp --provides
/usr/src/redhat/RPMS/x86_64/metrocast-openldap-22.3.43-1.x86_64.rpm).
 Everything looks great at this point, but when I actually run the rpm
upgrade command, it complains that my package has files that conflict
with the currently installed openldap packages.  I put in Obsoletes
lines for every package and version to be replaced (expressed this way
just for brevity:  Obsoletes:
openldap-{servers,clients,devel,servers-sql} <= 2.4) to no avail.

I eventually tired of wrestling with it, reverted the changed %{NAME},
then the upgrade ran fine.  So I'd just like to know if there is
indeed a proper way to change the name of a package and have it
replace an existing package of a different name?

- --
Andy Harrison
public key: 0x67518262
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: http://getfiregpg.org

iD8DBQFIt/ZDNTm8fWdRgmIRAvn5AKDE85O9hP+fNIMygTVYf1k+tVlfKACgkVss
Kh1SQyFCl1FEEURuvrXtlMQ=
=Os4K
-----END PGP SIGNATURE-----



More information about the Rpm-maint mailing list