Accepted:
cl-swank_20080223.dfsg-1_all.deb
to pool/main/s/slime/cl-swank_20080223.dfsg-1_all.deb
slime_20080223.dfsg-1.diff.gz
to pool/main/s/slime/slime_20080223.dfsg-1.diff.gz
slime_20080223.dfsg-1.dsc
to pool/main/s/slime/slime_20080223.dfsg-1.dsc
slime_20080223.dfsg-1_all.deb
to pool/m
Your message dated Sat, 02 May 2009 15:49:39 +
with message-id
and subject line Bug#517205: fixed in slime 1:20080223.dfsg-1
has caused the Debian Bug report #517205,
regarding cl-swank: Possible DFSG violation in xref.lisp
to be marked as done.
This means that you claim that the problem has
/parenscript_20090216-1_amd64.changes isn't signed with PGP/GnuPG
Removing /parenscript_20090216-1_amd64.changes, but keeping its associated
files for now.
Greetings,
Your Debian queue daemon
___
pkg-common-lisp-devel mailing list
pkg-common-l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Torsten,
I had hoped not to see an email like yours.
The issue is that cmucl with this new release will compile to two
different fasl formats: for x86 or for sse2.
I was going to fix the scripts to handle this correctly but then I
dawned on me
Probably you are the uploader of the following file(s) in
the Debian upload queue directory:
parenscript_20090216-1.diff.gz
parenscript_20090216-1.dsc
parenscript_20090216.orig.tar.gz
This looks like an upload, but a .changes file is missing, so the job
cannot be processed.
If no .changes fi
