cl-asdf postinstall script hangs: SYSTEM-SOURCE-FILE is undefined
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cl-asdf (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: cl-asdf
When trying to install cl-asdf 20091221-1 on lucid.
=======
Setting up cl-asdf (1:20091221-1) ...
Reinstalling for clisp
Recompiling Common Lisp Controller for clisp
Installing clc...
;; Loading file /usr/lib/
;; Loading file /usr/share/
;; Loaded file /usr/share/
;; Loading file /var/cache/
;; Loaded file /var/cache/
;; Loading file /var/cache/
;; Loaded file /var/cache/
;; Loading file /var/cache/
;; Loaded file /var/cache/
;; Loading file /var/cache/
;; Loaded file /var/cache/
;; Loaded file /usr/lib/
;; Wrote the memory image into /usr/lib/
created /usr/lib/
-rw-r--r-- 1 root root 3292836 2010-02-27 16:32 /usr/lib/
Done rebuilding
Reinstalling for ecl
Recompiling Common Lisp Controller for ecl
/usr/lib/
;;; Loading "/usr/lib/
;;; Loading #P"/usr/
;;; Loading #P"/usr/
Saving to new-ecl...
;;; Loading "/var/cache/
;;; Loading "/var/cache/
The function SYSTEM-SOURCE-FILE is undefined.
Available restarts:
1. (QUIT-DEBUGGER) Quit debugger level 1.
2. (ABORT) ABORT
Top level.
ASDF>
=======
The restarts don't seem to have any effect. Entering either 1 or 2
does not do anything. The only way out is to SIGINT
(ctrl-c). Configuration is reported as failed by aptitude. There is a
CPU intensive ecl-original process that gets spawned and is not
killed. Since the configuration is retried each time aptitude is run
these ecl-original processes accumulate and eventually dominate the
CPU.
I experience the exact same bug.