There you go, here's the limits of sponsoring showing up. Roberto told me that his main development machine has issues so he can't upload. I asked in #debian-mentors, someone told me he did upload, but it fact, he did not (as the package is not showing up in the archive after 12 hours). Here's the last message from Roberto:
"I am having problems with main workstation computer (which has my entire Debian development environment on it). I am not sure when I will get a chance to fix it, so it may be some days before I get to sponsor your dkiproxy package." Now, this clearly shows why being a DD would help me a lot for my packaging work, and how sponsoring is really creating issues. I have the package ready and tested, but yet, it is stuck in our private repository, while many are needing it... :( It also shows that I was not so wrong to tell that having many uploads in a life cycle is really time demanding when you need to have your package sponsored. If anyone reads this, please consider sponsoring: http://ftparchive.gplhost.com/debian/pool/lenny/main/d/dkimproxy/dkimproxy_1.2-1.dsc and also consider being my AM. Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
