Your message dated Fri, 26 Jan 2018 12:57:08 +0100
with message-id <[email protected]>
and subject line Re: borgbackup: borgfs doesn't work due to broken handling of
include/exclude patterns
has caused the Debian Bug report #887522,
regarding borgbackup: borgfs doesn't work due to broken handling of
include/exclude patterns
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
887522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887522
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: borgbackup
Version: 1.1.4-1~bpo9+1
Severity: important
Hi,
borgfs is completely unusable since 1.1.4-1~bpo9+1 since it throws an exception
during invocation, no matter the parameters.
For details, please refer to the upstream github issue I've created at [1].
Given the severity and impact, this bug report is meant to track a possible fix
by a patch in debian/ instead of waiting for a new testing release to migrate
to bpo.
Thanks
Daniel
[1] https://github.com/borgbackup/borg/issues/3551
-- System Information:
Debian Release: 9.3
APT prefers stable-updates
APT policy: (990, 'stable-updates'), (990, 'proposed-updates'), (990,
'stable'), (500, 'oldstable-updates'), (500, 'oldstable-proposed-updates'),
(500, 'testing'), (500, 'oldstable'), (98, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.14.0-0.bpo.2-amd64 (SMP w/8 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/bash
Init: sysvinit (via /sbin/init)
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~bpo9+1
ii libc6 2.24-11+deb9u2
ii liblz4-1 0.0~r131-2+b1
ii libssl1.1 1.1.0f-3+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:
ii borgbackup-doc 1.1.4-1~bpo9+1
--- End Message ---
--- Begin Message ---
On Wed, 17 Jan 2018 18:18:19 +0100 Daniel Reichelt <[email protected]>
wrote:
> Package: borgbackup
> Version: 1.1.4-1~bpo9+1
> Severity: important
>
> Hi,
>
> borgfs is completely unusable since 1.1.4-1~bpo9+1 since it throws an
> exception
> during invocation, no matter the parameters.
>
> For details, please refer to the upstream github issue I've created at [1].
>
> Given the severity and impact, this bug report is meant to track a possible
> fix
> by a patch in debian/ instead of waiting for a new testing release to migrate
> to bpo.
>
>
Sorry, there is still too much upstream activity on that issue, I'm closing
right now,
the fix will come with 1.1.5
G.
signature.asc
Description: OpenPGP digital signature
--- End Message ---
