Hi,

Any news on this ? I've upgraded to jessie and scripts using s3cmd broke because
of this bug. It renders the package unusable to me (and all using dots in the
buckets name).

As a workaround, just in case, I've used s3cmd from a python virtual env using
the last release. Probably the package from testing fixes it too.


If I can help with testing or something, please let me know





Thanks a lot,
Rodrigo


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to