Question #687576 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/687576
Status: Open => Answered
Aaron Whitehouse proposed the following answer:
Hello Byron,
Duplicity already has Python 3 support in the 0.8 series. Anything that
doesn't work with Python 3 is a
Question #686193 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/686193
Status: Open => Answered
Aaron Whitehouse proposed the following answer:
Your best option would be to install the deja dup snap:
https://snapcraft.io/install/deja-dup/ubuntu
As that includes
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/08-docker-local-import into lp:duplicity.
Commit message:
* Convert the Docker infrastructure to pull the local branch into
duplicity_test. This allows testing the local branch with the known-good Docker
environment, even
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/08-snap-python2 into lp:duplicity.
Commit message:
Add packaging code for Snapcraft/Snap packages
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~aaron-whitehouse
Question #682840 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/682840
Aaron Whitehouse requested more information:
Or:
https://snapcraft.io/deja-dup
if you are using deja dup.
--
You received this question notification because your team duplicity-team
is an answer
Question #682840 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/682840
Status: Open => Needs information
Aaron Whitehouse requested more information:
Thank you for your question Navratan.
What version are you running? (duplicity --version).
Can you please try ag
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/08-dockerfixes into lp:duplicity.
Commit message:
Update duplicity_test Dockerfile:
* Use 18.04 instead of 16.04
* Use Ubuntu 18.04 version of pip
* Add Python3 and 2to3 as a dependencies
* Set docker locale as UTF-8
Thanks Ken,
On Jun 1 2019, at 4:32 pm, Kenneth Loafman wrote:
> I was thinking of using GitHub instead of Launchpad for git. It would be a
> much more agreeable site rather than something patched together to provide a
> non-native addition.
Yes, I think that makes sense, though when we last
Thanks Ken,
On Jun 1 2019, at 4:45 pm, Kenneth Loafman wrote:
> Launchpad runs tests when building the package. It will fail if something is
> wrong.
Sure, and that is really helpful, but that is only at/post release time, rather
than on merge to trunk.
>
> I am working on a dev PPA for
Hello all,
Following on from discussions here:
https://answers.launchpad.net/duplicity/+question/284247
https://lists.nongnu.org/archive/html/duplicity-talk/2015-07/msg00033.html
and elsewhere, does anybody have any objection to me converting our bzr
repository in Launchpad to a Git repository,
Hello Ken,
On May 17 2019, at 4:13 pm, Kenneth Loafman wrote:
> Already have that fixed in setup.py and tox.ini. Anyplace else?
>
>
>
Looks like you've fixed the one I was talking about.
> I usually run .run_tests before merging into trunk. I need to pull the latest
> and double check.
Sorry,
Aaron Whitehouse has proposed merging lp:~aaron-whitehouse/duplicity/07-snap
into lp:duplicity/0.7-series.
Commit message:
Add snapcraft packaging instructions for 0.7 series
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~aaron
All,
On May 1 2019, at 10:34 pm, Aaron Whitehouse wrote:
> I have now created a snap package for duplicity and would appreciate all of
> your help testing it. You can install it by typing:
> snap install duplicity --classic --beta
>
If you do test this, it would be very helpful
All,
We currently lock our python dropbox version to 6.9.0 in the requirements.txt.
After a bit of looking around, I think this may have been added because of this
bug: https://bugs.launchpad.net/duplicity/+bug/1639664
and never removed, even though that bug was fixed.
I do not use Dropbox for
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/08-style-fixes into lp:duplicity.
Commit message:
* Fix pylint style issues (over-indented text, whitespace on blank lines etc)
* Removed "pylint: disable=bad-string-format-type" comment, which was throwing
an erro
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/08-uexc-fix into lp:duplicity.
Commit message:
Fix for Bug #1770929 with associated test cases (thanks to Pete Zaitcev
(zaitcev) in Bug #1797928 for the head start).
Requested reviews:
duplicity-team (duplicity-team
Review: Needs Fixing
Please correct the string literals as mentioned above and check everything
still works.
--
https://code.launchpad.net/~vam9/duplicity/0.8-series-s3-kms-support/+merge/362000
Your team duplicity-team is subscribed to branch lp:duplicity.
Thank you for your contribution.
Many of the string literals in commandline.py and _boto_single.py are also
unadorned. I would have expected this to flag up when a full ./run_tests was
run before submitting (it has for me)?
There are plenty of examples in the same python files to follow, but
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/08-README-TESTING into lp:duplicity.
Commit message:
Change README-TESTING to be correct for running individual tests now that we
have moved to Pytest.
Requested reviews:
duplicity-team (duplicity-team)
For more details
Question #678723 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/678723
Aaron Whitehouse posted a new comment:
Thank you Marcus.
It sounds as though you are using deja dup, which is a GUI/frontend to
duplicity. What you are suggesting would make much more sense
Question #678917 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/678917
Status: Open => Answered
Aaron Whitehouse proposed the following answer:
Please see the mailing list threads starting here:
https://lists.nongnu.org/archive/html/duplicity-talk/2015-08/msg00
Question #678866 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/678866
Status: Open => Answered
Aaron Whitehouse proposed the following answer:
Please see https://blueprints.launchpad.net/duplicity/+spec/python3
--
You received this question notification beca
> It's been in a while now.
Ah, sorry, I hadn't looked at trunk in a while and this was still marked as
Needs Review. I've flipped it to Merged.
--
https://code.launchpad.net/~mgorse/duplicity/0.8-series/+merge/359864
Your team duplicity-team is subscribed to branch lp:duplicity.
The proposal to merge lp:~mgorse/duplicity/0.8-series into lp:duplicity has
been updated.
Status: Needs review => Merged
For more details, see:
https://code.launchpad.net/~mgorse/duplicity/0.8-series/+merge/359864
--
Your team duplicity-team is subscribed to branch lp:duplicity.
Review: Approve
@Ken -- is there anything holding up you merging this or have you just not had
time yet?
--
https://code.launchpad.net/~mgorse/duplicity/0.8-series/+merge/359864
Your team duplicity-team is subscribed to branch lp:duplicity.
___
Bug #1415621 status changed in Duplicity:
New => Confirmed
https://bugs.launchpad.net/duplicity/+bug/1415621
"Option to specify changed files instead of scanning filesystem"
This bug is linked to #261358.
limit incremental backup to list of changed files
> > > I'm going to merge this in soon unless there are objections.
> >
> > Yes, sounds good. I have run a few tests and have not found anything
> > problematic (just that same code lint failure you noted). Given the
> extensive
> > changes, I would like to test the new tests against the old code
> > I'm going to merge this in soon unless there are objections.
>
> Yes, sounds good. I have run a few tests and have not found anything
> problematic (just that same code lint failure you noted). Given the extensive
> changes, I would like to test the new tests against the old code and vice
>
> I'm going to merge this in soon unless there are objections.
Yes, sounds good. I have run a few tests and have not found anything
problematic (just that same code lint failure you noted). Given the extensive
changes, I would like to test the new tests against the old code and vice versa
to
> But then an alternative would be to target all 3.5+ versions (ie, py35, py36,
> and py37)
I think ideally we would be testing against the specific Python 3 version that
was the lowest we support. When we last discussed this, we were planning to do
3.4+ on the basis that that is the Python 3
> > On a branch of this, running testing/run-tests gives:
> >
> > ./run-tests
> [snip]
> > return make_sdist(report, config, session)
> > File "/usr/local/lib/python2.7/dist-
> packages/tox/package/builder/legacy.py",
> > line 30, in make_sdist
> > return config.distdir.listdir()[0]
> >
Mike,
On a branch of this, running testing/run-tests gives:
./run-tests
GLOB sdist-make: /home/[...]/mgorse-python3/setup.py
Traceback (most recent call last):
File "/usr/local/bin/tox", line 11, in
sys.exit(cmdline())
File "/usr/local/lib/python2.7/dist-packages/tox/session.py", line
Many thanks for this Mike. This looks like great work and has been on my todo
list for far too long.
I had a quick flick over the first 5k lines of the diff on here and made a
couple of comments.
==
@Ken:
I cannot actually play with the code now, so would like a bit of time to look
into
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/08-adorn-strings into lp:duplicity.
Commit message:
Adorning string literals (normally to make these unicode), in support of a
transition to Python 3.
See https://blueprints.launchpad.net/duplicity/+spec/adorn-string-literals
The proposal to merge lp:~aaron-whitehouse/duplicity/08-unadorned-strings into
lp:duplicity has been updated.
Description changed to:
As set out in the Python 3 blueprint:
https://blueprints.launchpad.net/duplicity/+spec/python3
one of the most time consuming, and least easy to automate, parts
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/08-unadorned-strings into lp:duplicity with
lp:~aaron-whitehouse/duplicity/08-pycodestyle as a prerequisite.
Commit message:
* Added new script to find unadorned strings (testing/find_unadorned_strings.py
python_file) which
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/08-pycodestyle into lp:duplicity.
Commit message:
* Tox changes to accommodate new pycodestyle version warnings. Ignored W504 for
now and marked as a TODO. Marked W503 as a permanent ignore, as it is prefered
to the (mutually
Question #284247 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/284247
Aaron Whitehouse posted a new comment:
I suspect that we would go to GitLab if we move from Launchpad.
GitLab now has all the GitHub features that matter, is open source and
(largely for the preceding
Question #668671 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/668671
Status: Open => Needs information
Aaron Whitehouse requested more information:
Hello Rebecca,
I cannot see the attachment with your log file. You can upload it here:
https://paste.ubuntu.
Question #668671 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/668671
Aaron Whitehouse requested more information:
One thing that will be very important will be the duplicity command that
you ran, so please check this is in the beginning of your log file, or
also provide
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/08-ufn-to-fsdecode into lp:duplicity.
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~aaron-whitehouse/duplicity/08-ufn-to-fsdecode/+merge/335537
* Change util.fsdecode
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/08-fix-man-verify into lp:duplicity.
Requested reviews:
duplicity-team (duplicity-team)
Related bugs:
Bug #1688659 in Duplicity: "Improve man page for verify and --compare-data"
https://bugs.launchpad.net/dupl
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/tox_pylint_fixes into lp:duplicity.
Commit message:
Changes needed to run-tests without pylint E0401(import-error) errors
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net
Many thanks Martin!
Could you please submit some tests that ensure your code keeps working as
expected? There should be an example of most things you want to test and I
would be happy to help navigate them to the extent that I can.
Just an end-to-end functional test would be a great start.
--
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/pep8_E402_fixes into lp:duplicity.
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~aaron-whitehouse/duplicity/pep8_E402_fixes/+merge/318849
Fixed PEP8 errors: E402
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/pep8_test_fixes into lp:duplicity.
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~aaron-whitehouse/duplicity/pep8_test_fixes/+merge/317733
* Fix PEP-8 testing by moving
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/08-python-futurize-stage-1 into lp:duplicity.
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~aaron-whitehouse/duplicity/08-python-futurize-stage-1/+merge/317038
* Made
For reference, while this talks about a x25 (or x8) speedup, for me there is no
material speed difference for the test suite between r 1115 and r 1116, so this
speedup must be in a scenario not exhibited in the tests.
--
https://code.launchpad.net/~mwilck/duplicity/duplicity/+merge/301268
Your
For reference, while this talks about a x20 speedup, for me there is no
material speed difference for the test suite between r 1231 and r 1232, so this
speedup must be in a scenario not exhibited in the tests.
--
https://code.launchpad.net/~mwilck/duplicity/0.7-series/+merge/301332
Your team
of this as there is some risk of changes to functional behaviour
(which is why I waited until the 0.8 series), but there is no intended change
to what it should be doing. Potentially it will fix some unexpected glob
parsing behaviour.
--
https://code.launchpad.net/~aaron-whitehouse/duplicity/08-me
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/08-merge-glob-parsers into lp:duplicity.
Commit message:
* Use a single code path for glob strings whether or not these contain special
characters/wildcards (glob_get_normal_sf) and remove glob_get_filename_sf
The proposal to merge lp:~aaron-whitehouse/duplicity/08-merge-glob-parsers into
lp:duplicity has been updated.
Commit Message changed to:
* Use a single code path for glob strings whether or not these contain special
characters/wildcards (glob_get_normal_sf) and remove glob_get_filename_sf
Question #407759 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/407759
Aaron Whitehouse posted a new comment:
Hello Bent,
Can you please test without the > /home/../list.txt (just to keep
things simple) and see if that does the same? Can you also please try to
The aim is to add new features to lp:duplicity (the 0.8-series) and only
backport important fixes to 0.7-series. Any reason this feature is proposed to
go into 0.7-series?
Duplicity 0.7-series series
---
This was the focus of development until June 2016. This branch should now be
considered
The proposal to merge lp:~aaron-whitehouse/duplicity/0-8-merge_selection_tests
into lp:duplicity has been updated.
Description changed to:
* Merge in TestExcludeIfPresent from 0.7-series, which tests the behaviour of
duplicity's --exclude-if-present option.
* Move and rename TestTrailingSlash2
The proposal to merge lp:~aaron-whitehouse/duplicity/0-8-merge_selection_tests
into lp:duplicity has been updated.
Description changed to:
* Merge in TestExcludeIfPresent from 0.7-series, which tests the behaviour of
duplicity's --exclude-if-present option
* Move and rename TestTrailingSlash2
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/0-8-merge_selection_tests into lp:duplicity.
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~aaron-whitehouse/duplicity/0-8-merge_selection_tests/+merge/314789
* Merge
Question #407759 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/407759
Aaron Whitehouse posted a new comment:
Hello Bent Jessen,
Can you please test without the > /home/../list.txt (just to keep
things simple) and see if that does the same? Can you also please
Question #402919 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/402919
Aaron Whitehouse posted a new comment:
No problem at all. Glad that you recovered most of your data.
Obviously the latest version should have restored correctly unless you
deleted the source file
Kenneth, is there anything more I can do to get this merged? Would be good to
get this fixed, so let me know if there is more I can do to help.
--
https://code.launchpad.net/~aaron-whitehouse/duplicity/Bug_1624725_files_within_folder_slash/+merge/311357
Your team duplicity-team is requested
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/Bug_1624725_files_within_folder_slash into
lp:duplicity/0.7-series.
Commit message:
Fixed Bug #1624725, so that an include glob ending in "/" now includes folder
contents (for globs with and without special
Hi Kenneth,
Apologies for any confusion. This branch is based of the current 0.7-series
branch, not lp:duplicity.
I deliberately proposed this for merging into the 0.7-series (off which it was
based):
https://code.launchpad.net/~aaron-whitehouse/duplicity/bug_1620085_exclude-if-present-locked
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/bug_1620085_exclude-if-present-locked-folder
into lp:duplicity/0.7-series.
Requested reviews:
duplicity-team (duplicity-team)
Related bugs:
Bug #1620085 in Duplicity: "--exclude-if-present gives OSError looking for
Apologies for creating work, Kenneth, but we should probably do a release once
this is merged, as it is breaking deja dup for people with the duplicity PPA.
--
https://code.launchpad.net/~aaron-whitehouse/duplicity/07-fix_deja_dup_error_on_locked_files/+merge/300981
Your team duplicity-team
Bug #1605939 status changed in Duplicity:
New => In Progress
https://bugs.launchpad.net/duplicity/+bug/1605939
"Error on locked files causing deja-dup "Backup Failed""
This bug is linked to #295948.
Failed backups: /etc/.pwd.lock
https://answers.launchpad.net/duplicity/+question/295948
--
Question #295948 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/295948
Linked to bug: #1605939
https://bugs.launchpad.net/bugs/1605939
"Error on locked files causing deja-dup "Backup Failed""
--
You received this question notification because your team
Question #295948 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/295948
Assignee: None => Aaron Whitehouse
--
You received this question notification because your team duplicity-team
is an answer contact for Duplic
Question #295948 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/295948
Aaron Whitehouse posted a new comment:
Hi DiagonalArg,
> I didn't install any versions. This is what came with Ubuntu 16.04 Gnome:
> Version: 0.7.08-0ubuntu1ppa1227~ubuntu16.04.1
I'm prett
Question #295948 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/295948
Status: Open => Needs information
Aaron Whitehouse requested more information:
In Comment #8 you said:
> Actually, I see that `--verbosity=9` was already one of the options (closer
> t
Question #295948 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/295948
Aaron Whitehouse requested more information:
Interesting, thanks.
The backup program in Ubuntu is called Deja Dup and you are correct that
it uses duplicity. I would like to narrow down whether
Question #295948 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/295948
Status: Open => Needs information
Aaron Whitehouse requested more information:
Hello,
Can you please confirm what version you are running?
duplicity --version
Why can you not exclude sin
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/remove-python26 into lp:duplicity.
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~aaron-whitehouse/duplicity/remove-python26/+merge/298983
Remove Python 2.6 support
Question #294946 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/294946
Aaron Whitehouse posted a new comment:
Hello Frank,
Can you please explain why you are wanting to create a .deb package for
Debian?
A recent duplicity (0.7.07.1-2) is apparently already in Debian
diffdir.stats.Errors += 1
> +elif s == 1:
> +# Should be included
> yield (new_path, 0)
> elif s == 2 and new_path.isdir():
> + # Is a directory that should be scanned
>
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/fix_stat_errors into lp:duplicity.
Commit message:
Only give an error about not being able to access possibly locked file if that
file is supposed to be included or scanned (i.e. not excluded). Fixes Bug
#1089131
Requested
Question #295069 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/295069
Aaron Whitehouse posted a new comment:
$ pylint --version
No config file found, using default configuration
pylint 1.5.5,
astroid 1.4.5
Python 2.7.11+ (default, Apr 17 2016, 14:00:29)
[GCC 5.3.1
Question #295069 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/295069
Status: Open => Solved
Aaron Whitehouse confirmed that the question is solved:
Sorry, simple fix -- I didn't have the required packages on my machine:
$ sudo pip install boto python-cloudfi
Question #295069 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/295069
Status: Needs information => Open
Aaron Whitehouse gave more information on the question:
Thanks Ken,
No, I'm not running Python 3:
$ python --version
Python 2.7.11+
But copying and pasting y
Aaron Whitehouse has proposed merging lp:~aaron-whitehouse/duplicity/fix_pep8
into lp:duplicity.
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~aaron-whitehouse/duplicity/fix_pep8/+merge/297124
--
Your team duplicity-team is requested
Question #295069 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/295069
Aaron Whitehouse posted a new comment:
PEP8 issue patch is here:
http://paste.ubuntu.com/17129345/
Annoyingly, Bazaar has stopped working properly for me since 16.04
upgrade and keeps hanging
New question #295069 on Duplicity:
https://answers.launchpad.net/duplicity/+question/295069
On the latest revision for me (rev 1220), I'm getting failed tests on a clean
branch. The first is a pep8 error about a bracket that I've quickly fixed, but
the other is a pylint error about not being
Question #284247 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/284247
Aaron Whitehouse posted a new comment:
I think that I mentioned this somewhere else, but my main issue with
GitHub is that it is not open source.
GitLab is an open core equivalent if the aim is to go
Question #294800 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/294800
Aaron Whitehouse proposed the following answer:
> 2. Is there any way to make duplicity do some sort of signature/meta data
> verification only without pulling
> down the whole archive?
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/improve_present_get_sf_man_page into
lp:duplicity.
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~aaron-whitehouse/duplicity/improve_present_get_sf_man_page/+merge
Question #284247 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/284247
Aaron Whitehouse proposed the following answer:
PPA regen is likely to be the tough part. See, for example:
https://answers.launchpad.net/launchpad/+question/250434
Bazaar is comparatively easy
Looks like we should move away from shell=True ASAP.
https://docs.python.org/2/library/subprocess.html#frequently-used-arguments
"Warning
Executing shell commands that incorporate unsanitized input from an untrusted
source makes a program vulnerable to shell injection, a serious security flaw
Question #271470 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/271470
Status: Open => Needs information
Aaron Whitehouse requested more information:
Hi Robert,
Does a simple duplicity command work? For example:
cd /tmp
mkdir dup_test
cd dup_test
mkdir src
mk
Good work, thanks Wojciech. In addition to the debug messages, which are a good
idea, I like how you have rearranged this section.
--
https://code.launchpad.net/~w.baranowski/duplicity/selection_debug/+merge/268791
Your team duplicity-team is requested to review the proposed merge of
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/launchpad_tox_profile into lp:duplicity.
Commit message:
Add tox testing profile that mimics the packages installed on the Launchpad
build server, to reduce the likelihood of tests passing our test suite, but
failing
by the Python version or the obsolete build server package versions.
--
https://code.launchpad.net/~aaron-whitehouse/duplicity/launchpad_tox_profile/+merge/266859
Your team duplicity-team is requested to review the proposed merge of
lp:~aaron-whitehouse/duplicity/launchpad_tox_profile
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/disable_code_tests_for_lpbuildd into
lp:duplicity.
Commit message:
Set RUN_CODE_TESTS to 0 for lpbuildd tox profile, reflecting its value on the
Launchpad build server (and therefore skipping PEP8, 2to3 and pylint). More
Diff comments:
=== modified file 'duplicity/selection.py'
--- duplicity/selection.py2015-07-31 08:22:31 +
+++ duplicity/selection.py2015-08-03 18:32:04 +
@@ -151,16 +151,7 @@
for filename in robust.listpath(path):
new_path =
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/fix_patch_error into lp:duplicity.
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~aaron-whitehouse/duplicity/fix_patch_error/+merge/266676
Change use of mock.patch
Question #256613 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/256613
Aaron Whitehouse posted a new comment:
As I've now detailed in README-REPO (and as of
http://bazaar.launchpad.net/~duplicity-team/duplicity/0.7-series/revision/1113
):
You can run specific tests
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/fix_2to3_issues into lp:duplicity.
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~aaron-whitehouse/duplicity/fix_2to3_issues/+merge/266649
Fixed 2to3 issues. Updated
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/improve_tox_and_python2-6_testing into
lp:duplicity.
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~aaron-whitehouse/duplicity/improve_tox_and_python2-6_testing/+merge
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/improve_tox_and_python2-6_testing into
lp:duplicity.
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~aaron-whitehouse/duplicity/improve_tox_and_python2-6_testing/+merge
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/trailing_slash_match_dirs into lp:duplicity.
Requested reviews:
duplicity-team (duplicity-team)
Related bugs:
Bug #1479545 in Duplicity: Globbing patterns with trailing slashes should
only match directories
https
Aaron Whitehouse has proposed merging
lp:~aaron-whitehouse/duplicity/reenable_tests into lp:duplicity.
Requested reviews:
duplicity-team (duplicity-team)
For more details, see:
https://code.launchpad.net/~aaron-whitehouse/duplicity/reenable_tests/+merge/266210
Re-enable unit.test_selection
Note that this fixes all expectedFailures from the selection unit and
functional tests.
--
https://code.launchpad.net/~aaron-whitehouse/duplicity/bug_884371/+merge/266162
Your team duplicity-team is requested to review the proposed merge of
lp:~aaron-whitehouse/duplicity/bug_884371
1 - 100 of 131 matches
Mail list logo
