-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 27 Feb 2003 15:25:41 -0500
Source: gcl
Binary: gcl-doc gcl
Architecture: source all i386
Version: 2.5.0.cvs20020625-77
Distribution: unstable
Urgency: low
Maintainer: Camm Maguire <[EMAIL PROTECTED]>
Changed-By: Camm Maguire <[EMAIL PROTECTED]>
Description: 
 gcl        - GNU Common Lisp compiler
 gcl-doc    - Documentation for GNU Common Lisp
Changes: 
 gcl (2.5.0.cvs20020625-77) unstable; urgency=low
 .
   * Lintian cleanups
   * Don't strip libansi_gcl.a, need .data at end of .o, as with libgcl.a
   * Take newlines out of doc string for init-cmp-anon
   * Cleanup gcc-3.2 compiler warning
   * 64 bit STREF fixes
   * pcl and clcs need to have C rebuilt afresh, as 64 bit machines write
     different STREF offsets into the C files
   * Rework Debian package build a bit
   * README.Debian explaining the toggling of the ANSI image
   * Typo in debian/rules
   * Remove debian/gcl.conffiles
Files: 
 dd4b359dca798de1a549b804b665ba9f 735 interpreters optional 
gcl_2.5.0.cvs20020625-77.dsc
 d6113b6cdf7f69e10f1c445b9b728059 22915118 interpreters optional 
gcl_2.5.0.cvs20020625-77.tar.gz
 575ddc47b47d9baab70e00b85608782e 3138872 doc optional 
gcl-doc_2.5.0.cvs20020625-77_all.deb
 120f817e2a931291f22a574c4cc562c9 5143118 interpreters optional 
gcl_2.5.0.cvs20020625-77_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+XnneczG1wFfwRdwRAjtrAKC2Gm0Z6T5grTfMDxjhxAljs9b35QCgik3J
bN2WWRiofbgXG/dkYsyZFco=
=c7KY
-----END PGP SIGNATURE-----


Accepted:
gcl-doc_2.5.0.cvs20020625-77_all.deb
  to pool/main/g/gcl/gcl-doc_2.5.0.cvs20020625-77_all.deb
gcl_2.5.0.cvs20020625-77.dsc
  to pool/main/g/gcl/gcl_2.5.0.cvs20020625-77.dsc
gcl_2.5.0.cvs20020625-77.tar.gz
  to pool/main/g/gcl/gcl_2.5.0.cvs20020625-77.tar.gz
gcl_2.5.0.cvs20020625-77_i386.deb
  to pool/main/g/gcl/gcl_2.5.0.cvs20020625-77_i386.deb


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to