Subject: clisp: dpkg warning: unable to delete old directory `/usr/lib/clisp...
From: Luca Capello <[email-masked]>
To: Debian Bug Tracking System <[email-masked]>
Date: Mon, 29 Oct 2007 01:14:15 +0100

Package: clisp
Version: 1:2.42-3
Severity: normal

Hello,

I think the title and the output below speaks for himself:
=====
luca@gismo:~$ sudo apt-get install clisp
[...]

Selecting previously deselected package libsigsegv0.
(Reading database ... 94277 files and directories currently installed.)
Unpacking libsigsegv0 (from .../libsigsegv0_2.4-4_amd64.deb) ...
Preparing to replace clisp 1:2.41-2 (using .../clisp_1%3a2.42-3_amd64.deb) ...
Unpacking replacement clisp ...
dpkg: warning - unable to delete old directory `/usr/lib/clisp/full': Directory not empty
dpkg: warning - unable to delete old directory `/usr/lib/clisp': Directory not empty
Setting up libsigsegv0 (2.4-4) ...
Setting up clisp (1:2.42-3) ...
Installing clc...
;; Loading file /usr/lib/clisp-2.42/install-clc.lisp ...
;;  Loading file /usr/share/common-lisp/source/common-lisp-controller/common-lisp-controller.lisp ...
;;  Loaded file /usr/share/common-lisp/source/common-lisp-controller/common-lisp-controller.lisp
;;  Loading file /var/cache/common-lisp-controller/0/clisp/common-lisp-controller/common-lisp-controller.fas ...
;;  Loaded file /var/cache/common-lisp-controller/0/clisp/common-lisp-controller/common-lisp-controller.fas
;;  Loading file /var/cache/common-lisp-controller/0/clisp/asdf/asdf.fas ...
;;  Loaded file /var/cache/common-lisp-controller/0/clisp/asdf/asdf.fas
;;  Loading file /var/cache/common-lisp-controller/0/clisp/asdf/wild-modules.fas ...
;;  Loaded file /var/cache/common-lisp-controller/0/clisp/asdf/wild-modules.fas
;;  Loading file /var/cache/common-lisp-controller/0/clisp/common-lisp-controller/post-sysdef-install.fas ...
;;  Loaded file /var/cache/common-lisp-controller/0/clisp/common-lisp-controller/post-sysdef-install.fas
;; Loaded file /usr/lib/clisp-2.42/install-clc.lisp
created /usr/lib/clisp-2.42/full/lispinit.mem as expected.
-rw-r--r-- 1 root root 5167424 Oct 28 22:20 /usr/lib/clisp-2.42/full/lispinit.mem

luca@gismo:~$ ls /usr/lib/ | grep clisp
clisp
clisp-2.42

luca@gismo:~$ ls -R /usr/lib/clisp
/usr/lib/clisp:
full

/usr/lib/clisp/full:
lispinit.mem
luca@gismo:~$
=====

This obviously means that the sysadmin should manually remove the
/usr/lib/clisp folder, which should be a policy violation IIRC (but I
cannot find the relevant paragraph right now and this is why Severity:
is normal).

Is there any particular reason for clisp_2.42 to be installed in
/usr/lib/clisp-2.42 instead of /usr/lib/clisp?  Do we want to support
installations of more than one clisp version?

Thx, bye,
Gismo / Luca

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.23-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages clisp depends on:
ii  common-lisp-controller    6.12           Common Lisp source and compiler ma
ii  libc6                     2.6.1-6        GNU C Library: Shared libraries
ii  libice6                   2:1.0.4-1      X11 Inter-Client Exchange library
ii  libncurses5               5.6+20071013-1 Shared libraries for terminal hand
ii  libreadline5              5.2-3          GNU readline and history libraries
ii  libsigsegv0               2.4-4          Library for handling page faults i
ii  libsm6                    2:1.0.3-1+b1   X11 Session Management library
ii  libx11-6                  2:1.0.3-7      X11 client-side library
ii  libxau6                   1:1.0.3-2      X11 authorisation library
ii  libxext6                  1:1.0.3-2      X11 miscellaneous extension librar
ii  libxpm4                   1:3.5.7-1      X11 pixmap library

clisp recommends no packages.

-- no debconf information