Your message dated Thu, 25 Feb 2010 20:30:57 +0100
with message-id <87wry1un7y....@turtle.gmx.de>
and subject line Re: Bug#571467: fails to install
has caused the Debian Bug report #571467,
regarding emacs23: fails to install
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.)
--
571467: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs23
Version: 23.1+1-6
Severity: grave
Justification: renders package unusable
Trying to install emacs23 (but also emacs23-nox, emacs23-lucid and all the
emacs22*) I get this error:
In debian-run-directories:
debian-startup.el:131:25:Warning: `mapcar' called for effect; use `mapc' or
`dolist' instead
Wrote /usr/share/emacs23/site-lisp/debian-startup.elc
install/gtk-doc-tools: Handling install for emacsen flavor emacs23
cp: cannot stat `*.el': No such file or directory
emacs-install: /usr/lib/emacsen-common/packages/install/gtk-doc-tools emacs23
failed at /usr/lib/emacsen-common/emacs-install line 28, <TSORT> line 11.
dpkg: error processing emacs23 (--configure):
subprocess installed post-installation script returned error exit status 1
And the installation fails.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (990, 'unstable'), (750, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages emacs23 depends on:
ii emacs23-bin-common 23.1+1-6 The GNU Emacs editor's shared, arc
ii install-info 4.13a.dfsg.1-5 Manage installed documentation in
ii libasound2 1.0.22-2 shared library for ALSA applicatio
ii libatk1.0-0 1.28.0-1 The ATK accessibility toolkit
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii libcairo2 1.8.10-1 The Cairo 2D vector graphics libra
ii libdbus-1-3 1.2.20-2 simple interprocess messaging syst
ii libfontconfig1 2.8.0-2 generic font configuration library
ii libfreetype6 2.3.11-1 FreeType 2 font engine, shared lib
ii libgif4 4.1.6-9 library for GIF images (library)
ii libglib2.0-0 2.22.4-1 The GLib library of C routines
ii libgpm2 1.20.4-3.3 General Purpose Mouse - shared lib
ii libgtk2.0-0 2.18.7-1 The GTK+ graphical user interface
ii libice6 2:1.0.6-1 X11 Inter-Client Exchange library
ii libjpeg62 6b-16.1 The Independent JPEG Group's JPEG
ii libm17n-0 1.5.5-1 a multilingual text processing lib
ii libncurses5 5.7+20090803-2 shared libraries for terminal hand
ii libotf0 0.9.10-1 A Library for handling OpenType Fo
ii libpango1.0-0 1.26.2-1 Layout and rendering of internatio
ii libpng12-0 1.2.42-2 PNG library - runtime
ii librsvg2-2 2.26.0-1 SAX-based renderer library for SVG
ii libsm6 2:1.1.1-1 X11 Session Management library
ii libtiff4 3.9.2-3+b1 Tag Image File Format (TIFF) libra
ii libx11-6 2:1.3.3-1 X11 client-side library
ii libxft2 2.1.14-1 FreeType-based font drawing librar
ii libxpm4 1:3.5.8-1 X11 pixmap library
ii libxrender1 1:0.9.5-1 X Rendering Extension client libra
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
emacs23 recommends no packages.
Versions of packages emacs23 suggests:
ii emacs23-common-non-dfsg 23.1+1-1 GNU Emacs shared, architecture ind
-- no debconf information
--- End Message ---
--- Begin Message ---
On 2010-02-25 20:11 +0100, Leandro Noferini wrote:
> It was missing /usr/share/emacs/site-lisp/gtk-doc-tools/gtk-doc.el (from
> gtk-doc-tools package).
>
> Copying this file from the gtk-doc-tools package emacs23 installed normally.
This is what I had suspected. As this is not a problem in emacs23, I'm
closing the bug. If you can find out why the file had gone AWOL, please
reopen the bug and reassign it to the right package if necessary. But I
suspect that it's a glitch local to your site that cannot be reproduced.
Sven
--- End Message ---