Bug 1327946 - arch-specific noarch package available on all architectures
Summary: arch-specific noarch package available on all architectures
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: koji
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mike McLean
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-18 06:09 UTC by jiri vanek
Modified: 2020-04-09 07:55 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:49:41 UTC
Type: Bug


Attachments (Terms of Use)

Description jiri vanek 2016-04-18 06:09:14 UTC
Hello!

Even the summary sounds strange, so to be clear - I do  not insists this is bug.

On some arches, java-1.8.0-openjdk is built in loop. First build cycle normal, second with full debug on.
Then it is packed like: 
	java-1.8.0-openjdk
	java-1.8.0-openjdk-debug
	java-1.8.0-openjdk-devel
	java-1.8.0-openjdk-devel-debug
	java-1.8.0-openjdk-headless
	java-1.8.0-openjdk-headless-debug
see: http://koji.fedoraproject.org/koji/buildinfo?buildID=750919

However,second build is slow, so  it is done only on architectures, where hotspot is avaiable. In case of fedora on intels. (as whole loop is finished hours single loop of before arm  anyway.

Now - for sake of complexity and simplicity, also noarch javadoc is built in loop on intels:
	java-1.8.0-openjdk-javadoc
	java-1.8.0-openjdk-javadoc-debug
	java-1.8.0-openjdk-javadoc-zip
	java-1.8.0-openjdk-javadoc-zip-debug

However, as it is no arch - it is available also on arm.

Althugh it is probably harmless, I think it is an bug.

Also I think koji is right (http://koji.fedoraproject.org/koji/buildinfo?buildID=750919) when showing the noarchas simply as noarch. But yum install on arm should not pull the intel-specific noarch apckages... (again, I'm aware of how strangely this sounds...)


dnf install java-1.8.0-openjdk* on clean arm f23 board:
 ...
 jasper-libs                      armv7hl 1.900.1-31.fc23         fedora  129 k
 java-1.8.0-openjdk               armv7hl 1:1.8.0.77-1.b03.fc23   updates 194 k
 java-1.8.0-openjdk-accessibility armv7hl 1:1.8.0.77-1.b03.fc23   updates  30 k
 java-1.8.0-openjdk-demo          armv7hl 1:1.8.0.77-1.b03.fc23   updates 1.9 M
 java-1.8.0-openjdk-devel         armv7hl 1:1.8.0.77-1.b03.fc23   updates 7.8 M
 java-1.8.0-openjdk-headless      armv7hl 1:1.8.0.77-1.b03.fc23   updates  29 M
 java-1.8.0-openjdk-javadoc       noarch  1:1.8.0.77-1.b03.fc23   updates  15 M
 java-1.8.0-openjdk-javadoc-debug noarch  1:1.8.0.77-1.b03.fc23   updates  15 M
 java-1.8.0-openjdk-src           armv7hl 1:1.8.0.77-1.b03.fc23   updates  45 M
 java-atk-wrapper                 armv7hl 0.33.2-1.fc23           updates  79 k
 javapackages-tools               noarch  4.6.0-8.fc23            updates 103 k
 ...
 java-1.8.0-openjdk-javadoc-debug noarch  1:1.8.0.77-1.b03.fc23   updates  15 M
should not be there.

Comment 1 Jan Kurik 2016-07-26 04:36:08 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 2 Randy Barlow 2016-10-18 04:59:12 UTC
Hello Jiri! It sounds like this might be an issue with Koji and not Bodhi. Should we change the component to koji?

Comment 3 jiri vanek 2016-10-18 09:20:30 UTC
If you feel like it, then please go on,

Comment 4 Randy Barlow 2016-10-18 15:55:36 UTC
Thanks Jiri!

Comment 5 Mike McLean 2016-10-18 16:48:39 UTC
"noarch but not really noarch" is a persistent problem in a lot of areas.

It's not clear to me what you want koji to do differently. You seem to want the noarch packages blocked from certain repos. At that point, the rpm is out of koji's hands.

A compose tool outside of koji can cross reference the excludearch and exclusivearch headers of the corresponding srpm and opt to exclude a noarch package. Unfortunately rpm does not include those headers in the noarch package itself.

Comment 6 Mike McLean 2017-02-17 16:46:46 UTC
It looks like you're mainly concerned with the content of the yum repos that Fedora publishes. Those are not created by Koji.

If there is something that Koji itself should do differently, then please clarify. Otherwise this bug should probably be changed to another component (perhaps Pungi?)

Comment 7 Fedora End Of Life 2017-11-16 18:31:20 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's 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 Fedora  'version'
of '25'.

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 25 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 2017-12-12 10:49:41 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.