Re: The future of our mailing lists

Hello all, > For the -devel list, as told previously, I requested a list on > lists.debian.org > (see #886846). IMO this would be a better option, because such a list would be > permanent, while the lists migrated at alioth-lists.debian.net are only > temporary in nature (probably a couple of yea

Re: CMUCL violates the i386 baseline

Hello Sébastien, From 20f onwards [1] we have: 'Support for x87 has been dropped (effective with the 2014-05 snapshot). All further releases will require an x86 chip that supports sse2. SSE2 was introduced with the Pentium 4 in 2001. ' So upstream doesn't handle non-SSE2 anymore, and amd64 isn

Re: The future of common-lisp-controller

Hello Sébastien, > Does common-lisp-controller still serve any useful purpose? > > If not, we should aim at removing it. I think that it no longer serves a purpose and I would prefer to see it removed. (It already got reduced to a shadow of its former image a few years ago). I think removing

Re: Patch fixing build failures of clisp on several archs

Hello Sébastien, > BTW, the git repository of clisp packaging is rather complex with many > different branches (even one branch per release recently), making the > git-buildpackage workflow uneasy. My workflow predates a lot of the tooling available now... I could not find another way of having

Re: Patch fixing build failures of clisp on several archs

Hello Sébastien, >> - do you want me to do the upload itself? > > I am actually happy to do it myself, so I am going to do it soon. > > I was just refraining from pulling the trigger too fast, because I am not > familiar with the rules within the Debian CL team (strong or weak package > ownershi

Re: Patch fixing build failures of clisp on several archs

Hello Sébastien, I checked your patches and they look good. Two questions: - did you give them to ‘upstream’ already? - do you want me to do the upload itself? Best regards, Peter signature.asc Description: Message signed with OpenPGP ___ pkg-common-

Re: Patch fixing build failures of clisp on several archs

Hello Sébastien, > I attach a patch that fixes the build failure of clisp on i386, armel, armhf > and mipsel (I verified that on porterboxes). Oh great! This was on my (very long) to-do list. > I am not yet a member of the pkg-common-lisp group on Alioth, so I can't push > these changes. Please

Re: new clisp packages

Hello Bruno, > 1) It MUST be configured with --enable-portability. Ops. Didn’t do this, mea culpa. I’m uploading a fixed package now. > 2) Modules other than i18n, syscalls, regexp did not receive much attention > for some time and are not in the focus of version 2.50 either. That's >

Re: a new clisp upstream release is being prepared, please re-check the debian packages

Hello Joerg, Thanks for the hint on CLISP. I’ve naively tried packaging the current snapshot and I’ve run into a little snag or two: lintian complains of: W: clisp source: outdated-autotools-helper-file src/build-aux/config.guess 2010-04-03 N: N:The referenced file has a time stamp older th

Bug#821150: cmucl: non-DFSG license

Hello Dmitry, As mentioned before: the community considers this an 'optional request' not a requirement. Unless you have further comments I intend to close this bug in a few weeks. Best regards, Peter -- signature -at- pvaneynd.mailworks.org http://pvaneynd.dreamwidth.org/ God, root, what is d

Bug#821150: cmucl: non-DFSG license

Hello Dmitry, On 19/04/16 23:18, Dmitry Smirnov wrote: > But this requirement is not optional. License do not allow us to speculate > whether they are checking their post box or email and choose whether to > comply with this requirement... I checked and nobody is listening anymore at that email

Bug#821150: cmucl: non-DFSG license

Hello Dmitry, On 16/04/16 04:21, Dmitry Smirnov wrote: > The following files are licensed under non-DFSG compliant license: > > Files: > >

Bug#806246: cmucl: FTBFS (missing build-depends)

Hello Santiago, > Seems like a missing Build-Depends on hardening-includes, the package > containing /usr/share/hardening-includes/hardening.make, so it > should be quite easy to fix. Turns out it's not so easy after all, I'm still working on it... > BTW: I wonder why this package does not exist

Bug#801694: cmucl-source: please declare Multi-Arch: foreign

Hello Aaron, > Could you please declare cmucl-source to be Multi-Arch: foreign? As That's a most excellent idea! Stupid of me of not having thought of this... > Doing the same for cmucl-docs, which cmucl and cmucl-clm both suggest, > would be helpful too. I can do this for cmucl-docs, but cmuc

