[opensuse-buildservice] serious architecture problems with python packages

Mathias Homann

25 Apr 2007 25 Apr '07

11:53

Hi, I'm trying to build a few python packages (http://build.opensuse.org/package/show?package=python-extattr&project=home%3Alemmy04 for example), and they get build as noarch, but inside they are either x86_64 (python files in /usr/lib64) or i586 (python files in /usr/lib), depending on which packafe got built last. of course, that way they are not usable. How can i fix that, and have the packages built as their proper architecture instead of "noarch"? bye, MH --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Show replies by date

Dominique Leuenberger

25 Apr 25 Apr

11:59

New subject: [opensuse-buildservice] serious architecture problems with python packages

...

...
...
On 25-04-2007 at 14:53, Mathias Homann wrote: Hi,

I'm trying to build a few python packages

(http://build.opensuse.org/package/show?package=python-extattr&project=home%3A

...

lemmy04 for example), and they get build as noarch, but inside they are either x86_64 (python files in /usr/lib64) or i586 (python files in /usr/lib), depending on which packafe got built last. of course, that way they are not usable.

How can i fix that, and have the packages built as their proper architecture

instead of "noarch"?

As python with it's paths pointing to lib[64] is not really 'noarch', you should remove the line BuildArch: noarch from the spec-file. then the package is built in two different versions (i586 and x86_64) with the corresponding content. (at this time I could not access the BS and check your spec file.. so it's just my buest guess for the moment) Regards, Dominique -- TMF is a global management and accounting outsourcing firm with 72 offices in 56 countries and over 2,000 professionals (February 2007). TMF is expanding rapidly throughout the world. Learn more about our unique network and our services and visit our website at www.tmf-group.com. The information contained in this e-mail communication is confidential and solely intended for the person to whom it is addressed. If someone other than the intended recipient should receive or come into possession of this e-mail communication, he/she will not be entitled to read, disseminate, disclose or duplicate it. If you are not the intended recipient, you are requested to notify the sender and to destroy the original e-mail communication. TMF is neither liable for the correct and complete transmission of the information contained in this e-mail communication nor for any delay in its receipt. This footnote also confirms that this email message has been checked for the presence of computer viruses. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Mathias Homann

12:43

Am Mittwoch, 25. April 2007 13:59:51 schrieb Dominique Leuenberger:

...

As python with it's paths pointing to lib[64] is not really 'noarch', you should remove the line BuildArch: noarch from the spec-file.

then the package is built in two different versions (i586 and x86_64) with the corresponding content.

(at this time I could not access the BS and check your spec file.. so it's just my buest guess for the moment)

good guess. stupid me just imported the specfile made by the original author, which had a "buildarch: noarch" well-hidden between all kind of other statements. thanks all the same, MH --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

6223

Age (days ago)

6223

Last active (days ago)

List overview

Download

2 comments

2 participants

participants (2)

Dominique Leuenberger
Mathias Homann