Your message dated Mon, 4 Apr 2011 17:17:02 +0200
with message-id <20110404151702.ga4...@agmartin.aq.upm.es>
and subject line Re: works fine here (amd64)
has caused the Debian Bug report #617501,
regarding clisp does not run, claims to be missing a required file
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
617501: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Package: clisp
Version: 1:2.49-3+b1
Justification: renders package unusable
Severity: grave
*** Please type your report below this line ***
Running clisp from the command line with no arguments gives the
following error:
/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 file or directory.
After this the program terminates. Downgrading to stable (1:2.48-3)
fixes the problem.
I am not familiar with the code for this package, but I suspect that the
error is due to the spelling "buildd" (two d's) in the line referenced
in the error message.
- Anne
- -- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages clisp depends on:
ii libc6 2.11.2-13 Embedded GNU C Library:
Shared lib
ii libffcall1 1.10+cvs20100619-2 Foreign Function Call Libraries
ii libncurses5 5.8-1 shared libraries for
terminal hand
ii libreadline5 5.2-7 GNU readline and history
libraries
ii libsigsegv2 2.9-2 Library for handling page
faults i
clisp recommends no packages.
Versions of packages clisp suggests:
pn clisp-dev <none> (no description available)
pn clisp-doc <none> (no description available)
pn gdb <none> (no description available)
pn slime <none> (no description available)
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk13fIsACgkQwi82URPCSX4aIQCfUOShMUk7d6Clj8J63V+Ocims
kI8AnA2eU2sfIWjNq8QFiaaL0Wsgk+d7
=6GK5
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Version: 1:2.49-4
On Mon, Apr 04, 2011 at 03:57:03PM +0200, Christoph Egger wrote:
>
> Hi Agustin!
>
> Just tried in a clean unstable chroot environment and on my desktop
> system. Both of them don't seem to exhibit the problem you
> describe. Which architecture did you run for this test?
Hi,
Retried with the same result, until I noticed that 'dpkg -s lispinit.mem'
shows /usr/lib/clisp-2.49/base/lispinit.mem as indeed shipped by clisp-2.49-4.
Tried to find it under /usr/lib/clisp-2.49/base and was not there. I have
reinstalled clisp-2.49-4 and now it is there and problem no longer appears.
I am pretty sure I did not play with that dir, so I do not understand when
and why that file disappeared.
Anyway, I am closing this bug report since after reinstallation I cannot
reproduce it any longer.
Thanks for your help and sorry for the noise.
--
Agustin
--- End Message ---
