On Tue, Apr 7, 2009 at 11:48, Alexandre Fayolle <alexandre.fayo...@logilab.fr> wrote: > Le Tuesday 07 April 2009 10:26:48 Archive Administrator, vous avez écrit : >> GnuPG signature check failed on constraint_0.4.0-3_i386.changes >> gpg: Signature made Tue Apr 7 08:22:12 2009 UTC using RSA key ID A827CEDE >> gpg: WARNING: signing subkey A827CEDE is not cross-certified >> gpg: please see http://www.gnupg.org/faq/subkey-cross-certify.html for more >> information gpg: Can't check signature: general error >> (Exit status 2) >> /constraint_0.4.0-3_i386.changes has bad PGP/GnuPG signature! >> Removing /constraint_0.4.0-3_i386.changes, but keeping its associated files >> for now. > > Any help on this ? I seem to be affected by http://bugs.debian.org/522288 > > If someone from the team could upload constraint in the meantime, I'd be > grateful : this version fixes an important bug caused by the moving of > python-logilab-common from python-central to python-support.
Uploading now. Anyhow, there are a couple of simple lintian warning to fix, but the thing scaring me the most is the package name choosen: at least the binary package should be python-logilab-constraint, since "import constraint" fails, because it's in logilab namespace. The source package would be welcome to follow the current naming schema for logilab* stuff in debian. Anyhow, I upload, since that was your decision, and with no gpg error, it would have already happened, but please consider it carefully. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi _______________________________________________ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/python-modules-team
