Your message dated Tue, 19 Jan 2016 14:44:04 +0100
with message-id <[email protected]>
and subject line Re: Bug#810534: borgbackup backport to jessie
has caused the Debian Bug report #810534,
regarding borgbackup backport to jessie
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.)
--
810534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810534
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: borgbackup
Severity: wishlist
It would be great if borg would be backported to jessie (and, why not,
wheezy!).
It would also help in the long run if people have compatibility
problems such as the ones described in #809136: by having newer
versions available in stable, we can upgrade a fleet of debian
machines all at once without adverse effects (same as what's happening
with rdiff-backup, unison or syncthing, as described there).
from what i understand, there are two dependencies that need to be
backported:
* setuptools-scm: backported by Gianfranco already, but out of date
(1.8 backported vs 1.10 in stretch)
* python3-msgpack: backport missing. zigo contacted, said he would
backport himself. i'll open a bug report about this on msgpack to
track that
this is not a "whiny whiny i want my borg" bug report. it's a "let's
work together and see what's missing" bug report. coordination and
all. i would be happy to do the backport myself, i just don't want to
step on anyones toes or duplicate work.
thanks!
-- System Information:
Debian Release: 8.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'stable'), (500, 'oldstable'), (1, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.2.0-0.bpo.1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi,
>> Right now borgbackup-doc built this way has privacy breach
>> (loads javascripts from external url when browsing local doc),
>> which does not happen when building it on sid.
>>
>> Any thoughts?
I don't care :)
>
> I am not sure it's an issue that warrants blocking the backport -
> it's a bug in the toolchain, not specific to borg, no?
I think so.
anyway, uploading shortly since this morning msgpack has been accepted.
cheers,
G.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJWnj2eAAoJEPNPCXROn13ZUZgP/32GKad4MbvmiQ3sGQFjNf/I
n9Iywd5RJZ+OHxxSbv24aQf7aJP2TEQrUtJIJy6TF+zr7X3LsIxk6lEUMykodesW
GZwHzlXskEMIMd103MHlo51huHn0cG76mOLqsXOL9CjVaLO14ZIceNOBdGJ/84uk
F5jU2rVrWms97hJ3xWXynDUnfZavb7PPttAWe9RLW2oir/JJT3NUmCnf7GhuDCnK
uCAYahZg8twpBfIawWg9ocCkcbr6epihk1c8GtSaELzPTdQgrzmakgV5g36LVBZu
11Il5OlmJ/a0ijgOHZObmvSRgY941IQLtOiyTLsSz228Cpj4J/F77pvnESqEmcpM
rcKL4UYPoRmduTVM20xUE/brVdMAHKT3MCmFVsxLqjdifb4Kk0Urk71oJLfXqswL
0IFXIo6UjO/S0seE7wsZxfiASW7VFAYYPg07uUHfCxwHvK2VBMbFOHvm7gC8SwWD
K0DWp5XLa0Sr9YJCjw8yoSbjRPH6szmarrV2mNWPyyKWLy7MP7w4wzGobeVnAMoi
HYcpWUl4Loty8z5YeERZ9SsnlTW2/nus0ZLNA1GmVMJ/9Y3HfYdl4t3RTZtPgK5b
tPIa/RrSWjiDdkL0E5jBFn8g6JlS0hLkVs1aZXmzcEA53KJeAzUenoJOUSct0NNH
Cji500GiXbSmTVxHoMkd
=3nev
-----END PGP SIGNATURE-----
--- End Message ---
