Can the OO.o maintainers please work towards building the Linux RPM
packages with RPM v4 instead of RPM v3? I'm not sure there's any benefit
to using RPM v3, but I'm willing to be educated. :-)
Here's why:
I use a Red Hat RHN Satellite Server, and need to serve OO.o RPMs to our
client desktops. To do this, I need to re-sign the packages with our own
GPG key. The short version is "you can't, but there's a workaround".
When doing this with the regular version (v4) of the "rpm" command, the
packages are silently destroyed. ("rpm --resign *.rpm") They no longer can
be installed by any means. This seems to be a bug in rpm v4, but I'm not
sure why it hasn't been addressed, given that brand new RPMs are still
being built with v3.
It turns out that this problem stems from packages being built using
version (v3) of the RPM package.
The workaround is to re-sign the packages with version 3 of the "rpm"
command, (which incidentally dates back to RH Linux 6.2). The binary can
be downloaded via rpmfind.net, and extracted from the RPM using rpm2cpio.
(You would "rpm2cpio rpm-3.0.*.rpm | cpio -dimv".)
RPM v3 runs without problems on more recent Linuxes, but I would *not*
install it into the system: just move it to ~/bin/rpm3.
Regards,
Richard Smit
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
