Hi Antoine!
>It would be great if borg would be backported to jessie (and, why not, >wheezy!). lets go with little steps :) >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: sure! >* setuptools-scm: backported by Gianfranco already, but out of date > (1.8 backported vs 1.10 in stretch) yes, indeed I tried today (while discussing on 809136) to backport 1.10, and it is brutally failing to build in jessie http://debomatic-amd64.debian.net/distribution#jessie-backports/setuptools-scm/1.10.1-1~bpo8+1/buildlog I committed the changes on the git (no change bpo), but I can't obviously upload. so for now 1.10 is a no-go >* python3-msgpack: backport missing. zigo contacted, said he would> backport >himself. i'll open a bug report about this on msgpack to > track that thanks! (could you please block this one by the newly created one? so we don't loose the link!) >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. I can do the backport, no problems here :) But if you want to take over the package, or you have patches/suggestions, as usual packages in collab-maint are by definition open to everybody wants to contribute. So, I won't object on uploads/backports/patches/bugs/whatever :) thanks for opening this bug! Gianfranco
