Installing both .i586 and .x86_64 version of the same package

Discussion:

Joachim Schrod

2011-05-17 22:51:09 UTC

Hello,

On openSUSE 11.4 x86_64; I'd like to install both

libtcnative-1-0.x86_64=1.3.3-6.2
libtcnative-1-0.i586=1.3.3-6.2

I.e., both the 32bit and the 64bit versions of that library. Fwiw,
this is runtime stuff for Tomcat. (I suppose, what I really want is
a libtcnative-1-0-32bit package; but I didn't find one.)

I didn't find a way to do so; it can't be solved via multiversion
config, as they are the same version.

Is there a way to do this, short of taking the source rpm, renaming
it, and creating one's own package?

Joachim

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod Email: ***@acm.org
Roedermark, Germany
--
To unsubscribe, e-mail: opensuse+***@opensuse.org
For additional commands, e-mail: opensuse+***@opensuse.org

Philipp Thomas

2011-05-17 23:33:05 UTC

Permalink

Post by Joachim Schrod
Is there a way to do this, short of taking the source rpm, renaming
it, and creating one's own package?

Renaming it won't help. You need a 32 bit runtime package. We have
them in the distribution as packages with -32bit in their names. These
are essentially the bare dynamic libs taken from the i586 packages.
This is so that there is no overlap between the 32 and the 64 bit
packages.

Philipp

--
To unsubscribe, e-mail: opensuse+***@opensuse.org
For additional commands, e-mail: opensuse+***@opensuse.org

Joachim Schrod

2011-05-18 01:13:22 UTC

Permalink

Post by Philipp Thomas

Post by Joachim Schrod
Is there a way to do this, short of taking the source rpm, renaming
it, and creating one's own package?

Well, I suspected that, but considered to ask before exploring
other directions. There ain't no 32 bit runtime packages for the
libraries that I need, namely libapr1 and libtcnative-1-0. (I need
to have a Tomcat test environment with 32bit Java.)

How are the -32bit rpms normally created? I wanted to look if there
is a .spec file that creates them from the i586 packages; but
zypper source-install tells me it doesn't find appropriate source
packages for any -32bit.rpm that I tried.

If there is no automatism that I can re-use, I'll probably have to
go forward and write such a .spec file.

Anyhow, thanks a lot for the quick answer, it pointed me already to
the right direction.

Joachim

Dimstar / Dominique Leuenberger

2011-05-18 05:55:51 UTC

Permalink

Post by Joachim Schrod
How are the -32bit rpms normally created? I wanted to look if there
is a .spec file that creates them from the i586 packages; but
zypper source-install tells me it doesn't find appropriate source
packages for any -32bit.rpm that I tried.
If there is no automatism that I can re-use, I'll probably have to
go forward and write such a .spec file.
Anyhow, thanks a lot for the quick answer, it pointed me already to
the right direction.

Some packages have a baselibs.conf file, instruction the build service
to create the -32bit packages.

An example of this can be seen for example in the geoclue package.

The baselibs.conf generally is really simple:
A simple line with the basename of the library package that needs to be
provided when building this as well (so in geoclue you will see
libgeoclue0 in there).

This will result in libgeoclue-0.12.0-1.1 and
libgeoclue-32bit-0.12.0-1.1.

If you are not able to adapt this to your packages in need, let me know
and I will try to create a repository for you which does this steps for
your libs (please let me know then which baseversions and openSUSE you
are running: I do not really want to break your system with incompatible
libs).

Dominique

--
To unsubscribe, e-mail: opensuse+***@opensuse.org
For additional commands, e-mail: opensuse+***@opensuse.org

Joachim Schrod

2011-05-18 08:43:13 UTC

Permalink

Post by Dimstar / Dominique Leuenberger

Some packages have a baselibs.conf file, instruction the build service
to create the -32bit packages.

Ah, I see. That's easy; so I'm going to make my own changed lib
packages when 32bit variants are missing.

What would be the correct way to inquire for addition of such
baselibs.conf files to standard openSUSE packages -- via Bugzilla,
or via OpenFATE? Maybe I could trigger to get them into 12.1, and
thus would get them without own package building the next time.

Joachim

PS: Thanks a lot for your offer to set up a repository for me.
Luckily for you, it's not needed. :-) :-)

Michael Schroeder

2011-05-18 08:56:41 UTC

Permalink

Post by Joachim Schrod
On openSUSE 11.4 x86_64; I'd like to install both
libtcnative-1-0.x86_64=1.3.3-6.2
libtcnative-1-0.i586=1.3.3-6.2
I.e., both the 32bit and the 64bit versions of that library. Fwiw,
this is runtime stuff for Tomcat. (I suppose, what I really want is
a libtcnative-1-0-32bit package; but I didn't find one.)

You can't, as they obsolete each other.

Post by Joachim Schrod
I didn't find a way to do so; it can't be solved via multiversion
config, as they are the same version.
Is there a way to do this, short of taking the source rpm, renaming
it, and creating one's own package?

Install the 'build-mkbaselibs' package and do
echo 'libtcnative-1-0' > baselibs.conf
/usr/lib/mkbaselibs -c /usr/lib/build/baselibs_global.conf -c baselibs.conf <rpm>
on the libtcnative-1-0.i586 rpm. It'll create a '-32bit' package
that you can install.

(The buildservice automatically does this if the source a
"baselibs.conf" file.)

Cheers,
Michael.

--
Michael Schroeder ***@suse.de
SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: opensuse+***@opensuse.org
For additional commands, e-mail: opensuse+***@opensuse.org

Joachim Schrod

2011-05-18 11:33:37 UTC

Permalink

Post by Michael Schroeder

Install the 'build-mkbaselibs' package and do
echo 'libtcnative-1-0' > baselibs.conf
/usr/lib/mkbaselibs -c /usr/lib/build/baselibs_global.conf -c baselibs.conf <rpm>
on the libtcnative-1-0.i586 rpm. It'll create a '-32bit' package
that you can install.
(The buildservice automatically does this if the source a
"baselibs.conf" file.)

Thanks, that's a nice quickfix; while I set up a repository to use
the buildservice.

Joachim

Andreas Jaeger

2011-05-18 09:12:58 UTC

Permalink

Post by Joachim Schrod

Post by Dimstar / Dominique Leuenberger

Some packages have a baselibs.conf file, instruction the build service
to create the -32bit packages.

Ah, I see. That's easy; so I'm going to make my own changed lib
packages when 32bit variants are missing.
What would be the correct way to inquire for addition of such
baselibs.conf files to standard openSUSE packages -- via Bugzilla,
or via OpenFATE? Maybe I could trigger to get them into 12.1, and
thus would get them without own package building the next time.

Either via bugzilla or direct as a patch - branch the package, update it, and
submit the fixed version back...

Andreas

--
Andreas Jaeger, Program Manager openSUSE
aj@{novell.com,suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
--
To unsubscribe, e-mail: opensuse+***@opensuse.org
For additional commands, e-mail: opensuse+***@opensuse.org

Joachim Schrod

2011-05-18 11:34:06 UTC

Permalink

Post by Andreas Jaeger

Post by Joachim Schrod
What would be the correct way to inquire for addition of such
baselibs.conf files to standard openSUSE packages -- via Bugzilla,
or via OpenFATE? Maybe I could trigger to get them into 12.1, and
thus would get them without own package building the next time.

Either via bugzilla or direct as a patch - branch the package, update it, and
submit the fixed version back...

:-) I'll look into it.

Joachim