From edi at agharta.de  Mon Oct  1 08:08:46 2007
From: edi at agharta.de (Edi Weitz)
Date: Mon, 01 Oct 2007 10:08:46 +0200
Subject: [cl-debian] [ann] [drakma-announce] New release 0.11.0 (Was: Drakma
	and content-type)
In-Reply-To: <5aea26870709301426h406f328cx98eb845d1788fbc9@mail.gmail.com>
	(Peter Eddy's message of "Sun, 30 Sep 2007 17:26:33 -0400")
References: <5aea26870709301426h406f328cx98eb845d1788fbc9@mail.gmail.com>
Message-ID: <uprzz2r5d.fsf@agharta.de>

On Sun, 30 Sep 2007 17:26:33 -0400, "Peter Eddy" <peter.eddy at gmail.com> wrote:

> I've spent some time today converting some code (cl-s3) to use
> drakma instead of s-http-client. In the process, one thing I thought
> might be useful in drakma is a caller-defined way of indicating that
> the content type is text or not. For example, a function like the
> following passed to (http-request)
>
> (defun text-content-type-p (type subtype) ..)
>
> Or perhaps some table of text content types defined as a special
> var. I know the caller could implement this themselves, but it seems
> like doing so might require the re-implementation of portions of
> http-request that deal with the charset and chunked incoding
> (i.e. the code within (when (and (string-equal type "text").
>
> Do you think this makes sense, or am I'm missing something?

[Please use the mailing list to discuss Drakma.]

Yes, that sounds like a reasonable request and I was planning to add
something like that anyway.  Please check if the new release provides
what you need.

Cheers,
Edi.
_______________________________________________
drakma-announce mailing list
drakma-announce at common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/drakma-announce
_______________________________________________
announcements site list
announcements at common-lisp.net
http://common-lisp.net/mailman/listinfo/announcements


From nowhere.man at levallois.eu.org  Tue Oct  2 15:31:38 2007
From: nowhere.man at levallois.eu.org (Pierre THIERRY)
Date: Tue, 2 Oct 2007 17:31:38 +0200
Subject: [cl-debian] [RFS] Batch of packages
In-Reply-To: <20070930232259.GK8000@(none)>
References: <20070930232259.GK8000@(none)>
Message-ID: <20071002153138.GS8000@(none)>

Scribit Pierre THIERRY dies 01/10/2007 hora 01:22:
> But the main part is getting Vecto into Debian.

I uploaded to mentors.d.n the new upstream versions for Vecto and
Salza-PNG.

Quickly,
Pierre
-- 
nowhere.man at levallois.eu.org
OpenPGP 0xD9D50D8A
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071002/ef29cc7c/attachment.sig>

From pvaneynd at debian.org  Wed Oct  3 06:17:04 2007
From: pvaneynd at debian.org (Peter Van Eynde)
Date: Wed, 03 Oct 2007 06:17:04 +0000
Subject: [cl-debian] Accepted cl-asdf 1.109-2 (source all)
Message-ID: <E1IcxXc-00050B-Bc@ries.debian.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 27 Sep 2007 05:42:20 +0200
Source: cl-asdf
Binary: cl-cclan cl-asdf
Architecture: source all
Version: 1.109-2
Distribution: unstable
Urgency: low
Maintainer: Peter Van Eynde <pvaneynd at debian.org>
Changed-By: Peter Van Eynde <pvaneynd at debian.org>
Description: 
 cl-asdf    - Another System Definition Facility
 cl-cclan   - Comprehensive Common Lisp Archive Network
Closes: 436129
Changes: 
 cl-asdf (1.109-2) unstable; urgency=low
 .
   * stop trying to dump the package, use the package name instead.
     (Closes: #436129)
Files: 
 31f95227f67edb551db49f7f247b6b31 748 devel optional cl-asdf_1.109-2.dsc
 5b80fe3719301663a01dd59d18b2359e 14106 devel optional cl-asdf_1.109-2.diff.gz
 85166e4119e6b1a057fbbe6dd8b42111 223472 devel optional cl-asdf_1.109-2_all.deb
 c3413fb5acef70a9615b7dfc7e6f8853 20824 devel optional cl-cclan_1.109-2_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFG/BQF11ldN0tyliURAh1nAKDAwi4OdVqxVzdyM+rerLa3Mlz1ZQCgg67d
HG3D2I6nISE90JuzD8nFabc=
=jxuA
-----END PGP SIGNATURE-----


Accepted:
cl-asdf_1.109-2.diff.gz
  to pool/main/c/cl-asdf/cl-asdf_1.109-2.diff.gz
cl-asdf_1.109-2.dsc
  to pool/main/c/cl-asdf/cl-asdf_1.109-2.dsc
cl-asdf_1.109-2_all.deb
  to pool/main/c/cl-asdf/cl-asdf_1.109-2_all.deb
cl-cclan_1.109-2_all.deb
  to pool/main/c/cl-asdf/cl-cclan_1.109-2_all.deb




From pvaneynd at debian.org  Wed Oct  3 06:17:05 2007
From: pvaneynd at debian.org (Peter Van Eynde)
Date: Wed, 03 Oct 2007 06:17:05 +0000
Subject: [cl-debian] Accepted slime 1:20070927-1 (source all)
Message-ID: <E1IcxXd-00050f-JZ@ries.debian.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue, 02 Oct 2007 23:59:03 +0200
Source: slime
Binary: cl-swank slime
Architecture: source all
Version: 1:20070927-1
Distribution: unstable
Urgency: low
Maintainer: Peter Van Eynde <pvaneynd at debian.org>
Changed-By: Peter Van Eynde <pvaneynd at debian.org>
Description: 
 cl-swank   - Superior LISP Interaction Mode for Emacs (Lisp-side server)
 slime      - Superior LISP Interaction Mode for Emacs
Closes: 433802
Changes: 
 slime (1:20070927-1) unstable; urgency=low
 .
   * New upstream with fixes and a new contrib directory.
   * Also add contrib to load-path.
   * Use the upstream asd file as it works well with clc now.
   * This version also fixes the CMUCL crash on disconnect (Closes: #433802)
Files: 
 b0dcc30cb386e22d5f0640873e6dc323 759 devel optional slime_20070927-1.dsc
 b5ced1c6bdac87f2bce949cc04f28cd0 584183 devel optional slime_20070927.orig.tar.gz
 f6df92e2496a3af5919846e659847bc6 11711 devel optional slime_20070927-1.diff.gz
 787618f1282cc1b95b1eeb16c717caeb 777100 devel optional slime_20070927-1_all.deb
 528dc88f3c7b1586a94cb32c7d90d957 376448 devel optional cl-swank_20070927-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHAsA211ldN0tyliURAh+OAKCyezmZcDKbCG1WYPXlpYTuZ0VdvgCdF4zl
9ZSwH2CtR6dgqTWi0lKtu50=
=vxNg
-----END PGP SIGNATURE-----


Accepted:
cl-swank_20070927-1_all.deb
  to pool/main/s/slime/cl-swank_20070927-1_all.deb
slime_20070927-1.diff.gz
  to pool/main/s/slime/slime_20070927-1.diff.gz
slime_20070927-1.dsc
  to pool/main/s/slime/slime_20070927-1.dsc
slime_20070927-1_all.deb
  to pool/main/s/slime/slime_20070927-1_all.deb
slime_20070927.orig.tar.gz
  to pool/main/s/slime/slime_20070927.orig.tar.gz




From owner at bugs.debian.org  Wed Oct  3 06:24:04 2007
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Wed, 03 Oct 2007 06:24:04 +0000
Subject: [cl-debian] Bug#436129: marked as done ("Object #<"ASDF" package>
 cannot be externalized." when installing ecl)
References: <E1IcxXc-00050D-CS@ries.debian.org>
	<20070805160246.7396.70839.reportbug@suse.uxul.homelinux.org>
Message-ID: <handler.436129.D436129.11913925141327.ackdone@bugs.debian.org>

Your message dated Wed, 03 Oct 2007 06:17:04 +0000
with message-id <E1IcxXc-00050D-CS at ries.debian.org>
and subject line Bug#436129: fixed in cl-asdf 1.109-2
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)

-------------- next part --------------
An embedded message was scrubbed...
From: css <css at swissjabber.ch>
Subject: "Object #<"ASDF" package> cannot be externalized." when installing ecl
Date: Sun, 05 Aug 2007 18:02:46 +0200
Size: 2766
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071003/340d3c21/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Peter Van Eynde <pvaneynd at debian.org>
Subject: Bug#436129: fixed in cl-asdf 1.109-2
Date: Wed, 03 Oct 2007 06:17:04 +0000
Size: 3285
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071003/340d3c21/attachment-0001.mht>

From owner at bugs.debian.org  Wed Oct  3 06:24:03 2007
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Wed, 03 Oct 2007 06:24:03 +0000
Subject: [cl-debian] Bug#433802: marked as done (cl-swank: Slime crashes
 CMUCL on disconnect)
References: <E1IcxXd-00050h-KX@ries.debian.org>
	<20070719135020.25185.98527.reportbug@ponder.ncipher.com>
Message-ID: <handler.433802.D433802.11913925141291.ackdone@bugs.debian.org>

Your message dated Wed, 03 Oct 2007 06:17:05 +0000
with message-id <E1IcxXd-00050h-KX at ries.debian.org>
and subject line Bug#433802: fixed in slime 1:20070927-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)

-------------- next part --------------
An embedded message was scrubbed...
From: Mark Wooding <mdw at distorted.org.uk>
Subject: cl-swank: Slime crashes CMUCL on disconnect
Date: Thu, 19 Jul 2007 14:50:20 +0100
Size: 3174
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071003/10c49931/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Peter Van Eynde <pvaneynd at debian.org>
Subject: Bug#433802: fixed in slime 1:20070927-1
Date: Wed, 03 Oct 2007 06:17:05 +0000
Size: 3635
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071003/10c49931/attachment-0001.mht>

From pvaneynd at debian.org  Wed Oct  3 06:32:06 2007
From: pvaneynd at debian.org (Peter Van Eynde)
Date: Wed, 03 Oct 2007 06:32:06 +0000
Subject: [cl-debian] Accepted sbcl 1:1.0.10.0-1 (source all i386)
Message-ID: <E1IcxmA-0005Q1-Rq@ries.debian.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 27 Sep 2007 22:32:05 +0200
Source: sbcl
Binary: sbcl sbcl-source sbcl-doc
Architecture: source all i386
Version: 1:1.0.10.0-1
Distribution: unstable
Urgency: low
Maintainer: Peter Van Eynde <pvaneynd at debian.org>
Changed-By: Peter Van Eynde <pvaneynd at debian.org>
Description: 
 sbcl       - A Common Lisp compiler and development system
 sbcl-doc   - Documentation for Steel Bank Common Lisp
 sbcl-source - Source code files for SBCL
Changes: 
 sbcl (1:1.0.10.0-1) unstable; urgency=low
 .
   * New upstream version. Major changes:
      + new feature: SB-CLTL2 contrib module now implements
        FUNCTION-INFORMATION. (thanks to Larry D'Anna)
      + optimization: scavenging weak pointers is now more efficient,
        requiring O(1) instead of O(N) per weak pointer to identify
        scanvenged vs. unscavenged pointers. (thanks to Paul Khuong)
      + optimization: typechecking (SETF SLOT-VALUE) is now ~5x faster in
        method bodies using constant slot-names when the first argument is
        a specializer parameter for the method.
      + optimization: SLOT-VALUE &co are now ~50% faster for variable slot
        names, when the class of the instance is a direct instance
        STANDARD-CLASS or FUNCALLABLE-STANDARD-CLASS (making them only 3x
        as slow as the constant slot-name case.)
      + optimization: member type construction is now O(N) instead
        of O(N^2).
      + optimization: UNION and NUNION are now O(N+M) for large
        inputs as long as the :TEST function is one of EQ, EQL, EQUAL, or
        EQUALP.
      + enhancement: DEFINE-MODIFY-MACRO lambda-list information is
        now more readable in environments like Slime which display it.
        (thanks to Tobias C. Rittweiler)
      + bug fix: SB-EXT:COMPARE-AND-SWAP was non-atomic unless the compiler
        was able to infer the correct argument type for the object on which
        the CAS operation was being performed.
      + bug fix: copy propagation interfered with parallel assignment
        semantics in local calls. (reported by Paul Khuong)
      + bug fix: the signed modular fixnum shift compiled to wrong code on
        x86 and x86-64.  (spotted by a slight modification to some of
        PFD's random tests)
Files: 
 12317b4c125bad9af4f572cb5d6c13db 800 devel optional sbcl_1.0.10.0-1.dsc
 dd2d403ddb90c8712b6b9150ca4ad3d4 4616528 devel optional sbcl_1.0.10.0.orig.tar.gz
 0954f0800d9ede8fb1cbe1b1229096d8 34632 devel optional sbcl_1.0.10.0-1.diff.gz
 c392432a9d8c8dda64efde281165bc1a 1563216 doc optional sbcl-doc_1.0.10.0-1_all.deb
 42e6366bbc89665da2c87fb1ee5dfd3a 3887108 doc optional sbcl-source_1.0.10.0-1_all.deb
 7a220d6f57d21b2df8ca81b048811364 9047826 devel optional sbcl_1.0.10.0-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFG/HEA11ldN0tyliURAmecAJwM6v71K1eWeCKy9DDClytgDkU89ACfdvig
82m0FSu+VQSs1MTGmt5y5Us=
=XfBS
-----END PGP SIGNATURE-----


Accepted:
sbcl-doc_1.0.10.0-1_all.deb
  to pool/main/s/sbcl/sbcl-doc_1.0.10.0-1_all.deb
sbcl-source_1.0.10.0-1_all.deb
  to pool/main/s/sbcl/sbcl-source_1.0.10.0-1_all.deb
sbcl_1.0.10.0-1.diff.gz
  to pool/main/s/sbcl/sbcl_1.0.10.0-1.diff.gz
sbcl_1.0.10.0-1.dsc
  to pool/main/s/sbcl/sbcl_1.0.10.0-1.dsc
sbcl_1.0.10.0-1_i386.deb
  to pool/main/s/sbcl/sbcl_1.0.10.0-1_i386.deb
sbcl_1.0.10.0.orig.tar.gz
  to pool/main/s/sbcl/sbcl_1.0.10.0.orig.tar.gz




From pvaneynd at mailworks.org  Wed Oct  3 07:13:27 2007
From: pvaneynd at mailworks.org (Peter Van Eynde)
Date: Wed, 03 Oct 2007 09:13:27 +0200
Subject: [cl-debian] Bug#382430: c-l-c installation of ecl does things wrong
In-Reply-To: <653bea160608101444o6eaea720p9e5ad9a5fe370691@mail.gmail.com>
References: <653bea160608101444o6eaea720p9e5ad9a5fe370691@mail.gmail.com>
Message-ID: <47034117.3060109@mailworks.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Far?,

It took some time but I finally had a moment to look at the issues.

Far? wrote:
> (1) it uses the c-l-c version of asdf and not the ecl-provided one from

I almost fixed the 'official' asdf to support all the features the ecl
provided one has. I think having a 'special' asdf for ecl is asking for
compatibility problems.

> (2) it somehow gets cmp.fas and sysfun.lsp to systematically load verbosely
> in a way that isn't hushed up by flag -q resulting in an unremovable banner

This after some searching turns out to be caused because
common-lisp-controller.lisp uses the function 'compile-file'. As the clc
enabled ecl includes this it causes these messages:

> ;;; Loading #P"/usr/lib/ecl/cmp.fas"
> ;;; Loading #P"/usr/lib/ecl/sysfun.lsp"

I'm currently investigation how to fix this.

> (3) compiling configuration files everytime can be a performance issue,
> in addition to requiring to load the compiler. 

I'm not so certain what configuration files you're referring to here.

Groetjes, Peter

- --
signature -at- pvaneynd.mailworks.org
http://www.livejournal.com/users/pvaneynd/
"God, root, what is difference?" Pitr | "God is more forgiving." Dave
Aronson|

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHA0EV11ldN0tyliURAh9CAJ9kvvsI0PXRHNI+JOCnW2U0Q9U1cACgyaSs
CCYgIep6DCR0Ag1xPVzOZy8=
=STi4
-----END PGP SIGNATURE-----





From fahree at gmail.com  Wed Oct  3 13:54:54 2007
From: fahree at gmail.com (=?UTF-8?Q? Far=C3=A9 ?=)
Date: Wed, 3 Oct 2007 09:54:54 -0400
Subject: [cl-debian] Bug#382430: c-l-c installation of ecl does things wrong
In-Reply-To: <47034117.3060109@mailworks.org>
References: <653bea160608101444o6eaea720p9e5ad9a5fe370691@mail.gmail.com>
	<47034117.3060109@mailworks.org>
Message-ID: <653bea160710030654q195dbee0h9da69bc66a9b9096@mail.gmail.com>

Dear Peter,

On 03/10/2007, Peter Van Eynde <pvaneynd at mailworks.org> wrote:
> It took some time but I finally had a moment to look at the issues.
Thanks!

> Far? wrote:
> > (1) it uses the c-l-c version of asdf and not the ecl-provided one from
>
> I almost fixed the 'official' asdf to support all the features the ecl
> provided one has. I think having a 'special' asdf for ecl is asking for
> compatibility problems.
>
That's a valid fix indeed. Now introducing maintenance problems instead :-)

>> (2) it somehow gets cmp.fas and sysfun.lsp to systematically load verbosely
>> in a way that isn't hushed up by flag -q resulting in an unremovable banner
>
> This after some searching turns out to be caused because
> common-lisp-controller.lisp uses the function 'compile-file'. As the clc
> enabled ecl includes this it causes these messages:
>
> > ;;; Loading #P"/usr/lib/ecl/cmp.fas"
> > ;;; Loading #P"/usr/lib/ecl/sysfun.lsp"
>
> I'm currently investigation how to fix this.
>
Can't you use a :verbose nil option when loading these files, and/or
set *load-verbose* to nil?

> > (3) compiling configuration files everytime can be a performance issue,
> > in addition to requiring to load the compiler.
>
> I'm not so certain what configuration files you're referring to here.
>
I admit I don't remember anymore :-(
Maybe I was thinking of sysfun.lsp.
Maybe tracing compile-file will tell you.

<subliminal>cl-launch</subliminal>

[ Fran?ois-Ren? ?VB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
To this, I shall add one more example: the victim controls the torturer,
becauses if the victim screams very loudly at a particular method of torture,
this is the method the torturer will select to use.
        -- Ayn Rand, expounding behaviorist pseudo-psychology,
        in "Philosophy: Who Needs It?", "The Stimulus and the Response"





From erick at fsl.org.mx  Wed Oct  3 19:04:45 2007
From: erick at fsl.org.mx (Erick Lopez Carreon)
Date: Wed, 03 Oct 2007 14:04:45 -0500
Subject: [cl-debian] Bug#445174: slime 20070927-1 --configure error
Message-ID: <1191438285.4013.22.camel@localhost.cibercalli.com>

Package: slime
Version: 1:20070927-1
Severity: important

Hello Peter:

I just try to upgrade my slime to the 20070927-1 version, and i'm
getting this error in the configuration part of installation:

------------------------------------------------------------------------
Wrote /usr/share/emacs21/site-lisp/slime/contrib/slime-typeout-frame.elc
While compiling toplevel forms in
file /usr/share/emacs21/site-lisp/slime/contrib/slime-xref-browser.el:
  !! File error (("Cannot open load file" "tree-widget"))
Done
emacs-package-install: /usr/lib/emacsen-common/packages/install/slime
emacs21 emacs21 emacs22 failed
at /usr/lib/emacsen-common/emacs-package-install line 30, <TSORT> line
2.
dpkg: error processing slime (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 slime

------------------------------------------------------------------------

I get the same error on two different machines.

And dpkg -s slime says:

------------------------------------------------------------------------
Package: slime
Status: install ok half-configured
Priority: optional
Section: devel
Installed-Size: 1840
Maintainer: Peter Van Eynde <pvaneynd at debian.org>
Architecture: all
Version: 1:20070927-1
Config-Version: 1:20070628-1
------------------------------------------------------------------------

Because of this i can't start slime in emacs22, emacs22 says:

------------------------------------------------------------------------
Debugger entered--Lisp error: (file-error "Cannot open load file"
"slime")
  require(slime)
  eval-buffer(#<buffer  *load*> nil "/home/foo/.emacs" nil t)  ; Reading
at buffer position 512
  load-with-code-conversion("/home/foo/.emacs" "/home/foo/.emacs" t t)
  load("~/.emacs" t t)
  #[nil "" [init-file-user system-type user-init-file-1 user-init-file
otherfile source ms-dos "~" "/_emacs" windows-nt directory-files nil "^\
\.emacs\\(\\.elc?\\)?$" "~/.emacs" "^_emacs\\(\\.elc?\\)?$" "~/_emacs"
vax-vms "sys$login:.emacs" "/.emacs" t load expand-file-name "init"
file-name-as-directory "/.emacs.d" file-name-extension "elc"
file-name-sans-extension ".el" file-exists-p file-newer-than-file-p
message "Warning: %s is newer than %s" sit-for 1 "default" alt
inhibit-default-init inhibit-startup-message] 7]()
command-line()
  normal-top-level()
------------------------------------------------------------------------

In emacs21 slime works well.   :-?

------------------------------------------------------------------------
; SLIME 2007-09-27
CL-USER> 
------------------------------------------------------------------------

Could be something wrong with my ~/.emacs?



I am using 
- Debian GNU/Linux Sid 
- Architecture: i386 (i686)
- Kernel 2.6.18
- slime 1:20070927-1
- sbcl 1:1.0.10.0-1
- emacs21 21.4a+1-5.1
- emacs22 22.1+1-2

Thank you.










From pvaneynd at mailworks.org  Thu Oct  4 07:18:09 2007
From: pvaneynd at mailworks.org (Peter Van Eynde)
Date: Thu, 04 Oct 2007 09:18:09 +0200
Subject: [cl-debian] Bug#445174: slime 20070927-1 --configure error
In-Reply-To: <1191438285.4013.22.camel@localhost.cibercalli.com>
References: <1191438285.4013.22.camel@localhost.cibercalli.com>
Message-ID: <470493B1.9090708@mailworks.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Erick,

Erick Lopez Carreon wrote:
>   !! File error (("Cannot open load file" "tree-widget"))

What do I see in the ChangeLog:

        * tree-widget.el: File deleted. Only needed by contribs and is
        distributed with Emacs 21.

So something is not right. I'll check this.

Groetjes, Peter

- --
signature -at- pvaneynd.mailworks.org
http://www.livejournal.com/users/pvaneynd/
"God, root, what is difference?" Pitr | "God is more forgiving." Dave
Aronson|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHBJOv11ldN0tyliURAtFhAKCZ7gUFlWfoEiCy1qoE4Lcjr51prACguzwr
tWHXHy8CJPnVRYsLPxqN18E=
=elkC
-----END PGP SIGNATURE-----





From pvaneynd at debian.org  Thu Oct  4 07:32:03 2007
From: pvaneynd at debian.org (Peter Van Eynde)
Date: Thu, 04 Oct 2007 07:32:03 +0000
Subject: [cl-debian] Accepted slime 1:20070927-2 (source all)
Message-ID: <E1IdLBj-0002sf-TG@ries.debian.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 04 Oct 2007 09:09:47 +0200
Source: slime
Binary: cl-swank slime
Architecture: source all
Version: 1:20070927-2
Distribution: unstable
Urgency: low
Maintainer: Peter Van Eynde <pvaneynd at debian.org>
Changed-By: Peter Van Eynde <pvaneynd at debian.org>
Description: 
 cl-swank   - Superior LISP Interaction Mode for Emacs (Lisp-side server)
 slime      - Superior LISP Interaction Mode for Emacs
Closes: 445174
Changes: 
 slime (1:20070927-2) unstable; urgency=low
 .
   * Readded tree-widget to the sources. emacs21 on
     debian does _not_ have that file. emacs22 and xemacs do.
     (Closes: #445174)
Files: 
 6641a51bd978b3c2d12d8d8299a611dd 759 devel optional slime_20070927-2.dsc
 39efda1e445942aff98ebd3dc52d85c4 18486 devel optional slime_20070927-2.diff.gz
 d254dbecc0223a08003429bc59ad506c 783862 devel optional slime_20070927-2_all.deb
 860ffdb230ec7a908c9b23f9f074ac00 376508 devel optional cl-swank_20070927-2_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHBJL211ldN0tyliURAoPsAJ9HiOx96f2AZLpAm4MzbkOjYeUFTACfSjfT
kCRGZpcAr/kUwn5l0TPJwvY=
=n2NI
-----END PGP SIGNATURE-----


Accepted:
cl-swank_20070927-2_all.deb
  to pool/main/s/slime/cl-swank_20070927-2_all.deb
slime_20070927-2.diff.gz
  to pool/main/s/slime/slime_20070927-2.diff.gz
slime_20070927-2.dsc
  to pool/main/s/slime/slime_20070927-2.dsc
slime_20070927-2_all.deb
  to pool/main/s/slime/slime_20070927-2_all.deb




From owner at bugs.debian.org  Thu Oct  4 07:43:35 2007
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Thu, 04 Oct 2007 07:43:35 +0000
Subject: [cl-debian] Bug#445174: marked as done (slime 20070927-1 --configure
	error)
References: <E1IdLBj-0002sh-Tz@ries.debian.org>
	<1191438285.4013.22.camel@localhost.cibercalli.com>
Message-ID: <handler.445174.D445174.119148346910412.ackdone@bugs.debian.org>

Your message dated Thu, 04 Oct 2007 07:32:03 +0000
with message-id <E1IdLBj-0002sh-Tz at ries.debian.org>
and subject line Bug#445174: fixed in slime 1:20070927-2
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)

-------------- next part --------------
An embedded message was scrubbed...
From: Erick Lopez Carreon <erick at fsl.org.mx>
Subject: slime 20070927-1 --configure error
Date: Wed, 03 Oct 2007 14:04:45 -0500
Size: 4041
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071004/0dc77c7e/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Peter Van Eynde <pvaneynd at debian.org>
Subject: Bug#445174: fixed in slime 1:20070927-2
Date: Thu, 04 Oct 2007 07:32:03 +0000
Size: 3379
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071004/0dc77c7e/attachment-0001.mht>

From ingvar at hexapodia.net  Thu Oct  4 17:18:14 2007
From: ingvar at hexapodia.net (Ingvar Mattsson)
Date: Thu, 04 Oct 2007 18:18:14 +0100
Subject: [cl-debian] Bug#445299: slime: No LIST-ASDF-SYSTEMS in the SWANK
	package
Message-ID: <20071004171814.30981.15247.reportbug@head.hexapodia.net>

Package: slime
Version: 1:20070927-2
Severity: important

With the new "contrib-based", pluggable SLIME architecture, there seems
to be some out-of-sync problems between SLIME and SWANK.

A possible solution (I haven't carefully read what SLIEM is expecting, 
so this is more a sketch than a patch) would be something like:
 (loop for name being the hash-keys of asdf::*defined-systems*
       collect name)

If I load the slime-asdf extension and try to do ,load-system, this is the
result:
--- Emacs message
byte-code: Lisp connection closed unexpectedly
Lisp connection closed unexpectedly: exited abnormally with code 256
--- From *inferior-lisp*
READ: "(:emacs-rex (swank:list-asdf-systems) \"COMMON-LISP-USER\" :repl-thread 10)
"
;; Event history end.
;; Backtrace:
(0 [error printing frame])
(1 [error printing frame])
(2 [error printing frame])
(3 [error printing frame])
(4 [error printing frame])
(5 [error printing frame])
(6 [error printing frame])
(7 [error printing frame])
(8 [error printing frame])
(9 [error printing frame])
(10 [error printing frame])
(11 [error printing frame])
(12 [error printing frame])
(13 [error printing frame])
(14 (COMMON-LISP:READ-FROM-STRING "(:emacs-rex (swank:list-asdf-systems) \"COMMON-LISP-USER\" :repl-thread 10)
" T NIL :START 0 :END NIL :PRESERVE-WHITESPACE NIL))
(15 ((COMMON-LISP:LAMBDA NIL)))
(16 [error printing frame])
(17 [error printing frame])
(18 (SWANK::READ-FROM-SOCKET-IO))
(19 (SWANK::READ-FROM-EMACS))
(20 ((COMMON-LISP:LAMBDA NIL)))
(21 [error printing frame])
(22 [error printing frame])
(23 [error printing frame])
(24 [error printing frame])
(25 [error printing frame])
(26 ((COMMON-LISP:FLET SWANK::HANDLER)))
(27 [error printing frame])
(28 (SB-IMPL::SUB-SERVE-EVENT NIL NIL NIL))
(29 (SB-SYS:WAIT-UNTIL-FD-USABLE 0 :INPUT NIL))
(30 [error printing frame])
(31 [error printing frame])
(32 [error printing frame])
(33 [error printing frame])
(34 [error printing frame])
(35 [error printing frame])
(36 [error printing frame])
(37 [error printing frame])
(38 (SB-IMPL::REPL-FUN NIL))
(39 (SB-IMPL::REPL-FUN NIL))
(40 ((COMMON-LISP:LAMBDA NIL)))
(41 ((COMMON-LISP:LAMBDA NIL)))
(42 [error printing frame])
(43 (SB-IMPL::TOPLEVEL-REPL NIL))
(44 (SB-IMPL::TOPLEVEL-INIT))
(45 ((COMMON-LISP:LABELS SB-IMPL::RESTART-LISP)))
;; Connection to Emacs lost. [
;;  condition: SB-INT:SIMPLE-READER-PACKAGE-ERROR at 36 (line 1, column 36) on #<SB-IMPL::STRING-INPUT-STREAM {AB265F1}>:
  Symbol "LIST-ASDF-SYSTEMS" not found in the SWANK package.
;;  type: SB-INT:SIMPLE-READER-PACKAGE-ERROR
;;  encoding: NIL style: :FD-HANDLER dedicated: NIL]


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages slime depends on:
ii  cl-swank                    1:20070927-2 Superior LISP Interaction Mode for
ii  emacsen-common              1.4.17       Common facilities for all emacsen

Versions of packages slime recommends:
ii  emacs21 [info-browser]      21.4a+1-5.1  The GNU Emacs editor
ii  info [info-browser]         4.8.dfsg.1-6 Standalone GNU Info documentation 

-- no debconf information





From pvaneynd at mailworks.org  Thu Oct  4 19:25:56 2007
From: pvaneynd at mailworks.org (Peter Van Eynde)
Date: Thu, 04 Oct 2007 21:25:56 +0200
Subject: [cl-debian] Bug#445299: slime: No LIST-ASDF-SYSTEMS in the SWANK
	package
In-Reply-To: <20071004171814.30981.15247.reportbug@head.hexapodia.net>
References: <20071004171814.30981.15247.reportbug@head.hexapodia.net>
Message-ID: <47053E44.4020409@mailworks.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Ingvar,

Ingvar Mattsson wrote:
> With the new "contrib-based", pluggable SLIME architecture, there seems
> to be some out-of-sync problems between SLIME and SWANK.

Here I was thinking I had fixed most of them :-(.

> If I load the slime-asdf extension and try to do ,load-system, this is the
> result:
> --- Emacs message
> byte-code: Lisp connection closed unexpectedly
> Lisp connection closed unexpectedly: exited abnormally with code 256

Oh cool!

I'll investigate this further, but it could be a while before I find a
good solution...

Groetjes, Peter

- --
signature -at- pvaneynd.mailworks.org
http://www.livejournal.com/users/pvaneynd/
"God, root, what is difference?" Pitr | "God is more forgiving." Dave
Aronson|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHBT5B11ldN0tyliURArhYAKCcPQ5mGamL9H/X8DQXYt6X+UjsBgCfWnl9
y9HdoZh8FKr8q19CXGoLyJM=
=1mc5
-----END PGP SIGNATURE-----





From pvaneynd at mailworks.org  Thu Oct  4 19:25:56 2007
From: pvaneynd at mailworks.org (Peter Van Eynde)
Date: Thu, 04 Oct 2007 21:25:56 +0200
Subject: [cl-debian] Bug#445299: slime: No LIST-ASDF-SYSTEMS in the SWANK
	package
In-Reply-To: <20071004171814.30981.15247.reportbug@head.hexapodia.net>
References: <20071004171814.30981.15247.reportbug@head.hexapodia.net>
Message-ID: <47053E44.4020409@mailworks.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Ingvar,

Ingvar Mattsson wrote:
> With the new "contrib-based", pluggable SLIME architecture, there seems
> to be some out-of-sync problems between SLIME and SWANK.

Here I was thinking I had fixed most of them :-(.

> If I load the slime-asdf extension and try to do ,load-system, this is the
> result:
> --- Emacs message
> byte-code: Lisp connection closed unexpectedly
> Lisp connection closed unexpectedly: exited abnormally with code 256

Oh cool!

I'll investigate this further, but it could be a while before I find a
good solution...

Groetjes, Peter

- --
signature -at- pvaneynd.mailworks.org
http://www.livejournal.com/users/pvaneynd/
"God, root, what is difference?" Pitr | "God is more forgiving." Dave
Aronson|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHBT5B11ldN0tyliURArhYAKCcPQ5mGamL9H/X8DQXYt6X+UjsBgCfWnl9
y9HdoZh8FKr8q19CXGoLyJM=
=1mc5
-----END PGP SIGNATURE-----





From whooey1830 at web.de  Thu Oct  4 10:20:49 2007
From: whooey1830 at web.de (Brian Kudowski)
Date: Thu, 04 Oct 2007 12:20:49 +0200
Subject: [cl-debian] Bug#445241: slime: Readme.Debian seems to contain
 incorrect information
Message-ID: <20071004102049.12811.8125.reportbug@host1>

Package: slime
Version: 1:20070325-1
Severity: normal


File Readme.Debian states:
"In your [X]Emacs `use-init-file' [..]"

When i type `C-h v use-init-file  <RET>' nothing happens. It seems the
variable 'use-init-file' is not available any more.

Regards,
Brian


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages slime depends on:
ii  cl-swank                    1:20070325-1 Superior LISP Interaction Mode for
ii  emacsen-common              1.4.17       Common facilities for all emacsen

Versions of packages slime recommends:
ii  emacs [info-browser]      21.4a+1-3etch1 The GNU Emacs editor (metapackage)
ii  emacs21 [info-browser]    21.4a+1-3etch1 The GNU Emacs editor
ii  info [info-browser]       4.8.dfsg.1-4   Standalone GNU Info documentation 

-- no debconf information





From nowhere.man at levallois.eu.org  Sat Oct  6 03:55:33 2007
From: nowhere.man at levallois.eu.org (Pierre THIERRY)
Date: Sat, 6 Oct 2007 05:55:33 +0200
Subject: [cl-debian] Packages sponsoring
Message-ID: <20071006035532.GP13023@(none)>

Hi,

have anyone taken a look at the packages I uploaded to mentors.d.n? I'm
planning to work on bigger packages next, probably drakma and elephant,
and maybe CL-MIME in the meantime.

Quickly,
Pierre
-- 
nowhere.man at levallois.eu.org
OpenPGP 0xD9D50D8A
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071006/3575c79f/attachment.sig>

From ingvar at hexapodia.net  Sat Oct  6 09:07:21 2007
From: ingvar at hexapodia.net (Ingvar)
Date: Sat, 06 Oct 2007 10:07:21 +0100
Subject: [cl-debian] Bug#445299: slime: No LIST-ASDF-SYSTEMS in the SWANK
	package
In-Reply-To: <47053E44.4020409@mailworks.org>
References: <20071004171814.30981.15247.reportbug@head.hexapodia.net>
	<47053E44.4020409@mailworks.org>
Message-ID: <E1Ie5d3-0006R5-OF@head.hexapodia.net>

Here's a partial solution (still not perfect, because this only ends up 
hitting anoter missing function, SWANK:OPERATE-ON-SYSTEM-FOR-EMACS, and that 
one I haven't successfully made to work):

+(defslimefun list-asdf-systems ()
+  (loop for name being the hash-key of asdf::*defined-systems*
+        collect name))

What I (ideally) want to have back is the "load an ASDF-based system, get a 
list of warnings, errors, informational wossnames in a tree-based view, with a 
direct link to where in the source it was signalled from when that is known". 
I suspect that is a bit more than what I currently have working.

However, since it's been in previous versions, I suspect hunting down 
OPERATE-ON-SYSTEM-FOR-EMACS from there might be Just The Thing.

//Ingvar






From edi at agharta.de  Sat Oct  6 22:54:19 2007
From: edi at agharta.de (Edi Weitz)
Date: Sun, 07 Oct 2007 00:54:19 +0200
Subject: [cl-debian] [ann] [hunchentoot-announce] New release 0.14.3 (Was:
	get-gid-from-name support for SBCL)
In-Reply-To: <8E603415-893E-40FE-ABD8-5F336418D945@bobobeach.com> (Cyrus
	Harmon's message of "Sat, 6 Oct 2007 10:19:05 -0700")
References: <8E603415-893E-40FE-ABD8-5F336418D945@bobobeach.com>
Message-ID: <uy7efx3ac.fsf@agharta.de>

On Sat, 6 Oct 2007 10:19:05 -0700, Cyrus Harmon <ch-tbnl at bobobeach.com> wrote:

> The following patch implements get-gid-from-name for SBCL.
> Unfortunately, it requires SBCL 1.0.10.31 or later for sb-posix
> support for getgrnam.

Thanks.  That it's in the new release now.
_______________________________________________
tbnl-announce site list
tbnl-announce at common-lisp.net
http://common-lisp.net/mailman/listinfo/tbnl-announce
_______________________________________________
announcements site list
announcements at common-lisp.net
http://common-lisp.net/mailman/listinfo/announcements


From owner at bugs.debian.org  Sun Oct  7 23:33:06 2007
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sun, 07 Oct 2007 23:33:06 +0000
Subject: [cl-debian] Processed: Re: stumpwm: Clarify README.Debian - can't
 understand a thing how to start this wm
In-Reply-To: <87k5pyec66.fsf@gismo.pca.it>
References: <87k5pyec66.fsf@gismo.pca.it>
Message-ID: <handler.s.C.119179980914703.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> tags 356948 - help
Bug#356948: stumpwm: clarify how to start this WM in the README.Debian
Tags were: help
Tags removed: help

> tags 356948 + pending
Bug#356948: stumpwm: clarify how to start this WM in the README.Debian
There were no tags set.
Tags added: pending

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)




From luca at pca.it  Sun Oct  7 23:29:37 2007
From: luca at pca.it (Luca Capello)
Date: Mon, 08 Oct 2007 01:29:37 +0200
Subject: [cl-debian] Bug#356948: stumpwm: Clarify README.Debian - can't
 understand a thing how to start this wm
In-Reply-To: <87u06vhm6d.fsf@gismo.pca.it>
References: <20060314222747.16843.8083.reportbug@cante>
	<E1FmD53-0002F9-7z@cante> <87u06vhm6d.fsf@gismo.pca.it>
Message-ID: <87k5pyec66.fsf@gismo.pca.it>

tags 356948 - help
tags 356948 + pending
thanks

Hello!

On Thu, 08 Jun 2006 14:22:18 +0200, Luca Capello wrote:
> On Fri, 02 Jun 2006 19:05:01 +0200, Jari Aalto wrote:
>> Something is not connecting here. 
>>
>> - Aa per you explanation, the the sescription string should
>>   differentiate stumpwm from the other regular "window managers"
>>   by saing that this one is for only people that understand
>>   how to use it with common lisp.
> [...]
>> Currently
>>
>> - Description does not suggest anything to be different from
>>   standard WM
>> - README* lacks information for anyone else but CL-knowledgeable.
>
> I think that this is a problem not only for stumpwm, but for all the
> Common Lisp software.

I finally decided to provide a binary /usr/bin/stumpwm to start
StumpWM.  This has been implemented in the following darcs patch:

patch-ID: 20070925212754-f6b0c-29f0e2b5d823c5416c1281eee20c413a43d2cbb1.gz
comment:  Tue Sep 25 23:27:54 CEST 2007  Luca Capello <luca at pca.it>
            * debian/stumpwm.bin: new binary to resolve #356948

This bug will be closed with the next package upload.

Thx, bye,
Gismo / Luca





From luca at pca.it  Mon Oct  8 00:27:24 2007
From: luca at pca.it (Luca Capello)
Date: Mon, 08 Oct 2007 02:27:24 +0200
Subject: [cl-debian]
	Moving to darcs.debian.org, co-maintenance and other bits
Message-ID: <873awme9hv.fsf@gismo.pca.it>

Hi all,

I directly mailed all the people that I'm aware are involved in Common
Lisp packaging for Debian to be sure they read this mail (which is
quite long).

Don't take this mail as personal: this is just an attempt to improve
the current CL-Debian project.

1) Since Oct 4th, Alioth supports also darcs as VCS [1].  This means
   that we can move all the darcs maintained packages [2] to the
   commond darcs infrastructure, which is managed as explained at [3]:

     http://darcs.debian.org/$GROUP/$PACKAGE

   I'll start to move my packages as soon as the others keypoint
   expressed below are cleared.

2) AFAIK, at least three different VCSs are used for CL-Debian stuffs:
   bzr, darcs and git (this one especially by Kevin).  Moreover,
   Pierre has prepared his packages using mercurial [4].  For this
   reason, I think that we should ask for a $GROUP folder in all of
   the VCSs we use, similar to the collab-maint project [5].

   In this regard, I don't think we should restrict the number of VCSs
   we use: obviously, having only one VCS would be easier to learn and
   maintain, but whenever it's possible I prefer to follow upstream,
   providing that they use a distributed VCS.

   For example, all of my packages are in darcs: the upstream BESE
   ones [6] are in darcs, too, while the others upstream are in CVS.
   However, since StumpWM recently moved to git [7], I'm planning to
   follow that move for the Debian package as well, leaving darcs in
   favor of git.

3) During a private discussion between Peter and me, one idea that
   came out was to go for co-maintenance of the CL-Debian packages.
   Thus, all the people involved in the project (and registered in the
   Alioth group) would have write permission to all repositories
   within the group.

   This doesn't mean that the packages will be automagically and
   suddenly co-maintained by all of us, but that there's still a
   principal maintainer, while the others can sparely act on the
   package in case of urgency or small fixes.

   To achieve this goal, the Maintainer: field in debian/control will
   contain the mailing list address (see point 5 below), while the
   principal maintainer (with all the others involved) will end up in
   the Uploaders: field.

   In case someone would argue against this action and would preserve
   full control over his packages, I think that implementing a partial
   co-maintenance will be anyway worth it, so point 5 below stands in
   any case.

4) A further step in co-maintenance would be to allow write permission
   to DDs outside the CL-Debian project, in a way similar to the
   collab-maint one, as Stefano explained at [8].  This could be
   really useful for translators, for example.

5) Whatever we decide about a full or partial co-maintenance and since
   we're moving to 100% Alioth, we should move the mailing list as
   well.  Doing so, we should decide if we want to keep the current
   project name or change it to something similar to other packaging
   groups.  The latter includes pkg-commonlisp (or pkg-cl or what
   else) or simply Common Lisp team (thus common-lisp as the project
   name).

   Always WRT the mailing list, we can also ask for a commit mailing
   list, where all the commit to the different package archives will
   be automatically posted.  Would it be useful?

6) While searching for all the people/groups involved in Common Lisp
   and Debian, I found that clc (the Common Lisp Controller) has its
   own Alioth project [9].  Should it be incorporated into the
   CL-Debian group instead?

I hope to have missed nothing and I'm waiting for comments and
suggestions.

Thx, bye,
Gismo / Luca 

Footnotes: 
[1] http://lists.debian.org/debian-devel-announce/2007/10/msg00002.html
[2] http://cl-debian.alioth.debian.org/repositories/
[3] http://wiki.debian.org/Alioth/darcs
[4] http://common-lisp.net/pipermail/cl-debian/2007-September/002836.html
[5] http://alioth.debian.org/projects/collab-maint/
[6] http://common-lisp.net/project/bese/
[7] http://lists.gnu.org/archive/html/stumpwm-devel/2007-09/msg00003.html
[8] http://www.bononia.it/~zack/blog//posts/2007/08/DD_wide_commit_on_alioth.html
[9] http://alioth.debian.org/projects/clc/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071008/9c4b70d6/attachment.sig>

From nowhere.man at levallois.eu.org  Mon Oct  8 03:02:08 2007
From: nowhere.man at levallois.eu.org (Pierre THIERRY)
Date: Mon, 8 Oct 2007 05:02:08 +0200
Subject: [cl-debian] Moving to darcs.debian.org, co-maintenance and
	other bits
In-Reply-To: <873awme9hv.fsf@gismo.pca.it>
References: <873awme9hv.fsf@gismo.pca.it>
Message-ID: <20071008030208.GS13023@(none)>

Scribit Luca Capello dies 08/10/2007 hora 02:27:
> obviously, having only one VCS would be easier to learn and maintain,
> but whenever it's possible I prefer to follow upstream, providing that
> they use a distributed VCS.

In my case, it's not to follow upstream that I use Mercurial (most of my
upstreams don't have any VCS...), it's merely because it's the VCS I
know very well by using it for my everyday work.

> This doesn't mean that the packages will be automagically and suddenly
> co-maintained by all of us, but that there's still a principal
> maintainer, while the others can sparely act on the package in case of
> urgency or small fixes.

While I wouldn't really see an issue in having all repositories writable
by the whole group, I'd just note that it's not all that needed if we
mostly use DCVSes.

In any case, I suppose that it would be good to have a minimal set of
rules about where commits go. I would prefer that each package (or group
of packages when they share a repo...) have some main repo where there
is only history of code actually going into Debian. That is,
modifications committed for the maintainers of the package to review
would go in a separate repo, whereas an urgent fix for which there is a
package uploaded by a DD should go in that main repo.

Clear (read: written) rules about who can upload would also probably be
good (i.e. that everyone can write in the repos won't necessarily mean
every DD should upload the package...)

Not that I would mind that anyone upload any of my packages at the
moment. ;-)

> I think that implementing a partial co-maintenance will be anyway
> worth it,

I suppose each package under co-maintainance would be a gain, even for a
small fraction of the CL packages in Debian.

> A further step in co-maintenance would be to allow write permission to
> DDs outside the CL-Debian project

Inbox repos could be a good thing here, I'd say.

> This could be really useful for translators, for example.

And targetted inbox repos here.

> 5) Whatever we decide about a full or partial co-maintenance

As it is a matter of control, I'd suggest to be conservative and make
that an opt-in. If everyone wants to do it, that's great, but if that's
not the case, we avoid any possible conflict.

> we should move the mailing list as well

+1

> we should decide if we want to keep the current project name

I'd vote for debian-lisp or pkg-cl (a short name might prove handy...).

> Always WRT the mailing list, we can also ask for a commit mailing
> list, where all the commit to the different package archives will be
> automatically posted.  Would it be useful?

Depends on the traffic, I suppose. Let's try!

> I found that clc (the Common Lisp Controller) has its own Alioth
> project

It doesn't seem to be really used: no BTS, no tasks, no lists. So I'd
say we host clc in the pkg-cl project.

Gladly,
Pierre
-- 
nowhere.man at levallois.eu.org
OpenPGP 0xD9D50D8A
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071008/021e524c/attachment.sig>

From geraud_meyer at hotmail.com  Mon Oct  8 17:54:53 2007
From: geraud_meyer at hotmail.com (=?UTF-8?Q?G=C3=A9raud?= Meyer)
Date: Mon, 08 Oct 2007 19:54:53 +0200
Subject: [cl-debian] Bug#445863: bashism in
	/usr/lib/emacsen-common/packages/install/slime
Message-ID: <470A6EED.5010302@hotmail.com>

Package: slime
Version: 1:20070927-2
Severity: normal

sh points to dash and the following is displayed during an installation
(with apt):

    $ apt install <something>
    ...
    install/slime: Handling install for emacsen flavor emacs21
    [: 44: ==: unexpected operator
    rm: cannot remove `/usr/share/emacs21/site-lisp/slime/ChangeLog': No
such file or directory
    [: 55: ==: unexpected operator
    Loading 00debian-vars...
    ...
    $ grep -C3 == /usr/lib/emacsen-common/packages/install/slime
   
    # in case of a failed installation .el symlinks are left behind,
remove them
    if [ -d "${ELCDIR}" ] ; then
      if [ "${ELCDIR}" == "" ] ; then
        echo ELCDIR is empty, emergency stop
        exit 1
      else
    --
    fi
   
    if [ -d "${ELCDIR}/contrib" ] ; then
      if [ "${ELCDIR}" == "" ] ; then
        echo ELCDIR is empty, emergency stop
        exit 1
      else

== is not an operator for /usr/bin/[. It is one for the bash keyword [[.
[ after an if in bash probably also is interpreted directly by bash.







From nowhere.man at levallois.eu.org  Tue Oct  9 15:56:29 2007
From: nowhere.man at levallois.eu.org (Pierre THIERRY)
Date: Tue, 9 Oct 2007 17:56:29 +0200
Subject: Bug#445863: [cl-debian] Bug#445863: bashism in
	/usr/lib/emacsen-common/packages/install/slime
In-Reply-To: <470A6EED.5010302@hotmail.com>
References: <470A6EED.5010302@hotmail.com>
Message-ID: <20071009155629.GX13023@(none)>

tag 445863 + patch
thanks

Scribit G?raud Meyer dies 08/10/2007 hora 19:54:
> == is not an operator for /usr/bin/[. It is one for the bash keyword [[.
> [ after an if in bash probably also is interpreted directly by bash.

The == operator seems the only bashism to me. if [ "a" = $1 ]; then ...
is perfectly accepted by dash. So the correction should just be:

diff -r 4f0b69b9911b debian/emacsen-install
--- a/debian/emacsen-install    Tue Oct 09 17:48:14 2007 +0200
+++ b/debian/emacsen-install    Tue Oct 09 17:52:57 2007 +0200
@@ -32,7 +32,7 @@ fi

 # in case of a failed installation .el symlinks are left behind, remove them
 if [ -d "${ELCDIR}" ] ; then
-  if [ "${ELCDIR}" == "" ] ; then
+  if [ "${ELCDIR}" = "" ] ; then
     echo ELCDIR is empty, emergency stop
     exit 1
   else

Quickly,
Pierre
-- 
nowhere.man at levallois.eu.org
OpenPGP 0xD9D50D8A
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071009/11cf6011/attachment.sig>

From owner at bugs.debian.org  Tue Oct  9 16:00:04 2007
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Tue, 09 Oct 2007 16:00:04 +0000
Subject: Processed: Re: [cl-debian] Bug#445863: bashism in
	/usr/lib/emacsen-common/packages/install/slime
In-Reply-To: <20071009155629.GX13023@(none)>
References: <20071009155629.GX13023@(none)>
Message-ID: <handler.s.C.119194541413347.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> tag 445863 + patch
Bug#445863: bashism in /usr/lib/emacsen-common/packages/install/slime
There were no tags set.
Tags added: patch

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)




From luca at pca.it  Tue Oct  9 19:58:07 2007
From: luca at pca.it (Luca Capello)
Date: Tue, 09 Oct 2007 21:58:07 +0200
Subject: [cl-debian] Moving to darcs.debian.org,
	co-maintenance and other bits
References: <873awme9hv.fsf@gismo.pca.it> <20071008030208.GS13023@(none)>
Message-ID: <87y7ecm568.fsf@gismo.pca.it>

Hello!

I'm sorry, another long post :-)

On Mon, 08 Oct 2007 05:02:08 +0200, Pierre THIERRY wrote:
> Scribit Luca Capello dies 08/10/2007 hora 02:27:
>> obviously, having only one VCS would be easier to learn and
>> maintain, but whenever it's possible I prefer to follow upstream,
>> providing that they use a distributed VCS.
>
> In my case, it's not to follow upstream that I use Mercurial (most
> of my upstreams don't have any VCS...), it's merely because it's the
> VCS I know very well by using it for my everyday work.

As I said, at the end it's a matter of taste.  The message I wanted to
pass was that I don't see the point in having one VCS to rule the
others, since most of the time the basic commands are quite simple.

>> This doesn't mean that the packages will be automagically and
>> suddenly co-maintained by all of us, but that there's still a
>> principal maintainer, while the others can sparely act on the
>> package in case of urgency or small fixes.
>
> While I wouldn't really see an issue in having all repositories
> writable by the whole group, I'd just note that it's not all that
> needed if we mostly use DCVSes.

Read below below ;-)

> In any case, I suppose that it would be good to have a minimal set
> of rules about where commits go. I would prefer that each package
> (or group of packages when they share a repo...) have some main repo
> where there is only history of code actually going into Debian.

Fully ACK.

> That is, modifications committed for the maintainers of the package
> to review would go in a separate repo, whereas an urgent fix for
> which there is a package uploaded by a DD should go in that main
> repo.

And this main repository needs to be writable by at least the DDs that
upload it.  The general idea behind co-maintenance is not package
hijacking, but mostly overcome those situations when the maintainer is
busy, on holidays or, even worse, not responsive.

> Clear (read: written) rules about who can upload would also probably
> be good (i.e. that everyone can write in the repos won't necessarily
> mean every DD should upload the package...)

This is another point: we should distinguish between DDs involved in
the CL-Debian project and any DDs outside it.  While the former should
be able to upload any package from the project [1][2], the
latter should be avoided if the modifications touch the package code.

> Not that I would mind that anyone upload any of my packages at the
> moment. ;-)

I read your post, but while I'm indeed a DD since Aug 4th, I still
cannot upload, because only my old and lost GPG key has been included
in the Debian keyring (see the thread at [3]).  So, I'm waiting for
the new GPG key to be included in the Debian keyring as well.

>> I think that implementing a partial co-maintenance will be anyway
>> worth it,
>
> I suppose each package under co-maintainance would be a gain, even
> for a small fraction of the CL packages in Debian.

Fully ACK.

>> A further step in co-maintenance would be to allow write permission
>> to DDs outside the CL-Debian project
>
> Inbox repos could be a good thing here, I'd say.
>
>> This could be really useful for translators, for example.
>
> And targetted inbox repos here.

Are you proposing something like the following?

  $PACKAGE
    =>  repository that gives origin to the Debian package

  $PACKAGE.upstream
    =>  upstream repository (this is probably specific to darcs, but
        it's just to give an idea)

  $PACKAGE.contrib
    =>  repository for people outside the CL-Debian project, where
        patches can be submitted for peer-review

If most of our repositories use DVCSs, however, I don't see how the
latter would be so different from a patch in the BTS (which is where
I'd like to receive all the patches or notifications, even if other
people can commit).

>> 5) Whatever we decide about a full or partial co-maintenance
>
> As it is a matter of control, I'd suggest to be conservative and
> make that an opt-in. If everyone wants to do it, that's great, but
> if that's not the case, we avoid any possible conflict.

Exactly, this is why after having discussed with Peter and Ren? I
wrote this mail instead of directly acting :-)

>> we should decide if we want to keep the current project name
>
> I'd vote for debian-lisp or pkg-cl (a short name might prove
> handy...).

pkg-cl-* is my preferred, too, since this syntax is the most used in
Debian.  However, grepping my /var/lib/dpkg/status for
lists.alioth.debian.org gives different results (I think I've reported
one example for all of them):

    Debian GNOME Maintainers <pkg-gnome-maintainers at ...>
    Debian GnuTLS Maintainers <pkg-gnutls-maint at ...>
    Debian Fonts Task Force <pkg-fonts-devel at ...>

    Debian XML/SGML Group <debian-xml-sgml-pkgs at ...>

    Dpatch Maintainers <dpatch-maintainers at ...>

    Debconf Developers <debconf-devel at ...>

    CDBS Hackers <build-common-hackers at ...>

If we include clc in the CL-Debian project, we not only maintain
Debian packages, but we develop software, too.  Thus, I'd say the best
name would be

    Debian Common Lisp Team <pkg-cl-devel at ...>

with the variants Force/Group.  This because I don't see the need for
two different -maintainers and -devel lists, also considering that the
actual list is low traffic.

>> Always WRT the mailing list, we can also ask for a commit mailing
>> list, where all the commit to the different package archives will
>> be automatically posted.  Would it be useful?
>
> Depends on the traffic, I suppose. Let's try!

I guess the mailing list (pkg-cl-commits) should be read-only
(i.e. only commits can be automatically posted) and without archives,
since I don't see the need of a commit archive when you've the VCS
changelog anyway.

>> I found that clc (the Common Lisp Controller) has its own Alioth
>> project
>
> It doesn't seem to be really used: no BTS, no tasks, no lists. So
> I'd say we host clc in the pkg-cl project.

Fully ACK.  Kevin, Peter, what do you think about it?

Thx, bye,
Gismo / Luca

Footnotes: 
[1] obviously, after having checked that the package reaches the
    Debian standards
[2] this won't be so different from sponsorhip and following Don's
    recommendations explained at
      http://lists.debian.org/debian-devel/2007/08/msg00531.html      
[3] http://albatross.madduck.net/pipermail/debian-unizh/2007-February/000842.html


From nowhere.man at levallois.eu.org  Wed Oct 10 22:19:55 2007
From: nowhere.man at levallois.eu.org (Pierre THIERRY)
Date: Thu, 11 Oct 2007 00:19:55 +0200
Subject: [cl-debian] Moving to darcs.debian.org, co-maintenance and
	other bits
In-Reply-To: <87y7ecm568.fsf@gismo.pca.it>
References: <873awme9hv.fsf@gismo.pca.it> <20071008030208.GS13023@(none)>
	<87y7ecm568.fsf@gismo.pca.it>
Message-ID: <20071010221955.GB13023@(none)>

Scribit Luca Capello dies 09/10/2007 hora 21:58:
> This is another point: we should distinguish between DDs involved in
> the CL-Debian project and any DDs outside it.

I would suggest the following repos, by default, for each package.  Note
that anything but the main repo is optional, and could be created on
demand. 

- debian		code actually uploaded by maintainers
- upstream		upstream code
- nmu			code uploaded by non-maintainers
- proposed		code not uplaoded, for review

At least git and hg have the ability to hardlink repository data. A
Mercurial repo can also be updated to its null revision so as not to
have a working copy (or, actaully, an empty one). So we could create
automatically a dozen of repos for each package basically at no cost
(things like nmu-l10n).

We may also have repos or tags to make it easy to track Debian releases.
It may not be equally easy for each DVCS. I read that Git makes it hard
to have moving tags, for example (and actually discourages it).

An upstream repo would only be needed if we don't use upstream's DVCS,
actually.

> If we include clc in the CL-Debian project, we not only maintain
> Debian packages, but we develop software, too.  Thus, I'd say the best
> name would be
> 
>     Debian Common Lisp Team <pkg-cl-devel at ...>

+1

> I guess the mailing list (pkg-cl-commits) should be read-only [...]
> and without archives

Yes, the only use is to be notified.

Quickly,
Pierre
-- 
nowhere.man at levallois.eu.org
OpenPGP 0xD9D50D8A
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071011/15831a90/attachment.sig>

From noreply at henning.makholm.net  Wed Oct 10 22:39:09 2007
From: noreply at henning.makholm.net (Debian testing watch)
Date: Wed, 10 Oct 2007 16:39:09 -0600
Subject: [cl-debian] libsigsegv 2.4-4 MIGRATED to testing
Message-ID: <E1IfkCr-0007iO-2p@merkel.debian.org>

FYI: The status of the libsigsegv source package
in Debian's testing distribution has changed.

  Previous version: 2.4-3
  Current version:  2.4-4

-- 
This email is automatically generated; henning at makholm.net is responsible.
See http://people.debian.org/~henning/trille/ for more information.



From noreply at henning.makholm.net  Wed Oct 10 22:39:09 2007
From: noreply at henning.makholm.net (Debian testing watch)
Date: Wed, 10 Oct 2007 16:39:09 -0600
Subject: [cl-debian] libsigsegv 2.4-4 MIGRATED to testing
Message-ID: <E1IfkCr-0007iO-2p@merkel.debian.org>

FYI: The status of the libsigsegv source package
in Debian's testing distribution has changed.

  Previous version: 2.4-3
  Current version:  2.4-4

-- 
This email is automatically generated; henning at makholm.net is responsible.
See http://people.debian.org/~henning/trille/ for more information.



From edi at agharta.de  Thu Oct 11 07:03:17 2007
From: edi at agharta.de (Edi Weitz)
Date: Thu, 11 Oct 2007 09:03:17 +0200
Subject: [cl-debian] [ann] [flexi-streams-announce] New release 0.13.1
Message-ID: <uzlyqgmkq.fsf@agharta.de>

ChangeLog:

  Version 0.13.1
  2007-10-11
  Small fix for AllegroCL's "modern" mode

Download:

  http://weitz.de/files/flexi-streams.tar.gz
_______________________________________________
flexi-streams-announce mailing list
flexi-streams-announce at common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/flexi-streams-announce
_______________________________________________
announcements site list
announcements at common-lisp.net
http://common-lisp.net/mailman/listinfo/announcements


From edi at agharta.de  Thu Oct 11 08:50:59 2007
From: edi at agharta.de (Edi Weitz)
Date: Thu, 11 Oct 2007 10:50:59 +0200
Subject: [cl-debian] [ann] [drakma-announce] New release 0.11.1 (Was: New
 releases 0.10.3 (Drakma) and 0.4.1 (Chunga))
In-Reply-To: <7c23adaa0710110143s67825b94he6d9268a524a124d@mail.gmail.com>
	(Ivan Toshkov's message of "Thu, 11 Oct 2007 11:43:10 +0300")
References: <278250439.53301191303854664.JavaMail.root@mail-101.colo.sourcelabs.com>
	<uve9egmh7.fsf@agharta.de>
	<7c23adaa0710110143s67825b94he6d9268a524a124d@mail.gmail.com>
Message-ID: <uwstunifg.fsf_-_@agharta.de>

On Thu, 11 Oct 2007 11:43:10 +0300, "Ivan Toshkov" <ivan at toshkov.org> wrote:

> Hmm, it's strange, because you've released drakma 0.11.0 on 1
> October.

Yes, sorry, S?bastien Saint-Sevin also just emailed me about this.  I
switched laptops recently and it seems I released 0.11.0 from the old
one after I had already copied my repository to the new machine.
Should be fixed now, i.e. 0.11.1 is online which includes the
additions from both 0.11.0 and "0.10.3".

Thanks to you both,
Edi.
_______________________________________________
drakma-announce mailing list
drakma-announce at common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/drakma-announce
_______________________________________________
announcements site list
announcements at common-lisp.net
http://common-lisp.net/mailman/listinfo/announcements


From noreply at henning.makholm.net  Sat Oct 13 22:39:08 2007
From: noreply at henning.makholm.net (Debian testing watch)
Date: Sat, 13 Oct 2007 16:39:08 -0600
Subject: [cl-debian] cl-asdf 1.109-2 MIGRATED to testing
Message-ID: <E1IgpdU-0000wP-54@merkel.debian.org>

FYI: The status of the cl-asdf source package
in Debian's testing distribution has changed.

  Previous version: 1.109-1
  Current version:  1.109-2

-- 
This email is automatically generated; henning at makholm.net is responsible.
See http://people.debian.org/~henning/trille/ for more information.



From noreply at henning.makholm.net  Sat Oct 13 22:39:08 2007
From: noreply at henning.makholm.net (Debian testing watch)
Date: Sat, 13 Oct 2007 16:39:08 -0600
Subject: [cl-debian] cl-asdf 1.109-2 MIGRATED to testing
Message-ID: <E1IgpdU-0000wP-54@merkel.debian.org>

FYI: The status of the cl-asdf source package
in Debian's testing distribution has changed.

  Previous version: 1.109-1
  Current version:  1.109-2

-- 
This email is automatically generated; henning at makholm.net is responsible.
See http://people.debian.org/~henning/trille/ for more information.



From noreply at henning.makholm.net  Sun Oct 14 22:39:14 2007
From: noreply at henning.makholm.net (Debian testing watch)
Date: Sun, 14 Oct 2007 16:39:14 -0600
Subject: [cl-debian] slime 1:20070927-2 MIGRATED to testing
Message-ID: <E1IhC78-0006uF-2m@merkel.debian.org>

FYI: The status of the slime source package
in Debian's testing distribution has changed.

  Previous version: 1:20070628-1
  Current version:  1:20070927-2

-- 
This email is automatically generated; henning at makholm.net is responsible.
See http://people.debian.org/~henning/trille/ for more information.



From noreply at henning.makholm.net  Sun Oct 14 22:39:14 2007
From: noreply at henning.makholm.net (Debian testing watch)
Date: Sun, 14 Oct 2007 16:39:14 -0600
Subject: [cl-debian] slime 1:20070927-2 MIGRATED to testing
Message-ID: <E1IhC78-0006uF-2m@merkel.debian.org>

FYI: The status of the slime source package
in Debian's testing distribution has changed.

  Previous version: 1:20070628-1
  Current version:  1:20070927-2

-- 
This email is automatically generated; henning at makholm.net is responsible.
See http://people.debian.org/~henning/trille/ for more information.



From igor.stirbu at gmail.com  Sun Oct 14 21:45:15 2007
From: igor.stirbu at gmail.com (Igor Stirbu)
Date: Mon, 15 Oct 2007 00:45:15 +0300
Subject: [cl-debian] Bug#446690: cl-mcclim: Failure in building mcclim
Message-ID: <20071014214515.8978.86964.reportbug@keo>

Package: cl-mcclim
Version: 0.9.5.dfsg.1-1
Severity: grave
Justification: renders package unusable


Hello,

I followed the guide [1] and ran the following command:

 (asdf:oos 'asdf:load-op :mcclim)

Here is the error message I got:

** - READ from
       #<INPUT BUFFERED FILE-STREAM CHARACTER #P"/usr/share/common-lisp/source/mcclim/Backends/CLX/port.lisp" @1289>
      : #<PACKAGE XLIB> has no external symbol with name "SET-SELECTION-OWNER"


[1] http://mcclim.cliki.net/GettingStarted

Thanks,
Igor


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (700, 'unstable'), (650, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-2-k7 (SMP w/1 CPU core)
Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages cl-mcclim depends on:
ii  cl-clx-sbcl               0.7.2-1        An X11 Common Lisp client library 
ii  cl-flexichain             1.2.dfsg.1-3   An efficient gap buffer with a wel
ii  cl-spatial-trees          0.2-1          Spatial trees Common Lisp library
ii  cl-swank                  1:20070927-2   Superior LISP Interaction Mode for
ii  cmucl-source              19d-20061116-3 The CMUCL lisp sources
ii  common-lisp-controller    6.12           Common Lisp source and compiler ma
ii  libgtk2.0-dev             2.12.0-2       Development files for the GTK+ lib

cl-mcclim recommends no packages.

-- no debconf information





From lnp at healy.washington.dc.us  Mon Oct 15 12:57:22 2007
From: lnp at healy.washington.dc.us (Liam Healy)
Date: Mon, 15 Oct 2007 08:57:22 -0400
Subject: [cl-debian] Bug#446758: slime: Lost functionality: ,l and M-tab
Message-ID: <654935030710150557u58af0f72r566fff11191f4533@mail.gmail.com>

Package: slime
Version: 1:20070927-2
Severity: normal

1) ,l (load system) is unrecognized; ,? lists the following:

Click <mouse-2> on a completion to select it.
In this buffer, type RET to select the completion near point.

Possible completions are:
!				   !d
!p				   +d
+p				   -d
-p				   ?
cd				   change-directory
change-package			   cl
compile-and-load		   defparameter
disconnect			   help
in				   in-package
pop-directory			   pop-package
popd				   push-directory
push-package			   pushd
pwd				   quit
resend-form			   restart-inferior-lisp
sayoonara

2) M-tab no longer works:
Debugger entered--Lisp error: (void-function slime-fuzzy-complete-symbol)
  slime-fuzzy-complete-symbol()
  slime-complete-symbol()
  call-interactively(slime-complete-symbol)

Both ,l and M-tab worked in the previous version.

Liam

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

Kernel: Linux 2.6.22-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 slime depends on:
ii  cl-swank                    1:20070927-2 Superior LISP Interaction Mode for
ii  emacsen-common              1.4.17       Common facilities for all emacsen

Versions of packages slime recommends:
ii  emacs21 [info-browser]  21.4a+1-5.1      The GNU Emacs editor
ii  emacs22-gtk [info-brows 22.1+1-2         The GNU Emacs editor (with GTK use
ii  info [info-browser]     4.8.dfsg.1-6     Standalone GNU Info documentation
ii  konqueror [info-browser 4:3.5.8.dfsg.1-1 KDE's advanced file manager, web b
ii  xemacs21-nomule [info-b 21.4.20-2        highly customizable text editor --

-- no debconf information





From owner at bugs.debian.org  Tue Oct 16 20:03:03 2007
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Tue, 16 Oct 2007 20:03:03 +0000
Subject: [cl-debian] Processed: Bug#446690: cl-mcclim: Failure in building
	mcclim
In-Reply-To: <87prze25jk.fsf@zamazal.org>
References: <87prze25jk.fsf@zamazal.org>
Message-ID: <handler.s.C.119256488626051.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> severity 446690 important
Bug#446690: cl-mcclim: Failure in building mcclim
Severity set to `important' from `grave'

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)




From pdm at debian.org  Tue Oct 16 20:03:05 2007
From: pdm at debian.org (Milan Zamazal)
Date: Tue, 16 Oct 2007 22:03:05 +0200
Subject: [cl-debian] Bug#446690: cl-mcclim: Failure in building mcclim
In-Reply-To: <20071014214515.8978.86964.reportbug@keo>
	(sfid-20071014_234946_995141_36E4AF9D) (Igor Stirbu's message of
	"Mon\, 15 Oct 2007 00\:45\:15 +0300")
References: <20071014214515.8978.86964.reportbug@keo>
Message-ID: <87lka225fq.fsf@zamazal.org>

>>>>> "IS" == Igor Stirbu <igor.stirbu at gmail.com> writes:

    IS>  (asdf:oos 'asdf:load-op :mcclim)

    IS> Here is the error message I got:

    IS> ** - READ from
    IS>        #<INPUT BUFFERED FILE-STREAM CHARACTER #P"/usr/share/common-lisp/source/mcclim/Backends/CLX/port.lisp" @1289>
    IS>       : #<PACKAGE XLIB> has no external symbol with name "SET-SELECTION-OWNER"

What is the Common Lisp compiler and its exact Debian version that emits
this message?

Regards,

Milan Zamazal






From luca at pca.it  Wed Oct 17 02:08:20 2007
From: luca at pca.it (Luca Capello)
Date: Wed, 17 Oct 2007 04:08:20 +0200
Subject: [cl-debian] Re: Bug#446971: ITP: zpb-exif -- Common Lisp package to
 access EXIF metadata
In-Reply-To: <20071017013231.GA24958@unige.ch>
References: <20071017013231.GA24958@unige.ch>
Message-ID: <873awaijcb.fsf@gismo.pca.it>

Hi Pierre!

Could you also X-Debbugs-CC: the CL-Debian mailing list [1] the
next ITP about CL software, please?

On Wed, 17 Oct 2007 03:32:31 +0200, Pierre THIERRY wrote:
> * Package name    : zpb-exif
[...]
> EXIF is a standard for embedding information in an image file
> created by a digital camera. ZPB-EXIF is a library that makes Exif
> data accessible to Common Lisp programs.

I'd call the binary cl-zpb-exit, similar to S-XML [2], since as far as
I understand it it's not intended to be used stand-alone.

Thx, bye,
Gismo / Luca

Footnotes: 
[1] http://cl-debian.alioth.debian.org
[2] http://packages.qa.debian.org/s/s-xml.html


From nowhere.man at levallois.eu.org  Wed Oct 17 02:17:44 2007
From: nowhere.man at levallois.eu.org (Pierre THIERRY)
Date: Wed, 17 Oct 2007 04:17:44 +0200
Subject: [cl-debian] [RFS] ZPB-EXIF
Message-ID: <20071017021743.GD14139@(none)>

Hi,

I just packaged another CL package from Xach, namely ZPB-EXIF. It's
avalaible at mentors.d.n, as usual:

http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=zpb-exif

The history of my packaging work is available as a Mercurial repository:

http://arcanes.fr.eu.org/~pierre/2007/10/zpb-exif-pkg/

Quickly,
Pierre
-- 
nowhere.man at levallois.eu.org
OpenPGP 0xD9D50D8A
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071017/c5c5c916/attachment.sig>

From nowhere.man at levallois.eu.org  Wed Oct 17 02:24:51 2007
From: nowhere.man at levallois.eu.org (Pierre THIERRY)
Date: Wed, 17 Oct 2007 04:24:51 +0200
Subject: [cl-debian] Re: Bug#446971: ITP: zpb-exif -- Common Lisp
	package to access EXIF metadata
In-Reply-To: <873awaijcb.fsf@gismo.pca.it>
References: <20071017013231.GA24958@unige.ch> <873awaijcb.fsf@gismo.pca.it>
Message-ID: <20071017022451.GE14139@(none)>

Scribit Luca Capello dies 17/10/2007 hora 04:08:
> Could you also X-Debbugs-CC: the CL-Debian mailing list [1] the next
> ITP about CL software, please?

No problem.

> I'd call the binary cl-zpb-exit,

Yes, that's what I did, as with my other packages. I try to have source
package name as close as possible as the original project name and the
binary package name beginning with "cl-".

Quickly,
Pierre
-- 
nowhere.man at levallois.eu.org
OpenPGP 0xD9D50D8A
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071017/21b13418/attachment.sig>

From luca at pca.it  Wed Oct 17 02:58:45 2007
From: luca at pca.it (Luca Capello)
Date: Wed, 17 Oct 2007 04:58:45 +0200
Subject: [cl-debian] Re: Bug#446971: ITP: zpb-exif -- Common Lisp package
	to access EXIF metadata
In-Reply-To: <20071017022451.GE14139@unige.ch>
References: <20071017013231.GA24958@unige.ch> <873awaijcb.fsf@gismo.pca.it>
	<20071017022451.GE14139@unige.ch>
Message-ID: <87y7e2h2fu.fsf@gismo.pca.it>

Hi Pierre!

On Wed, 17 Oct 2007 04:24:51 +0200, Pierre THIERRY wrote:
> Scribit Luca Capello dies 17/10/2007 hora 04:08:
>> Could you also X-Debbugs-CC: the CL-Debian mailing list [1] the
>> next ITP about CL software, please?
>
> No problem.

I guess this should be in the CL-Debian policy ;-)

>> I'd call the binary cl-zpb-exit,
>
> Yes, that's what I did, as with my other packages. I try to have
> source package name as close as possible as the original project
> name and the binary package name beginning with "cl-".

While I guessed that, I wrote it anyway to be sure (and I was too lazy
to wait for your package link and check).

Thank you for the package!

Thx, bye,
Gismo / Luca


From nowhere.man at levallois.eu.org  Wed Oct 17 13:00:56 2007
From: nowhere.man at levallois.eu.org (Pierre THIERRY)
Date: Wed, 17 Oct 2007 15:00:56 +0200
Subject: CL Policy (was Re: [cl-debian] Re: Bug#446971: ITP: zpb-exif --
	Common Lisp package to access EXIF metadata)
In-Reply-To: <87y7e2h2fu.fsf@gismo.pca.it>
References: <20071017013231.GA24958@unige.ch> <873awaijcb.fsf@gismo.pca.it>
	<20071017022451.GE14139@unige.ch> <87y7e2h2fu.fsf@gismo.pca.it>
Message-ID: <20071017130055.GF14139@(none)>

Scribit Luca Capello dies 17/10/2007 hora 04:58:
> I guess this should be in the CL-Debian policy ;-)

After discussing a bit with maintainers involved with Perl or Python
packaging, I wonder if our policy shouldn't be extended a bit and made
mandatory for Common Lisp packaging.

Being mandatory ensures packages will be consistent, which is better
both for maintainers (they know for sure where to put things and how to
name things) and users (they know fore sure where to find things and how
they would be named).

Methodoligocally,
Pierre
-- 
nowhere.man at levallois.eu.org
OpenPGP 0xD9D50D8A
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071017/1a39bdbe/attachment.sig>

From luca at pca.it  Thu Oct 18 19:52:33 2007
From: luca at pca.it (Luca Capello)
Date: Thu, 18 Oct 2007 21:52:33 +0200
Subject: [cl-debian] Moving to darcs.debian.org,
	co-maintenance and other bits
In-Reply-To: <20071010221955.GB13023@(none)> (Pierre THIERRY's message of
	"Thu\, 11 Oct 2007 00\:19\:55 +0200")
References: <873awme9hv.fsf@gismo.pca.it> <20071008030208.GS13023@(none)>
	<87y7ecm568.fsf@gismo.pca.it> <20071010221955.GB13023@(none)>
Message-ID: <87r6js19q6.fsf@gismo.pca.it>

Hi Pierre!

On Thu, 11 Oct 2007 00:19:55 +0200, Pierre THIERRY wrote:
> Scribit Luca Capello dies 09/10/2007 hora 21:58:
>> This is another point: we should distinguish between DDs involved
>> in the CL-Debian project and any DDs outside it.
>
> I would suggest the following repos, by default, for each package.
> Note that anything but the main repo is optional, and could be
> created on demand.

Fully agree, assuming that "main" means "the one from where the Debian
package is built (and uploaded).  However...

> - upstream		upstream code

This is needed for example if you work with darcs-buildpackage (and
it's called package.upstream).  I don't know anything about the others
$VCS-buildpackage tools and if anyone uses them.

> - nmu			code uploaded by non-maintainers

I'd say that NMUs patches can be directly applied to the Debian repo,
at least I won't consider them a problem at all.  This because as soon
as a package is NMUed, then Debian contains anyway the NMU patch.  So,
if the official maintainer doesn't like the patch it can revert it.
This avoids code/repo duplication, too.

> - proposed		code not uplaoded, for review

I'd prefer the patch posted to the mailing list, but this is personal.

> At least git and hg have the ability to hardlink repository data. A
> Mercurial repo can also be updated to its null revision so as not to
> have a working copy (or, actaully, an empty one). So we could create
> automatically a dozen of repos for each package basically at no cost
> (things like nmu-l10n).

Especially for l10n, if we coordinate the work with the l10n team I
see no hurt in giving them write permissions to the Debian repo
(similarly to the NMU situation I explained above).

Since we use DVCSs, people can have their personal repositories on
Alioth as public_VCS, which can be easily downloaded.  Yes, I'd prefer
less repos in the group and, if needed, more personal repos.

> We may also have repos or tags to make it easy to track Debian
> releases.

Mmm, can you elaborate on this?  I see the need for a Debian release
specific repo only in case of backports (because usually you need to
change the dependencies and maybe patch upstream).

> An upstream repo would only be needed if we don't use upstream's
> DVCS, actually.

As I already explained for darcs, the upstream repo is necessary to
use darcs-buildpackage (which is optional, but helps).

>> If we include clc in the CL-Debian project, we not only maintain
>> Debian packages, but we develop software, too.  Thus, I'd say the
>> best name would be
>> 
>>     Debian Common Lisp Team <pkg-cl-devel at ...>
>
> +1

Any other opionion except Pierre and me?

Thx, bye,
Gismo / Luca


From luca at pca.it  Thu Oct 18 19:55:42 2007
From: luca at pca.it (Luca Capello)
Date: Thu, 18 Oct 2007 21:55:42 +0200
Subject: [cl-debian] Re: CL Policy
In-Reply-To: <20071017130055.GF14139@(none)> (Pierre THIERRY's message of
	"Wed\, 17 Oct 2007 15\:00\:56 +0200")
References: <20071017013231.GA24958@unige.ch> <873awaijcb.fsf@gismo.pca.it>
	<20071017022451.GE14139@unige.ch> <87y7e2h2fu.fsf@gismo.pca.it>
	<20071017130055.GF14139@(none)>
Message-ID: <87myug19kx.fsf@gismo.pca.it>

Hi Pierre!

On Wed, 17 Oct 2007 15:00:56 +0200, Pierre THIERRY wrote:
> Scribit Luca Capello dies 17/10/2007 hora 04:58:
>> I guess this should be in the CL-Debian policy ;-)
>
> After discussing a bit with maintainers involved with Perl or Python
> packaging, I wonder if our policy shouldn't be extended a bit and
> made mandatory for Common Lisp packaging.

I think that because of clc the "policy" is already mandatory and I
don't know of any CL package that doesn't follow it.

> Being mandatory ensures packages will be consistent, which is better
> both for maintainers (they know for sure where to put things and how
> to name things) and users (they know fore sure where to find things
> and how they would be named).

Fully ACK.

The "Common Lisp in Debian Manual" [1] written by Ren? should be the
start for the policy, IMO.

Comments, suggestions, opinions?

Thx, bye,
Gismo / Luca

Footnotes: 
[1] http://cl-debian.alioth.debian.org/clid/clid.html/


From nowhere.man at levallois.eu.org  Fri Oct 19 01:10:57 2007
From: nowhere.man at levallois.eu.org (Pierre THIERRY)
Date: Fri, 19 Oct 2007 03:10:57 +0200
Subject: [cl-debian] Moving to darcs.debian.org, co-maintenance and
	other bits
In-Reply-To: <87r6js19q6.fsf@gismo.pca.it>
References: <873awme9hv.fsf@gismo.pca.it> <20071008030208.GS13023@(none)>
	<87y7ecm568.fsf@gismo.pca.it> <20071010221955.GB13023@(none)>
	<87r6js19q6.fsf@gismo.pca.it>
Message-ID: <20071019011057.GA31559@(none)>

Scribit Luca Capello dies 18/10/2007 hora 21:52:
> > - proposed		code not uplaoded, for review
> I'd prefer the patch posted to the mailing list, but this is personal.

That or on personal repos, yes. That's clearly the prefered way with a
DVCS.

> Especially for l10n, if we coordinate the work with the l10n team I
> see no hurt in giving them write permissions to the Debian repo
> (similarly to the NMU situation I explained above).

Wouldn't it be better if the l10n team needn't do NMU? That is, if they
provide us with the patches, and we do regular uploads with them.

> > We may also have repos or tags to make it easy to track Debian
> > releases.
> Mmm, can you elaborate on this?  I see the need for a Debian release
> specific repo only in case of backports (because usually you need to
> change the dependencies and maybe patch upstream).

Having a branch for stable may be useful if security fixes are applied,
as well as for backports. Tags would also probably be very good. For
example, in my repos, I tag every upstream and debian version with its
version, so you can do "hg up 1.0-2" to have the source code from which
1.0-2 was built, and "hg up 1.0" to have upstream-only source code...
Tags with release codenames could be good, too. So to see what is the
code of current testing for some package, you'd do "hg up lenny".

The latter may not be easy or even possible with all DVCSes. It's
trivial to have a moving tag in Mercurial, I read in Git's documentation
it's complicated by design (Git developers consider a moving tag a bug).

Quickly,
Pierre
-- 
nowhere.man at levallois.eu.org
OpenPGP 0xD9D50D8A
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071019/a8c06927/attachment.sig>

From nowhere.man at levallois.eu.org  Fri Oct 19 14:00:05 2007
From: nowhere.man at levallois.eu.org (Pierre THIERRY)
Date: Fri, 19 Oct 2007 16:00:05 +0200
Subject: [cl-debian] Re: CL Policy
In-Reply-To: <87myug19kx.fsf@gismo.pca.it>
References: <20071017013231.GA24958@unige.ch> <873awaijcb.fsf@gismo.pca.it>
	<20071017022451.GE14139@unige.ch> <87y7e2h2fu.fsf@gismo.pca.it>
	<20071017130055.GF14139@(none)> <87myug19kx.fsf@gismo.pca.it>
Message-ID: <20071019140005.GB31559@(none)>

Scribit Luca Capello dies 18/10/2007 hora 21:55:
> I think that because of clc the "policy" is already mandatory and I
> don't know of any CL package that doesn't follow it.

You're free not to use clc, and how you package your package exactly is
left at the maintainer's will entirely.

The policy should state explicitely, independently of the tool, where
files should be installed, what actions should be triggered in
maintainer scripts and how to deal with dependencies.

> The "Common Lisp in Debian Manual" [1] written by Ren? should be the
> start for the policy, IMO.

And having dh_lisp obviously helps.

Quickly,
Pierre
-- 
nowhere.man at levallois.eu.org
OpenPGP 0xD9D50D8A
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071019/31578a8b/attachment.sig>

From igor.stirbu at gmail.com  Wed Oct 17 14:40:32 2007
From: igor.stirbu at gmail.com (Igor Stirbu)
Date: Wed, 17 Oct 2007 17:40:32 +0300
Subject: [cl-debian] Bug#446690: cl-mcclim: Failure in building mcclim
In-Reply-To: <873aw925u8.fsf@zamazal.org>
References: <20071014214515.8978.86964.reportbug@keo>
	<87lka225fq.fsf@zamazal.org>
	<2f38019b0710161339i1e2dab5akea86fb1a30661c20@mail.gmail.com>
	<873aw925u8.fsf@zamazal.org>
Message-ID: <2f38019b0710170740o1973ff70t5be7c96858558051@mail.gmail.com>

2007/10/17, Milan Zamazal <pdm at debian.org>:
>
> >>>>> "IS" == Igor Stirbu <igor.stirbu at gmail.com> writes:
>
>     IS> I am using clisp 1:2.41-2 and Debian unstable.
>
> I see.  I can reproduce the error, even with the recent McCLIM CVS
> version.
>
> AFAIK CLISP support in McCLIM is somewhat tentative, McCLIM is usually
> run with SBCL or CMUCL.  I'd suggest to report the problem to the McCLIM
> development list (mcclim-devel at common-lisp.net or
> gmane.lisp.mcclim.devel on GMANE) and to try to work on fixing it with
> the McCLIM developers directly.


Thanks for the details. I will contact the McCLIM team.

Igor

-- 
:wq
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071017/a5b1509f/attachment.html>

From edi at agharta.de  Fri Oct 19 23:54:11 2007
From: edi at agharta.de (Edi Weitz)
Date: Sat, 20 Oct 2007 01:54:11 +0200
Subject: [cl-debian] [ann] [hunchentoot-announce] New release 0.14.4
Message-ID: <u8x5yy82k.fsf@agharta.de>

ChangeLog:

  Version 0.14.4
  2007-10-20
  Made log stream shared on OpenMCL (thanks to Gary Byers)	

Download:

  http://weitz.de/files/hunchentoot.tar.gz
_______________________________________________
tbnl-announce site list
tbnl-announce at common-lisp.net
http://common-lisp.net/mailman/listinfo/tbnl-announce
_______________________________________________
announcements site list
announcements at common-lisp.net
http://common-lisp.net/mailman/listinfo/announcements


From kmr at debian.org  Sun Oct 21 20:48:02 2007
From: kmr at debian.org (Kevin M. Rosenberg)
Date: Sun, 21 Oct 2007 20:48:02 +0000
Subject: [cl-debian] Accepted cl-lml2 1.6.5-1 (source all)
Message-ID: <E1IjhiM-0005kk-Mi@ries.debian.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 21 Oct 2007 14:34:29 -0600
Source: cl-lml2
Binary: cl-lml2
Architecture: source all
Version: 1.6.5-1
Distribution: unstable
Urgency: low
Maintainer: Kevin M. Rosenberg <kmr at debian.org>
Changed-By: Kevin M. Rosenberg <kmr at debian.org>
Description: 
 cl-lml2    - Lisp Markup Language
Changes: 
 cl-lml2 (1.6.5-1) unstable; urgency=low
 .
   * New upstream
Files: 
 2b510bf791a120070f81e6aef76a2899 564 devel optional cl-lml2_1.6.5-1.dsc
 d9cbb5eed22586fa10108cd440664e12 27032 devel optional cl-lml2_1.6.5.orig.tar.gz
 6d92a78da8fdee03575d1cc5e142c272 4369 devel optional cl-lml2_1.6.5-1.diff.gz
 0e8a26f9b24b12f6de194b6a998b934c 22786 devel optional cl-lml2_1.6.5-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHG7iiES7N8sSjgj4RAkQJAJ4mwp7KDqdcgkECaG0gV9kdmVDs0gCfXe5e
qOXlDlBGzx2Jby9CiS4Doxo=
=9GUF
-----END PGP SIGNATURE-----


Accepted:
cl-lml2_1.6.5-1.diff.gz
  to pool/main/c/cl-lml2/cl-lml2_1.6.5-1.diff.gz
cl-lml2_1.6.5-1.dsc
  to pool/main/c/cl-lml2/cl-lml2_1.6.5-1.dsc
cl-lml2_1.6.5-1_all.deb
  to pool/main/c/cl-lml2/cl-lml2_1.6.5-1_all.deb
cl-lml2_1.6.5.orig.tar.gz
  to pool/main/c/cl-lml2/cl-lml2_1.6.5.orig.tar.gz




From edi at agharta.de  Sun Oct 21 21:23:43 2007
From: edi at agharta.de (Edi Weitz)
Date: Sun, 21 Oct 2007 23:23:43 +0200
Subject: [cl-debian] [ann] [hunchentoot-announce] New cl-webdav release 0.1.2
 (Was: cl-webdav patch for current cxml)
In-Reply-To: <20071021185940.GF10680@radon> (David Lichteblau's message of
	"Sun, 21 Oct 2007 20:59:40 +0200")
References: <20071021185940.GF10680@radon>
Message-ID: <umyucmaao.fsf@agharta.de>

On Sun, 21 Oct 2007 20:59:40 +0200, David Lichteblau <david at lichteblau.com> wrote:

> the attached patch updates cl-webdav's use of SAX for the current
> cxml release.
>
> User code is now strongly encouraged to implement SAX handlers as
> subclasses of sax:default-handler or sax:abstract-handler.
>
> Without the patch, cl-webdav will still work (at least for a
> transition period), but issue warnings at run time.

Thanks, the patch is in the new release.

Edi.
_______________________________________________
tbnl-announce site list
tbnl-announce at common-lisp.net
http://common-lisp.net/mailman/listinfo/tbnl-announce
_______________________________________________
announcements site list
announcements at common-lisp.net
http://common-lisp.net/mailman/listinfo/announcements


From johan at nforced.com  Sun Oct 21 19:18:06 2007
From: johan at nforced.com (Johan Andersson)
Date: Sun, 21 Oct 2007 21:18:06 +0200
Subject: [cl-debian] Bug#447511: slime: Disconnect on tab-completetion
Message-ID: <20071021191806.15896.22666.reportbug@localhost>

Package: slime
Version: 1:20070927-2
Severity: normal


Steps to reproduce:

$ emacs -q

(require 'slime)
(require 'slime-fancy)

C-u M-x slime

Run lisp: sbcl

CL-USER> foo<TAB>

Connection closed.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-2-686 (SMP w/2 CPU cores)
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages slime depends on:
ii  cl-swank                    1:20070927-2 Superior LISP Interaction Mode for
ii  emacsen-common              1.4.17       Common facilities for all emacsen

Versions of packages slime recommends:
ii  emacs21 [info-browser]      21.4a+1-5.1  The GNU Emacs editor
ii  emacs22 [info-browser]      22.1+1-2     The GNU Emacs editor
ii  info [info-browser]         4.8.dfsg.1-6 Standalone GNU Info documentation 

ii  sbcl           1:0.9.16.0-1   A Common Lisp compiler and development syste

-- no debconf information





From owner at bugs.debian.org  Tue Oct 23 08:21:02 2007
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Tue, 23 Oct 2007 08:21:02 +0000
Subject: [cl-debian] Processed: reassign 441898 to cl-flexichain
In-Reply-To: <1193127526-836-bts-lucas@lucas-nussbaum.net>
References: <1193127526-836-bts-lucas@lucas-nussbaum.net>
Message-ID: <handler.s.C.119312758318395.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> # Automatically generated email from bts, devscripts version 2.10.9
> reassign 441898 cl-flexichain
Bug#441898: cl-mcclim: depends on cl-flexichain which is missing
Bug reassigned from package `cl-mcclim' to `cl-flexichain'.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)




From sscholl at common-lisp.net  Wed Oct 24 11:27:52 2007
From: sscholl at common-lisp.net (Stefan Scholl)
Date: Wed, 24 Oct 2007 13:27:52 +0200
Subject: [cl-debian] [ann] [cl-wiki-announce] New Release CL-WIKI 0.2.0
Message-ID: <20071024112752.GG21756@parsec.no-spoon.de>

New release CL-WIKI 0.2.0

CL-WIKI is a wiki engine for Common Lisp. It uses Hunchentoot,
CL-PPCRE, CL-WHO and CL-EMB. Can be used stand-alone, with
Apache + mod_lisp, or behind any http proxy.


You can download it from http://common-lisp.net/project/cl-wiki/
or install with ASDF-Install.

CL-USER> (asdf:operate 'asdf:load-op :asdf-install)
CL-USER> (asdf-install:install :cl-wiki)


Changes:

- Switched from TBNL to Hunchentoot.



darcs repository removed. A git repository will be published later.


_______________________________________________
cl-wiki-announce mailing list
cl-wiki-announce at common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/cl-wiki-announce
_______________________________________________
announcements site list
announcements at common-lisp.net
http://common-lisp.net/mailman/listinfo/announcements


From owner at bugs.debian.org  Thu Oct 25 10:00:04 2007
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Thu, 25 Oct 2007 10:00:04 +0000
Subject: [cl-debian] Processed: setting package to cmucl cmucl-clm cmucl-docs
 cmucl-source, tagging 443705
In-Reply-To: <20071025095300.CDDE64CB14@frost.pvaneynd.mailworks.org>
References: <20071025095300.CDDE64CB14@frost.pvaneynd.mailworks.org>
Message-ID: <handler.s.C.119330598310581.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> # Automatically generated email from bts, devscripts version 2.9.27ubuntu13
> package cmucl cmucl-clm cmucl-docs cmucl-source
Ignoring bugs not assigned to: cmucl-source cmucl-clm cmucl cmucl-docs

> tags 443705 + pending
Bug#443705: FTBFS: sectsty.sty not found
Tags were: patch
Tags added: pending

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)




From fare at tunes.org  Fri Oct 26 05:32:02 2007
From: fare at tunes.org (Francois-Rene Rideau)
Date: Fri, 26 Oct 2007 05:32:02 +0000
Subject: [cl-debian] Accepted cl-launch 2.07-1 (source all)
Message-ID: <E1IlHne-0003WU-Ht@ries.debian.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 17 May 2007 18:22:23 -0400
Source: cl-launch
Binary: cl-launch
Architecture: source all
Version: 2.07-1
Distribution: unstable
Urgency: low
Maintainer: Francois-Rene Rideau <fare at tunes.org>
Changed-By: Francois-Rene Rideau <fare at tunes.org>
Description: 
 cl-launch  - uniform frontend to running Common Lisp code from the shell
Changes: 
 cl-launch (2.07-1) unstable; urgency=low
 .
   * commented out (sb-pcl::precompile-random-code-segments) in save-image
     as it may cause some systems to grind to a halt. Users can still do it
     themselves if they want it, it is purely a performance issue.
   * added a compute-arguments early in cl-launch.
Files: 
 0369733a15fd30dbf05455e0f335e1ce 683 devel optional cl-launch_2.07-1.dsc
 26539406e4be110855ee4f7eb3c11458 34401 devel optional cl-launch_2.07.orig.tar.gz
 59f73ef96b7c0872598ce1014b45d616 8999 devel optional cl-launch_2.07-1.diff.gz
 368aa6a763e848213ea7dff63de495fc 58784 devel optional cl-launch_2.07-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHIQDF11ldN0tyliURAg6DAJ9XffeggazkUo4Jh/ood4tNo/+YdACaArTO
KxlDsd+b3yka7ANloRxdENo=
=+6OY
-----END PGP SIGNATURE-----


Accepted:
cl-launch_2.07-1.diff.gz
  to pool/main/c/cl-launch/cl-launch_2.07-1.diff.gz
cl-launch_2.07-1.dsc
  to pool/main/c/cl-launch/cl-launch_2.07-1.dsc
cl-launch_2.07-1_all.deb
  to pool/main/c/cl-launch/cl-launch_2.07-1_all.deb
cl-launch_2.07.orig.tar.gz
  to pool/main/c/cl-launch/cl-launch_2.07.orig.tar.gz




From installer at ftp-master.debian.org  Fri Oct 26 05:32:03 2007
From: installer at ftp-master.debian.org (Debian Installer)
Date: Fri, 26 Oct 2007 05:32:03 +0000
Subject: [cl-debian] clisp_2.42-2_i386.changes REJECTED
Message-ID: <E1IlHnf-0003Ww-Ux@ries.debian.org>


Rejected: clisp_2.42-2.dsc refers to clisp_2.42.orig.tar.gz, but I can't find it in the queue or in the pool.


===

If you don't understand why your files were rejected, or if the
override file requires editing, reply to this email.



From owner at bugs.debian.org  Fri Oct 26 05:36:08 2007
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Fri, 26 Oct 2007 05:36:08 +0000
Subject: [cl-debian] Bug#447511: marked as done (slime: Disconnect on
	tab-completetion)
References: <E1IlHni-0003Xv-Ik@ries.debian.org>
	<20071021191806.15896.22666.reportbug@localhost>
Message-ID: <handler.447511.D447511.119337678730081.ackdone@bugs.debian.org>

Your message dated Fri, 26 Oct 2007 05:32:06 +0000
with message-id <E1IlHni-0003Xv-Ik at ries.debian.org>
and subject line Bug#447511: fixed in slime 1:20070927-3
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)

-------------- next part --------------
An embedded message was scrubbed...
From: Johan Andersson <johan at nforced.com>
Subject: slime: Disconnect on tab-completetion
Date: Sun, 21 Oct 2007 21:18:06 +0200
Size: 2600
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071026/38648a92/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Peter Van Eynde <pvaneynd at debian.org>
Subject: Bug#447511: fixed in slime 1:20070927-3
Date: Fri, 26 Oct 2007 05:32:06 +0000
Size: 3568
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071026/38648a92/attachment-0001.mht>

From pvaneynd at debian.org  Fri Oct 26 05:32:06 2007
From: pvaneynd at debian.org (Peter Van Eynde)
Date: Fri, 26 Oct 2007 05:32:06 +0000
Subject: [cl-debian] Accepted slime 1:20070927-3 (source all)
Message-ID: <E1IlHni-0003Xl-Dp@ries.debian.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Fri, 26 Oct 2007 05:10:07 +0200
Source: slime
Binary: cl-swank slime
Architecture: source all
Version: 1:20070927-3
Distribution: unstable
Urgency: low
Maintainer: Peter Van Eynde <pvaneynd at debian.org>
Changed-By: Peter Van Eynde <pvaneynd at debian.org>
Description: 
 cl-swank   - Superior LISP Interaction Mode for Emacs (Lisp-side server)
 slime      - Superior LISP Interaction Mode for Emacs
Closes: 445241 445299 445863 446758 447511
Changes: 
 slime (1:20070927-3) unstable; urgency=low
 .
   * Now we unconditionally load all the fancy stuff.
     (Closes: #447511, #446758, #445299)
   * Fixed bashism in emacs install script
     (Closes: #445863)
   * Modifying the .emacs is not needed anymore. Cleaned up
     Readme.Debian (Closes: #445241)
   * Now uses Vcs-Bzr in control file.
Files: 
 ad5af85ef4a6551c8ea220606a949d89 759 devel optional slime_20070927-3.dsc
 25a86bdb8b68dba88143eec5299e09aa 18602 devel optional slime_20070927-3.diff.gz
 cd87c491b47a5d741b9c41dd9de7355f 783928 devel optional slime_20070927-3_all.deb
 1773869809d77c54405f98ce6d4c5d67 376660 devel optional cl-swank_20070927-3_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHIVxf11ldN0tyliURAnicAJ9wN/nz5zf84LjMvTsCunLzza+SVgCghMEL
tXkZNtOiDcNr4UF/XRA/80E=
=s+pf
-----END PGP SIGNATURE-----


Accepted:
cl-swank_20070927-3_all.deb
  to pool/main/s/slime/cl-swank_20070927-3_all.deb
slime_20070927-3.diff.gz
  to pool/main/s/slime/slime_20070927-3.diff.gz
slime_20070927-3.dsc
  to pool/main/s/slime/slime_20070927-3.dsc
slime_20070927-3_all.deb
  to pool/main/s/slime/slime_20070927-3_all.deb




From owner at bugs.debian.org  Fri Oct 26 05:36:03 2007
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Fri, 26 Oct 2007 05:36:03 +0000
Subject: [cl-debian] Bug#445241: marked as done (slime: Readme.Debian seems
 to contain incorrect information)
References: <E1IlHni-0003Xn-Er@ries.debian.org>
	<20071004102049.12811.8125.reportbug@host1>
Message-ID: <handler.445241.D445241.119337679230137.ackdone@bugs.debian.org>

Your message dated Fri, 26 Oct 2007 05:32:06 +0000
with message-id <E1IlHni-0003Xn-Er at ries.debian.org>
and subject line Bug#445241: fixed in slime 1:20070927-3
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)

-------------- next part --------------
An embedded message was scrubbed...
From: Brian Kudowski <whooey1830 at web.de>
Subject: slime: Readme.Debian seems to contain incorrect information
Date: Thu, 04 Oct 2007 12:20:49 +0200
Size: 2084
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071026/a2515176/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Peter Van Eynde <pvaneynd at debian.org>
Subject: Bug#445241: fixed in slime 1:20070927-3
Date: Fri, 26 Oct 2007 05:32:06 +0000
Size: 3568
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071026/a2515176/attachment-0001.mht>

From owner at bugs.debian.org  Fri Oct 26 05:36:06 2007
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Fri, 26 Oct 2007 05:36:06 +0000
Subject: [cl-debian] Bug#446758: marked as done (slime: Lost functionality: ,
	l and M-tab)
References: <E1IlHni-0003Xt-Hm@ries.debian.org>
	<654935030710150557u58af0f72r566fff11191f4533@mail.gmail.com>
Message-ID: <handler.446758.D446758.119337679330152.ackdone@bugs.debian.org>

Your message dated Fri, 26 Oct 2007 05:32:06 +0000
with message-id <E1IlHni-0003Xt-Hm at ries.debian.org>
and subject line Bug#446758: fixed in slime 1:20070927-3
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)

-------------- next part --------------
An embedded message was scrubbed...
From: "Liam Healy" <lnp at healy.washington.dc.us>
Subject: slime: Lost functionality: ,l and M-tab
Date: Mon, 15 Oct 2007 08:57:22 -0400
Size: 3184
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071026/4d9f0286/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Peter Van Eynde <pvaneynd at debian.org>
Subject: Bug#446758: fixed in slime 1:20070927-3
Date: Fri, 26 Oct 2007 05:32:06 +0000
Size: 3568
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071026/4d9f0286/attachment-0001.mht>

From owner at bugs.debian.org  Fri Oct 26 05:36:05 2007
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Fri, 26 Oct 2007 05:36:05 +0000
Subject: [cl-debian] Bug#445863: marked as done (bashism in
	/usr/lib/emacsen-common/packages/install/slime)
References: <E1IlHni-0003Xr-Gn@ries.debian.org> <470A6EED.5010302@hotmail.com>
Message-ID: <handler.445863.D445863.119337678830092.ackdone@bugs.debian.org>

Your message dated Fri, 26 Oct 2007 05:32:06 +0000
with message-id <E1IlHni-0003Xr-Gn at ries.debian.org>
and subject line Bug#445863: fixed in slime 1:20070927-3
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)

-------------- next part --------------
An embedded message was scrubbed...
From: =?UTF-8?B?R8OpcmF1ZCBNZXllcg==?= <geraud_meyer at hotmail.com>
Subject: bashism in /usr/lib/emacsen-common/packages/install/slime
Date: Mon, 08 Oct 2007 19:54:53 +0200
Size: 2356
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071026/f7d62234/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Peter Van Eynde <pvaneynd at debian.org>
Subject: Bug#445863: fixed in slime 1:20070927-3
Date: Fri, 26 Oct 2007 05:32:06 +0000
Size: 3568
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071026/f7d62234/attachment-0001.mht>

From owner at bugs.debian.org  Fri Oct 26 05:36:04 2007
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Fri, 26 Oct 2007 05:36:04 +0000
Subject: [cl-debian] Bug#445299: marked as done (slime: No LIST-ASDF-SYSTEMS
 in the SWANK package)
References: <E1IlHni-0003Xp-Fp@ries.debian.org>
	<20071004171814.30981.15247.reportbug@head.hexapodia.net>
Message-ID: <handler.445299.D445299.119337678830103.ackdone@bugs.debian.org>

Your message dated Fri, 26 Oct 2007 05:32:06 +0000
with message-id <E1IlHni-0003Xp-Fp at ries.debian.org>
and subject line Bug#445299: fixed in slime 1:20070927-3
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)

-------------- next part --------------
An embedded message was scrubbed...
From: Ingvar Mattsson <ingvar at hexapodia.net>
Subject: slime: No LIST-ASDF-SYSTEMS in the SWANK package
Date: Thu, 04 Oct 2007 18:18:14 +0100
Size: 4486
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071026/053296df/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Peter Van Eynde <pvaneynd at debian.org>
Subject: Bug#445299: fixed in slime 1:20070927-3
Date: Fri, 26 Oct 2007 05:32:06 +0000
Size: 3568
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071026/053296df/attachment-0001.mht>

From pvaneynd at debian.org  Sat Oct 27 08:48:58 2007
From: pvaneynd at debian.org (Peter Van Eynde)
Date: Sat, 27 Oct 2007 08:48:58 +0000
Subject: [cl-debian] Accepted sbcl 1:1.0.11.0-1 (source all i386)
Message-ID: <E1IlhLm-0005SL-4s@ries.debian.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Fri, 26 Oct 2007 23:38:00 +0200
Source: sbcl
Binary: sbcl sbcl-source sbcl-doc
Architecture: source all i386
Version: 1:1.0.11.0-1
Distribution: unstable
Urgency: low
Maintainer: Peter Van Eynde <pvaneynd at debian.org>
Changed-By: Peter Van Eynde <pvaneynd at debian.org>
Description: 
 sbcl       - A Common Lisp compiler and development system
 sbcl-doc   - Documentation for Steel Bank Common Lisp
 sbcl-source - Source code files for SBCL
Changes: 
 sbcl (1:1.0.11.0-1) unstable; urgency=low
 .
   * Use Vcs-Bzr in control file
   * New upstream release. Major changes:
      + incompatible change: hash-table accessor functions are no longer
        automatically protected by locks. Concurrent accesses on the same hash-table
        from multiple threads can give inconsistent results or even corrupt the
        hash-table completely. Multi-threaded applications should do their own
        locking at the correct granularity. In the current implementation it is
        still safe to have multiple readers access the same table, but it's not
        guaranteed that this property will be maintained in future releases.
      + minor incompatible change: (SETF MUTEX-VALUE) is not longer supported,
        and will signal an error at runtime.
      + enhancement: SB-THREAD package now exports a semaphore interface.
      + enhancement: CONS can now stack-allocate on x86 and
        x86-64. (Earlier LIST and LIST* supported stack-allocation, but
        CONS did not.)
      + enhancement: nested lists can now be stack allocated on
        platforms providing stack allocation support.
      + enhancement: dynamic-extent support has been extended to support
        cases where there are multiple possible sources for the stack
        allocated value.
      + optimization: RELEASE-MUTEX no longer needs to perform a syscall
        if the mutex is uncontested on Linux.
      + bug fix: symbol-macro expansion now uses the *MACROEXPAND-HOOK*
        as specified by the CLHS. (thanks to Tobias Rittweiler)
      + bug fix: NaN comparison now works on x86-64.
      + bug fix: CLOSE :ABORT T on a stream with pending output now
        works.
      + bug fix: instances of non-standard metaclasses using standard
        instance structure protocol sometimes missed the slot type checks
        in safe code.
      + bug fix: known functions can be inlined in high-debug code.
Files: 
 b9ef16a7b3e43fbfaf6e28683f5867c5 800 devel optional sbcl_1.0.11.0-1.dsc
 cd10b99df02ee1e010509fe0fefd9530 4632456 devel optional sbcl_1.0.11.0.orig.tar.gz
 d84e8919415347e3c1796f1b9dfe530c 35244 devel optional sbcl_1.0.11.0-1.diff.gz
 216e34003cd5f6cc88faf6991f20e23a 1600160 doc optional sbcl-doc_1.0.11.0-1_all.deb
 8eb966099ca374d9f40c74a56b6da3d6 3902768 doc optional sbcl-source_1.0.11.0-1_all.deb
 7286f6ef43cfc053f90bb3f6cb100fef 9090764 devel optional sbcl_1.0.11.0-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHIuoF11ldN0tyliURAq6uAKCZYWkbJJiFg/SCAQfYviVzHB/2VACfXm/J
hwhEKzOukQKcl3JrVwABWaI=
=O3Bx
-----END PGP SIGNATURE-----


Accepted:
sbcl-doc_1.0.11.0-1_all.deb
  to pool/main/s/sbcl/sbcl-doc_1.0.11.0-1_all.deb
sbcl-source_1.0.11.0-1_all.deb
  to pool/main/s/sbcl/sbcl-source_1.0.11.0-1_all.deb
sbcl_1.0.11.0-1.diff.gz
  to pool/main/s/sbcl/sbcl_1.0.11.0-1.diff.gz
sbcl_1.0.11.0-1.dsc
  to pool/main/s/sbcl/sbcl_1.0.11.0-1.dsc
sbcl_1.0.11.0-1_i386.deb
  to pool/main/s/sbcl/sbcl_1.0.11.0-1_i386.deb
sbcl_1.0.11.0.orig.tar.gz
  to pool/main/s/sbcl/sbcl_1.0.11.0.orig.tar.gz




From installer at ftp-master.debian.org  Sat Oct 27 09:17:05 2007
From: installer at ftp-master.debian.org (Debian Installer)
Date: Sat, 27 Oct 2007 09:17:05 +0000
Subject: [cl-debian] sbcl_1.0.11.0-1_i386.changes REJECTED
Message-ID: <E1Ilhmz-00072Q-9J@ries.debian.org>


Rejected: sbcl_1.0.11.0-1_i386.changes: a file with this name already exists in the Accepted directory.
Rejected: sbcl_1.0.11.0.orig.tar.gz file already exists in the Accepted directory.
Rejected: sbcl-doc_1.0.11.0-1_all.deb file already exists in the Accepted directory.
Rejected: sbcl-source_1.0.11.0-1_all.deb file already exists in the Accepted directory.
Rejected: sbcl_1.0.11.0-1_i386.deb file already exists in the Accepted directory.
Rejected: sbcl_1.0.11.0-1.dsc file already exists in the Accepted directory.
Rejected: sbcl_1.0.11.0-1.diff.gz file already exists in the Accepted directory.


===

If you don't understand why your files were rejected, or if the
override file requires editing, reply to this email.



From pvaneynd at debian.org  Sun Oct 28 01:47:04 2007
From: pvaneynd at debian.org (Peter Van Eynde)
Date: Sun, 28 Oct 2007 01:47:04 +0000
Subject: [cl-debian] Accepted clisp 1:2.42-3 (source all i386)
Message-ID: <E1IlxF2-0001rq-MJ@ries.debian.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Fri, 26 Oct 2007 23:41:53 +0200
Source: clisp
Binary: clisp-dev clisp clisp-doc
Architecture: source all i386
Version: 1:2.42-3
Distribution: unstable
Urgency: low
Maintainer: Peter Van Eynde <pvaneynd at debian.org>
Changed-By: Peter Van Eynde <pvaneynd at debian.org>
Description: 
 clisp      - GNU CLISP, a Common Lisp implementation
 clisp-dev  - GNU CLISP, a Common Lisp implementation (development files)
 clisp-doc  - GNU CLISP, a Common Lisp implementation (documentation)
Changes: 
 clisp (1:2.42-3) unstable; urgency=low
 .
   * Forgot to regenerate configure script. 2.42 for real this time!
Files: 
 187369c9aee3c5b1265f7c7e77fbe9d0 827 interpreters optional clisp_2.42-3.dsc
 7d83da9830ca66695177744b1162aed7 10348491 interpreters optional clisp_2.42.orig.tar.gz
 d65fe92f306010d09b0419bf48cd1afa 135711 interpreters optional clisp_2.42-3.diff.gz
 970c557832b2e60625198877e0cfa996 863222 doc optional clisp-doc_2.42-3_all.deb
 b3be7499b2cb56c13bbd7549d795b021 3466324 interpreters optional clisp_2.42-3_i386.deb
 3a7636006b26615b51d50b88e59e239d 3301560 devel optional clisp-dev_2.42-3_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHIvXg11ldN0tyliURAhhQAKCn0FutuSJO6bs5Jms6+esNYwkrEgCePWaa
G0/iBpf3YhFiSdLhD2TyPxQ=
=tIjL
-----END PGP SIGNATURE-----


Accepted:
clisp-dev_2.42-3_i386.deb
  to pool/main/c/clisp/clisp-dev_2.42-3_i386.deb
clisp-doc_2.42-3_all.deb
  to pool/main/c/clisp/clisp-doc_2.42-3_all.deb
clisp_2.42-3.diff.gz
  to pool/main/c/clisp/clisp_2.42-3.diff.gz
clisp_2.42-3.dsc
  to pool/main/c/clisp/clisp_2.42-3.dsc
clisp_2.42-3_i386.deb
  to pool/main/c/clisp/clisp_2.42-3_i386.deb
clisp_2.42.orig.tar.gz
  to pool/main/c/clisp/clisp_2.42.orig.tar.gz




From erick at fsl.org.mx  Sun Oct 28 16:59:07 2007
From: erick at fsl.org.mx (Erick Lopez Carreon)
Date: Sun, 28 Oct 2007 10:59:07 -0600
Subject: [cl-debian] Bug#448382: slime: Readme seems to contain incorrect
 information about contrib
Message-ID: <1193590747.4237.4.camel@localhost.cibercalli.com>

Package: slime
Version: 1:20070927-3
Severity: normal

File /usr/share/doc/slime/README give the following instructions to
activate contrib stuff like slime-reindent-defun which is
in: /usr/share/emacs/site-lisp/slime/contrib/slime-editing-commands.el
and /usr/share/emacs22/site-lisp/slime/contrib/slime-editing-commands.el

"To use the packages here, you should add this directory to your Emacs
load-path.  E.g. for fuzzy completion add this to your .emacs:

 (add-to-list 'load-path "<this-directory>")
  (add-hook 'slime-load-hook (lambda () (require 'slime-fuzzy)))"


But this instructions seems to be unuseful, because after modify
accordingly ~/.emacs, typing C-c M-q in Emacs still results in:

"C-c M-q is undefined"


I managed it worked again modifying ~/.emacs in this way:

(add-to-list 'load-path "/usr/share/emacs/site-lisp/slime/contrib/")
(setq inferior-lisp-program "/usr/bin/sbcl")
(require 'slime)
(slime-setup
 '(slime-editing-commands))


Thanks.
  


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-xpsm1210 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages slime depends on:
ii  cl-swank                    1:20070927-3 Superior LISP Interaction
Mode for
ii  emacsen-common              1.4.17       Common facilities for all
emacsen

Versions of packages slime recommends:
ii  emacs21 [info-browser]      21.4a+1-5.1  The GNU Emacs editor
ii  emacs22 [info-browser]      22.1+1-2     The GNU Emacs editor
ii  info [info-browser]         4.8.dfsg.1-6 Standalone GNU Info
documentation 







From owner at bugs.debian.org  Sun Oct 28 18:27:05 2007
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sun, 28 Oct 2007 18:27:05 +0000
Subject: [cl-debian] Bug#448382: marked as done (slime: Readme seems to
 contain incorrect information about contrib)
References: <1193595844.4106.10.camel@localhost.cibercalli.com>
	<1193590747.4237.4.camel@localhost.cibercalli.com>
Message-ID: <handler.448382.D448382.11935958518370.ackdone@bugs.debian.org>

Your message dated Sun, 28 Oct 2007 12:24:04 -0600
with message-id <1193595844.4106.10.camel at localhost.cibercalli.com>
and subject line slime: Readme seems to contain incorrect information about contrib
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)

-------------- next part --------------
An embedded message was scrubbed...
From: Erick Lopez Carreon <erick at fsl.org.mx>
Subject: slime: Readme seems to contain incorrect information about contrib
Date: Sun, 28 Oct 2007 10:59:07 -0600
Size: 2884
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071028/51a0717d/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Erick Lopez Carreon <erick at fsl.org.mx>
Subject: slime: Readme seems to contain incorrect information about contrib
Date: Sun, 28 Oct 2007 12:24:04 -0600
Size: 1990
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20071028/51a0717d/attachment-0001.mht>

From luca at pca.it  Mon Oct 29 00:14:15 2007
From: luca at pca.it (Luca Capello)
Date: Mon, 29 Oct 2007 01:14:15 +0100
Subject: [cl-debian] Bug#448431: clisp: dpkg warning: unable to delete old
 directory `/usr/lib/clisp...
Message-ID: <87y7dmrd48.fsf@gismo.pca.it>

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

Hello,

I think the title and the output below speaks for himself:
=====
luca at 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 at gismo:~$ ls /usr/lib/ | grep clisp
clisp
clisp-2.42

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

/usr/lib/clisp/full:
lispinit.mem
luca at 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





From pvaneynd at mailworks.org  Mon Oct 29 19:49:53 2007
From: pvaneynd at mailworks.org (Peter Van Eynde)
Date: Mon, 29 Oct 2007 20:49:53 +0100
Subject: [cl-debian] Bug#448431: clisp: dpkg warning: unable to delete old
 directory `/usr/lib/clisp...
In-Reply-To: <87y7dmrd48.fsf@gismo.pca.it>
References: <87y7dmrd48.fsf@gismo.pca.it>
Message-ID: <47263961.8040902@mailworks.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ciao Luca,

Luca Capello wrote:
> 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

Damn. I'll have to think about what I can do about this.

> 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?

clisp itself changed the location and it was easiest just to follow
their lead.

Groetjes, Peter

- --
signature -at- pvaneynd.mailworks.org
http://www.livejournal.com/users/pvaneynd/
"God, root, what is difference?" Pitr | "God is more forgiving." Dave
Aronson|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHJjld11ldN0tyliURAqAfAJ9VsEuTJqgyR9sek47Oon6Grb25DgCaAzdU
dtPWxeAE/RCDkcU4ZnUtkmk=
=Jy0z
-----END PGP SIGNATURE-----






From vsedach at gmail.com  Wed Oct 31 07:17:12 2007
From: vsedach at gmail.com (Vladimir Sedach)
Date: Wed, 31 Oct 2007 00:17:12 -0700
Subject: [cl-debian] [ann] [parenscript-announce] "Halloween" Parenscript
	release.
Message-ID: <c07e645b0710310017k72917f55g5a2cdc48929b8960@mail.gmail.com>

A new Parenscript release is now up on common-lisp.net. It mostly
addresses bug fixes, although some more control over the way
JavaScript is printed is exposed as well.

Happy hacking,
Vladimir
_______________________________________________
parenscript-announce mailing list
parenscript-announce at common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-announce
_______________________________________________
announcements site list
announcements at common-lisp.net
http://common-lisp.net/mailman/listinfo/announcements


From whooey1830 at web.de  Wed Oct 31 20:39:04 2007
From: whooey1830 at web.de (Brian Kudowski)
Date: Wed, 31 Oct 2007 21:39:04 +0100
Subject: [cl-debian] Bug#448772: slime: emacs one line minibuffer too narrow
 to show larger help texts
Message-ID: <20071031203904.4820.10922.reportbug@host1>

Package: slime
Version: 1:20070325-1
Severity: normal


Hello,

in the emacs slime REPL type in f.e.

CL-USER > (make-array

The one line minibuffer (?, the most bottom window) is too narrow to display the
whole function, macro, etc. call convention help.

Thank you,
Brian


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages slime depends on:
ii  cl-swank                    1:20070325-1 Superior LISP Interaction Mode for
ii  emacsen-common              1.4.17       Common facilities for all emacsen

Versions of packages slime recommends:
ii  emacs21 [info-browser]    21.4a+1-3etch1 The GNU Emacs editor
ii  info [info-browser]       4.8.dfsg.1-4   Standalone GNU Info documentation 

-- no debconf information





From flatlander at yellow-hut.com  Wed Oct 31 13:38:07 2007
From: flatlander at yellow-hut.com (Tomi Neste)
Date: Wed, 31 Oct 2007 15:38:07 +0200
Subject: [cl-debian] [ann] [pal-announce] PAL v1.1 & PAL-GUI v0.1 released
Message-ID: <op.t02dhtyau6rk5c@otto>

PAL v1.1 was just released. Unfortunately I needed to make a few changes  
to the api that might break something.
Most important changes from v1.0:

- Name changes; reset-blend-mode => reset-blend, circles-overlap =>  
circles-overlap-p,
   point-inside-rectangle => point-inside-rectangle-p, point-in-line =>  
point-in-line-p.

- Added color.lisp, WITH-BLEND now uses COLOR struct instead of a list of  
rgba
   values. By v1.2 all rgba arguments will be replaced with COLOR.

- Removed CURRY.

- Image drawing should be much faster under certain conditions.

- I finally started working on the manual...

PAL-GUI is slowly approaching usable state (I hope...). Currently there  
are still some look and feel issues (clipping etc.) but there are already  
a few working widgets. Naturally, it is not documented yet but there are a  
few examples and it shouldn't be too hard to use. Basically it is just a  
regular windows/widgets/callbacks gui implemented in pal and integrated  
with its event loop.

Currently on my todo list for v1.2:

- Few utility functions for using PAL with Imago  
(http://common-lisp.net/project/imago/), for screenshots etc.

- Real drawing primitives would be nice, proper polygons and lines, svg  
importer etc. Currently PAL's draw-* functions map fairly directly to  
OpenGL and are quite limited (and slow).

- Batched image rendering for extra speed. Kinda like improved draw-image*.

- TTF support.

- Possibly merge pal and pal-gui.

- Documentation. Always the last one ;)


-- 
tomppa
_______________________________________________
pal-announce mailing list
pal-announce at common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/pal-announce
_______________________________________________
announcements site list
announcements at common-lisp.net
http://common-lisp.net/mailman/listinfo/announcements


From tomi.neste at netikka.fi  Wed Oct 31 17:52:52 2007
From: tomi.neste at netikka.fi (Tomi Neste)
Date: Wed, 31 Oct 2007 19:52:52 +0200
Subject: [cl-debian] [ann] [pal-announce] PAL v1.1 & PAL-GUI v0.1 released
Message-ID: <op.t02paekg53cznb@otto>

PAL v1.1 was just released. Unfortunately I needed to make a few changes  
to the api that might break something.
Most important changes from v1.0:

- Name changes; reset-blend-mode => reset-blend, circles-overlap =>  
circles-overlap-p,
   point-inside-rectangle => point-inside-rectangle-p, point-in-line =>  
point-in-line-p.

- Added color.lisp, WITH-BLEND now uses COLOR struct instead of a list of  
rgba
   values. By v1.2 all rgba arguments will be replaced with COLOR.

- Removed CURRY.

- Image drawing should be much faster under certain conditions.

- I finally started working on the manual...

PAL-GUI is slowly approaching usable state (I hope...). Currently there  
are still some look and feel issues (clipping etc.) but there are already  
a few working widgets. Naturally, it is not documented yet but there are a  
few examples and it shouldn't be too hard to use. Basically it is just a  
regular windows/widgets/callbacks gui implemented in pal and integrated  
with its event loop.

Currently on my todo list for v1.2:

- Few utility functions for using PAL with Imago  
(http://common-lisp.net/project/imago/), for screenshots etc.

- Real drawing primitives would be nice, proper polygons and lines, svg  
importer etc. Currently PAL's draw-* functions map fairly directly to  
OpenGL and are quite limited (and slow).

- Batched image rendering for extra speed. Kinda like improved draw-image*.

- TTF support.

- Possibly merge pal and pal-gui.

- Documentation. Always the last one ;)



-- 
tomppa
_______________________________________________
pal-announce mailing list
pal-announce at common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/pal-announce
_______________________________________________
announcements site list
announcements at common-lisp.net
http://common-lisp.net/mailman/listinfo/announcements