Bug 1871096 - genesis-simulator (probably incorrectly) build-depends on flex-devel
Summary: genesis-simulator (probably incorrectly) build-depends on flex-devel
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: genesis-simulator
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ankur Sinha (FranciscoD)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-21 10:20 UTC by Arjun Shankar
Modified: 2021-06-17 01:10 UTC (History)
1 user (show)

Fixed In Version: genesis-simulator-2.4-9.20210608git7b0a66b.fc34 genesis-simulator-2.4-9.20210608git7b0a66b.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-16 20:50:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Arjun Shankar 2020-08-21 10:20:42 UTC
I'm filing this report because when I run the following command:
dnf repoquery --disablerepo="*" --enablerepo="*-source" --arch=src --whatdepends flex-devel

I see genesis-simulator listed among the results.

flex-devel used to provide only libfl.a, a static library.

As per Fedora packaging guidelines, a build dependency on a static library should be represented by depending on the -static subpackage, not the -devel one that might actually contain the static library:

https://docs.fedoraproject.org/en-US/packaging-guidelines/#_statically_linking_executables

I just changed the subpackage split of flex, and have obsoleted flex-devel.

Although build-dependent packages will continue to build, a build-dependency requiring libfl.a should now ideally build-depend on libfl-static. flex now also provides shared libraries, and a build-dependency on libfl.so, should now depend on libfl2 (shared library) and libfl2-devel (headers).

Comment 1 Ben Cotton 2021-02-09 15:16:12 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 2 Fedora Update System 2021-06-08 11:45:28 UTC
FEDORA-2021-c3b870b4df has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-c3b870b4df

Comment 3 Fedora Update System 2021-06-08 11:45:29 UTC
FEDORA-2021-8d0ffe083f has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-8d0ffe083f

Comment 4 Fedora Update System 2021-06-09 03:09:46 UTC
FEDORA-2021-c3b870b4df has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-c3b870b4df`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-c3b870b4df

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

Comment 5 Fedora Update System 2021-06-09 03:29:10 UTC
FEDORA-2021-8d0ffe083f has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-8d0ffe083f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-8d0ffe083f

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

Comment 6 Fedora Update System 2021-06-16 20:50:27 UTC
FEDORA-2021-8d0ffe083f has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2021-06-17 01:10:46 UTC
FEDORA-2021-c3b870b4df has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.


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