Bug 2491173

Summary: openjph-0.30.1 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: openjphAssignee: Simone Caronni <negativo17>
Status: MODIFIED --- QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: multimedia-sig, negativo17
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Upstream Release Monitoring 2026-06-21 14:55:38 UTC
Releases retrieved: 0.30.0
Upstream release that is considered latest: 0.30.0
Current version/release in rawhide: 0.29.0-1.fc45
URL: https://github.com/aous72/OpenJPH

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/375199/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/openjph

Comment 1 Upstream Release Monitoring 2026-06-22 01:26:59 UTC
Releases retrieved: 0.30.1
Upstream release that is considered latest: 0.30.1
Current version/release in rawhide: 0.29.0-1.fc45
URL: https://github.com/aous72/OpenJPH

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/375199/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/openjph

Comment 2 Fedora Update System 2026-08-10 17:21:05 UTC
FEDORA-2026-26ae66c60f (darktable-5.4.1-12.fc45, digikam-9.1.0-3.fc45, and 25 more) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-26ae66c60f

Comment 3 Fedora Update System 2026-08-12 19:38:22 UTC
FEDORA-2026-823e06dfcf (darktable-5.4.1-12.fc45, digikam-9.1.0-3.fc45, and 25 more) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-823e06dfcf

Comment 4 Fedora Update System 2026-08-12 19:40:37 UTC
FEDORA-2026-b8ff7153f1 (darktable-5.4.1-12.fc46, digikam-9.1.0-3.fc46, and 25 more) has been submitted as an update to Fedora 46.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-b8ff7153f1

Comment 5 Fedora Update System 2026-08-15 11:50:33 UTC
FEDORA-2026-823e06dfcf (darktable-5.4.1-12.fc45, digikam-9.1.0-3.fc45, and 25 more) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2026-08-15 11:51:04 UTC
FEDORA-2026-b8ff7153f1 (darktable-5.4.1-12.fc46, digikam-9.1.0-3.fc46, and 25 more) has been pushed to the Fedora 46 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Miloš Komarčević 2026-09-22 08:08:32 UTC
Can be closed, superseded by bug 2536103 now.