Your message dated Sat, 16 Jan 2016 08:11:54 +0100
with message-id <5699ed3a.1040...@danny-edel.de>
and subject line Upload done
has caused the Debian Bug report #809136,
regarding Block borgbackup migration to stable for now
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 ow...@bugs.debian.org
immediately.)
--
809136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: borgbackup
Version: 0.29.0-1
Severity: important
Hi.
borgbackup broke API compatibility between 0.28 and 0.29 versions. You
need to have both server and client on the same version for borgbackup
to work.
This has been documented by upstream, telling users that they need to
have both server and client on the same version. This has,
unfortunately, been ignored by Debian when packaging the software.
The workaround suggested by upstream seriously is to have all
incompatible versions of the server installed and having the client
choose which server to use.
So debian would need to have a borgbackup-0.28 package and a
borgbackup-0.29 package and all incompatible API versions
simultaneously since it is extremely unlikely that Debian unstable,
testing and stable will have compatible versions of borgbackup and
that one surely will want to back up unstable systems to a stable
server or vice versa.
With uncooperative (and not even understanding the issue) upstream
like that, providing a Debian package of borgbackup will be an extreme
challenge.
I suggest the following addition to the package description in case
this issue is not solveable:
"
Please note that the server and the client should be on the same
version of borgbackup. Using different versions of borgbackup on
client and server might result in 'incompatible API version' error
messages and a non-working backup.
"
Greetings
Marc
--- End Message ---
--- Begin Message ---
Version: 0.29.0-3
The changes have been uploaded to the Debian archive, and the changelog
did contain a Closes: stance[1].
Since the bug didn't close, I'm doing it manually this way.
Antoine: This should ready the way for the backport, if there's anything
else I can do or help with, please let me know.
Cheers!
- Danny
[1]: https://tracker.debian.org/news/740683
--- End Message ---
