-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
htt
Package: libxcb1
Version: 1.3-2
Severity: important
After upgrading libxcb to 1.3-2 awesome will crash when starting either a
terminal (Mod4-enter) or another client (Mod-4 r xosview).
I've tried using gdb to investigate where it crashes, but eip == 0x0 and the
stack seem empty.
The kernel re
-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
-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
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
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|
--
To UNSUBSCRI
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|
--
To
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
maximilian attems wrote:
checkout 2.6.25 from unstable installs just fine in testing.
can you reporduce there!?
2.6.25 uses the e1000e driver for that card, which does not show this
problem.
Groetjes, Peter
--
signature -at- pvaneynd.mailworks.org
http://www.livejournal.com/users/pvaneynd/
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 di
-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.livejourna
Package: linux-image-2.6.24-1-686
Version: 2.6.24-1
Severity: important
*** Please type your report below this line ***
Configuring CONFIG_E1000_NAPI on the 2.6 kernel causes my laptop (Lenovo
T60) to hang on high network load. This is easely reproduced and
building a customer image without this
Hello,
Ross Boylan wrote:
> During a recent emacs upgrade the install log shows
> Setting up emacs22 (22.1+1-2.1+lenny1) ...
> emacs-install emacs22
>
> Loading /etc/emacs/site-start.d/50slime.el (source)...
> Error while loading 50slime
I've tried analysing this problem but I have no idea w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciao Luca,
Luca Capello wrote:
> dpkg: warning - unable to delete old directory `/usr/lib/clisp/full':
> Directory not empty
> dpkg: warning - unable to delete old directory `/usr/lib/clisp': Directory
> not empty
Damn. I'll have to think about wha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Ingvar,
Ingvar Mattsson wrote:
> With the new "contrib-based", pluggable SLIME architecture, there seems
> to be some out-of-sync problems between SLIME and SWANK.
Here I was thinking I had fixed most of them :-(.
> If I load the slime-asdf exten
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Erick,
Erick Lopez Carreon wrote:
> !! File error (("Cannot open load file" "tree-widget"))
What do I see in the ChangeLog:
* tree-widget.el: File deleted. Only needed by contribs and is
distributed with Emacs 21.
So somethi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Faré,
It took some time but I finally had a moment to look at the issues.
Faré wrote:
> (1) it uses the c-l-c version of asdf and not the ecl-provided one from
I almost fixed the 'official' asdf to support all the features the ecl
provided one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Andreas,
Andreas Krüger wrote:
> I cannot run clisp without getting this error, see below.
> (I'm a Lisp beginner.)
I think I know what causes your problem: it is caused by having a file
in your home directory with a name that cannot be encoded
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Ross,
Ross Boylan wrote:
> Thank you for the pointer. I think I missed a couple key points. Let
> me see if I've got them now:
> 1) anyone can add a tag, not just the package author
> 2) the tags are not part of the package; they are part of t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Pablo,
J. Pablo Fernandez wrote:
> It would be very nice if the SBCL package already included shebang
How would you like this? As part of the standard startup might cause
problems for other people, not?
Groetjes, Peter
- --
signature -at- pva
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry for the late reply.
Michael Biebl wrote:
> do you still experience the bug with an up-to-date version of knetworkmanager
> (1:0.2~svn678822-3) and network-manager (0.6.4-8+b1)?
I fear I changed portable and with the T60 (ipw3945d card) I cannot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Faré
I tried with the environment set as you gave, but still it works.
Actually I cannot find serious references to TERMCAP in the cmucl
sources so I fail to see where it could crash the image...
What does strace say?
Groetjes, Peter
- --
sig
Faré wrote:
After some experimentation, it looks like the problem is a buffer
overflow (of all things!) when variable $TERMCAP is too big.
Interesting. And dangerous.
But I cannot reproduce it:
$ echo $TERMCAP | wc -c
11448
$ cmucl
CMU Common Lisp CVS 19d 19d-release (19D), running on frost
W
On Wednesday 11 April 2007 23:26, [EMAIL PROTECTED] wrote:
> It seems to me that whenever you quit emacs while slime displays sbcl
> debugger and waits for user input on how to proceed within slime, you'll
> end up with corrupted fasl files.
Ah. Now this is interesting. It is very good that y
Hello,
On Wednesday 11 April 2007 19:17, commi wrote:
> I am using sbcl version 0.9.16.0-1 and when executing
> (clc:clc-require :sdl-demos) within my slime (Version:
> 1:20060925-1) i get the following error:
I fear I cannot reproduce the problem. The compilation does throw an error
because
On Wednesday 14 March 2007 10:44, Drake Wilson wrote:
> Quoth Peter Van Eynde <[EMAIL PROTECTED]>, on 2007-03-14 10:39:25 +0100:
> > So I'm guessing your cl-swank and slime packages are out of sync and the
> > backwards compatibility of slime leaves something to be desi
On Tuesday 13 March 2007 10:12, Drake Wilson wrote:
> Trying to start SBCL using M-x slime-start from GNU Emacs fails with
> an error on the Common Lisp side. "important" because inferior-lisp
> is a big part of SLIME by my understanding.
I'm guessing you are using C-u M-x slime and then sbcl the
On Friday 23 February 2007 10:36, Jan wrote:
> >(and you can get it from my p.d.o pages),
> Where is this page located?
http://people.debian.org/~pvaneynd/cl-packages/
add
deb http://people.debian.org/~pvaneynd/cl-packages ./
to your /etc/apt/sources.list file
>
> I tried: deb http://people.deb
Hi
First of all: thank you for bringing these bugs to my attention. I'm currently
working on a newer ecl package, however I fear it look like it will take a
little more time. Unless etch gets released first I'll upload new packages to
experimental.
Groetjes, Peter
--
signature -at- pvaneynd.
On Monday 05 February 2007 08:31, anoop aryal wrote:
> Package: cl-hunchentoot
> Severity: important
>
>
> cl-hunchentoot depends on cl-plus-ssl which seems to be a virtual package.
Not that virtual, I've packaged it (and you can get it from my p.d.o pages),
but I had to figure out some license
On Saturday 20 January 2007 05:28, Faré wrote:
> *** Please type your report below this line ***
> Since I last upgraded cmucl, I get the following error and backtrace
> whenever I start it.
>
> $ cmucl
>
>
> Error in function UNIX::SIGSEGV-HANDLER: Segmentation Violation at
#x10044FB8.
>[
Thank you for the report.
On Monday 11 December 2006 12:16, Juhapekka Tolvanen wrote:
> > "cat /proc/sys/kernel/randomize_va_space" return?
>
> 1
>
> > Are you running prelink?
>
> I have installed it beacause of OpenOffice.org:
>
> Status: install ok installed
>
I'm guessing this problem i
Hello,
On Sunday 10 December 2006 22:47, Juhapekka Tolvanen wrote:
> (Reading database ... 345386 files and directories currently installed.)
> Preparing to replace sbcl 1:0.9.16.0-1
(using .../sbcl_1%3a1.0.0.0-1_i386.deb) ...
> Unpacking replacement sbcl ...
> Setting up sbcl (1.0.0.0-1) ...
> /
On Saturday 11 November 2006 13:23, Julien Danjou wrote:
> On Sat, Nov 11, 2006 at 09:48:29AM +0100, Peter Van Eynde wrote:
> > In the backtrace of
> > > > unhandled SB-INT:SIMPLE-FILE-ERROR in thread
#:
> > > > The file "/nonexistent/" does not
Hi
I fear that the log you give does not give the basic reason
for the failure.
On Fri, 10 Nov 2006 23:27:01 +0100, "Julien Danjou" <[EMAIL PROTECTED]>
said:
> > make[1]: Leaving directory `/build/buildd/sbcl-0.9.18.0/contrib/sb-sprof'
> > Failed contribs:
> > asdf-install
> > sb-aclrepl
> >
On Wed, 8 Nov 2006 10:21:01 +0100, "Lucas Nussbaum"
> During a rebuild of all packages in etch, I discovered that your package
> failed to build on i386.
This turns out to be hevea problem:
hevea -fix cmu-user.hva cmu-user.tex
./cmu-user.hva:13: Warning: Not (re)-defining environment 'minipage'
w
Hello,
Your logs show that there is a memory layout conflict in sbcl:
On Saturday 04 November 2006 10:45, J.P. Larocque wrote:
> > cat /proc/self/maps
>
> ---8<---8<---
> 0001-00014000 r-xp 08:01 6201
> /bin/cat
> 00022000-00024000 rwxp 2000 08:01
On Saturday 04 November 2006 15:01, commi wrote:
> Package: cmucl
> Version: 19c-release-20051115-3
> Severity: normal
>
>
> The package fails to install with:
>
> Richte cmucl ein (19c-release-20051115-3) ...
> Installing Common Lisp Controller in CMU CL ...
> Couldn't mmap at 0xbe00, len 1
Hello,
Let me first thank you for the bugreport, it is pretty clean and complete.
On Monday 23 October 2006 01:51, J.P. Larocque wrote:
> The stack trace produced below probably doesn't convey any meaningful
> information.
gdb does not work well with lispy environments I fear.
> Loaded symbols
On Wednesday 25 October 2006 11:10, Michael Stevens wrote:
> Package: clisp
> Version: 1:2.41-1
> Severity: normal
>
> Today's update in testing refuses to install:
>
> Setting up clisp (2.41-1) ...
> Installing clc...
> ;; Loading file /usr/lib/clisp/install-clc.lisp ...
> ;; Loading file
> /us
Package: wnpp
Severity: wishlist
Owner: Peter Van Eynde <[EMAIL PROTECTED]>
* Package name: cl-chunga
Version : 0.2.0
Upstream Author : Dr. Edmund Weitz
* URL : http://weitz.de/chunga/
* License : BSD
Programming Lang: Common Lisp
Description : Po
Package: wnpp
Severity: wishlist
Owner: Peter Van Eynde <[EMAIL PROTECTED]>
* Package name: cl-cffi
Version : 20061013
Upstream Author : James Bielman
* URL : http://common-lisp.net/project/cffi/
* License : BSD
Programming Lang: Common Lisp
Descr
Package: wnpp
Severity: wishlist
Owner: Peter Van Eynde <[EMAIL PROTECTED]>
* Package name: cl-plus-ssl
Version : 20060904
Upstream Author : various
* URL : http://common-lisp.net/project/cl-plus-ssl/
* License : Lisp LGPL
Programming Lang: Commo
Package: wnpp
Severity: wishlist
Owner: Peter Van Eynde <[EMAIL PROTECTED]>
* Package name: cl-hunchentoot
Version : 0.4.4
Upstream Author : Dr. Edmund Weitz
* URL : http://weitz.de/hunchentoot/
* License : BSD
Programming Lang: Common Lisp
Descr
Package: wnpp
Severity: wishlist
Owner: Peter Van Eynde <[EMAIL PROTECTED]>
* Package name: cl-trivial-https
Version : 20051125
Upstream Author : Brian Mastenbrook / David Lichteblau
* URL : http://common-lisp.net/project/cl-plus-ssl/
* License
On Monday 16 October 2006 20:50, you wrote:
>
> You probably noticed that ia64 is outdated too, and that requires some
> action too to get it back in sync for etch -- either removal or a fix.
I'm a bit stumped w.r.t the ia64 problem:
./lisp.run -B . -N locale -E 1:1 -Efile UTF-8 -Eterminal UTF-8
Hello
I recently tested a standard debian kernel and with linux-image-2.6.18-1-686 I
can again run sbcl and cmucl. So there is a debian kernel that can be used,
however it is not the kernel that will be used for etch. :-(
2.6.17-2-686 still has the broken
CONFIG_PAGE_OFFSET=0xB000
I will
On Friday 29 September 2006 21:53, Kevin L wrote:
> Package: cl-statistics
>
> This is strange: cl-statistics compiles fine in CMUCL and *appears* to
> compile fine in SBCL, but SBCL still throws an error.
From the log, and from experience, I guess that the error is 'compile-file
warned while'
On Tue, 03 Oct 2006 21:45:13 -0600, "Rob Aagaard" <[EMAIL PROTECTED]> said:
> Package: common-lisp-controller Version: 6.3 Severity: normal
>
> Attempting to load any library through asdf fails.
6.3 and 6.4 were pretty bad releases. 6.5 should would, at least it does
for me, could you check this
Wolffelaar wrote:
> tags 388398 moreinfo
> thanks
>
> On Wed, Sep 20, 2006 at 11:19:43AM +0200, Peter Van Eynde wrote:
> > Package: ftp.debian.org
> > Severity: normal
> >
> > Hello,
> >
> > clisp does not build anymore on sparc (see 386075). Upstream
On Thursday 28 September 2006 20:29, Kevin L wrote:
> Package: cmucl
>
> I typed in an invalid Lisp form and was surprised that CMUCL responded
> in this way:
>
That is really stunning. A new cmucl release is being worked on, I expect a
release in a few days, I will check if the bug is in that
Package: cl-fad
Version: 0.5.0-2
Severity: wishlist
Hi,
>From weitz.de:
CL-FAD - A portable pathname library for Common Lisp.
version: [0.5.1 / 2006-08-11]
No big changes it seems.
Groetjes, Peter
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500
Package: cl-tbnl
Version: 0.9.10-1
Followup-For: Bug #367969
upstream changelog:
Version 0.11.1
2006-09-14
Cleaner implementation of *CATCH-ERRORS-P*
Version 0.11.0
2006-09-14
Added *CATCH-ERRORS-P*
Version 0.10.3
2006-09-05
Appease SBCL (thanks to Juho Snellman)
Version 0.10.2
2006-09-05
Bett
Package: ftp.debian.org
Severity: normal
Hello,
clisp does not build anymore on sparc (see 386075). Upstream is unable to
fix the problem, nor do I have access to a sparc porting machine.
So with regret I ask to remove the sparc packages of the clisp
package, I will upload a clisp binary with m
Alle Tuesday 05 September 2006 06:17, Jurij Smakov ha scritto:
> Latest version of clisp fails to build on sparc [0]:
Hello,
As on the buildd host it seems to work I'm lowering the severity to normal,
but this does not mean I'm going to ignore this problem.
Groetjes, Peter
--
signature -at-
Alle Monday 21 August 2006 23:08, Kevin L ha scritto:
> I just "upgraded" from Sarge to testing and CMUCL is now dead.
>
> If this is fixed upstream, when is the fix going into testing?
>
> Is an end-user just supposed to compile their own kernel in the meantime?
I fear so. That or use the ubunt
Alle Tuesday 12 September 2006 18:38, Jurij Smakov ha scritto:
> Hi,
>
> Yesterday I have successfully rebuilt sbcl in a up-to-date pbuilder chroot
> on sparc. The log of the build is available at
>
> http://www.wooyd.org/debian/misc/sbcl-build.log.bz2
Very helpful indeed.
> Perhaps it was s
Package: libhal1
Version: 0.5.7.1-1+b1
Severity: critical
Justification: breaks unrelated software
Hello,
After the upgrade from 0.5.7.1-1 to 0.5.7.1-1+b1 vmware fails to start.
Browsing a bit find a thread talking about this problem on
ubuntu and a bugreport there:
http://www.vmware.com/communit
Hello,
As clisp does not provide a FFI on:
arm hppa ia64 m68k s390
mcvs should not be build on those architectures.
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|
Alle Wednesday 26 July 2006 16:41, Don Geddis ha scritto:
> I understand the conflict, that it appears the kernel guys did make an
> unintentional error. Nevertheless, I find the phrase "non-standard kernel"
> to be suspect. If a user tries to install the default linux-2.6 kernel in
> Debian ("te
Hello Don,
Alle Monday 24 July 2006 19:27, Don Geddis ha scritto:
> So what's the current status? CMUCL is WONTFIX, and the kernel folks claim
> the same thing? Nobody cares that the application and the kernel are no
> longer compatible?
I'm not going to create a separate memory layout for debi
Package: linux-image-2.6.17-1-686
Version: 2.6.17-4
Followup-For: Bug #360598
Hello,
I just wanted to report that this bug is still present in version
2.6.17-4 of the kernel.
Groetjes, Peter
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unst
Alle Sunday 09 July 2006 09:35, Peder Chr. Nørgaard ha scritto:
> Package: cl-asdf
> Version: 1.99-2
> Severity: important
>
> I try to upgrade to 1.99-2, apt-get says:
>
> % apt-get install cl-asdf
> Reading package lists... Done
> Building dependency tree... Done
> The following packages will b
Alle Monday 10 July 2006 23:35, Thiemo Seufer ha scritto:
> Package: clisp
> Version: 2.38-8
> Tags: patch
>
> The appended patch re-enables FFI for mips/mipsel.
Thanks, with -R it applied without problems.
Groetjes, Peter
--
signature -at- pvaneynd.mailworks.org
http://www.livejournal.com/us
Package: darcs
Version: 1.0.6-1
Severity: normal
Hello,
While stressing darcs to the limits I fear ran into the error
described at:
http://www.haskell.org/pipermail/glasgow-haskell-bugs/2006-March/006246.html
error message:
darcs: internal error: update_fwd: unknown/strange object 57
this see
Package: network-manager-kde
Version: 0.09+0.1r550737-1
Severity: normal
Hello,
I have a WEP protected wlan that does not transmit the SSID at home. (I
know this is not safe, but with 2 other open networks nearby they will
not bother with mine I guess).
I have installed and configured wpa_suppli
Hello,
I managed to isolate the problem even more: the tailor will only fail if you
already create the repository.
For example:
$ ls -FAC
$ tailor --debug --verbose --encoding=ISO-8859-1 \
--source-kind=cvs --target-kind=darcs \
--source-repository=":pserver:[EMAIL PROTECTED]:/project/cl-pl
Package: tailor
Version: 0.9.23-1
Severity: normal
Hello,
I've been trying to use tailor to convert my upstream cvs'ses into nice
darcs archives, and for most packages this works like a charm. But some
fail: the resulting darcs archive is borken:
1/[EMAIL PROTECTED]:~/fakeroot/repository/trivial
101 - 200 of 286 matches
Mail list logo
