Bug 2396873

Summary: ramalama: Please rebuild in Fedora 43
Product: [Fedora] Fedora Reporter: Karolina Surma <ksurma>
Component: ramalamaAssignee: Stephen John Smoogen <smooge>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 43CC: dwalsh, go-sig, lsm5, mhroncok, smooge
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ramalama-0.12.3-1.fc43 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-10-07 13:51:14 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: 2373702    

Description Karolina Surma 2025-09-19 13:43:46 UTC
Dear package maintainer,

Due to reasons described in https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/O6LBYY446Q2FWVBEVJCOJ34ADXTEIH65/ a rebuild of ramalama is needed in Fedora 43.

During the mass rebuild, it was determined that rawhide and f43 branches differ, hence I did not know if I could safely merge rawhide into f43 or if the f43 branch needs a diverging bump.

Please, determine this yourself and rebuild the package in Fedora 43, ideally before the Fedora 43 Final freeze (2025-10-07).

Thank you. Let me know if you need help.

Comment 1 Lokesh Mandvekar 2025-09-19 15:42:44 UTC
The differing branches are because of Packit creating individual PRs for active branches https://src.fedoraproject.org/rpms/ramalama/pull-requests?status=Merged . AFAICT, merging rawhide into f43 shouldn't be a problem as there are no actual code changes for the package between the two branches. I'll defer to Stephen though.

Comment 2 Stephen John Smoogen 2025-09-19 16:12:27 UTC
Correct there should be no problem. I just do not know what is involved with rebuilds when auto generated release numbers are done.. do I just make an empty commit and then start a build or is there some sort of exception needed?

Comment 3 Karolina Surma 2025-09-22 14:33:49 UTC
Yes, an empty commit is alright, we do:
$ git commit -am "Rebuilt for Python 3.14.0rc3 bytecode" --allow-empty

Comment 4 Karolina Surma 2025-09-29 14:22:56 UTC
Hello. This is a bulk comment.

This package still needs to be rebuilt and/or shipped with Python 3.14.0rc3+ bytecode in Fedora 43.

The Final Freeze of Fedora 43 is scheduled to start next week. Please prioritize this bugzilla accordingly.

Thanks.

Comment 5 Stephen John Smoogen 2025-09-29 15:14:46 UTC
Package has been rebuilt in https://koji.fedoraproject.org/koji/buildinfo?buildID=2833137

Comment 6 Fedora Update System 2025-09-29 15:42:41 UTC
FEDORA-2025-619c380538 (ramalama-0.12.3-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-619c380538

Comment 7 Fedora Update System 2025-09-30 01:32:37 UTC
FEDORA-2025-619c380538 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-619c380538`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-619c380538

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

Comment 8 Fedora Update System 2025-10-07 13:51:14 UTC
FEDORA-2025-619c380538 (ramalama-0.12.3-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.