Your message dated Wed, 08 Nov 2006 00:17:32 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#397529: fixed in slib 3a4-4
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: slib
Version: 3a4-3
Example:
$ mzscheme
Welcome to MzScheme version 352, Copyright (c) 2004-2006 PLT Scheme Inc.
> (load "/usr/share/slib/init/DrScheme.init")
/usr/share/slib/require.scm:27:4: define: not allowed in an expression context
in: (define slib:features *features*)
=== context ===
repl-loop
>
This appears to relate to the code added to require.scm in slib 3a4-3:
;;;; Accommodate scm versions < 5e3 which set *features* but not
;;;; slib:features
;;;; -- [EMAIL PROTECTED], 10/24/2006
(if (and (eq? (scheme-implementation-type) 'SCM)
(not (defined? slib:features)))
(define slib:features *features*))
There's really no way this can work in general. Even if it were to be
written as something like
(if ...
(begin
(define ...)))
to make it valid Scheme, it would produce a definition local to the
scope of the 'begin'.
At least in the case of SCM, particular SCM versions are rather closely
tied to corresponding SLIB versions (5e2 needs 3a3, 5e3 needs 3a4)
partly because SLIB 'require' support is integrated into SCM. You may
have noticed that Aubrey Jaffer has tended to release new versions of
both SCM and SLIB simultaneously for some time now. Other Schemes
should work with various SLIB versions.
I don't know if it's worth trying to make SCM versions before 5e3 work
with SLIB 3a4. I'd suggest maybe just adjusting the package
dependencies to keep SCM 5e2 and SLIB 3a3 together, and SCM 5e3 and SLIB
3a4 together, and not try to hack backward compatibility into SLIB for
earlier SCM versions.
--- End Message ---
--- Begin Message ---
Source: slib
Source-Version: 3a4-4
We believe that the bug you reported is fixed in the latest version of
slib, which is due to be installed in the Debian FTP archive:
slib_3a4-4.diff.gz
to pool/main/s/slib/slib_3a4-4.diff.gz
slib_3a4-4.dsc
to pool/main/s/slib/slib_3a4-4.dsc
slib_3a4-4_all.deb
to pool/main/s/slib/slib_3a4-4_all.deb
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.
Thomas Bushnell, BSG <[EMAIL PROTECTED]> (supplier of updated slib 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: Wed, 8 Nov 2006 00:06:50 -0800
Source: slib
Binary: slib
Architecture: source all
Version: 3a4-4
Distribution: unstable
Urgency: medium
Maintainer: Thomas Bushnell, BSG <[EMAIL PROTECTED]>
Changed-By: Thomas Bushnell, BSG <[EMAIL PROTECTED]>
Description:
slib - Portable Scheme library
Closes: 397529
Changes:
slib (3a4-4) unstable; urgency=medium
.
* Medium urgency because this fixes a release critical bug.
.
* require.scm: Revert change from 3a4-2.
* debian/control (slib): Conflict with scm (<< 5e3). (Closes: #397529)
Files:
3ee04e9cd11ed1f34f6008fc2b5bfee0 556 devel optional slib_3a4-4.dsc
5973cc3ece7c350b9981c659610755c0 11885 devel optional slib_3a4-4.diff.gz
f1a42ca8d9c2db348cc300769cae528f 887060 devel optional slib_3a4-4_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFFUZErqMsB9b6fcOoRAhnsAJ96TxdpwE0cfw/7jdYyR2iXiwDHZwCfV6x8
QxZkTheVlsGzN0odrKcops8=
=hYyM
-----END PGP SIGNATURE-----
--- End Message ---
