Re: [Duplicity-team] Stable snap broken? (was Re: Duplicity 0.8.09 Released)

I'm up for centralizing the discussion on anything but email. Since a lot of the discussion has already gone on in issue #119 , let's centralize there for now. It has the ability to do limited threading and markdown. As for building on

Re: [Duplicity-team] Stable snap broken? (was Re: Duplicity 0.8.09 Released)

On 21.03.2022 22:05, Aaron wrote: On 2022-03-21 20:50, Aaron wrote: I feel like the "proper" solution here is to add a step to the CI/CD process on Gitlab to test the snap before it goes to stable. That is a bit awkward as snaps do not run inside Docker containers, which are what is easiest

Re: [Duplicity-team] Stable snap broken? (was Re: Duplicity 0.8.09 Released)

and while this autoupdating may be nice, it is really risky for production systems. so once again. let's adopt snap versioning like blender does it (see below and https://snapcraft.io/blender). let's keep 'latest/{stable..edge}' but additionally push at least '/stable', so users can decide to

Re: [Duplicity-team] Stable snap broken? (was Re: Duplicity 0.8.09 Released)

OK, snap is in candidate as 0.8.10.1558. It's been checked with snapcraft.io release-tools. ...Ken On Mon, Jan 13, 2020 at 11:23 AM Kenneth Loafman wrote: > Aaron, > > I agree with everything you said! > > I'll start pushing to *candidate* instead of *stable* for releases. You > can check it

Re: [Duplicity-team] Stable snap broken? (was Re: Duplicity 0.8.09 Released)

Aaron, I agree with everything you said! I'll start pushing to *candidate* instead of *stable* for releases. You can check it out and promote it to stable. Snaps may lag behind repo releases, but that's OK. One change I've made is that now snaps are versioned with the revno of the repo, like

Re: [Duplicity-team] Stable snap broken? (was Re: Duplicity 0.8.09 Released)

Kenneth, On 2020-01-09 18:25, Kenneth Loafman wrote: > Gave up and swapped to Python3 for snaps. It works now. > > As to what was happening, I don't know, I can't reproduce it. Great that you turned around a fix so quickly. Are we happy enough with Python 3 for backends etc that we want to

Re: [Duplicity-team] Stable snap broken? (was Re: Duplicity 0.8.09 Released)

Gave up and swapped to Python3 for snaps. It works now. As to what was happening, I don't know, I can't reproduce it. ...Ken On Thu, Jan 9, 2020 at 10:29 AM Kenneth Loafman wrote: > Found the problem, but don't know of a fix yet. > > Snaps run under Python2.7 and it's dying in

Re: [Duplicity-team] Stable snap broken? (was Re: Duplicity 0.8.09 Released)

Found the problem, but don't know of a fix yet. Snaps run under Python2.7 and it's dying in duplicity/dup_time.py with: >>> from duplicity import dup_time Traceback (most recent call last): File "", line 1, in File "duplicity/dup_time.py", line 67, in page for more information.""")

Re: [Duplicity-team] Stable snap broken? (was Re: Duplicity 0.8.09 Released)

OK, reverted to rev 33, 0.8.08. Will check it out tomorrow. There were no changes to the yaml file and the snap build went fine. Very odd! :-( ...Thanks, ...Ken On Wed, Jan 8, 2020 at 5:07 PM Aaron wrote: > Kenneth, > > The 0.8.09 (45) snap seems completely broken for me on two machines >

[Duplicity-team] Stable snap broken? (was Re: Duplicity 0.8.09 Released)

Kenneth, The 0.8.09 (45) snap seems completely broken for me on two machines (16.04 and 19.04): $ duplicity --version Traceback (most recent call last):   File "/snap/duplicity/45/bin/duplicity", line 31, in     from future import standard_library ModuleNotFoundError: No module named