Using Opensuse Tumbleweed, the latest Deja Dup, version 49.0, can’t find the Restic that’s already there. It prompts to install it, acts like it’s installing it, then prompts all over again for an installation. Version 48.0 worked.
Weird… we use packagekit to manage that. I’ll have to install an opensuse vm and see why that’s failing.
Just to double check, I booted into my 9/25 snapshot. Version 48.0 was working there.
There’s always the possibility that something else in Tumbleweed changed since then and Deja Dup is just an innocent bystander.
48.0 was working because it didn’t yet rely on Restic - 49.0 switched to Restic by default. So that’s a new dependency. So that at least explains the behavior change. But I’m not sure why the packagekit integration is failing.
OK, when searching for installed packages, we include the PK_FILTER_ENUM_ARCH flag, limiting search results to packages that match the primary arch - if I remove that, we find restic just find. So that’s a big clue. Now I have to figure out if we should not be using that flag or if OpenSUSE PackageKit integration is in the wrong here.
You can test this on the console:
pkcon resolve restic --filter 'installed;arch'
vs
pkcon resolve restic --filter 'installed'
edit: ah, this is OpenSUSE bug 1212486 – Deja-dup (Gnome backup) insists on installing an already installed duplicity
This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.