Bug 2139226 - OpenColorIO-2.2.1 is available
Summary: OpenColorIO-2.2.1 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: OpenColorIO
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Shaw
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1981045
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-01 21:58 UTC by Upstream Release Monitoring
Modified: 2023-01-13 19:25 UTC (History)
1 user (show)

Fixed In Version: OpenColorIO-2.2.1-1.fc38
Clone Of:
Environment:
Last Closed: 2023-01-13 19:25:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Update to 2.2.0 (#2139226) (974 bytes, patch)
2022-11-01 21:58 UTC, Upstream Release Monitoring
no flags Details | Diff
Update to 2.2.1 (#2139226) (1.00 KB, patch)
2023-01-09 20:00 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2022-11-01 21:58:12 UTC
Releases retrieved: 2.2.0
Upstream release that is considered latest: 2.2.0
Current version/release in rawhide: 2.1.2-4.fc38
URL: https://opencolorio.org/

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/9631/


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

Comment 1 Upstream Release Monitoring 2022-11-01 21:58:20 UTC
Created attachment 1921577 [details]
Update to 2.2.0 (#2139226)

Comment 2 Upstream Release Monitoring 2022-11-01 22:19:00 UTC
the-new-hotness/release-monitoring.org's scratch build of OpenColorIO-2.2.0-1.fc36.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=93684365

Comment 3 Upstream Release Monitoring 2023-01-09 19:59:53 UTC
Releases retrieved: 2.0.5, 2.1.3, 2.2.1
Upstream release that is considered latest: 2.2.1
Current version/release in rawhide: 2.1.2-5.fc38.1
URL: https://opencolorio.org/

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/9631/


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

Comment 4 Upstream Release Monitoring 2023-01-09 20:00:01 UTC
Created attachment 1936909 [details]
Update to 2.2.1 (#2139226)

Comment 5 Upstream Release Monitoring 2023-01-09 20:28:26 UTC
the-new-hotness/release-monitoring.org's scratch build of OpenColorIO-2.2.1-1.fc36.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=95933298

Comment 6 Fedora Update System 2023-01-13 19:18:42 UTC
FEDORA-2023-8d23d5e39a has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-8d23d5e39a

Comment 7 Fedora Update System 2023-01-13 19:25:52 UTC
FEDORA-2023-8d23d5e39a has been pushed to the Fedora 38 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.