#129 Duplicity with Snap

[Cristhian Martinez Ochoa]

Hi,

Duply is failing to retrieve some data from Duplicity when is installed from SNAP, which is now promoted like the official repo for Duplicity, and also is the prefered method in Ubuntu.

"Could not parse the python interpreter used from duplicity"

This is causing taking the default version defined in Duply, this is a problem because Python2 is already "End Of Life", due to this reason, most of the new servers do not have it installed by default now. Python3 would be more appropriate these days.

In my particular case, just changing this variable (DEFAULT_PYTHON='python3') in Duply solved my problem.

SNAP Packages are "containerized" and code is not human-readable, that's why Duply can not read the file.

Thanks and regards!

[ede]

is there any way to detect that duplicity is snap packaged? is the location under '/snap/bin/' a trustworthy indicator?

regards.. ede

[Cristhian Martinez Ochoa]

It should be enough!

According to the official docs: https://snapcraft.io/docs/system-snap-directory

This folder is defined and recognized as "where the files and folders from installed snap packages appear on your system.".

[ede]

hmmm, i don't like the by default part of

The /snap directory is, by default, where the files and folders from installed snap packages appear on your system.

it implies there may be scenarios when it might be snap packaged but located elsewhere.

will have a more detailed look soonish.. ede

[ede]

hi Cristhian,

can you please test if this v2.4dev snapshot
https://duply.net/tmp/duply.sh
works for you?

thanks.. ede

[Cristhian Martinez Ochoa]

Hi Edgar.

Thanks a lot for the follow up!
It works fine, I tested it using SNAP and PIP packages, both successful.

I have to mention that I stopped using Duplicity from SNAP, now I'm using PIP package instead.

• I'm aware Duplicity is having a lot of issues with Snap, you guys have put a lot of effort the last weeks in the Gitlab repo solving these issues.

• I've been using Duplicity and Duply for more than 7 years without any major problems, in fact it can be considered very stable.

• Using SNAP package for some months, I found some major issues. Running everyday after some months I started getting some random errors that I was unable to reproduce in a clean installation, that's why I never reported these issues. But after weeks of running everyday using Cron, I always got these errors. So, that's why I stopped using Snap.

• One of the main reasons I started using Snap (instead of the PPA) was because the ARM support that was removed some days ago. I know you guys are working on this issue too. But definitely Snap is still far from being considered a stable package.

At the end, that's why I considered that PIP is now the more stable and safe way to use Duplicity and Duply.

Thanks a lot!
Regards.

[ede]

thx Cristhian! will close the ticket then. fix will be in the next release.

wrt, to duplicity bugs/issues. pls report them, even if they only occur sporadically. the more reports are there, the more likely it is we will find the underlying issue ;)

the "new" duplicity snap will contain and run it's own python3.8 . we surely hope that this encapsulation will bring some more stability to duplicity snap. also armhf/64 will be back, if only as edge snaps for the time being!

regards.. ede