Latest upstream release: 3.2.4 Current version/release in rawhide: 3.2.3-1.fc35 URL: https://nextcloud.com/install/#install-clients 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://fedoraproject.org/wiki/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/18381/
Created attachment 1798805 [details] [patch] Update to 3.2.4 (#1979745)
the-new-hotness/release-monitoring.org's scratch build of nextcloud-client-3.2.4-1.fc32.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=71415174
Waiting to see changelog.
FEDORA-2021-cf8c2d291c has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-cf8c2d291c
FEDORA-2021-cf8c2d291c has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-cf8c2d291c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-cf8c2d291c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2021-57ac471b84 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-57ac471b84
FEDORA-EPEL-NEXT-2021-d82a519a4f has been submitted as an update to Fedora EPEL 8 Next. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2021-d82a519a4f
FEDORA-EPEL-2021-57ac471b84 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-57ac471b84 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-NEXT-2021-d82a519a4f has been pushed to the Fedora EPEL 8 Next testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2021-d82a519a4f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-NEXT-2021-d82a519a4f has been pushed to the Fedora EPEL 8 Next stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-NEXT-2021-be5d11e8c1 has been submitted as an update to Fedora EPEL 8 Next. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2021-be5d11e8c1
FEDORA-EPEL-2021-fec62c9d9f has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-fec62c9d9f
FEDORA-2021-cf8c2d291c has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2021-fec62c9d9f has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-fec62c9d9f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-NEXT-2021-be5d11e8c1 has been pushed to the Fedora EPEL 8 Next testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2021-be5d11e8c1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-NEXT-2021-be5d11e8c1 has been pushed to the Fedora EPEL 8 Next stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2021-fec62c9d9f has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.