control: severity -1 serious I fully agree with you :) Cheers G. Sent from Yahoo Mail on Android On Tue, 29 Dec, 2015 at 13:15, Danny Edel<deb...@danny-edel.de> wrote: On 12/27/2015 02:42 PM, Marc Haber wrote: > 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.
Hello Marc, I doubt that it would work just that easy, since these packages would (without deviating from upstream) not be co-installable because of path conflicts, so in the plausible use case that you want to share a stable server with an unstable and a stable client, you'd have to keep deleting and re-installing borgbackup between the version in stable and the backport of the newer version. That does not sound like a viable solution to me. (Manually installing the other versions into a non-dpkg-managed directory does not count either) I do agree that this is a serious problem, and if Gianfranco (cc'd) does not have any objections, we should define this bug to a severity level that prevents a migration to Debian stable until upstream decides on a stable API and file format version, which probably won't come before the 1.0 release. I personally don't see a problem with having it in debian "unstable" until then (since its users will upgrade regularly), but we should maybe stop further migrations or even ask for a removal from testing until this is resolved. Gianfranco, what do you think about the situation? Cheers, - Danny
