June 2007 - cl-debian@common-lisp.net - mailman3.common-lisp.net

[cl-debian] Bug#330468: sbcl: Can't start sbcl with kernel 2.4.27-2-686
by Didier Verna 28 Jun '07

28 Jun '07

Package: sbcl Version: 1:0.9.4.65-1 Severity: grave Hi ! When I try to launch SBCL, I get the following message: ,---- | fatal error encountered in SBCL pid 10204(tid 16384): | This version of sbcl is compiled with threading support, but your kernel is | too old to support this. Please use a more recent kernel or a version of sbcl | without threading support. `----- ... which I consider a bug since the Debian package installed just fine, and there don't seem to be an alternative sbcl package usable for me. I don't want to use a 2.6 kernel on my machine. So what should I do ? Thanks ! -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.27-2-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages sbcl depends on: ii common-lisp-controller 4.18 This is a Common Lisp source and c ii libc6 2.3.5-6 GNU C Library: Shared libraries an ii sbcl-common 1:0.9.4.65-1 Architecture independent files for Versions of packages sbcl recommends: ii binfmt-support 1.2.6 Support for extra binary formats -- no debconf information

4 4

[cl-debian] Bug#227196: marked as done (cl-sdl-opengl: compile files with nvidia 4496 under kernel 2.6.0-test11 (tls?))
by owner＠bugs.debian.org 28 Jun '07

28 Jun '07

Your message dated Thu, 28 Jun 2007 21:26:28 +0200 with message-id <46840B64.6090208(a)debian.org> and subject line closing out-of-date bugreports has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)

1 0

[cl-debian] Bug#397026: cmucl: package does not install in etch
by commi 28 Jun '07

28 Jun '07

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 0xbe000000, len 1048576; got mapping at 0xa7d11000 insteadensur e_space: Failed to validate 1048576 bytes at 0xbe000000 FAILED ------------------------------------------- mimi@host1:~$ cmucl --version Couldn't mmap at 0xbe000000, len 1048576; got mapping at 0xa7d0f000 insteadensure_space: Failed to validate 1048576 bytes at 0xbe000000 -- System Information: Debian Release: testing/unstable Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages cmucl depends on: ii common-lisp-controller 6.6 This is a Common Lisp source and c ii debconf [debconf-2.0] 1.5.6 Debian configuration management sy Versions of packages cmucl recommends: ii binfmt-support 1.2.8 Support for extra binary formats -- debconf information: cmucl/upgradeproblems:

3 2

[cl-debian] Bug#360561: cmucl: CMUCL does not run under kernel version 2.6.16
by Christian Lynbech 28 Jun '07

28 Jun '07

Package: cmucl Version: 19c-release-20051115-2 Severity: normal When trying to run CMUCL under the recently released 2.6.16 kernels, it fails to start with the error: chateau:~> lisp Couldn't mmap at 0xbe000000, len 1048576; got mapping at 0xa7cc1000 insteadensure_space: Failed to validate 1048576 bytes at 0xbe000000 The problem is semi-serious in the sense that Debian unstable only really has the 2.6.16 kernels left and thus it kind of is not possible to run CMUCL together with a supported distributed kernel. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-k7 Locale: LANG=C, LC_CTYPE=da_DK (charmap=ISO-8859-1) Versions of packages cmucl depends on: ii common-lisp-controller 5.13 This is a Common Lisp source and c ii debconf [debconf-2.0] 1.4.72 Debian configuration management sy Versions of packages cmucl recommends: ii binfmt-support 1.2.7 Support for extra binary formats -- debconf information: cmucl/upgradeproblems:

4 3

[cl-debian] Bug#168225: marked as done (Doesn't get compiled properly)
by owner＠bugs.debian.org 28 Jun '07

28 Jun '07

Your message dated Thu, 28 Jun 2007 21:26:28 +0200 with message-id <46840B64.6090208(a)debian.org> and subject line closing out-of-date bugreports has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)

1 0

[cl-debian] Bug#168223: marked as done (lisp crashes with a segmentation fault.)
by owner＠bugs.debian.org 28 Jun '07

28 Jun '07

Your message dated Thu, 28 Jun 2007 21:26:28 +0200 with message-id <46840B64.6090208(a)debian.org> and subject line closing out-of-date bugreports has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)

1 0

[cl-debian] Processed: note that this has been fixed a while ago
by owner＠bugs.debian.org 28 Jun '07

28 Jun '07

Processing commands for control(a)bugs.debian.org: > notfound 390967 6.5 Bug#390967: common-lisp-controller: File permission errors for .fasl files Bug marked as not found in version 6.5. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)

1 0

[cl-debian] Bug#430231: ldbl128 transition for alpha, powerpc, sparc, s390
by Matthias Klose 27 Jun '07

27 Jun '07

Package: ecl Severity: serious User: debian-release(a)lists.debian.org Usertags: goal-ldbl128 Discussed in http://lists.debian.org/debian-devel/2007/05/msg01173.html With glibc-2.5 and gcc-4.1.2 (and gcc-4.2), the 'long double' data type did change from a 64bit representation to a 128bit representation on alpha, powerpc, sparc, s390. To allow partial upgrades of packages, we will need to rename all packages holding libraries with the long double data type in their API. Both libc and libstdc++ do not need to be renamed, because they support both representations. We rename the library packages on all architectures to avoid name mismatches between architectures (you can avoid the renaming by supporting both datatype representations in the library as done in glibc and libstdc++, but unless a library is prepared for that, it does not seem to be worth the effort). It is suggested to rename a package libfoo1 to libfoo1ldbl; please wait with the renaming if the package depends on another library package which needs renaming. This package has been indentified as one with header files in /usr/include matching 'long *double'. Please close this bug report if it is a false positive, or rename the package accordingly.

2 1

[cl-debian] Processed: notfound 427220 in 1:20070409-3
by owner＠bugs.debian.org 27 Jun '07

27 Jun '07

Processing commands for control(a)bugs.debian.org: > notfound 427220 1:20070409-3 Bug#427220: slime - FTBFS: /usr/bin/texi2dvi: etex exited with bad status, quitting. Bug marked as not found in version 1:20070409-3. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)

1 0

[cl-debian] [ann] [drakma-announce] New version 0.8.0 (Was: Two problems with cookies expiry dates format)
by Edi Weitz 25 Jun '07

25 Jun '07

On Tue, 19 Jun 2007 22:56:26 +0200, Didier Verna <didier(a)lrde.epita.fr> wrote: > I've run into 2 formats that parse-cookie-date can't currently handle: > > - the first one looks like this: "Sun, 18 Jun 2006 04:01:09 > GMT-07:00" I presume it means GMT minus 7 hours. > > - the second one is almost one of the recognized formats, except > that it says PDT (Pacific Daylight Time AFAIK) instead of GMT. > > Note that I have no idea if these formats are standard or not. I > just ran into them... The latest release 0.8.0 should hopefully be able to parse these dates correctly. Note that I've also added a special variable so you can allow Drakma to fail when parsing cookie dates. Still, I'd prefer if people would report any date format Drakma can't parse to this mailing list. Thanks for the report, Edi. _______________________________________________ drakma-announce mailing list drakma-announce(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/drakma-announce _______________________________________________ announcements site list announcements(a)common-lisp.net http://common-lisp.net/mailman/listinfo/announcements

1 0