Bug 63796 - Automatic multi-arch builds no longer work.
Summary: Automatic multi-arch builds no longer work.
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rpm-build
Version: 7.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-04-18 19:46 UTC by Sam Varshavchik
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-09-29 21:48:53 UTC
Embargoed:


Attachments (Terms of Use)

Description Sam Varshavchik 2002-04-18 19:46:04 UTC
The fix for rpm -q bug #27589 introduced a side effect of disabling automatic
multi-architecture builds by rpm -bb and -ba (and -tb and -ta).  Prior to 4.0.3,
running an 'rpm -bb' on a

BuildArch: i386 noarch

resulted in rpmb making two passes over the spec file automatically, one for
each listed architecture.  After 4.0.3 rpmb would run a single pass only, for i386.

As a result, it is no longer possible to distribute packages that are to be
built against multiple architectures without additional out-of-band instructions
specifying that rpm should be executed multiple times with different --target
options.  The problem with the rpm --query really didn't affect building, before
4.0.3.

The only issue with multi-arch builds is the generation of the source RPM. 
There are three options:

* Leave it as it is.  Before 4.0.3 the source RPM was created after the last
arch pass.  Explicitly define this as the official behavior.

* Introduce a SourceArch: header that specifies a single architecture.  rpm -ba
would create a source RPM only after a pass for the architecture specified by
SoruceArch: (in absence of SourceArch: the platform build is defaulted).

* Introduce an ExtraArch: header, listing multiple architectures to run
additional spec file passes for, after processing -ba or -bb.

Comment 1 Bill Nottingham 2005-09-29 21:48:53 UTC
Closing bugs on older, no longer supported, releases. Apologies for any lack of
response.

For RPM issues, please try a current release such as Fedora Core 4; if bugs
persist, please open a new issue.


Note You need to log in before you can comment on or make changes to this bug.