[ François Guerraz ] [ ... ]
> I think it should be fixed in Jessie eventually and it seems common enough a > use case that some people will hit the bug on day one. I agree, the question is whether it can wait for a future point release, or whether I should approach the release team for an unblock with a little under a week left before release. Note that, even if it's the former, I think this warrants getting a fixed package into backports as quickly as possible. Given the volatile nature of boto (and AWS APIs in general), I suspect quite a lot of people go there anyway. > Now, is it worth delaying the release of Jessie for that? I lean toward 'no' > as there are two possible workarounds (disabling multipart and installing it > via pip). But it still severely affects the usability of the package. I wasn't able to replicate this with duplicity (though my backups are using a north american region). Can you update this report with the exact steps to reproduce, and for posterity sake, what you do to work around it? Thanks, -- Eric Evans eev...@sym-link.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
