Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1096480 - Koji uses "--target arm" and thus causes wrong build failures
Summary: Koji uses "--target arm" and thus causes wrong build failures
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: koji
Version: el6
Hardware: arm
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Dennis Gilmore
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-10 23:02 UTC by Robert Scheck
Modified: 2020-11-30 15:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-30 15:54:31 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
root.log (99.59 KB, text/plain)
2014-05-10 23:03 UTC, Robert Scheck 		no flags Details
build.log (1.66 KB, text/plain)
2014-05-10 23:03 UTC, Robert Scheck 		no flags Details
View All

Description Robert Scheck 2014-05-10 23:02:06 UTC 
Description of problem:
If a SRPM is built via Koji on ARM (from GIT checkout) a command like this
is fired:

$ rpmbuild -bs --target arm --nodeps clamav.spec 
Building target platforms: arm
Building for target arm
error: line 166: Dependency tokens must begin with alpha-numeric, '_' or '/': Requires(pre):		%_initrddir
$ 

And this fails...there is no architecture "arm" but e.g. "armv7l". And that
one succeeds:

$ rpmbuild -bs --target armv7l --nodeps clamav.spec 
Building target platforms: armv7l
Building for target armv7l
warning: Could not canonicalize hostname: arm03-qa03.cloud.fedoraproject.org
Wrote: /home/fedora/robert/rpmbuild/SRPMS/clamav-0.98.3-1.fc20.src.rpm
$ 

Version-Release number of selected component (if applicable):
koji-1.9.0-1.fc21.noarch
rpm-4.11.2-10.fc21.armv7hl
mock-1.1.38-1.fc21.noarch

How reproducible:
Everytime, see above and below.

Actual results:
Build failure that should not happen.

Expected results:
No build failure.

Additional info:
This might be a duplicate of bug #1021001 - not sure. However we are still
experiencing this issue in our regular Fedora Koji buildsystem.
Comment 1 Robert Scheck 2014-05-10 23:03:20 UTC 
Created attachment 894338 [details]
root.log
Comment 2 Robert Scheck 2014-05-10 23:03:44 UTC 
Created attachment 894339 [details]
build.log
Comment 3 Kevin Fenzi 2020-04-25 18:30:03 UTC 
Is this still happening?
Comment 4 Panu Matilainen 2020-08-10 09:08:13 UTC 
Yes it is. See https://bugzilla.redhat.com/show_bug.cgi?id=1839372
Comment 5 Ben Cotton 2020-11-05 16:46:05 UTC 
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

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 EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 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.
Comment 6 Ben Cotton 2020-11-30 15:54:31 UTC 
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 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
EPEL 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.