Possible problems in your Debian packages
=== cedilla:
= Not in testing for 17 days.
If things don't change, it won't be part of lenny!
See <http://release.debian.org/migration/testing.pl?package=cedilla>
=== cl-asdf:
= No migration to testing for 128 days.
See <http://release.debian.org/migration/testing.pl?package=cl-asdf>
=== cl-irc:
= No migration to testing for 273 days.
See <http://release.debian.org/migration/testing.pl?package=cl-irc>
=== cl-usocket:
= Not in testing for 92 days.
If things don't change, it won't be part of lenny!
See <http://release.debian.org/migration/testing.pl?package=cl-usocket>
=== clisp:
= 4 bug(s) that should be fixed for the next Debian release:
- #450452 <http://bugs.debian.org/450452>
does install a dangling symlink as clisp-link -> ../lib/clisp-*/clisp-link
- #467585 <http://bugs.debian.org/467585>
xindy: FTBFS: ordrulei.c:24: error: 'clisp_dirent_off_t' undeclared (first use in this function)
- #474810 <http://bugs.debian.org/474810>
clisp: FTBFS: floatparam.h:18:2: error: #error "Unknown rounding mode for type double!"
- #478000 <http://bugs.debian.org/478000>
clisp: FTBFS on sparc: ALLOCATE-METAOBJECT-INSTANCE: length 0 should be of type (INTEGER (0) (0000))
= Missing build(s) on s390,arm
This might need manual action from your side.
See http://buildd.debian.org/pkg.cgi?pkg=clisp
= Not in testing for 17 days.
If things don't change, it won't be part of lenny!
See <http://release.debian.org/migration/testing.pl?package=clisp>
=== cmucl:
= 1 bug(s) that should be fixed for the next Debian release:
- #483331 <http://bugs.debian.org/483331>
cmucl: FTBFS: Error in function UNIX::SIGSEGV-HANDLER: Segmentation Violation at #x10044FF0.
= Not in testing for 3 days.
If things don't change, it won't be part of lenny!
See <http://release.debian.org/migration/testing.pl?package=cmucl>
=== common-lisp-controller:
= No migration to testing for 125 days.
See <http://release.debian.org/migration/testing.pl?package=common-lisp-controller>
=== ecl:
= 1 bug(s) that should be fixed for the next Debian release:
- #471223 <http://bugs.debian.org/471223>
ecl - FTBFS: dpkg-genchanges: failure: cannot read files list file: No such file or directory
= Missing build(s) on s390,sparc,hppa,i386,armel,mips,ia64,alpha,powerpc,mipsel,arm
This might need manual action from your side.
See http://buildd.debian.org/pkg.cgi?pkg=ecl
= No migration to testing for 100 days.
See <http://release.debian.org/migration/testing.pl?package=ecl>
=== xml-to-sexp:
= 1 bug(s) that should be fixed for the next Debian release:
- #471217 <http://bugs.debian.org/471217>
xml-to-sexp - FTBFS: dpkg-genchanges: failure: cannot read files list file: No such file or directory
= No migration to testing for 94 days.
See <http://release.debian.org/migration/testing.pl?package=xml-to-sexp>
=== Packages with a new upstream version according to DEHS:
clisp 2.45 (Debian: 2.44-1)
cmucl 19e (Debian: 19d-20061116-4.1)
ecl 0.9j-p1 (Debian: 0.9j-20080306-1)
------------ interesting stuff probably ends here ------------
This is an automated mail. These mails are sent two times per month.
For more information about these mails, refer to
http://wiki.debian.org/qa.debian.org/DdpoByMail
We are sorry if this mail was useless for you. If you think it was
avoidable (that we can detect easily that the problems weren't
actually problems), please reply to it and let us know.
If you don't want to receive this type of mail any more, you can reply
to this mail and use one of the following commands at the beginning of
the mail:
- only1permonth <email>
You will only receive this mail once per month, not twice.
- unsubscribe <email>
You will no longer receive any mail for any package. If you received
this email because you are subscribed to packages on the PTS, this
won't remove your PTS subscription.
- ignore <package> <email>
You will no longer receive information about that package in those
mails. So if that package is the only one with problems, you won't
receive anything.
- ignore <bug> <email>
You will no longer receive information about this bug.
All commands are manually processed, but you will receive
confirmation. The commands are just here so that we know precisely
what you want.
A more detailed status of your packages is available from the DDPO.
See:
http://qa.debian.org/developer.php?login=pkg-common-lisp-devel at lists.alioth.debian.org
Don't hesitate to reply to this mail if you have questions. The wiki
page will be updated with useful information.
--
DDPOMail, run by Lucas Nussbaum
Reply to: