On Mon, 2022-05-16 at 16:08 -0600, James Szinger wrote: > On Mon, 16 May 2022 20:56:10 +0100 > Patrick O'Callaghan <pocallaghan@xxxxxxxxx> wrote: > > > On Mon, 2022-05-16 at 18:20 +0200, Markus Schönhaber wrote: > > > 16.05.22, 17:45 +0200, Patrick O'Callaghan: > > > > > > > I updated to F36 a few days ago and everything seemed to go > > > > smoothly > > > > until I noticed my regular nightly backups were failing. I use > > > > Borgbackup and the configuration has been stable for a long > > > > time > > > > with > > > > no problems. The actual backup does seem to succeed, but Borg > > > > runs > > > > a > > > > post-backup repository check that is now failing, even for > > > > backups > > > > taken before the system upgrade. > > > > > I upgraded a laptop to F36 few days ago and borgmatic runs without > error, including the check. I suspect something else is happening. > Try increasing borgmatic’s verbosity to see the borg error message. > I may do that. However the Borg (not Borgmatic) BZ is reporting errors related to 1.2. I'm not sure it's the same thing as my errors only appeared after the F35->F36 update and I had been running Borg 1.2 before that. > borgmatic-1.6.0 does have some breaking changes, but that is the > current version for both 35 and 36. > > Also, my systems are using borgbackup-1.1.17-1.fc35 and > borgbackup-1.2.0-1.fc36. How did you get 1.2.0 on F35? I simply updated with dnf and there it was. Didn´t do anything special. 1.1x was the version on F35's initial release, but it changed subsequently. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
