Issue 86032 - Use RPM version 4.x for rpm-based distribution
Summary: Use RPM version 4.x for rpm-based distribution
Status: ACCEPTED
Alias: None
Product: Installation
Classification: Application
Component: ui (show other issues)
Version: OOo 2.3.1
Hardware: PC Linux, all
: P4 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-12 07:33 UTC by tserries
Modified: 2013-08-07 15:26 UTC (History)
7 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description tserries 2008-02-12 07:33:36 UTC 
Please, use a newer version of rpm (4.x) to build the OOo rpm packages. The
currently used version (3.0.6) is incompatible with our system management
system: Red-Hat Satellite server.

We run a Red-Hat satellite server to manage our Red-Hat Enterprise Linux Desktop
systems (approximately 3.500 of them using OOo). The satellilte server only
accepts signed rpms (with rpm version >= 4.x). The rpms provided by OOo are
unsigned; when we sign the rpms with our own GPG key the satellite server runs
into internal errors.

Currently we need to "repackage" the OOo rpms by a script developed by
ourselves; with the risk of missing or breaking something. It would be a relief
for us if we could use the original OOo rpms.

Best Reguards
Thomas Serries
Comment 1 Olaf Felka 2008-02-12 08:42:46 UTC 
Please have a look.
Comment 2 jens-heiner.rechtien 2008-02-12 11:15:13 UTC 
In principle we need to use a rpm packager which produces packages which can be
installed on the oldest supported systems, which is currently (OOo-2.4) defined
as systems with at least glibc-2.2.4. It's unfortunate if one distribution
decides to no longer accept older package formats, breaking upward compability.
I'm pretty sure that rpm-4.x packages do not install on the older systems.

Ingo, can you shed some light on this?

@is: reassign
Comment 3 ingo.schmidt-rosbiegal 2008-02-13 09:16:26 UTC 
Hm, I have not tested yet, if packages created with rpm 4.x can be installed
with older rpm versions. But if rpms have to be signed, we should not wait too
long to switch to rpm 4.x. It is surely not acceptable that users have to
repackage our packages.
This needs a clarification for OOo 3.0 -> setting target
Comment 4 nospam4obr 2008-04-11 10:09:55 UTC 
AFAIK the latest 3.x versions of RPM are capable of installing RPM 4 packages. However, signing is also 
possible with RPM 3 and the current LSB still specifies the RPM major as "shall be 3" ( see http://refspecs.linux-foundation.org/LSB_3.2.0/LSB-Core-generic/LSB-Core-generic/pkgformat.html ).

Did you use RPM 3 or 4 when signing the vanilla OOo RPM (of v3) ? 

Maybe providing properly signed RPM 3 packages might work as well  ..
Comment 5 ingo.schmidt-rosbiegal 2008-05-27 16:31:54 UTC 
Target 3.x