How to build bzip2-payload rpms on 11.0?

English Programming/Scripting
#1

Is there any way to build bzip2-payload rpms on newer rpm versions?
The thing is, our application must be installable out-of-the-box on different opensuse versions (starting with 10.2). Everything works if I package it on 10.3, but when doing it on 11.0, I get an rpmlib(PayloadIsLzma) dependency error. Requiring users to upgrade their versions of rpm is not an option.
The man pages don’t seem to contain any information in this regard.

Thanks a lot!

#2

Nevermind, I found a way.
For those who are interested, you should add this to your .spec files:

set payload compression to bzip2 to allow installation on non-lzma rpms.

%define _binary_payload w9.bzdio

#3

On Thu, 24 Jul 2008 11:46:03 GMT
alex sh <alex_sh@no-mx.forums.opensuse.org> wrote:

>
> Is there any way to build bzip2-payload rpms on newer rpm versions?
> The thing is, our application must be installable out-of-the-box on
> different opensuse versions (starting with 10.2). Everything works if
> I package it on 10.3, but when doing it on 11.0, I get an
> rpmlib(PayloadIsLzma) dependency error. Requiring users to upgrade
> their versions of rpm is not an option.
> The man pages don’t seem to contain any information in this regard.
>
> Thanks a lot!
>
>
Hi
Have a look at the release notes;
http://www.suse.com/relnotes/i386/openSUSE/11.0/RELEASE-NOTES.en.html#05

You need to create two versions.

–
Cheers Malcolm °¿° (Linux Counter #276890)
SLED 10 SP2 i586 Kernel 2.6.16.60-0.25-default
up 0:58, 2 users, load average: 1.03, 0.56, 0.28
GPU GeForce Go 6600 TE/6200 TE Version: 173.14.09

#4

That’s why you use a dedicated build root. Building rpms on 11.0 and then expecting them to work on 10.3 is bound to break. It begins with simple missing libraries, followed by ABI inconsistencies, and lastly, differing RPM payloads. Use a 10.3 build tool to create 10.3 rpms.

#5

Thanks for the reply, but the program is compiled elsewhere.
I mean, I only want to use 11.0 for packaging, not for building.
And since the program I’m packaging has almost no external dependencies (the same binary is working on lots of different systems), there’s only the package compatibility part.
Anyway, I resolved it already (see the second post), but thanks anyway.