Bug#789515: cmucl: is the libxp dependency necessary?

Hello Graham, On 21/06/15 19:06, Graham Inggs wrote: > Your package depends on libxp. This situation sometimes arises > historically from the time before xprint was considered obsolete, with > Build-depends: libxp-dev being set in the past and then forgotten and > untouched. In fact upstream set

Re: moving cl-alexandria to git?

Hello Christoph, On 17 Nov 2012, at 05:28, Christoph Egger wrote: > does anyone have an (strong) opinion about moving cl-alexandria > packaging to git (upstream changed to git as well)? Yes, strongly in favour :) Best regards, Peter -- signature -at- pvaneynd.mailworks.org http://pvaneynd.d

Re: followup to comment on http://mentors.debian.net/package/ccl

Hello Faheem, On 09 Oct 2012, at 07:06, Faheem Mitha wrote: > On Mon, 8 Oct 2012, Christoph Egger wrote: >> I'm sorry to not responding to your requests for comment. It's >> currently rather hard for me to free some more time for Debian so I'm >> not really active currently. though I'll try to fr

Bug#654255: cmucl: FTBFS: Error: Unbound symbol.

Hello Jakub, On 02/01/12 16:44, Jakub Wilk wrote: > Source: cmucl > Version: 20b-1 > Severity: serious > Justification: fails to build from source this is not really correct: in fact cmucl cannot be rebuild from source in unstable. It worked before :(. Or are you running stable perhaps? This mu

Bug#598152: clisp: FTBFS on ARM EABI (armel)

Hello Michael, On 17/11/11 18:43, Michael Terry wrote: > I get pretty far these days. I was looking into why it was failing in > Ubuntu and it gets to this point: > > ./lisp.run -B . -N locale -E UTF-8 -Epathname 1:1 -Emisc 1:1 -norc -m > 2MW -lp /home/mterry/clisp-2.49/src/ -x '(and (load > "/h

Re: sbcl double build

Hello all, On 07/10/11 20:58, Christoph Egger wrote: > Does anyone still remember why sbcl is built twice when building the > debian package? Stability. Otherwise you will release a version which is build by just any random version on the build farm. Building it twice not only makes certain t

Bug#617501: clisp does not run, claims to be missing a required file

Hello Desmond and friends, This bug is due to the fact that the rebuild used dh_lisp 0.7 which causes the rebuild version not to call the clisp.sh scripts. So the package is not installed correctly. In fact no rebuild implementation will work anymore. This is clearly sub-optimal as this new vers

Bug#617501: clisp does not run, claims to be missing a required file

Hello Anne, On 09/03/11 14:11, Anne C. Hanna wrote: > /usr/lib/clisp-2.49/base/lisp.run: operating system error during load of > initialization file `/usr/lib/clisp-2.49/base/lispinit.mem' > [/build/buildd-clisp_2.49-3+b1-amd64-lEeikj/clisp-2.49/src/spvw_memfile.d:982] > errno = ENOENT: No such fi

Re: ECL

Hello Christoph, On 04/03/11 23:52, Christoph Egger wrote: > Jep that was the cause for my mail -- noticing you were doing > something as well so I was trying to not duplicate work. Didn#t work > perfectly unfortunately. Well I could also have communicated more :). master.debian.org bouncing

Re: ECL

cy=low > > * New upstream. > * Move to use quilt > * Removed Luca from uploaders > * Updated Standards-Version no real changes > > -- Peter Van Eynde Thu, 03 Mar 2011 07:27:01 +0100 I've just noticed that you pushed your changes to experimental... I'll c

Bug#608017: clisp: error with no xlib, when start stumpwm

Hello, On 20/02/11 02:53, Wang Lei wrote: > Today after upgrading clisp, stumpwm can't startup. Report no xlib. This is a problem of stumpwm I fear. With the new version of clisp clx is no longer build in, you need to also depend on the module "clisp-module-clx". After installing this you can l

new upload of clisp, slight hacking of git history

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello all, I finally did an upload of 2.49-2 to unstable. The bad news is that I had to modify the git history quite a bit because when I came back to creating the package I realised that I was stupid before and that it was better to move to git+qu

Bug#607743: Bug #607743 clisp: starnge behaviour of STORE-VALUE

Hello Miĥail, Checking this on 2.49 I cannot reproduce the problem: > Welcome to GNU CLISP 2.49 (2010-07-07) > ... ... > TEST[14]> (length "abc") > > *** - The value of L should be of type LIST. > The value is: "abc" > The following restarts are available: > STORE

Re: Redesign of Common Lisp Controller

Hello Desmond, On 01/12/10 03:10, Desmond O. Chang wrote: ASDF2 has been mature. C-L-C is basically a thin wrapper now. I plan to remove some redundant features from c-l-c and related packages. This is a good idea and a path that I would have followed if RL was not preventing me from contri

Bug#592768: complementary information

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Stef, On 01/10/10 22:15, stef louise wrote: > This was a little tricky. I successfully built and installed > libsigsegv2_2.8 binary+dev > Then the git build-package was successful, nonetheless it is uninstallable: > > # LANG=C dpkg -i ../clis

Bug#592768: complementary information

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Stef, On 22/09/10 21:53, stef louise wrote: > I may have some time to check it by the end of the week. I know how to > compile stuff, even quite complex projects, but I'm quite unfamiliar > with git (even though I shouldn't), and I don't know

Bug#598152: clisp: FTBFS on ARM EABI (armel)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Hector, On 27/09/10 00:58, Hector Oron wrote: > For 2.49 (latest upstream release), it also fails but on another part, when > building i18n (also reported to upstream) [2] > > configure: loading cache ../config.cache > configure: error: `b

Bug#592768: complementary information

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Stef, On 16/09/10 21:57, stef louise wrote: > /usr/share/common-lisp/source/common-lisp-controller/common-lisp-controller.lisp > *** - handle_fault error2 ! address = 0x77dc3ba0 not in > [0x699c60d8,0x69aa3000) ! I have a new clisp version pr

Re: On the use of Git

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Desmond, Thanks for your comments! On 11/09/10 11:26, Desmond O. Chang wrote: > There are too many branches. We should use tag for each version. The > 'patch' and 'typo' branches are both unnecessary. Using one > 'packaging' branch is ok.

On the use of Git

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello all, While working on clisp I noticed that our current strategy for Git slightly sucks. Currently we have upstream that moves forward with upstream and we pull this into master. The issue which I found is that often you have conflicts and yo

Bug#177057: Redoing the clisp package, advice wanted

Hello Sam, I'm redoing the clisp package from scratch to fix long standing issues like: * unnecessary dependencies in clisp-dev: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504514 * clisp: base/full in clisp-package http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=177057 * clisp: ple

a status update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello all, As you have noticed I was rather busy the last few months. This should improve and I again have a bit of time for some debian work. As I got overwhelmed by the amount of bugs I decided to concentrate on clisp and I'm trying to rework the

Bug#577210: tries to write FASL in wrong directory

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Faré, I'll try to update clc and friends as soon as possible. On 14/04/10 00:28, Faré wrote: > 2- C-L-C needs to (asdf:clear-output-translations) and > (asdf:clear-source-registry) right before it dumps images, for all > implementations. ok

Bug#554081: this is due to the old libgc in unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, ECL needs a more recent version of libgc, but we only have 7.1 in experimental so until 446068 and 559345 are fixed in unstable we can only continue to use the included libgc (and libatomic-ops) version. If you do have patches that make libgc w

Bug#567912: common-lisp-controller: clc:clc-require gives "*** - Program stack overflow. RESET" with clisp

Package: common-lisp-controller Version: 7.0 Severity: important When using the new clc with clisp you always get a stack overflow on the first use of clc:clc-require. If you retry it works. For some reason it loops somewhere it cannot loop. I need to investigate this in more detail. -- System

Re: Bug#560781: (require :package) no longer works for CLC-managed packages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 19/01/10 21:52, James Y Knight wrote: > Only root would be able to use clc-clbuild, right? Correct. Except for "clc-clbuild slime" which should start an emacs with slime running. This mostly works (I had to do some patched to clbuild itself). >

Bug#566686: clisp: FTBFS on kfreebsd: illegal hardware instruction

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Christoph, On 24/01/10 21:48, Christoph Egger wrote: > Downgrading libsigsegv to 2.3-3 does indeed make clisp build > again on kFreeBSD (ignoring the general failure because of > incompatibility with bdb 4.8 which can be solved by using

Bug#560781: (require :package) no longer works for CLC-managed packages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Faré, I was actually thinking about this feature of yours in the traffic jam: instead of /etc/common-lisp/source-registry.conf I would like to see /etc/common-lisp/source-registry.conf.d where instead of having one file that you might have t

Re: Bug#560781: (require :package) no longer works for CLC-managed packages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Faré, On 12/01/10 17:46, Faré wrote: > Can you make the path to those files compatible with what I'm > preparing for ASDF? I've taken a look at the bug and the idea seems to be to have a place to define the locations of systems in on a system

Bug#559954: can not install sbcl in a openvz container

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Rafael, I fear that openvz containers are just not supported upstream. SBCL needs some pretty unusual low level support and demands a lot of memory (which it doesn't all use). I don't think it has sense to make custom patches through Debian, I ad

Bug#560781: (require :package) no longer works for CLC-managed packages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello James, Just FYI I've started working on CLC v7 where this will be a system-wide setting overrideable with a user-specific configuration file. Groetjes, Peter - -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaney

Bug#560963: clc and central-registry issues

Hi all, These bugs only describe expected behavior. From 6.19 onwards common-lisp-controller is no longer doing this. I will update the clc documentation and add a NEWS file to point this out more clearly (I hope). I've attached the NEWS file for you to review. Groetjes, Peter -- signature -a

Bug#518744: cl-plplot: FTBFS: unhandled condition in --disable-debugger mode, , quitting

Hello all, Just FYI: cl-babel is now in Debian. 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| ___ pkg-common-lisp-

Bug#549264: cl-cffi: cffi depends on babel which is not part of debian

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I looked into babel and there is a small license issue to resolve first. I also am checking all dependencies just to be certain. Groetjes, Peter - -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root,

Bug#551133: sbcl: TIME sometimes endlessly spews zeroes

Hi, I'm trying but cannot reproduce this anymore with 1:1.0.31.0-2: > 2/pvane...@sharrow:~/fakeroot/clean/git/sbcl :) $ sbcl --noinform --eval > '(time (sleep 2))' --eval '(sb-ext:quit)' > ; loading system definition from > ; /usr/lib/sbcl/sb-bsd-sockets/sb-bsd-sockets.asd into # > ; registering

Bug#530054: clisp-dev: bashism in /bin/sh script

Hello Raphael, I don't know what went wrong there, but you're right it is still there, however in the code you can read: > # Use a simple mkdir command. It is guaranteed to fail if the directory > # already exists. $RANDOM is bash specific and expands to empty in shells > # other tha

sbcl_1:1.0.27.0-1(mips/unstable): FTBFS on mips

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 It is almost impossible to debug this. I'm going to drop support for alpha, sparc, mips, mipsel and powerpc in the next release. Groetjes, Peter - -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root, what

cl-cffi: cffi depends on babel which is not part of debian

This seems to be because dh_lisp is not setting dependencies correctly, so babel got removed by accident. Oops. We need to check why this is and now check all CL libraries. Groetjes, Peter -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root, what is

Bug#545625: ecl: FTBFS: rm: cannot remove `/build/user-ecl_9.8.4-1-amd64-YJh2Lk/ecl-9.8.4/debian/ecl/usr/share/info/dir.old': No such file or directory

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Lucas, Lucas Nussbaum wrote: > Why are you building in a lenny chroot ? Because I was testing before with a sid chroot, which worked and I got confused. So I redid a build of 9.8.4-1 in a clean chroot and ... it just worked... Groetjes, Pe

Bug#545625: ecl: FTBFS: rm: cannot remove `/build/user-ecl_9.8.4-1-amd64-YJh2Lk/ecl-9.8.4/debian/ecl/usr/share/info/dir.old': No such file or directory

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Lucas, Lucas Nussbaum wrote: > On 22/09/09 at 18:47 +0200, Peter Van Eynde wrote: >> I'm a bit surprised by this FTBFS as ecl is also auto-build for other >> platforms. What research did you do in this failure? > >

Bug#545625: ecl: FTBFS: rm: cannot remove `/build/user-ecl_9.8.4-1-amd64-YJh2Lk/ecl-9.8.4/debian/ecl/usr/share/info/dir.old': No such file or directory

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Lucas, I'm a bit surprised by this FTBFS as ecl is also auto-build for other platforms. What research did you do in this failure? Groetjes, Peter - -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, roo

Bug#492004: package removed from debian [eom]

___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-common-lisp-devel

Bug#518605: 518605 Don't put generated/non-config files not in /etc

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 tag 518605 +confirmed thanks Hello Jörg, Of course you are right, but currently all lisp implementations will read this file on startup. We should cleanup this policy and then fix all the lisp implementations... one day ;-( Groetjes, Peter - --

Bug#535305: 535305 Re: common-lisp-controller: update fails rebuilding sb-grovel, , asdf broken as a result

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello David, Fredrik, Indeed the clc version 6.18 does not work with older versions of sbcl. I've had to change the native-file-kind package. However I've also added a Conflict against "sbcl (<< 1:1.0.29.0)". So why did it want to install with an o

Re: Etch to Lenny (6.9 to 6.17) change in asdf:output files wrapper

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello John, John McAleely wrote: > Oops. How embarrassing. I think your deduction is correct. I must have > patched this on my etch system, and then failed to keep a record of so > doing. My 'rediscovery' of this issue over the last few days failed

Re: Slowly giving up on most packages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Luca Capello wrote: > Adoption requested, I will ask for their removal in two weeks: > > http://bugs.debian.org/540699 > http://bugs.debian.org/540700 > http://bugs.debian.org/540702 > http://bugs.debian.org/540703 Luca never did, they neve

Re: Etch to Lenny (6.9 to 6.17) change in asdf:output files wrapper

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello John, John McAleely wrote: > The lisp in question is Clozure CL, which I have created a debian > package for, which integrates with c-l-c. Aha interesting. > When I upgrade to lenny (ie to c-l-c 6.17 from 6.9), An attempt to load > c-l-c ins

the survivors

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, The following packages survived the culling, got updated to the latest upstream and uploaded: > 2/pvane...@sharrow:~/fakeroot/clean :) $ find . -maxdepth 2 -type d -not \( > -name "darcs" -or -name "git" -or -name "." \) > ./darcs/cl-clo

Re: /usr/share/common-lisp/systems/ not in asdf:*central-registry*

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello all, [context: the newest clc does not longer add /usr/share/common-lisp/systems to asdf:*central-registry*] Desmond O. Chang wrote: > On Fri, Sep 11, 2009 at 2:40 AM, Luca Capello wrote: >> I still consider this a regression, since previo

Re: /usr/share/common-lisp/systems/ not in asdf:*central-registry*

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Tamas, Tamas Papp wrote: > I thought I would write before filing a bug report. Apparently > /usr/share/common-lisp/systems/ is not in asdf:*central-registry* any > more by default. Of course adding it manually fixes this, but it used > to be

restart of asdf git repository

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, While trying to make the 'update package via git' tutorial, I noticed that asdf now actually is maintained in git. The good part is that I could rebase the debian version on the official asdf tree, the bad part is that this resulting branch

Re: the list of packages to remove

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Rupert, Rupert Swarbrick wrote: > I personally would be extremely happy if (revamped?) versions of the > following packages were in the archive. If I've got it right, these are > basically what's needed for hunchentoot to work. ... > As I ke

Re: pan pan pan

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Milan, Milan Zamazal wrote: > Please note I'm unable to join right now, I hope I'll be able to start > doing something in September or October. Please just don't remove nor > orphan the package in the meantime. Ok, no problem. Groetjes, Pet

the list of packages to remove

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello all, I've done some playing round with grep-available and I've come up with a list of packages that is 'owned' by kg-common-lisp-devel and that are not used by members outside the team: Package: cl-aima Package: cl-aserve Package: cl-cclan Pa

Re: pan pan pan

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Milan and friends, Milan Zamazal wrote: > If you give up on the package and nobody wants it, I'll probably take it > over. Not that I have any reason to suppose it would be less tricky for > me, but SLIME is important enough to be available i

Re: pan pan pan

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Christian, How is Castafiore doing? Could you revive her? Christian Lynbech wrote: > Would there be any point in discussing this at next months European > Common Lisp meeting? I fear that I won't be there. The 'next' conference that I will

Re: pan pan pan

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello all, Milan Zamazal wrote: > I'm a DD interested in CL. I maintain (although not very actively) a > few Debian CL packages and I'm not going to give up on them, so I need > at least common-lisp-controller (in addition to CL implementations) in

pan pan pan

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, With regret I'll copy the message that I've put on my blog: > After some consideration I must conclude that the state of the Common Lisp > packages in Debian is becoming unreasonable. One of the goals of forming the > pkg-common-lisp team

Bug#526584: CMUCL requires SSE2 CPU on i386 architecture

-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

Bug#517205: fixed in slime 1:20090409-1

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Evgeny, Evgeny M. Zubok wrote: > Peter Van Eynde writes: > >>* Removed xref.lisp again and added a test in the makefile for it >> (Closes: #517205) > > And what about Lenny? Does this DFSG violat

Bug#507302: not a bug I think...

The ` in bridge.el seems to use the new standard but to fire the warning: (setq bridge-last-failure `((funcall ',handler ',proc ,string) "Caused: " ,err not? Groetjes, Peter -- signature -at- pvaneynd.mailworks.org http://www.livejournal.co

Bug#474483: xref in swank/slime bug

I cannot reproduce this bug anymore. Do you still have the problem with a recent slime and sbcl? 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|

quilt use in clisp

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I tried to update clisp to the latest upstream, but I discovered that it now uses quilt. I have severe issues with quilt, most of them personal no doubt, so much so that I gave up in disgust. I can either remove the quilt stuff or give up an

Bug#508922: SLIME doesn't like a non-Debian Lisp

Hi Juliusz, Good idea, however how can I tell your non-debian CCL to load swank? What method should I use? 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| __

Bug#492943: slime: Package depencies: add recommmend konqueror

Hi, Good idea, however I don't see 'kfmclient' anywhere in the sources. And I use the build-in emacs browser Isn't this an emacs setting? Groetjes, Peter -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root, what is difference?" Pitr | "God is mor

Re: debs and asdf-install

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Igor, Igor Stirbu wrote: > Is there a recommendation on whether I should install > a library as a deb package or get it over asdf-install? The main point of difference between asdf-install and using deb packages is that with deb packages the sy

Re: SBCL blocked at 0.9.16 in testing

Hi all, Luca Capello wrote: >> Given the bootstrap problem, we should IMHO rather get SBCL going >> again on those architectures than ask for removal of the 0.9.16 >> binaries from lenny. > > Since manpower for the Debian Common Lisp Team is lacking (help is > always appreciated), I think that w

Re: CL-Debian ancient darcs repository

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ciao Luca, Luca Capello wrote: | However, since most of the old packages migrated from darcs to git, | maybe it should be a good idea to keep the old repositories as history, | what do you think? I would make a last record, removing all files and lea

Bug#470447: cmucl: FTBFS: make[1]: *** [all] Error 133

Hi, On a real i386 rebuilding cmucl works. So I'm a bit confused as to why you see the problem. My guess is that the reason is that you are building on an AMD64 machine. Groetjes, Peter -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root, what is dif

Bug#469896: cl-geodesics - FTBFS: dpkg-genchanges: failure: cannot read files list file: No such file or directory

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Can you describe how you build this package? I've tried to reproduce the problem with "debuild binary-indep", but it nor "debuild binary-arch" produce the problem. Groetjes, Peter - -- signature -at- pvaneynd.mailworks.org http://www.livejournal

Re: Common Lisp at DebCamp/DebConf8

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Luca Capello wrote: | 1) finish package migration, including all the "features" (e.g. like |commit notifications) and trying to have a common layout for all the |packages (which also means fixing some bugs) I wanted to move all my package

PTS: editing the subscribers 'by hand'?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, [this is a resend because I got an email from smartlist to confirm my unsubscription (!). So now I'm using spam techniques to get it to reach the mailing list... ] The Common Lisp packages are slowly moving to group maintenance, and as a step in

PTS: editing the subscribers 'by hand'?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, The Common Lisp packages are slowly moving to group maintenance, and as a step in this process we need to unsubscribe the old mailing list from all packages in the PTS and subscribe the new mailing list. After two 'unsubscribe/confirm' cycles thi