Hi.
I'm the "maintainer". I'll readily admit I've failed miserably to
track this issue appropriately.
Part of it is due to some rather unfortunate e-mail filtering, but
that's certainly not all. (Debian bug mail ended in a folder I didn't
subscribe to, but I noticed the issue when it was first raised on the
libcloud list)
I've had no time to drive this issue personally, but idly following
the upstream libcloud mailing list (where Pietro has done a great job
trying to get things moving), there doesn't seem to be any resolution.
The final e-mail in the thread (AFAIK) being this:
http://mail-archives.apache.org/mod_mbox/incubator-libcloud/201011.mbox/%3caanlkti=x9nfbv7igzcakwuqoumoe-j1tk6duw3y6a...@mail.gmail.com%3e
I was sort of hoping it would be resolved soon so that we could get
the fix in. I didn't see much point in getting 0.4 into squeeze since
this issue would remain. (Was that wrong?)
I agree the issue is important. I'm not sure I personally think it
warrants removal, but if that's how things are done, that's of course
fine.
On a more general note, I'm going to thoroughly reconsider my
maintaining this package. I don't really use it anymore, and if I did,
it wouldn't be on Debian, so if anyone else wants to take it over,
that'd be great. If not, it'll be on a best-effort basis, were "best"
probably isn't going to be very awesome :(
--
Soren Hansen
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/aanlkti=asj+mrf2--rj5k2sdb_dh6qbmzapecx8k8...@mail.gmail.com
