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 2264960 - F41FailsToInstall: primecount, primecount-libs
Summary: F41FailsToInstall: primecount, primecount-libs
Keywords:
Status: CLOSED COMPLETED
Alias: None
Product: Fedora
Classification: Fedora
Component: primecount
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jerry James
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F41FailsToInstall, RAWHIDEFailsToInstall
TreeView+ depends on / blocked
 
Reported: 2024-02-19 19:04 UTC by Fedora Fails To Install
Modified: 2024-02-19 21:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-02-19 20:32:56 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Fedora Fails To Install 2024-02-19 19:04:42 UTC 
Hello,

Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/

Your package (primecount) Fails To Install in Fedora 41:

can't install primecount:
  - nothing provides libprimesieve.so.11()(64bit) needed by primecount-7.10-4.fc40.x86_64
  
can't install primecount-libs:
  - nothing provides libprimesieve.so.11()(64bit) needed by primecount-libs-7.10-4.fc40.x86_64
  
If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.


If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks.


P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. To reproduce, use the koji/local repo only, e.g. in mock:

    $ mock -r fedora-41-x86_64 --config-opts mirrored=False install primecount primecount-libs


P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages

Thanks!
Comment 1 Kim Walisch 2024-02-19 20:06:51 UTC 
Hi Jerry,

I have released a new major version of the primesieve library today where I have also increased the major version of the .so file to libprimesieve.so.12, and this libprimesieve is a dependency of the primecount package. The current primecount package seems to depend on the previous libprimesieve.so.11. So I wanted to simply increase the libprimesieve so version in the primecount.spec file, but the libprimesieve so version is not specified there!? So I don't really understand where I can fix the old libprimesieve so version?

Note that the C/C++ API and ABI of primesieve-12.0 are fully backwards compatible with primesieve-11.*. Hence the current primecount package works just fine with the latest primesieve-12.0 release.
Comment 2 Kim Walisch 2024-02-19 20:27:41 UTC 
Maybe a new build of primecount is all that is needed after the new primesieve-12.0 release. So I tried it and it seems to have fixed the issue:

* https://koji.fedoraproject.org/koji/taskinfo?taskID=113763124
* https://src.fedoraproject.org/rpms/primecount/c/6851c77cf43eecdde547219adfa4efe9f6eca85f?branch=rawhide
Comment 3 Jerry James 2024-02-19 21:51:39 UTC 
Yes, a new build is all that is needed, so that the primecount binary depends on the new soname.  Sorry I wasn't around earlier to answer your question, but you figured it out.
Note You need to log in before you can comment on or make changes to this bug.