Uploading 0.0.19 to Debian at this time is surely a bad idea.  Should
we raise the severity of this bug to serious, since it is FTBFS, and
do another upload of 0.0.18 plus the minimal patch that solve the bug?
Or is it not worth another upload?  Not supporting amd64 seems like an
unfortunate thing, but maybe it is too late to get into etch.  I don't
really know the best practice for this.

FWIW, the minimal patch is the one below.  I don't really know how to
apply it with cdbs, but I recall seeing other packages do it, so I
could easily take care of that tomorrow.

Thanks!
/Simon

Index: asn1.c
===================================================================
RCS file: /home/jas/self/public-cvs/gss/lib/asn1.c,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -p -r1.21 -r1.22
--- asn1.c      6 Nov 2006 21:25:47 -0000       1.21
+++ asn1.c      8 Jan 2007 23:19:52 -0000       1.22
@@ -175,7 +175,7 @@ _gss_decapsulate_token (const char *in, 
                        char **oid, size_t * oidlen,
                        char **out, size_t * outlen)
 {
-  int i;
+  size_t i;
   size_t asn1lenlen;
 
   if (inlen-- == 0)



_______________________________________________
Help-gss mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-gss

Reply via email to