Bug 672605 - rpmbuild should croak on unsupported BuildArch
Summary: rpmbuild should croak on unsupported BuildArch
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fedora Packaging Toolset Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-25 17:28 UTC by Petr Pisar
Modified: 2015-02-17 13:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 13:35:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Broken spec file (1.95 KB, text/plain)
2011-01-25 17:29 UTC, Petr Pisar
no flags Details

Description Petr Pisar 2011-01-25 17:28:29 UTC
I've written bad spec file with invalid BuildArch value:

BuildArch:    noarch
BuildArch:    perl(File::Spec)
BuildArch:    perl(File::Spec::Unix)

(The last two BuildArch should be BuildRequires.)

Local compilation with rpmbuild -ba succeeded. Compilation on koji failed with error message `BuildError: No matching arches were found'.

I think rpmbuild should fail too.

Comment 1 Petr Pisar 2011-01-25 17:29:20 UTC
Created attachment 475220 [details]
Broken spec file

This is the broken spec file.

Comment 2 Petr Pisar 2011-01-26 07:58:44 UTC
Ville Skyttä's observation:

And FWIW it seems that rpmbuild (4.8.1 on F-13)
silently ignores all but the first BuildArch in the specfile; perhaps it should
fail the build if there are more of them or just process them all (like it does
if there are multiple values in the first BuildArch line).

Comment 3 Panu Matilainen 2011-01-26 10:50:52 UTC
Architectures known to rpm are user-configurable so one users invalid build arch can be somebody elses perfectly valid arch. But at least a warning about unknown build architecture would help catch silly mistakes like this.

Comment 4 Fedora Admin XMLRPC Client 2012-04-13 23:05:46 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 5 Fedora Admin XMLRPC Client 2012-04-13 23:08:45 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 6 Fedora End Of Life 2013-04-03 16:45:35 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 7 Fedora End Of Life 2015-01-09 16:31:45 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Fedora End Of Life 2015-02-17 13:35:25 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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