Releases retrieved: 3.0.3 Upstream release that is considered latest: 3.0.3 Current version/release in rawhide: 3.0.2-1.fc41 URL: https://gitlab.com/duplicity/duplicity 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/635/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/duplicity
Created attachment 2058321 [details] Update to 3.0.3 (#2326840)
the-new-hotness/release-monitoring.org's scratch build of duplicity-3.0.3-1.fc40.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=125955920
FEDORA-2024-c476c3fcc3 (duplicity-3.0.3-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-c476c3fcc3
FEDORA-2024-29ef7c771e (duplicity-3.0.3-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-29ef7c771e
FEDORA-2024-c476c3fcc3 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-2024-c476c3fcc3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-c476c3fcc3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-29ef7c771e 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-2024-29ef7c771e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-29ef7c771e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-af5db8453a 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-2024-af5db8453a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-af5db8453a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-745e10010f 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-2024-745e10010f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-745e10010f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-f9ebcc4f38 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-2024-f9ebcc4f38` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-f9ebcc4f38 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-f9ebcc4f38 (duplicity-3.0.3.2-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-2024-745e10010f (duplicity-3.0.3.2-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.