Hello Andrew,the bug is "fixed" in testing, so closing it is the appropriate
action.
Buster is getting released soon, I don't plan to do a stretch p-u, feel free to
request one
with release team, the debdiff is trivial (adding fuse runtime dependency to
borgbackup debian/control file)
G.
Il sabato 5 gennaio 2019, 16:15:16 CET, Andrew Hunter
<andrew@hunter.camera> ha scritto:
Hi Gianfranco,
All of those versions of the package have a newer version of borg in addition
to listing the fuse dependency.
I don't think this bug report should be closed as functionality in the current
stable version is broken due to a missing dependency in the packaging. This
strikes me as a suitable candidate for a proposed-update to stable.
Sincerely,Andrew
On Sat, Jan 5, 2019 at 6:06 AM Debian Bug Tracking System
<ow...@bugs.debian.org> wrote:
This is an automatic notification regarding your Bug report
which was filed against the borgbackup package:
#917358: borgbackup: Borg mount fails as fuse is not listed as dependancy in
stable
It has been closed by Gianfranco Costamagna <locutusofb...@debian.org>.
Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Gianfranco Costamagna
<locutusofb...@debian.org> by
replying to this email.
--
917358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917358
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---------- Forwarded message ----------
From: Gianfranco Costamagna <locutusofb...@debian.org>
To: Debian Bug Tracking System <sub...@bugs.debian.org>, Andrew Hunter
<andrew@hunter.camera>, "917358-d...@bugs.debian.org"
<917358-d...@bugs.debian.org>
Cc:
Bcc:
Date: Sat, 5 Jan 2019 11:02:50 +0000 (UTC)
Subject: Re: Bug#917358: borgbackup: Borg mount fails as fuse is not listed as
dependancy in stable
Hello, can you please confirm the bug is fixed in stretch-backports, sid and
testing?
thanks!
G.
Il mercoledì 26 dicembre 2018, 17:21:14 CET, Andrew Hunter
<andrew@hunter.camera> ha scritto:
Package: borgbackup
Version: 1.0.9-1
Severity: normal
Dear Maintainer,
Please add fuse as a dependancy to the 1.0.9 version of borg in stable. Borg
mount is a built in command that requires the fuse package. Fuse is listed a
dependancy in both testing and stretch-backports.
* What led up to the situation?
$ borg mount <repo> failed
* What exactly did you do (or not do) that was effective (or
ineffective)?
# apt install fuse
* What was the outcome of this action?
$ borg mount suceeds
* What outcome did you expect instead?
-- System Information:
Debian Release: 9.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages borgbackup depends on:
ii libacl1 2.2.52-3+b1
ii libc6 2.24-11+deb9u3
ii liblz4-1 0.0~r131-2+b1
ii libssl1.1 1.1.0j-1~deb9u1
ii python3 3.5.3-1
ii python3-llfuse 1.2+dfsg-1
ii python3-msgpack 0.4.8-1
ii python3-pkg-resources 33.1.1-1
borgbackup recommends no packages.
Versions of packages borgbackup suggests:
pn borgbackup-doc <none>
-- no debconf information
---------- Forwarded message ----------
From: Andrew Hunter <andrew@hunter.camera>
To: Debian Bug Tracking System <sub...@bugs.debian.org>
Cc:
Bcc:
Date: Wed, 26 Dec 2018 11:17:14 -0500
Subject: borgbackup: Borg mount fails as fuse is not listed as dependancy in
stable
Package: borgbackup
Version: 1.0.9-1
Severity: normal
Dear Maintainer,
Please add fuse as a dependancy to the 1.0.9 version of borg in stable. Borg
mount is a built in command that requires the fuse package. Fuse is listed a
dependancy in both testing and stretch-backports.
* What led up to the situation?
$ borg mount <repo> failed
* What exactly did you do (or not do) that was effective (or
ineffective)?
# apt install fuse
* What was the outcome of this action?
$ borg mount suceeds
* What outcome did you expect instead?
-- System Information:
Debian Release: 9.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages borgbackup depends on:
ii libacl1 2.2.52-3+b1
ii libc6 2.24-11+deb9u3
ii liblz4-1 0.0~r131-2+b1
ii libssl1.1 1.1.0j-1~deb9u1
ii python3 3.5.3-1
ii python3-llfuse 1.2+dfsg-1
ii python3-msgpack 0.4.8-1
ii python3-pkg-resources 33.1.1-1
borgbackup recommends no packages.
Versions of packages borgbackup suggests:
pn borgbackup-doc <none>
-- no debconf information
--
--
+1 416 567 9514
andrew@hunter.camera
