On Tuesday 22 November 2005 05:04, Robin Verduijn wrote: > Package: clisp > Version: 2.35-8 > Severity: important > > The clisp package contains an invalid symbolic link: > /usr/lib/clisp/base/lispinit.mem --> ../full/lispinit.mem ... > It seems like simply renaming lispinit-orig.mem to lispinit.mem in the > packaging should do the trick, unless I'm missing something. >
Well. During configuration, clisp uses the -orig file to load and install common-lisp-controller and then priduce the lispinit.mem file. But be aware the common-lisp-controller before version 4.26 would not correctly propagate a failure to configure back to dpkg, so the packaging system might think clisp got configured while in fact it did not. Could you try to run /usr/sbin/register-common-lisp-implementation "clisp" as root and report the generated output? Does it still fail after this? 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 UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
