README.rst | 2 0 + 2 - 0 !
1 file changed, 2 deletions(-)

 remove online build services' badges

Lintian Tag: privacy-breach-generic

Reading the html docs would automatically open connections to their
servers in order to show the build status. While this may be of interest
when loading the github page, it's not relevant for the end-user reading
the docs.

Also, remove the link to the online docs of the 'stable' version, since
they could be out of sync with the Debian version.

README.rst | 6 6 + 0 - 0 !
1 file changed, 6 insertions(+)

 readme.rst: replace img src with text link

Lintian Tag: privacy-breach-generic

Replaced the image linking to the asciinema.org screencast with a
text-based link.

docs/installation.rst | 10 2 + 8 - 0 !
1 file changed, 2 insertions(+), 8 deletions(-)

---

docs/conf.py | 2 2 + 0 - 0 !
1 file changed, 2 insertions(+)

---

scripts/shell_completions/bash/borg | 6 3 + 3 - 0 !
1 file changed, 3 insertions(+), 3 deletions(-)

---

MANIFEST.in | 4 4 + 0 - 0 !
1 file changed, 4 insertions(+)

 [patch] packaging: explicit add data files to the manifest

We've started seeing some failures to build in Debian and Ubuntu that
can be traced to those files missing from the manifest when we're
calling setup.py install.

Now, this started failing fairly recently, so I'm guessing it's actually
a change of behaviour in the SCM plugin and/or setuptools. It makes
sense though, since we're packaging from the tarball, which isn't in the
Git context needed to actually include those data files.

Signed-off-by: Simon Chopin <simon.chopin@canonical.com>

src/borg/testsuite/shell_completions_test.py | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 adjous paths for .pybuild directory, to fix a test failure

src/borg/testsuite/shell_completions_test.py | 9 8 + 1 - 0 !
1 file changed, 8 insertions(+), 1 deletion(-)

 tests: tweak some unit tests when using the installed testsuite

In autopkgtests we want to test the installed code, but a couple of unit
tests assume (not unreasonably) that they're run from the source repo.

We introduce a new environment variable that allows us to tweak a few
tests, either disabling them out-right or changing some of the paths to
point to the installed files.

This is *very* Debian-specific, no need to push upstream.

Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/borgbackup2/+bug/2118916
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110195