Package: borgbackup
Version: 1.1.4-2
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
qgis 2.18.16 has been installed and used on the system for a considerable 
period. borgbackup was installed from the stretch repository and functioned 
correctly without any problems.
To get the latest version of borgbackup I have installed the sid package. This 
caused all installed versions of qgis to be uninstalled from the system and 
they could not be reinstalled.
I have been able to reinstall both borgbackup and qgis on a new installation of 
Debian 3, using the borgbackup package from testing instead.
   * What exactly did you do (or not do) that was effective (or
Installed borgbackup from sid repository
   * What was the outcome of this action?
qgis 2.18 and 2.99 packages were uninstalled by apt in the course of installing 
borg 1.1.4
   * What outcome did you expect instead?
the Qgis packages should not have been removed

*** End of the template - remove these template lines ***

-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages borgbackup depends on:
ii  fuse                   2.9.7-1
ii  libacl1                2.2.52-3+b1
ii  libb2-1                0.97+git20171226-2
ii  libc6                  2.26-6
ii  liblz4-1               0.0~r131-2+b1
ii  libssl1.1              1.1.0f-3+deb9u1
ii  libzstd1               1.3.3+dfsg-1
ii  python3                3.6.4-1
ii  python3-llfuse         1.3.2+dfsg-2
ii  python3-msgpack        0.4.8-1+b1
ii  python3-pkg-resources  33.1.1-1

borgbackup recommends no packages.

Versions of packages borgbackup suggests:
pn  borgbackup-doc  <none>

-- no debconf information

Reply via email to