Hi Eric, Thanks for your reply.
Not all package maintainers are as understanding as you are when it comes to bug severity, it's a subject that is easy to get into an argument about! 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. 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. Best regards, François. On 19 April 2015 04:25:35 BST, Eric Evans <eev...@sym-link.com> wrote: > >severity 782251 important >tag 782251 -patch >thanks > >[ Francois Guerraz ] >> Package: python-boto >> Version: 2.34.0-2 >> Severity: normal >> Tags: patch upstream >> >> Using boto as a backend for duplicity with multipart upload in the >Frankfurt region result in crash: >> >> TypeError: argument of type 'int' is not iterable >> >> I believe this bug was reported and fixed upstream: >https://github.com/boto/boto/issues/2731 > >Hi Francois, > >Thanks for the report; I try to keep an out for upstream bug reports >that >effect the package, but I clearly missed this one. > >For posterity sake, the canonical upstream bug report seems to be: >https://github.com/boto/boto/pull/2744. > >I think this more serious than severity 'normal', the question is: is >it >'important', or 'serious' (serious would make it release-critical)? >It's >not entirely clear to me what it takes to exercise this code (the >assignment >of the integer in boto/connection.py), but I assume it's uncommon >enough >that 'serious' isn't warranted. Let me know if you disagree. > >In this meantime, I'll put together a new upstream release for upload >to >experimental, at least. > >Regards, > >-- >Eric Evans >eev...@sym-link.com -- Sent from Kaiten Mail. Please excuse my brevity.
