[cl-debian] Bug#397026: cmucl: package does not install in etch

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:

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 0xbe000000, len 1048576; got mapping at 0xa7d11000 insteadensur e_space: Failed to validate 1048576 bytes at 0xbe000000 FAILED ... Your kernel is broken see bug 360561: Kernel: Linux 2.6.17-2-686
This problem is fixed in the 2.6.18 kernel. 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|

Your message dated Thu, 28 Jun 2007 21:26:28 +0200 with message-id <46840B64.6090208@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)
participants (3)
-
commi
-
owner@bugs.debian.org
-
Peter Van Eynde