← Back to team overview

duplicity-team team mailing list archive

Re: 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 <kenneth@xxxxxxxxxxx> wrote:

> 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 "<stdin>", line 1, in <module>
>   File "duplicity/dup_time.py", line 67, in <module>
>     page for more information.""")
> TypeError: 'str' object is not callable
>
> Line 76 is a long message in dup_time using _(), which is supposed to be
> installed globally through duplicity/__init__.py.
>
> Essentially, _() is not working anymore.
>
> On Wed, Jan 8, 2020 at 7:33 PM Kenneth Loafman <kenneth@xxxxxxxxxxx>
> wrote:
>
>> 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 <lists@xxxxxxxxxxxxxxxxxx> wrote:
>>
>>> 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 <module>
>>>      from future import standard_library
>>> ModuleNotFoundError: No module named 'future'
>>>
>>> Reverting to 0.8.08 (sudo snap revert duplicity) works as expected.
>>>
>>> If this is broken for others we need to fix this in the store asap --
>>> I'm tracking the stable channel on a real box and this completely broke
>>> it when it auto-updated last night.
>>>
>>> We need to be super-sensitive about putting things in the stable channel
>>> that are not production ready as the blessing and the curse of snaps is
>>> that they keep themselves up to date with the latest thing in the
>>> channel without user interaction. Thankfully that also should mean we
>>> can fix it quickly by just reverting stable to 0.8.08.
>>>
>>> Kind regards,
>>>
>>> Aaron
>>>
>>>
>>> _______________________________________________
>> Mailing list: https://launchpad.net/~duplicity-team
>> Post to     : duplicity-team@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~duplicity-team
>> More help   : https://help.launchpad.net/ListHelp
>>
>

Follow ups

References