the survivors

Peter Van Eynde pvaneynd at debian.org
Sat Sep 12 09:00:38 UTC 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi all,

The following packages survived the culling, got updated to the latest
upstream and uploaded:

> 2/pvaneynd at sharrow:~/fakeroot/clean :) $ find .  -maxdepth 2  -type d -not \( -name "darcs" -or -name "git" -or -name "." \)
> ./darcs/cl-closer-mop
> ./darcs/cl-contextl-upstream
> ./darcs/cl-contextl
> ./darcs/cffi-upstream
> ./darcs/cl-lw-compat-upstream
> ./darcs/cffi
> ./darcs/cl-closer-mop-upstream
> ./darcs/cl-lw-compat
> ./darcs/cedilla
> ./darcs/cedilla-upstream
> ./git/cl-split-sequence
> ./git/cl-usocket
> ./git/hyperspec
> ./git/cl-md5
> ./git/sbcl
> ./git/ecl
> ./git/slime
> ./git/cl-pg
> ./git/cmucl
> ./git/cl-irc
> ./git/cl-xmls
> ./git/cl-ptester
> ./git/cltl
> ./git/common-lisp-controller
> ./git/cl-portable-aserve
> ./git/libsigsegv
> ./git/flexi-streams
> ./git/clisp
> ./git/cl-rt
> ./git/cl-ppcre
> ./git/cl-asdf

The following packages need some loving attention, even from a non-DD or DM:

./git/libsigsegv -> the self-test fails on AMD64 even with git head.
                    (#544905) I have no idea why... Someone should
                    investigate and talk to upstream.

All packages should contain a debian/README.building with instructions
on how to get the git/darcs version, how to update upstream and how to
build. I tried to test them but of course my system is well-worn in and
I might have forgotten steps...

Milan offered to maintain slime.

I should investigate the new bugs that got reported against the new
uploads...

Groetjes, Peter

- --
signature -at- pvaneynd.mailworks.org
http://www.livejournal.com/users/pvaneynd/
"God, root, what is difference?" Pitr | "God is more forgiving." Dave
Aronson|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJKq2M0AAoJEB4VNT76eIlaMWUP/Awa4DI8RHBmyq6dSYbTUJX5
e3IvqO3HGUr6QX7FCIBzi8dpIqP+B5ETxNXt2i4fiKXgfifglU/ac2UbBXR08DWB
8azLjfvVIZ1qh3xLedQTZj+KPAuqvjcIyDJjjfDbHqCeZ0NFTXtGF83V9IccbUnY
mME80plANsF6JXzcUr3W6fd2bkpR5NdhYXwrN6B6ThJktzjvUJLtqlFj8YjTRVzg
ovcVane410H3f+ewpxtvbN2W83dEEgnqolYiYbCSSWG1kWBsJpdJe5lhp/ouzx3p
wm4S4EPfFkUJ9w/Ss2dFYG+t1uRNY4UQc5aDOE8TKGD0fUfbVGNo1dMi5nbsTj9S
FkH8YerUG3G1fXC+6NWcFpzanI24/B5sEiDPfkVN3LJ3bp/xaXZ2QWuwWHzfZvhw
2UD05+TOc5O8PFkfNp/JirF8vlRzfQuC9TiTmwKSwslUjeC9hEl68GPw16Fp1o5A
IdaR8psN6IRuwIcmaZTVThTv4OGRyVx1sa+3FW1VB2rwPEuGV5hC1apHiff/gBi2
h3PO/zzjeCSMh/+qoS/V9E3YomySOhPLNRf2hYrKPravZndXEkDu7LLmd3SdgQ7T
q+frRDldTSfJieDGPtN2IUVg9OArIauqzosw7+pJ98eRVqbJ78s10rK4ICS/dbaI
6Ir9wmHRyLOXf+lHWW8r
=QduM
-----END PGP SIGNATURE-----



More information about the pkg-common-lisp-devel mailing list