duplicity-team team mailing list archive

[Michael Terry <mike@xxxxxxxxxxx>]

OK, fixed.

I've uploaded a few trusty packages to support fasteners.  And I dropped
the precise/vivid builds (it was going to be harder to backport
fasteners to precise, and it's EOL anyway).
The stable release PPA has the backported packages too, so there
shouldn't be any issue when you release 0.7.13.
(The trusty builds seems to be successful, but stuck 'uploading'.  Might
just need to wait for next commit to kick new builds that do work.)

On Thu, May 11, 2017, at 11:14, Kenneth Loafman wrote:
> Thanks for the help!
> 
> ...Ken
> 
> 
> On Thu, May 11, 2017 at 10:11 AM, Michael Terry
> <mike@xxxxxxxxxxx> wrote:>> __
>> Although, I will mention that precise and vivid are really EOL.
>> Precise is only still open because Canonical sells extended support
>> for it.  And vivid is only still open because Canonical used it as
>> the base for their phones.>> 
>> 
>> On Thu, May 11, 2017, at 11:06, Michael Terry wrote:
>>> I think the best approach is to backport the package to the
>>> precise/trusty/vivid in the PPA (stable and nightly).  I'll try to
>>> do that today.>>> 
>>> 
>>> On Thu, May 11, 2017, at 10:06, Kenneth Loafman wrote:
>>>> @Michael,
>>>> 
>>>> I swapped duplicity over to the fasteners module, from the lockfile
>>>> module, and it does indeed release the lockfile if duplicity
>>>> crashes, so all good there.  Now, I'm trying to build the daily's
>>>> on Launchpad, and three of the releases do not have the python-
>>>> fasteners module in the repository, so will not build.>>>> 
>>>> What's the policy on this?  I know we can't access pip modules.  Is
>>>> there another way?  Should I just include the fasteners module in
>>>> the package?>>>> 
>>>> ...Thanks,
>>>> ...Ken
>>>> 
>>>> 
>>> 
>>