Hi, Yann Leboulanger wrote (12 Dec 2012 11:50:25 GMT) : > Ok then we wait for an answer from secure-testing-team?
I think so. > I don't think I need to do somthing, do I? I think you don't, now that I added them to the loop myself. Which means we can now get back to why this update of an embedded library should be unblocked. Why is this update needed? Is the version embedded in testing / in unstable (based on) the same as the one packaged in python-gnupg? Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
