Bug#702933: unblock: duplicity/0.6.20-3
Control: tag -1 + moreinfo
Hi Alexander,
(disclaimer: I'm not part of the release team, just trying to help
a bit with the pile of unblock requests.)
Alexander Zangerl wrote (13 Mar 2013 03:05:26 GMT) :
> dear release team, duplicity's version in testing (0.6.18.-3)
> suffers from bug #702563, which makes the sftp/ssh storage backend
> not work with non-standard ssh ports.
Thanks for trying to fix this for Wheezy, much appreciated.
> this problem is solved in the version in unstable (0.6.20-3),
Any particular reason why #702563 is not marked as such, then?
Also, it would be good to have a confirmation by the bug reporter
(Cc'd) that 0.6.20-3 indeed fixes the problem for them. Kwadronaut,
please follow-up on #702563 about this, and not on the unblock request
(#702933).
> along with a number of other issues
It may be just me, but it would be good to have bug numbers with
severity for these, not just an isolated (important) example.
> (e.g. #682837 which i personally consider of higher impact/priority
> than the above bug).
Would debian/patches/02unicode.dpatch apply to the duplicity version
currently in Wheezy? If not, how hard would it be to extract the
minimal upstream changes needed by this workaround?
> i didn't debianize 0.6.19 at all, and the differences between .18
> and .20 are all coming from upstream (no added dependencies) but
> they are unfortunately not exactly minimal.
Yes, unfortunately:
55 files changed, 7310 insertions(+), 3904 deletions(-)
... is *very* unlikely to be reviewed and unblocked by the release
team at this point.
So, I recommend you investigate how targeted fixes for the most
serious bugs could go into Wheezy through t-p-u. Too bad new upstream
releases were uploaded to sid, as the proposed t-p-u changes won't see
as much testing as usual :(
Regards,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
Reply to: