Latest upstream release: 1.3.2 Current version/release in rawhide: 1.3.1-4.fc36 URL: https://github.com/bit-team/backintime 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/156/
Created attachment 1865718 [details] Update to 1.3.2 (#2063491)
the-new-hotness/release-monitoring.org's scratch build of backintime-1.3.2-1.fc34.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=84106603
According to changelog, there are fixes for Python 3.10 as in Fedora 35. https://github.com/bit-team/backintime/issues/1175
> Patch1: backintime-fix-python-3.10-tests.patch(In reply to Upstream Release Monitoring from comment #2) > the-new-hotness/release-monitoring.org's scratch build of > backintime-1.3.2-1.fc34.src.rpm for rawhide failed > http://koji.fedoraproject.org/koji/taskinfo?taskID=84106603 Patch #1 (backintime-fix-python-3.10-tests.patch): + echo 'Patch #1 (backintime-fix-python-3.10-tests.patch):' + /usr/bin/patch --no-backup-if-mismatch -f -p1 -b --suffix .fix_tests --fuzz=0 patching file common/tools.py Hunk #1 FAILED at 1802. 1 out of 1 hunk FAILED -- saving rejects to file common/tools.py.rej patch unexpectedly ends in middle of line What's source for this now failing patch? There has to be a comment with source according to policy.
It's the patch, which is as far as I can see the only change in the new release. https://github.com/bit-team/backintime/issues/1175
Okay, could you increase version then to avoid potential confusion? As that patch is now officially accepted a new source tarball with the updated version would be nice, too.
I don't really see any benefit in that, but feel free to apply the changes. The update doesn't add anything, which is not yet in fedora. I would just wait for a proper new release.
All righty. Let me take care about this issue.
Thanks. Could you add this bug to those new bodhi updates?
FEDORA-2022-a4728e2182 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a4728e2182
FEDORA-2022-26bd71adaa has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-26bd71adaa
FEDORA-2022-a4728e2182 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-26bd71adaa has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.