Your message dated Sat, 08 Jul 2006 07:10:51 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#323274: fixed in sbcl 1:0.9.14.0-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: sbcl
Version: 1:0.9.3.0-2
Severity: wishlist
[*] Introduction
Today, I was trying to use SLIME's `slime-edit-definition', in order to
learn a bit more about what is defined in SBCL. However, on a number of
forms, when I tried to view their definitions, SBCL produced messages like
Error: Source filename not recorded for ...
That was so, on
(DEFGENERIC STREAM-LINE-COLUMN)
(METHOD STREAM-LINE-COLUMN (FUNDAMENTAL-CHARACTER-OUTPUT-STREAM))
Yet, for
(METHOD STREAM-LINE-COLUMN (SWANK-BACKEND::SLIME-OUTPUT-STREAM))
SBCL is able to determine where that method is defined -- presumably, given
that the sources for that method's definition are available on the local
system, and given that the code would have been compiled with an DEBUG
OPTIMIZE of quality 2 or greater [incidental ref: SBCL manual, Source
Location Availability], and given the nature of it, a method definition,
such that the source location would be recoded, for it.
[*] The Request
I do not mean to ask overmuch, but if there would be an opportunity that the
SBCL sources would be made available in a Debian package, and if SBCL -- in
its availability with Debian -- would be available as being compiled, with
such an OPTIMIZE DEBUG proclamation that SBCL would record the source
defintions of appropriate forms, then I am sure it would be of help, for
many users of SBCL (at the very least, for our becoming acquainted with the
SBCL source-code)
Though I realize that I may try to address this request, directly upon the
Debian source package for SBCL, yet it might take me some while, as to
produce anything useful of it. Also, I would only be able to address it for
x86 architectures.
Regardless, I have thought that this should be addressed as a wishlist item,
about the Debian SBCL release.
While I realize that it would probably result in some change in the
performance of SBCL, if it would be compiled with such a DEBUG quality as
would be needed for it to record source locations, yet it may be
of use, to who would intend to see the definition of a form, within the SBCL
sources. As such, it may be of help, towards the continuing development of
SBCL.
[*] Addressing Attendant Concerns
If it would serve to ease any concern about performance, then to have the
matter brought to any reader's attention: Anyone might derive a package for a
particularly optimized SBCL, deriving the package upon the Debian SBCL
packages -- editing the debian/* files, as to adapt the commands for the
compilation, and to adjust package-names, in order to avoid naming conflicts
-- then, of course, running debuild and/or any more of the
pacakge-buiding tools.
Hopefully, such would not result in a bewildering array of SBCL packags, but
hey, "what can one say".
Thank you.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i586)
Kernel: Linux 2.6.11.8
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages sbcl depends on:
ii common-lisp-controller 4.12 This is a Common Lisp source and c
ii libc6 2.3.5-3 GNU C Library: Shared libraries an
ii sbcl-common 1:0.8.21.16-2 Architecture independent files for
-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: sbcl
Source-Version: 1:0.9.14.0-1
We believe that the bug you reported is fixed in the latest version of
sbcl, which is due to be installed in the Debian FTP archive:
sbcl-doc_0.9.14.0-1_all.deb
to pool/main/s/sbcl/sbcl-doc_0.9.14.0-1_all.deb
sbcl-source_0.9.14.0-1_all.deb
to pool/main/s/sbcl/sbcl-source_0.9.14.0-1_all.deb
sbcl_0.9.14.0-1.diff.gz
to pool/main/s/sbcl/sbcl_0.9.14.0-1.diff.gz
sbcl_0.9.14.0-1.dsc
to pool/main/s/sbcl/sbcl_0.9.14.0-1.dsc
sbcl_0.9.14.0-1_i386.deb
to pool/main/s/sbcl/sbcl_0.9.14.0-1_i386.deb
sbcl_0.9.14.0.orig.tar.gz
to pool/main/s/sbcl/sbcl_0.9.14.0.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Peter Van Eynde <[EMAIL PROTECTED]> (supplier of updated sbcl package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sat, 1 Jul 2006 00:07:41 +0200
Source: sbcl
Binary: sbcl sbcl-source sbcl-doc
Architecture: source all i386
Version: 1:0.9.14.0-1
Distribution: unstable
Urgency: low
Maintainer: Peter Van Eynde <[EMAIL PROTECTED]>
Changed-By: Peter Van Eynde <[EMAIL PROTECTED]>
Description:
sbcl - A Common Lisp compiler and development system
sbcl-doc - Documentation for Steel Bank Common Lisp
sbcl-source - Source code files for SBCL
Closes: 323274
Changes:
sbcl (1:0.9.14.0-1) unstable; urgency=low
.
[René van Bevern]
.
* debian/install-clc.lisp: unify logical pathname translations for
"SYS:SRC;**;*.*.*" and "SYS:CONTRIB;**;*.*.*" to "SYS:**;*.*.*" and
fix with that the missing "contrib/" part in the SYS:CONTRIB
translation. All source definitions are accessible now, this Closes:
#323274
.
* Split the package sbcl-common to sbcl-doc and sbcl-source, so that the
rather big source code does not need to be installed with the small
documentation. Also make sbcl-doc include the "SBCL Internals" book
.
+ debian/control:
- build-depend on graphviz and gs-gpl, because the
SBCL Internals documentation wants to draw graphs with "dot" and
convert them with Ghostscript
.
- declare sbcl-source and sbcl-doc packages, make SBCL description
point at them
.
+ debian/sbcl-common.doc-base split to debian/sbcl-doc.doc-base.sbcl,
debian/sbcl-doc.doc-base.sbcl-internals, debian/sbcl-doc.doc-base.asdf
.
+ debian/rules
- install source to sbcl-source and documentation to sbcl-doc
- build, install and make clean "SBCL Internals" documentation
.
+ debian/sbcl-common.dirs split into sbcl-doc.dirs and sbcl-source.dirs
.
+ debian/sbcl-common.postinst, debian/sbcl-common.prerm: removed,
handled by dh_installdocs
.
+ debian/control: build-depend on graphviz and gs-gpl, because the
SBCL Internals documentation wants to draw graphs with "dot" and
convert them with Ghostscript
.
* sbcl-run is not intented for usage by end-users. It is used by the
SBCL package to execute SBCL binary files with binfmt-misc only and
pollutes the $PATH namespace
.
+ debian/rules: do not install manual-page for sbcl-run, install
sbcl-run to /usr/lib/sbcl instead of /usr/bin
.
+ debian/binfmt: point to /usr/lib/sbcl/sbcl-run as interpreter
.
[ Peter Van Eynde ]
* Move asdf.info and .pdf to cl-asdf package
* New upstream
* also clean up ./doc/internals/sbcl-internals.cps
* move -doc and -source package to doc section
Files:
cbb94ce075195e7f0dd78702015bb5c2 707 devel optional sbcl_0.9.14.0-1.dsc
138560ff32a7e231e143d888358f72a0 3523854 devel optional
sbcl_0.9.14.0.orig.tar.gz
525bbe286eb3d9d2a6a0983878898d1c 420642 devel optional sbcl_0.9.14.0-1.diff.gz
58cc92ec572ead4147215a0b41ce1ce3 1210982 doc optional
sbcl-doc_0.9.14.0-1_all.deb
6ffaf5c269fe7fb9d41190d6f1813cb0 3173076 doc optional
sbcl-source_0.9.14.0-1_all.deb
0957a8f675473d7b3b0eddb09f374c26 8361364 devel optional
sbcl_0.9.14.0-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEpiI/11ldN0tyliURAtNtAKCWfEzUBqw3vPdYOVSzes+Ts4IQ4QCfap8H
F+5qBCwQl11/qUIZoEiX0IY=
=+cxK
-----END PGP SIGNATURE-----
--- End Message ---
