Bug 2104099

Summary:	native scalpel depends on to be removed i686 java-openjdk packages
Product:	[Fedora] Fedora	Reporter:	jiri vanek <jvanek>
Component:	scalpel	Assignee:	Michal Ambroz <rebus>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	37	CC:	java-maint-sig, jhuttana, jvanek, pmikova, rebus, sgehwolf, zzambers
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	scalpel-2.1-0.rc2.35e1367.fc38.1 scalpel-2.1-0.rc2.35e1367.fc37.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-03-11 03:13:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2083750

Description jiri vanek 2022-07-05 14:49:47 UTC

Dear maintainer, we are going to drop i686 java packages in f37 - https://fedoraproject.org/wiki/Changes/Drop_i686_JDKs
your package (or maybe jsut some subpackage)  is directly depending on java and is native.

Please take care, and adapt  your package to exclude java on i686. For  your convenience, there was added macro %{java_arches}, including all arches java is available on,  which you can use to ifarch-out java specific features out in i686 (on non-java arches). Although for plain java package, the change is as simple as https://src.fedoraproject.org/rpms/maven/c/520942645bfd1e4721dacd536a6ccbf80495a8ae?branch=rawhide, you can not use it. The ExclusiveArch: %{java_arches} is not going to work for you, because your package is not simple java application, and also non-java world depends on it.

See exemplar PR: https://src.fedoraproject.org/rpms/graphviz/pull-request/9#request_diff
See more details eg in:: https://bugzilla.redhat.com/show_bug.cgi?id=2102298
See why in : https://pagure.io/fesco/issue/2772
Please read carefully proposal: https://fedoraproject.org/wiki/Changes/Drop_i686_JDKs
Please see tracking bug for most up to date informations: https://bugzilla.redhat.com/show_bug.cgi?id=2083750

I'm terribly sorry to report this bug so late in f37 lifecycle. If you can, please handle this with priority.

Comment 1 Ben Cotton 2022-08-09 13:20:40 UTC

This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.

Comment 2 Fedora Update System 2023-03-04 23:27:20 UTC

FEDORA-2023-acbbaf26fc has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-acbbaf26fc

Comment 3 Fedora Update System 2023-03-04 23:27:21 UTC

FEDORA-2023-2537b5fcc2 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-2537b5fcc2

Comment 4 Fedora Update System 2023-03-05 02:31:40 UTC

FEDORA-2023-2537b5fcc2 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-2537b5fcc2`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-2537b5fcc2

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2023-03-05 03:10:34 UTC

FEDORA-2023-acbbaf26fc has been pushed to the Fedora 38 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-acbbaf26fc

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2023-03-11 03:13:49 UTC

FEDORA-2023-acbbaf26fc has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2023-03-13 00:59:15 UTC

FEDORA-2023-2537b5fcc2 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.