Releases retrieved: 0.6.1 Upstream release that is considered latest: 0.6.1 Current version/release in rawhide: 0.6.0-4.fc41 URL: https://octave.sourceforge.io/dicom/ 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/9242/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/octave-dicom
Created attachment 2040333 [details] Update to 0.6.1 (#2299770)
the-new-hotness/release-monitoring.org's scratch build of octave-dicom-0.6.1-1.fc40.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=120987337
Summary of important user-visible changes for dicom 0.6.1 (2024/07/24): ------------------------------------------------------------------------- * minor doc updates * miscellaneous build, test and load changes Sounds like we could skip this update.
FEDORA-2025-859228d224 (octave-dicom-0.6.1-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-859228d224
FEDORA-2025-93cc6f5e1d (octave-dicom-0.6.1-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-93cc6f5e1d
FEDORA-2025-859228d224 (octave-dicom-0.6.1-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-2195bd71af (octave-dicom-0.6.1-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-2195bd71af
FEDORA-2025-39976e1595 (octave-dicom-0.6.1-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2025-39976e1595
FEDORA-2025-93cc6f5e1d has been pushed to the Fedora 42 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-93cc6f5e1d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-93cc6f5e1d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-39976e1595 has been pushed to the Fedora 40 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-39976e1595` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-39976e1595 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-2195bd71af has been pushed to the Fedora 41 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-2195bd71af` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-2195bd71af See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-39976e1595 (octave-dicom-0.6.1-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-2195bd71af (octave-dicom-0.6.1-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-93cc6f5e1d (octave-dicom-0.6.1-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.