Your message dated Tue, 08 Aug 2006 11:59:32 -0600
with message-id <[EMAIL PROTECTED]>
and subject line WNPP bug closing
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: wnpp
Severity: wishlist
Owner: "René van Bevern" <[EMAIL PROTECTED]>
* Package name : cl-clg
Version : 0.90
Upstream Author : Espen S. Johnsen
* URL : http://sf.net/projects/clg
* License : LGPL, MIT
Description : GTK and Glade bindings for Common Lisp
CLG provides bindings to GTK 2.6 and Glade in a Lisp-like manner. There
are other GTK bindings for Common Lisp, all of them which have some
disadvantages IMHO:
cl-clg: Supports GTK 2.6, works fine on CMUCL, needs modifications to
SBCLs FFI to support callbacks. The second issue is about to be
solved, at least there are discussions and work on the SBCL
development mailinglist about including these modifications.
cl-gtk: Supports GTK 2.0, not as recent as CLG and talks down a pipe to
a daemon like CLM. Tricky to build on recent CMUCL and SBCL.
lambda-gtk: Suffers from the same problem als cl-clg, but its interface
is not very lisp-alike at all.
lgtk: lacks a lot of GTK 2.0 functionality, resembles the C-API as
much as possible (imho a downside)
cl-clg comes with example programs and the whole GTK test suite
translated to CL, as well as an GTK based inspector. It cleanly compiles
with CMUCL and SBCL from unstable (after the FFI modifications that
are to be found http://jupiter.td.org.uit.no/lisp/sbcl-0.8.21-af.tar.gz
and could also be packaged)
René
--- End Message ---
--- Begin Message ---
Hello,
This is an automatic mail sent to close the ITP you have reported or
are involved with.
Your ITP wnpp bug is being closed because of the following reasons:
- It is, as of today, older than 365 days.
- It hasn't had any activity recently.
As this is an automatic procedure, it could of course have something
wrong and probably it would be closing some bugs that are not
intended by owners and submitters (like you) to be closed, for
example if the ITP is still of your interest, or there has been
some kind of activity around it. In that case, please reopen the
bug, do it, DO IT NOW! (I don't want to be blamed because of
mass closing and not let people know that they can easily reopen
their bugs ;-).
To re-open it, you simply have to mail [EMAIL PROTECTED]
with a body text like this:
reopen 316237
thanks bts
Further comments on the work done in the bug sent to
[EMAIL PROTECTED] would be truly welcomed.
Anyway, if you have any kind of problems when dealing with
the BTS, feel free to contact me and I'd be more than happy to help
you on this: <[EMAIL PROTECTED]>.
A similar process is being applied to other kind of wnpp bugs.
Thanks for your cooperation,
-- David Moreno Garza <[EMAIL PROTECTED]>.
--- End Message ---
