Martin Wilck has proposed merging lp:~mwilck/duplicity/duplicity into
lp:duplicity.
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~mwilck/duplicity/duplicity/+merge/301268
Glob matching in current duplicity uses a selector function that
The same change can be trivially merged into the 0.7 series, providing a
similar speed-up. I did that in lp:~mwilck/duplicity/0.7-series. I'll postpone
officially requesting this merge until someone has commented here.
--
https://code.launchpad.net/~mwilck/duplicity/duplicity/+merge/301268
Your
Martin Wilck has proposed merging lp:~mwilck/duplicity/0.7-series into
lp:duplicity/0.7-series.
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~mwilck/duplicity/0.7-series/+merge/301332
This merge request contains the same change as
I added a merge request for the 0.7-series now,
https://code.launchpad.net/~mwilck/duplicity/0.7-series/+merge/301332.
--
https://code.launchpad.net/~mwilck/duplicity/duplicity/+merge/301268
Your team duplicity-team is requested to review the proposed merge of
lp:~mwilck/duplicity/duplicity into
Hmm, that would mean that setsid behaves differently on different
distributions. It might be a difference in how setsid behaves, or a difference
in pexpect.
In which test did the problems with "setsid -w" occur on precise / trusty?
--
https://code.launchpad.net/~mwilck/duplicity/0.7-series/+me
To make sure I understand correctly - my changes work on Xenial and Wily but
not on older Ubuntu releases? Are you using Ubuntu native pexpect packages or
pexpect from PyPi?
--
https://code.launchpad.net/~mwilck/duplicity/0.7-series/+merge/301332
Your team duplicity-team is requested to review
That might be the reason, then? Maybe we need to put in a version check on the
pexpect module?
--
https://code.launchpad.net/~mwilck/duplicity/0.7-series/+merge/301332
Your team duplicity-team is requested to review the proposed merge of
lp:~mwilck/duplicity/0.7-series into lp:duplicity/0.7-ser
The problem is caused by different syntax of setsid invocation. setsid on
Trusty doesn't support -w.
I am pushing a patch that tests for -w support and uses the flag only if
supported.
--
https://code.launchpad.net/~mwilck/duplicity/0.7-series/+merge/301332
Your team duplicity-team is request
Martin Wilck has proposed merging lp:~mwilck/duplicity/0.7-series into
lp:duplicity/0.7-series.
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~mwilck/duplicity/0.7-series/+merge/301492
Fix the regression on Trusty.
--
Your team
Martin Wilck has proposed merging lp:~mwilck/duplicity/duplicity into
lp:duplicity.
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~mwilck/duplicity/duplicity/+merge/306331
GPG: enable truly non-interactive operation with gpg2
This
Martin Wilck has proposed merging lp:~mwilck/duplicity/0.7-series into
lp:duplicity/0.7-series.
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~mwilck/duplicity/0.7-series/+merge/306333
GPG: enable truly non-interactive operation with
Martin Wilck has proposed merging lp:~mwilck/duplicity/0.7-series into
lp:duplicity/0.7-series.
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~mwilck/duplicity/0.7-series/+merge/316852
Fixed the documentation of --use-agent in the man
ong ago).
Regards
Martin
>
> 2.
> please check if gpg2.1 does start a gpg-agent. according to my tests a
> gpg-agent instance is started and keeps lingering if not killed manually.
>
> ..ede/duply.net
>
>
> On 09.02.2017 14:44, Martin Wilck wrote:
>> Martin
13 matches
Mail list logo
