From luca at pca.it Tue Aug 1 11:21:10 2006 From: luca at pca.it (Luca Capello) Date: Tue, 01 Aug 2006 13:21:10 +0200 Subject: [cl-debian] Re: [Bese-devel] error starting with ucwctl - problem with cl-launch? In-Reply-To: <187B5F39-5673-484A-A016-9C4251123A18@mammalia.net> References: <187B5F39-5673-484A-A016-9C4251123A18@mammalia.net> Message-ID: <87mzaoitw9.fsf@gismo.pca.it> Hello! For the CL-Debian mailing list, the parent post is here [1]. On Mon, 31 Jul 2006 06:59:41 +0200, Joseph Wright wrote: > I'm trying to start ucw using ucwctl on recent debian unstable > (because it has recent sbcl and threads). I may downgrade or try it > on another system such as redhat to see if I get similar results. Actually, this is a known problem, reported the first time back in April at [2] (BTW, I don't know why the first message isn't complete). I remember I experienced it (indeed I've a complete backtrace of it), but it's quite a long time since I haven't started ucwctl, as I was busy with other stuff. I'll try to narrow down the problem ASAP. I cc:ed the CL-Debian mailing list, as I bet this is a Debian specific problem, as I never experienced it with an upstream SBCL, SLIME and CL-Launch (tested on 2 different machines). Thx, bye, Gismo / Luca [1] http://common-lisp.net/pipermail/bese-devel/2006-July/002530.html [2] http://common-lisp.net/pipermail/bese-devel/2006-April/001926.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: not available URL: From owner at bugs.debian.org Wed Aug 2 11:34:01 2006 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Wed, 02 Aug 2006 04:34:01 -0700 Subject: [cl-debian] Processed: severity of 365230 is serious In-Reply-To: <20060802110752.962E154273@wavehammer.waldi.eu.org> References: <20060802110752.962E154273@wavehammer.waldi.eu.org> Message-ID: Processing commands for control at bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.9.20 > severity 365230 serious Bug#365230: mcvs - FTBFS: There is no package with name "FFI" Bug#230947: There is no package with name "FFI" for hppa Bug#270876: clisp: FFI not available on arm hppa m68k mips mipsel s390 Severity set to `serious' from `wishlist' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) From pvaneynd at mailworks.org Wed Aug 2 19:41:10 2006 From: pvaneynd at mailworks.org (Peter Van Eynde) Date: Wed, 2 Aug 2006 21:41:10 +0200 Subject: [cl-debian] Re: Using Darcs for Debian package maintenance Message-ID: <200608022141.11328.pvaneynd@mailworks.org> Hello, Hello, I fear I'm running into some problems using darcs for my debian packages: pull's are getting slower and slower and in some cases are not finishing even over the weekend. I'm putting what I learn on the debian wiki (http://wiki.debian.org/PackagingWithDarcsAndTailor). Basicly I often have a 'doubleganger' patch problem. I import upstream changes (in the past from a tarfile or directly from cvs, now with tailor) into -upstream, do a 'get' into a repository, and do my debian stuff in that directory. When upstream releases a new version I pull/import this into the -upstream repository and then pull this into the directory. The problem is that sometimes upstream applies my patches and I get a doubleganger, and I've managed to hack round them most of the time. But now I have a issue with slime, that I do not think is a doubleganger. I imported the (then) current CVS into http://cl-debian.alioth.debian.org/repository/pvaneynd/slime-upstream/ and did my thing in http://cl-debian.alioth.debian.org/repository/pvaneynd/slime/ Now I updated the slime-upstream repository and tried to pull those changes into slime, but after leaving it to run over the weekend it still was at 'diffing directory'. So I suspect there is a conflicting patch, but I'm at a loss to know which. I also tried using --partial to make smaller repositories, but even if I can merge the patch in the branch, merging it into the main repository seems equally difficult as working on the full repository. Is there a way to find out where darcs is blocking? This is getting a rather big problem for me and unless I find some ways to work round this problem I fear I will have to abandon darcs :-( 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| 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| From owner at bugs.debian.org Thu Aug 3 00:51:31 2006 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Wed, 02 Aug 2006 17:51:31 -0700 Subject: [cl-debian] Bug#368271: marked as done (No clsql_uffi64.so on amd64, but clsql_uffi.so instead.) References: <20060802233914.GA20781@rosenberg.net> <446FDC9E.2020809@corp.netease.com> Message-ID: Your message dated Wed, 2 Aug 2006 17:39:14 -0600 with message-id <20060802233914.GA20781 at rosenberg.net> and subject line clsql_uffi.so report 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: "Chun Tian (binghe)" Subject: No clsql_uffi64.so on amd64, but clsql_uffi.so instead. Date: Sun, 21 May 2006 11:21:02 +0800 Size: 4104 URL: -------------- next part -------------- An embedded message was scrubbed... From: Kevin Rosenberg Subject: clsql_uffi.so report Date: Wed, 2 Aug 2006 17:39:14 -0600 Size: 1852 URL: From fahree at gmail.com Thu Aug 3 03:32:16 2006 From: fahree at gmail.com (=?ISO-8859-1?Q?Far=E9?=) Date: Wed, 2 Aug 2006 23:32:16 -0400 Subject: [cl-debian] cl-launch in debian Message-ID: <653bea160608022032l30a191c5w365b2e872ad37cd1@mail.gmail.com> Dear all, I have a cl-launch 1.83 ready on my computer, that should close a current Debian bug in 1.80 as well as add ECL support. However, I'm not sure what to add in the Uploaders: field of the control file. Certainly, I need to put something since I'm not a Debian Developer (should I apply?). Will some kind DDs step up and accept to be official uploaders? Until you do, I will refrain from publishing a debian package. NB: cl-launch 1.83 is on its usual URL at http://fare.tunes.org/files/cl-launch/ but an up-to-date debian package is missing pending clarification. Thanks a lot for the efforts you put in cl-debian! [ Fran?ois-Ren? ?VB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Don't have good ideas if you aren't willing to be responsible for them. -- Alan Perlis From ssmith at vislab.usyd.edu.au Thu Aug 3 06:50:53 2006 From: ssmith at vislab.usyd.edu.au (Stephen Smith) Date: Thu, 03 Aug 2006 16:50:53 +1000 Subject: [cl-debian] Bug#381259: cl-sdl-opengl: No mapping for "gluOrtho2D" Message-ID: <20060803065053.17008.94054.reportbug@moth.vislab.usyd.edu.au> Package: cl-sdl-opengl Version: 1:0.2.2-3 Severity: normal Tags: patch There is no mapping for gluOrtho2D defined. Patch attached. There are probably others, I'll address them if/when I find them. Cheers, Steve diff -Nurw cl-sdl-0.2.2.orig/opengl/glu.lisp cl-sdl-0.2.2/opengl/glu.lisp --- cl-sdl-0.2.2.orig/opengl/glu.lisp 2006-04-28 01:28:23.000000000 +1000 +++ cl-sdl-0.2.2/opengl/glu.lisp 2006-08-03 16:01:58.000000000 +1000 @@ -106,3 +106,10 @@ (width gl:double) (height gl:double) (viewport (* gl:int))) + +(def-foreign-routine ("gluOrtho2D" ortho-2d) void + (left gl:double) + (right gl:double) + (bottom gl:double) + (top gl:double)) + -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages cl-sdl-opengl depends on: ii cl-sdl 1:0.2.2-3 Common Lisp bindings to the SDL gr ii cl-uffi 1.5.14-1 Universal Foreign Function Library ii libc6 2.3.6-16 GNU C Library: Shared libraries ii libgl1-mesa-glx [libgl1] 6.4.2-1 A free implementation of the OpenG ii libglu1-mesa [libglu1] 6.4.2-1 The OpenGL utility library (GLU) ii libglu1-mesa-dev [libglu-dev] 6.4.2-1 The OpenGL utility library -- deve cl-sdl-opengl recommends no packages. -- no debconf information From ruipb at debianpt.org Thu Aug 3 22:14:58 2006 From: ruipb at debianpt.org (Rui Branco) Date: Thu, 03 Aug 2006 23:14:58 +0100 Subject: [cl-debian] Bug#381375: [INTL:pt] Portuguese translation for common-lisp-controller (debconf)(correction) Message-ID: <44D27562.30102@debianpt.org> Package: common-lisp-controller Version: 6.1 Tags: l10n, patch Severity: wishlist Portuguese (pt) translation for common-lisp-controller's debconf messages by Ricardo Silva . Feel free to use it. For translation updated please contact Ricardo Silva and CC the Portuguese translation team -------------- next part -------------- # Portuguese translation for common-lisp-controller debconf messages. # This file is distributed under the same license as the common-lisp-controller package. # Ricardo Silva , 2006 # msgid "" msgstr "" "Project-Id-Version: common-lisp-controller 6.1\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2004-07-26 16:40+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Ricardo Silva \n" "Language-Team: Native Portuguese \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: string #. Default #: ../templates:3 msgid "Unknown" msgstr "Desconhecido" #. Type: string #. Description #: ../templates:4 msgid "The short common LISP site name" msgstr "O nome curto do site LISP comum" #. Type: string #. Description #: ../templates:4 msgid "" "You can configure what the common LISP implementations are going to use as " "\"short site name\". This is mostly unused except in some error reporting " "tools." msgstr "" "Pode configurar o que as implementa????es de LISP comum v??o usar como \"nome " "do site curto\". Isto ?? maioritariamente n??o usado excepto em algumas " "ferramentas de relat??rio de erros." #. Type: string #. Default #: ../templates:11 msgid "Site name not initialized" msgstr "Nome do site n??o inicializado" #. Type: string #. Description #: ../templates:12 msgid "The long common LISP site name" msgstr "O nome longo do site LISP comum" #. Type: string #. Description #: ../templates:12 msgid "" "You can configure what the common LISP implementations are going to use as " "\"long site name\". This is mostly unused except in some error reporting " "tools." msgstr "" "Pode configurar o que as implementa????es de LISP comum v??o usar como " "\"nome longo do site\". Isto ?? maioritariamente n??o usado excepto " "em algumas ferramentas de relat??rio de erros." From ruipb at debianpt.org Thu Aug 3 22:08:26 2006 From: ruipb at debianpt.org (Rui Branco) Date: Thu, 03 Aug 2006 23:08:26 +0100 Subject: [cl-debian] Bug#381374: [INTL:pt] Portuguese translation for common-lisp-controller (debconf) Message-ID: <44D273DA.3090208@debianpt.org> Package: common-lisp-controller Version: 6.1 Tags: l10n, patch Severity: wishlist Portuguese (pt) translation for common-lisp-controller's debconf messages by Ricardo Silva . Feel free to use it. For translation updated please contact Ricardo Silva and CC the Portuguese translation team -------------- next part -------------- # Portuguese translation for common-lisp-controller debconf messages. # This file is distributed under the same license as the common-lisp-controller package. # Ricardo Silva , 2006 # msgid "" msgstr "" "Project-Id-Version: common-lisp-controller 6.1\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2004-07-26 16:40+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Ricardo Silva \n" "Language-Team: Native Portuguese \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: string #. Default #: ../templates:3 msgid "Unknown" msgstr "Desconhecido" #. Type: string #. Description #: ../templates:4 msgid "The short common LISP site name" msgstr "O nome curto do site LISP comum" #. Type: string #. Description #: ../templates:4 msgid "" "You can configure what the common LISP implementations are going to use as " "\"short site name\". This is mostly unused except in some error reporting " "tools." msgstr "" "Pode configurar o que as implementa????es de LISP comum v??o usar como \"nome " "do site curto\". Isto ?? maioritariamente n??o usado excepto em algumas " "ferramentas de relat??rio de erros." #. Type: string #. Default #: ../templates:11 msgid "Site name not initialized" msgstr "Nome do site n??o inicializado" #. Type: string #. Description #: ../templates:12 msgid "The long common LISP site name" msgstr "O nome longo do site LISP comum" #. Type: string #. Description #: ../templates:12 msgid "" "You can configure what the common LISP implementations are going to use as " "\"long site name\". This is mostly unused except in some error reporting " "tools." msgstr "" "Pode configurar o que as implementa????es de LISP comum v??o usar como " "\"nome longo do site\". Isto ?? maioritariamente n??o usado excepto " "em algumas ferramentas de reportagem de erros." From rvb at debian.org Fri Aug 4 07:27:09 2006 From: rvb at debian.org (=?UTF-8?Q?Ren=C3=A9?= van Bevern) Date: Fri, 04 Aug 2006 09:27:09 +0200 Subject: Bug#381375: [cl-debian] Bug#381375: [INTL:pt] Portuguese translation for common-lisp-controller (debconf)(correction) In-Reply-To: <44D27562.30102@debianpt.org> (Rui Branco's message of "Thu, 03 Aug 2006 23:14:58 +0100") References: <44D27562.30102@debianpt.org> Message-ID: <87bqr17ygi.fsf@marx.progn.org> Rui Branco writes: Hello, > msgid "The short common LISP site name" > msgstr "O nome curto do site LISP comum" Does one really translate proper names like "Common Lisp" in portuguese? It is that the language is called "Common Lisp", as by the ANSI Standard. I agree that this fact doesn't come out from the english text very well either, because of its spelling. ;-) Ren? -- Heap exhausted, game over. -- Steel Bank Common Lisp's Garbage Collector running out of memory -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: not available URL: From ardoric at gmail.com Fri Aug 4 08:41:08 2006 From: ardoric at gmail.com (ardoRic) Date: Fri, 4 Aug 2006 09:41:08 +0100 Subject: Bug#381375: [cl-debian] Bug#381375: [INTL:pt] Portuguese translation for common-lisp-controller (debconf)(correction) In-Reply-To: <87bqr17ygi.fsf@marx.progn.org> References: <44D27562.30102@debianpt.org> <87bqr17ygi.fsf@marx.progn.org> Message-ID: Hi, On this particular case, I actually see no harm. Capitalization wouldnt harm, but having an english word in mid-sentence could be strange. Like you said, from the english text we couldn't make out very well that it was a proper name. I'll leave it to the proofreader (Rui) to make a final decision on this matter :) Ricardo Silva On 8/4/06, Ren? van Bevern wrote: > Rui Branco writes: > > Hello, > > > msgid "The short common LISP site name" > > msgstr "O nome curto do site LISP comum" > > Does one really translate proper names like "Common Lisp" in > portuguese? It is that the language is called "Common Lisp", as by the > ANSI Standard. > > I agree that this fact doesn't come out from the english text very > well either, because of its spelling. ;-) > > Ren? > -- > Heap exhausted, game over. > -- Steel Bank Common Lisp's Garbage Collector running out of memory > > > From luca at pca.it Fri Aug 4 08:59:48 2006 From: luca at pca.it (Luca Capello) Date: Fri, 04 Aug 2006 10:59:48 +0200 Subject: Bug#381375: [cl-debian] Bug#381375: [INTL:pt] Portuguese translation for common-lisp-controller (debconf)(correction) In-Reply-To: <87bqr17ygi.fsf@marx.progn.org> References: <44D27562.30102@debianpt.org> <87bqr17ygi.fsf@marx.progn.org> Message-ID: <87r6zwri4b.fsf@gismo.pca.it> Hello! On Fri, 04 Aug 2006 09:27:09 +0200, Ren? van Bevern wrote: > Rui Branco writes: >> msgid "The short common LISP site name" ^^^^^^ >> msgstr "O nome curto do site LISP comum" > > Does one really translate proper names like "Common Lisp" in > portuguese? It is that the language is called "Common Lisp", as by > the ANSI Standard. Shouldn't it be then "Common" (note the uppercase C) instead of "common"? In this case, IMHO it's more difficult to misunderstand the adjective as not part of the language name. Just my 0.02?... Thx, bye, Gismo / Luca -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: not available URL: From ruipb at debianpt.org Fri Aug 4 11:17:52 2006 From: ruipb at debianpt.org (Rui Branco) Date: Fri, 04 Aug 2006 12:17:52 +0100 Subject: Bug#381375: [cl-debian] Bug#381375: [INTL:pt] Portuguese translation for common-lisp-controller (debconf)(correction) In-Reply-To: <87r6zwri4b.fsf@gismo.pca.it> References: <44D27562.30102@debianpt.org> <87bqr17ygi.fsf@marx.progn.org> <87r6zwri4b.fsf@gismo.pca.it> Message-ID: <44D32CE0.8090000@debianpt.org> Luca Capello wrote: > Hello! > > On Fri, 04 Aug 2006 09:27:09 +0200, Ren? van Bevern wrote: > >> Rui Branco writes: >> >>> msgid "The short common LISP site name" >>> >>> >>> msgstr "O nome curto do site LISP comum" >>> >> Does one really translate proper names like "Common Lisp" in >> portuguese? It is that the language is called "Common Lisp", as by >> the ANSI Standard. >> > > Shouldn't it be then "Common" (note the uppercase C) instead of > "common"? In this case, IMHO it's more difficult to misunderstand the > adjective as not part of the language name. > > Just my 0.02?... > > Thx, bye, > Gismo / Luca > Hello all, Indeed IMHO there's no point to translate the language proper name. I agree with Luca, the translation that better suits is "Common Lisp". If that's fine with Ricardo , I will send the correction. Thank you all, Cheers, Rui Branco Portuguese Debian Translator Team (debianPT) From ruipb at debianpt.org Fri Aug 4 18:18:54 2006 From: ruipb at debianpt.org (Rui Branco) Date: Fri, 04 Aug 2006 19:18:54 +0100 Subject: [cl-debian] Bug#381375: [INTL:pt] Portuguese translation for common-lisp-controller (debconf) Message-ID: <44D38F8E.20809@debianpt.org> Package: common-lisp-controller Version: 6.1 Tags: l10n, patch Severity: wishlist Portuguese (pt) translation for common-lisp-controller's debconf messages by Ricardo Silva . Feel free to use it. For translation updated please contact Ricardo Silva and CC the Portuguese translation team -------------- next part -------------- # Portuguese translation for common-lisp-controller debconf messages. # This file is distributed under the same license as the common-lisp-controller package. # Ricardo Silva , 2006 # msgid "" msgstr "" "Project-Id-Version: common-lisp-controller 6.1\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2004-07-26 16:40+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Ricardo Silva \n" "Language-Team: Native Portuguese \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: string #. Default #: ../templates:3 msgid "Unknown" msgstr "Desconhecido" #. Type: string #. Description #: ../templates:4 msgid "The short common LISP site name" msgstr "O nome curto do site Common LISP" #. Type: string #. Description #: ../templates:4 msgid "" "You can configure what the common LISP implementations are going to use as " "\"short site name\". This is mostly unused except in some error reporting " "tools." msgstr "" "Pode configurar o que as implementa????es de Common LISP v??o usar como \"nome " "curto do site \". Isto n??o ?? maioritariamente usado excepto em algumas " "ferramentas de relat??rio de erros." #. Type: string #. Default #: ../templates:11 msgid "Site name not initialized" msgstr "Nome do site n??o inicializado" #. Type: string #. Description #: ../templates:12 msgid "The long common LISP site name" msgstr "O nome longo do site Common LISP" #. Type: string #. Description #: ../templates:12 msgid "" "You can configure what the common LISP implementations are going to use as " "\"long site name\". This is mostly unused except in some error reporting " "tools." msgstr "" "Pode configurar o que as implementa????es de Common LISP v??o usar como " "\"nome longo do site\". Isto n??o ?? maioritariamente usado excepto " "em algumas ferramentas de relat??rio de erros." From pvaneynd at debian.org Fri Aug 4 21:01:11 2006 From: pvaneynd at debian.org (Peter Van Eynde) Date: Fri, 4 Aug 2006 23:01:11 +0200 Subject: [cl-debian] yet another versioning change? Message-ID: <200608042301.12900.pvaneynd@debian.org> Hello, For the last week I've been trying to upgrade slime to the newest version and failed. slime-upstream works fine, but I cannot pull the changes into slime. I've send emails to the darcs-users list and debian-devel, but no-one offered any clues as to how I can solve this. I fear that basically darcs is not suited to debian package management because we often introduce 'conflicts' and 'doubleganger patches' (upstream includes a patch we've send). darcs seems to just break down under these conditions. I've been redoing my work on sbcl for the last year with bzr and so far it did not blow up ;-S. Using tailor to convert from darcs to bzr does seem to take quite some time and I have not been able to check if you can do a merge between a -upstream and a branch after converting them with tailor. I fear not and that would mean we would have to restart all repositories. again. Opinions? 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| From noreply at henning.makholm.net Sat Aug 5 21:08:22 2006 From: noreply at henning.makholm.net (Debian testing watch) Date: Sat, 05 Aug 2006 15:08:22 -0600 Subject: [cl-debian] ecl 0.9i-2 MIGRATED to testing Message-ID: FYI: The status of the ecl source package in Debian's testing distribution has changed. Previous version: 0.9i-1 Current version: 0.9i-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 Aug 5 21:08:18 2006 From: noreply at henning.makholm.net (Debian testing watch) Date: Sat, 05 Aug 2006 15:08:18 -0600 Subject: [cl-debian] cl-rsm-string 1.5 MIGRATED to testing Message-ID: FYI: The status of the cl-rsm-string source package in Debian's testing distribution has changed. Previous version: 1.4 Current version: 1.5 -- 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 Aug 5 21:08:18 2006 From: noreply at henning.makholm.net (Debian testing watch) Date: Sat, 05 Aug 2006 15:08:18 -0600 Subject: [cl-debian] cl-asdf 1.99-3 MIGRATED to testing Message-ID: FYI: The status of the cl-asdf source package in Debian's testing distribution has changed. Previous version: 1.99-2 Current version: 1.99-3 -- 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 Aug 5 21:08:18 2006 From: noreply at henning.makholm.net (Debian testing watch) Date: Sat, 05 Aug 2006 15:08:18 -0600 Subject: [cl-debian] cltl 1.0.20 MIGRATED to testing Message-ID: FYI: The status of the cltl source package in Debian's testing distribution has changed. Previous version: 1.0.19 Current version: 1.0.20 -- 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 Aug 5 21:08:31 2006 From: noreply at henning.makholm.net (Debian testing watch) Date: Sat, 05 Aug 2006 15:08:31 -0600 Subject: [cl-debian] hyperspec 1.22 MIGRATED to testing Message-ID: FYI: The status of the hyperspec source package in Debian's testing distribution has changed. Previous version: 1.21 Current version: 1.22 -- This email is automatically generated; henning at makholm.net is responsible. See http://people.debian.org/~henning/trille/ for more information. From owner at bugs.debian.org Mon Aug 7 10:18:12 2006 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Mon, 07 Aug 2006 03:18:12 -0700 Subject: [cl-debian] Processed: reassign 365230 to mcvs In-Reply-To: <20060807095759.ADE50179C70@sharrow> References: <20060807095759.ADE50179C70@sharrow> Message-ID: Processing commands for control at bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.9.20 > reassign 365230 mcvs Bug#365230: mcvs - FTBFS: There is no package with name "FFI" Bug#230947: There is no package with name "FFI" for hppa Bug#270876: clisp: FFI not available on arm hppa m68k mips mipsel s390 Bug reassigned from package `clisp' to `mcvs'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) From pvaneynd at debian.org Mon Aug 7 10:03:28 2006 From: pvaneynd at debian.org (Peter Van Eynde) Date: Mon, 7 Aug 2006 12:03:28 +0200 Subject: [cl-debian] Bug#365230: mcvs should not be build on non-FFI enabled architectures Message-ID: <200608071203.31782.pvaneynd@debian.org> Hello, As clisp does not provide a FFI on: arm hppa ia64 m68k s390 mcvs should not be build on those architectures. 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| From pvaneynd at debian.org Mon Aug 7 14:02:11 2006 From: pvaneynd at debian.org (Peter Van Eynde) Date: Mon, 07 Aug 2006 07:02:11 -0700 Subject: [cl-debian] Accepted cl-sdl 1:0.2.2-4 (source i386 all) Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Sat, 5 Aug 2006 22:54:44 +0200 Source: cl-sdl Binary: cl-sdl-ttf cl-sdl cl-sdl-opengl cl-sdl-mix cl-sdl-demos cl-sdl-img Architecture: source i386 all Version: 1:0.2.2-4 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde Changed-By: Peter Van Eynde Description: cl-sdl - Common Lisp bindings to the SDL graphics library cl-sdl-demos - CL-SDL and OpenGL example programs cl-sdl-img - Support for the SDL_image library in Common Lisp cl-sdl-mix - Support for the SDL_mixer library in Common Lisp cl-sdl-opengl - Support for OpenGL in Common Lisp, via CL-SDL cl-sdl-ttf - Support for the SDL_ttf library in Common Lisp Closes: 381259 Changes: cl-sdl (1:0.2.2-4) unstable; urgency=low . * Included patch from Stephen Smith for gluOrtho2D support. (Closes: #381259) Files: 9575445d4b1a8ac5e9e574fee9484aa8 775 devel optional cl-sdl_0.2.2-4.dsc 42e9b91b34977140bed78761f800f83f 2656 devel optional cl-sdl_0.2.2-4.diff.gz d0e1fd242d580c853aed1e6439e9370a 68900 devel optional cl-sdl-demos_0.2.2-4_all.deb a71fc7fa0a26bb143d15735a10445c1a 29148 devel optional cl-sdl_0.2.2-4_i386.deb c3dc5f1f5acb1a6b00d64accbb127985 22332 devel optional cl-sdl-opengl_0.2.2-4_i386.deb 5759b371e7d72534c7ac1b628a22d66b 8178 devel optional cl-sdl-ttf_0.2.2-4_i386.deb a9c7a5dc2f7460040cbbd2738ee9ca4e 6456 devel optional cl-sdl-img_0.2.2-4_i386.deb 4e0ec8ef823cdc77d14aa30be766c5a2 7408 devel optional cl-sdl-mix_0.2.2-4_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE1l4g11ldN0tyliURAsv7AJ9QwuRctflkd1BRy07mkrFN8yvt9QCfWbe1 akqFmnMdBVS3rav0fVaDMwM= =o7+U -----END PGP SIGNATURE----- Accepted: cl-sdl-demos_0.2.2-4_all.deb to pool/main/c/cl-sdl/cl-sdl-demos_0.2.2-4_all.deb cl-sdl-img_0.2.2-4_i386.deb to pool/main/c/cl-sdl/cl-sdl-img_0.2.2-4_i386.deb cl-sdl-mix_0.2.2-4_i386.deb to pool/main/c/cl-sdl/cl-sdl-mix_0.2.2-4_i386.deb cl-sdl-opengl_0.2.2-4_i386.deb to pool/main/c/cl-sdl/cl-sdl-opengl_0.2.2-4_i386.deb cl-sdl-ttf_0.2.2-4_i386.deb to pool/main/c/cl-sdl/cl-sdl-ttf_0.2.2-4_i386.deb cl-sdl_0.2.2-4.diff.gz to pool/main/c/cl-sdl/cl-sdl_0.2.2-4.diff.gz cl-sdl_0.2.2-4.dsc to pool/main/c/cl-sdl/cl-sdl_0.2.2-4.dsc cl-sdl_0.2.2-4_i386.deb to pool/main/c/cl-sdl/cl-sdl_0.2.2-4_i386.deb From pvaneynd at debian.org Mon Aug 7 14:02:12 2006 From: pvaneynd at debian.org (Peter Van Eynde) Date: Mon, 07 Aug 2006 07:02:12 -0700 Subject: [cl-debian] Accepted common-lisp-controller 6.2 (source all) Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Mon, 7 Aug 2006 07:35:13 +0200 Source: common-lisp-controller Binary: common-lisp-controller Architecture: source all Version: 6.2 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde Changed-By: Peter Van Eynde Description: common-lisp-controller - This is a Common Lisp source and compiler manager Closes: 381374 381375 Changes: common-lisp-controller (6.2) unstable; urgency=low . * Added debconf-updatepo to clean target * Included Portuguese translation for common-lisp-controller (Closes: #381375, #381374) * Updated standard version without real changes Files: af400d3f7ed66d1cc6ef830a799712ab 585 devel optional common-lisp-controller_6.2.dsc 19286635266e6c6e46c44ef18082d257 31530 devel optional common-lisp-controller_6.2.tar.gz 925955040d6b8829f37c488e225fc89a 30516 devel optional common-lisp-controller_6.2_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE1tGP11ldN0tyliURAlopAJ9qKumNAmycI2ObuoXhlKOYqzP+bQCgrlod 7slWTGgfFa84vgIy0tddhas= =WYp9 -----END PGP SIGNATURE----- Accepted: common-lisp-controller_6.2.dsc to pool/main/c/common-lisp-controller/common-lisp-controller_6.2.dsc common-lisp-controller_6.2.tar.gz to pool/main/c/common-lisp-controller/common-lisp-controller_6.2.tar.gz common-lisp-controller_6.2_all.deb to pool/main/c/common-lisp-controller/common-lisp-controller_6.2_all.deb From pvaneynd at debian.org Mon Aug 7 14:02:29 2006 From: pvaneynd at debian.org (Peter Van Eynde) Date: Mon, 07 Aug 2006 07:02:29 -0700 Subject: [cl-debian] Accepted sbcl 1:0.9.15.0-1 (source all i386) Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Sat, 5 Aug 2006 23:15:03 +0200 Source: sbcl Binary: sbcl sbcl-source sbcl-doc Architecture: source all i386 Version: 1:0.9.15.0-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde Changed-By: Peter Van Eynde 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:0.9.15.0-1) unstable; urgency=low . [ Ren?? van Bevern ] . * manually bootstrapped the previous SBCL version on Sparc, so that SBCL should autobuild again there . * Build SBCL on Sparc and Alpha with GCC 4.1 + fixed src/runtime/{sparc,alpha}-arch.c for compilation with GCC 4.1 + debian/control: do not depend on gcc-3.4 for sparc, alpha + debian/rules: use gcc (default 4.1) for sparc and alpha . * debian/ld-script.alpha-linux: document the purpose of this ld script . * Minor cleanup of our diff.gz: reverted Debian's changes on files: + src/runtime/ld-script.alpha-linux: overwritten by debian/ld-script.alpha-linux at build-time + src/runtime/Config.alpha-linux, src/code/toplevel.lisp: they had no effect . [ Peter Van Eynde ] * Move to bzr * New upstream, changes: - added support for the ucs-2 external format. (contributed by Ivan Boldyrev) - minor incompatible change: pretty printing of objects of type (cons symbol) is, in the default pprint-dispatch-table, now sensitive to whether the symbol satisfies FBOUNDP. (thanks to Marcus Pearce) - minor incompatible change: SB-MOP:FINALIZE-INHERITANCE is now called later in a class's lifetime, possibly as late as when the first instance of the class is created. Previously, SB-MOP:FINALIZE-INHERITANCE was called by the system as soon as a class became finalizeable. - fixed bug: FILE-POSITION sometimes returned inconsistent results for multibyte external-format streams. (thanks to "vbzoli") - fixed bug: CHANGE-CLASS would fail to preserve the values of slots with :ALLOCATION :CLASS inherited from superclasses of the original class. - fixed bug: anonymous classes can now be created using the :NAME initarg and MAKE-INSTANCE / REINITIALIZE-INSTANCE, as specified by AMOP. (reported by Leonid Slobodov on comp.lang.lisp) - fixed bug: core-files saved with :EXECUTABLE T can again be executed when SBCL_HOME isn't set. (reported by James Knight) - fixed bug: toplevel LOCALLY forms with declarations could occasionally get miscompiled. (reported by Yaroslav Kavenchuk) - fixed bug: printing from several different threads using different values of *print-case* could cause invalid output, due to some internal special variables of the printer not being bound thread-locally (reported by Max Mikhanosha) - fixed bug: SPECIALIZER metaobjects (including anonymous classes and EQL-SPECIALIZERs) can be used as specializers to DEFMETHOD. (reported by Pascal Costanza) - fixed bug: FINALIZE-INHERITANCE is called from REINITIALIZE-INSTANCE on classes when the class has previously been finalized, as required by AMOP. - minor code generation optimizations: ** better register allocation in CLOS dispatching functions ** overflow detection when coercing signed bytes to fixnums on x86-64 ** is now implemented with one IMUL instruction instead of three shifts ** more efficient bit-vector access on x86 and x86-64 ** more efficient access to raw structure slots on x86 and x86-64 - fixed some bugs revealed by Paul Dietz' test suite: ** ENSURE-DIRECTORIES-EXIST.8: ENSURE-DIRECTORIES-EXIST must return its argument. Files: 8662ced81a6432b78cf5affedd4693d9 694 devel optional sbcl_0.9.15.0-1.dsc 04455e084c2a1e0e331fc12e0a22fe70 4023239 devel optional sbcl_0.9.15.0.orig.tar.gz 00b7ffc9d338bc014e60fe2da89862db 22771 devel optional sbcl_0.9.15.0-1.diff.gz 269725beda8c5831699c9285f2ceeb9a 1314918 doc optional sbcl-doc_0.9.15.0-1_all.deb 0ba46e83aebb2a8064967a460d519220 3278866 doc optional sbcl-source_0.9.15.0-1_all.deb f0f28c7b572ffa92607ade8035ae72a3 8361180 devel optional sbcl_0.9.15.0-1_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE1mcj11ldN0tyliURAobeAKCY/BP+o/kXC5T6CP4vyXE5I838UQCgqnWb dkxZdlHN2oyRSAgGOhgj61M= =dTW2 -----END PGP SIGNATURE----- Accepted: sbcl-doc_0.9.15.0-1_all.deb to pool/main/s/sbcl/sbcl-doc_0.9.15.0-1_all.deb sbcl-source_0.9.15.0-1_all.deb to pool/main/s/sbcl/sbcl-source_0.9.15.0-1_all.deb sbcl_0.9.15.0-1.diff.gz to pool/main/s/sbcl/sbcl_0.9.15.0-1.diff.gz sbcl_0.9.15.0-1.dsc to pool/main/s/sbcl/sbcl_0.9.15.0-1.dsc sbcl_0.9.15.0-1_i386.deb to pool/main/s/sbcl/sbcl_0.9.15.0-1_i386.deb sbcl_0.9.15.0.orig.tar.gz to pool/main/s/sbcl/sbcl_0.9.15.0.orig.tar.gz From owner at bugs.debian.org Mon Aug 7 14:49:05 2006 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Mon, 07 Aug 2006 07:49:05 -0700 Subject: [cl-debian] Bug#381374: marked as done ([INTL:pt] Portuguese translation for common-lisp-controller (debconf)) References: <44D273DA.3090208@debianpt.org> Message-ID: Your message dated Mon, 07 Aug 2006 07:02:12 -0700 with message-id and subject line Bug#381374: fixed in common-lisp-controller 6.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: Rui Branco Subject: [INTL:pt] Portuguese translation for common-lisp-controller (debconf) Date: Thu, 03 Aug 2006 23:08:26 +0100 Size: 4216 URL: -------------- next part -------------- An embedded message was scrubbed... From: Peter Van Eynde Subject: Bug#381374: fixed in common-lisp-controller 6.2 Date: Mon, 07 Aug 2006 07:02:12 -0700 Size: 3151 URL: From owner at bugs.debian.org Mon Aug 7 14:49:03 2006 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Mon, 07 Aug 2006 07:49:03 -0700 Subject: [cl-debian] Bug#381259: marked as done (cl-sdl-opengl: No mapping for "gluOrtho2D") References: <20060803065053.17008.94054.reportbug@moth.vislab.usyd.edu.au> Message-ID: Your message dated Mon, 07 Aug 2006 07:02:11 -0700 with message-id and subject line Bug#381259: fixed in cl-sdl 1:0.2.2-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -------------- next part -------------- An embedded message was scrubbed... From: Stephen Smith Subject: cl-sdl-opengl: No mapping for "gluOrtho2D" Date: Thu, 03 Aug 2006 16:50:53 +1000 Size: 2805 URL: -------------- next part -------------- An embedded message was scrubbed... From: Peter Van Eynde Subject: Bug#381259: fixed in cl-sdl 1:0.2.2-4 Date: Mon, 07 Aug 2006 07:02:11 -0700 Size: 3977 URL: From owner at bugs.debian.org Mon Aug 7 14:49:07 2006 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Mon, 07 Aug 2006 07:49:07 -0700 Subject: [cl-debian] Bug#381375: marked as done ([INTL:pt] Portuguese translation for common-lisp-controller (debconf)(correction)) References: <44D27562.30102@debianpt.org> Message-ID: Your message dated Mon, 07 Aug 2006 07:02:13 -0700 with message-id and subject line Bug#381375: fixed in common-lisp-controller 6.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: Rui Branco Subject: [INTL:pt] Portuguese translation for common-lisp-controller (debconf)(correction) Date: Thu, 03 Aug 2006 23:14:58 +0100 Size: 4210 URL: -------------- next part -------------- An embedded message was scrubbed... From: Peter Van Eynde Subject: Bug#381375: fixed in common-lisp-controller 6.2 Date: Mon, 07 Aug 2006 07:02:13 -0700 Size: 3176 URL: From luca at pca.it Mon Aug 7 15:57:19 2006 From: luca at pca.it (Luca Capello) Date: Mon, 07 Aug 2006 17:57:19 +0200 Subject: [cl-debian] yet another versioning change? In-Reply-To: <200608042301.12900.pvaneynd@debian.org> References: <200608042301.12900.pvaneynd@debian.org> Message-ID: <87wt9kmtcw.fsf@gismo.pca.it> Hello! Sorry for the long mail, it contains a bit of output to explain my problem. On Fri, 04 Aug 2006 23:01:11 +0200, Peter Van Eynde wrote: > For the last week I've been trying to upgrade slime to the newest > version and failed. slime-upstream works fine, but I cannot pull the > changes into slime. If you remember, I have a similar problem with my arnesi repositories: every time I pull from arnesi-upstream into arnesi, the pull takes at least 90min (with the darcs process going up to 99% of the CPU). This was probably due to some `darcs unrecord` I performed on arnesi (not -upstream) and it's reproducible with a fresh copy: ===== luca at gismo:~$ cd test/ luca at gismo:~/test$ ls arnesi* ls: arnesi*: No such file or directory luca at gismo:~/test$ time darcs get \ http://cl-debian.alioth.debian.org/repository/lcapello/arnesi-upstream Copying patch 285 of 285... done! Applying patch 285 of 285... done. Finished getting. real 0m18.841s user 0m0.948s sys 0m0.040s luca at gismo:~/test$ time darcs get \ http://cl-debian.alioth.debian.org/repository/lcapello/arnesi Copying patch 307 of 307... done! Applying patch 307 of 307... done. Finished getting. real 1m44.539s user 0m1.032s sys 0m0.112s luca at gismo:~/test$ cd arnesi-upstream/ luca at gismo:~/test/arnesi-upstream$ time darcs pull --all \ http://common-lisp.net/project/bese/repos/arnesi_dev Pulling from "http://common-lisp.net/project/bese/repos/arnesi_dev"... Finished pulling and applying. real 0m1.930s user 0m0.220s sys 0m0.004s luca at gismo:~/test/arnesi-upstream$ cd ../arnesi luca at gismo:~/test/arnesi$ time darcs pull ../arnesi-upstream/ Pulling from "../arnesi-upstream"... withSignalsHandled: Interrupted! real 11m48.508s user 11m20.451s sys 0m1.624s luca at gismo:~/test/arnesi$ ===== > I've send emails to the darcs-users list and debian-devel, but > no-one offered any clues as to how I can solve this. I read them. I asked once on #darcs at irc.freenode.net about my problem with arnesi, but no one could solve it :-( > I fear that basically darcs is not suited to debian package > management because we often introduce 'conflicts' and 'doubleganger > patches' (upstream includes a patch we've send). darcs seems to just > break down under these conditions. Well, actually I think for me darcs is OK because I work differently AFAIU. I don't record the debian specific patches as darcs patches, but I apply them through dpatch instead (and `darcs record` the dpatch files). In this case, if a patch is applied upstream, it's just a question of removing the corresponding dpatch file. I know that this isn't probably the aim of an SCM, but it works quite well for me, so I'm not inclined to change it. > I've been redoing my work on sbcl for the last year with bzr and so > far it did not blow up ;-S. Using tailor to convert from darcs to > bzr does seem to take quite some time and I have not been able to > check if you can do a merge between a -upstream and a > branch after converting them with tailor. I fear not and that would > mean we would have to restart all repositories. again. IMHO this won't be a problem as far as the debian/changelog documents all the changes. > Opinions? I'm for one SCM for all the CL-Debian packages, but we need to deal with different upstream SCMs and in my case most of them uses darcs. I don't really know what the Right Thing? is :-( Thx, bye, Gismo / Luca -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: not available URL: From luca at pca.it Mon Aug 7 16:01:22 2006 From: luca at pca.it (Luca Capello) Date: Mon, 07 Aug 2006 18:01:22 +0200 Subject: [cl-debian] Problem when trying to use pdebuild In-Reply-To: <200607261041.47734.pvaneynd@mailworks.org> References: <87d5bttbby.fsf@gismo.pca.it> <200607261041.47734.pvaneynd@mailworks.org> Message-ID: <87r6zsmt65.fsf@gismo.pca.it> Hello! On Wed, 26 Jul 2006 10:41:46 +0200, Peter Van Eynde wrote: > Good luck with pbuilder, I never got it to work as I wanted :-( Actually, it works quite well on my Debian, except for the fact that it's not optimized for speed (i.e., it still uses the base.tgz mechanism instead of cowdancer). What I was missing is the automatic lintian and linda checks as debuild, so I hacked the /usr/bin/pdebuild script. About this subject, a bug is already present in the BTS (bug #357066 [1]), so ASAP I'll add there my hacks. Thx, bye, Gismo / Luca Footnotes: [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357066 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: not available URL: From pvaneynd at debian.org Tue Aug 8 09:30:30 2006 From: pvaneynd at debian.org (Peter Van Eynde) Date: Tue, 8 Aug 2006 11:30:30 +0200 Subject: [cl-debian] yet another versioning change? In-Reply-To: <200608042301.12900.pvaneynd@debian.org> References: <200608042301.12900.pvaneynd@debian.org> Message-ID: <200608081130.31910.pvaneynd@debian.org> Alle Friday 04 August 2006 23:01, Peter Van Eynde ha scritto: > I've been redoing my work on sbcl for the last year with bzr and so far it did > not blow up ;-S I've uploaded my test bzr repositories to alioth. You can do a branch with To get the repository: $ bzr branch http://cl-debian.alioth.debian.org/repository/pvaneynd/bzr-moved/sbcl/ To add files: $ bzr add To commit changes: $ bzr commit -m 'added unicode support' To see what changed: $ bzr diff To unify with another tree: $ bzr merge after which you have to do a commit to commit the merge. (Which is a bit nicer then in darcs) Sending your changes via email seems to be coming soon: http://bazaar-vcs.org/SubmitByMail I have also make a yet-untested http://cl-debian.alioth.debian.org/repository/pvaneynd/bzr-moved/bzr-build.sh script. It uses a special commit message of UPSTREAM_sbcl_0.9.15.0 to act as 'tag'. I expect bzr to gain tags soonish (http://bazaar-vcs.org/BzrTagging), but with this trick I can handle my work-flow as is. The repositories that darcs can handle I'll just leave as-is for the moment. 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| From pvaneynd at mailworks.org Wed Aug 2 19:41:10 2006 From: pvaneynd at mailworks.org (Peter Van Eynde) Date: Wed, 2 Aug 2006 21:41:10 +0200 Subject: [cl-debian] [darcs-users] Re: Using Darcs for Debian package maintenance Message-ID: <200608022141.11328.pvaneynd@mailworks.org> Hello, Hello, I fear I'm running into some problems using darcs for my debian packages: pull's are getting slower and slower and in some cases are not finishing even over the weekend. I'm putting what I learn on the debian wiki (http://wiki.debian.org/PackagingWithDarcsAndTailor). Basicly I often have a 'doubleganger' patch problem. I import upstream changes (in the past from a tarfile or directly from cvs, now with tailor) into -upstream, do a 'get' into a repository, and do my debian stuff in that directory. When upstream releases a new version I pull/import this into the -upstream repository and then pull this into the directory. The problem is that sometimes upstream applies my patches and I get a doubleganger, and I've managed to hack round them most of the time. But now I have a issue with slime, that I do not think is a doubleganger. I imported the (then) current CVS into http://cl-debian.alioth.debian.org/repository/pvaneynd/slime-upstream/ and did my thing in http://cl-debian.alioth.debian.org/repository/pvaneynd/slime/ Now I updated the slime-upstream repository and tried to pull those changes into slime, but after leaving it to run over the weekend it still was at 'diffing directory'. So I suspect there is a conflicting patch, but I'm at a loss to know which. I also tried using --partial to make smaller repositories, but even if I can merge the patch in the branch, merging it into the main repository seems equally difficult as working on the full repository. Is there a way to find out where darcs is blocking? This is getting a rather big problem for me and unless I find some ways to work round this problem I fear I will have to abandon darcs :-( 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| 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| _______________________________________________ darcs-users mailing list darcs-users at darcs.net http://www.abridgegame.org/mailman/listinfo/darcs-users From alceste at muvara.org Tue Aug 8 20:44:24 2006 From: alceste at muvara.org (Alceste Scalas) Date: Tue, 08 Aug 2006 22:44:24 +0200 Subject: [cl-debian] Blatant Mercurial plug [was: yet another versioning change?] In-Reply-To: <200608081130.31910.pvaneynd@debian.org> References: <200608042301.12900.pvaneynd@debian.org> <200608081130.31910.pvaneynd@debian.org> Message-ID: <1155069864.6236.36.camel@sidoru> Il giorno mar, 08/08/2006 alle 11.30 +0200, Peter Van Eynde ha scritto: > Sending your changes via email seems to be coming soon: > http://bazaar-vcs.org/SubmitByMail > > [...] > > I have also make a yet-untested > http://cl-debian.alioth.debian.org/repository/pvaneynd/bzr-moved/bzr-build.sh > script. It uses a special commit message of UPSTREAM_sbcl_0.9.15.0 to act > as 'tag'. I expect bzr to gain tags soonish > (http://bazaar-vcs.org/BzrTagging), but with this trick I can handle my > work-flow as is. If you're going to do some tests, I'd suggest to try Mercurial: http://selenic.com/mercurial I've used it for some time (with small source trees), without problems and with a lot of pleasure. Some goods: * it is fully supported by Tailor; * it supports tagging; * it supports sending and importing changeset via email; * it does scale. About scaling: Mercurial was created as an alterative to Git for the development of Linux, and their speed is almost the same (but Mercurial is written in Python instead of C, and requires a lot less bandwidth and disk space for transmitting and managing repositories). It is currently hosting the Linux source tree (see http://kernel.org/hg/linux-2.6/ ) and has been selected as the official distributes SCM system for OpenSolaris. Oh, it also offers a nice webserver/CGI for browsing the repositories, generating RSS feeds for changelogs, and eventually push'ing changesets through HTTP/HTTPS. Regards, alceste -- Alceste Scalas -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 191 bytes Desc: Questa ? una parte del messaggio firmata digitalmente URL: From noreply at henning.makholm.net Tue Aug 8 21:08:06 2006 From: noreply at henning.makholm.net (Debian testing watch) Date: Tue, 08 Aug 2006 15:08:06 -0600 Subject: [cl-debian] cl-ppcre 1.2.16-1 MIGRATED to testing Message-ID: FYI: The status of the cl-ppcre source package in Debian's testing distribution has changed. Previous version: 1.2.15-1 Current version: 1.2.16-1 -- This email is automatically generated; henning at makholm.net is responsible. See http://people.debian.org/~henning/trille/ for more information. From fahree at gmail.com Tue Aug 8 21:14:54 2006 From: fahree at gmail.com (=?ISO-8859-1?Q?Far=E9?=) Date: Tue, 8 Aug 2006 17:14:54 -0400 Subject: [cl-debian] gclcvs? Message-ID: <653bea160608081414o2c5645cdkfcc67446a523bd0c@mail.gmail.com> gclcvs seems completely broken in unstable, with a series of long outstanding issues. Is it now officially unsupported? I wanted to fix the support for GCL 2.7.0 in cl-launch... [ Fran?ois-Ren? ?VB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Can anyone squash this butterfly in Tokyo? I'm sick with its flapping wings changing the outcome of my life. From noreply at henning.makholm.net Tue Aug 8 21:08:06 2006 From: noreply at henning.makholm.net (Debian testing watch) Date: Tue, 08 Aug 2006 15:08:06 -0600 Subject: [cl-debian] cl-who 0.6.1-1 MIGRATED to testing Message-ID: FYI: The status of the cl-who source package in Debian's testing distribution has changed. Previous version: 0.6.0-1 Current version: 0.6.1-1 -- This email is automatically generated; henning at makholm.net is responsible. See http://people.debian.org/~henning/trille/ for more information. From trentbuck at gmail.com Tue Aug 8 23:47:13 2006 From: trentbuck at gmail.com (Trent Buck) Date: Wed, 9 Aug 2006 09:47:13 +1000 Subject: [cl-debian] Blatant Mercurial plug [was: yet another versioning change?] In-Reply-To: <1155069864.6236.36.camel@sidoru> References: <200608042301.12900.pvaneynd@debian.org> <200608081130.31910.pvaneynd@debian.org> <1155069864.6236.36.camel@sidoru> Message-ID: <20060808234713.GB6701@malambruno.twb.ath.cx> On Tue, Aug 08, 2006 at 10:44:24PM +0200, Alceste Scalas wrote: > If you're going to do some tests, I'd suggest to try Mercurial. See also http://en.wikipedia.org/wiki/Comparison_of_revision_control_software -- Trent Buck, Student Errant From lamont at debian.org Wed Aug 9 08:46:30 2006 From: lamont at debian.org (lamont at debian.org) Date: Wed, 9 Aug 2006 02:46:30 -0600 Subject: [cl-debian] Bug#382145: gcl_2.6.7-17(ia64/unstable): FTBFS: "Can't allocate." Message-ID: <20060809084630.GI5985@mmjgroup.com> Package: gcl Version: 2.6.7-17 Severity: serious There was an error while trying to autobuild your package: > Automatic build of gcl_2.6.7-17 on caballero by sbuild/ia64 85 > Build started at 20060803-1527 [...] > ** Using build dependencies supplied by package: > Build-Depends: debhelper (>= 4.1.16), libreadline5-dev | libreadline-dev, m4, tk8.4-dev, tetex-bin, texinfo, libgmp3-dev, autotools-dev, libxmu-dev, libxaw7-dev [...] > ("gcl_Xlib" "gcl_Xutil" "gcl_X" "gcl_XAtom" "gcl_defentry-events" > "gcl_Xstruct" "gcl_XStruct-l-3" "gcl_general" "gcl_keysymdef" > "gcl_X10" "gcl_Xinit" "gcl_dwtrans" "gcl_tohtml" "gcl_index") > > > > Unrecoverable error: Can't allocate. Good-bye!. > sh: line 1: 12091 Aborted ./raw_saved_xgcl /build/buildd/gcl-2.6.7/unixport/ > "saved_xgcl" > > >make[2]: Leaving directory `/build/buildd/gcl-2.6.7/xgcl-2' > mv: cannot stat `saved_xgcl': No such file or directory > make[1]: *** [system] Error 1 > make[1]: Leaving directory `/build/buildd/gcl-2.6.7' > make: *** [build-gprof-stamp] Error 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=ia64&pkg=gcl&ver=2.6.7-17 From fare at tunes.org Wed Aug 9 17:57:53 2006 From: fare at tunes.org (Francois-Rene Rideau) Date: Wed, 09 Aug 2006 13:57:53 -0400 Subject: [cl-debian] Bug#382247: gclcvs segfaults during c-l-c initialization Message-ID: <20060809175753.7138.52653.reportbug@lux> Package: gclcvs Version: 2.7.0-54 Severity: grave Justification: renders package unusable gclcvs.sh seems to not have been updated for the latest common-lisp-controller, and dies horribly on both i386 and amd64 architectures. On amd64, the error is as follows: COMMON-LISP-CONTROLLER>/usr/lib/common-lisp/bin/gclcvs.sh: line 58: 7556 Bus error $gcl_bin <Segmentation violation: c stack ok:signalling error/usr/lib/common-lisp/bin/gclcvs.sh: line 58: 6462 Segmentation fault $gcl_bin <' is created, and the feeble attempt to remove it with rm fails; rmdir would be required instead. ------>8------>8------>8------>8------>8------>8------>8------>8------>8------ Unpacking gclcvs (from .../gclcvs_2.7.0-54_i386.deb) ... Setting up gclcvs (2.7.0-54) ... gclcvs.sh Uninstalling clc image and purging object cache ... chown: `cl-builder.cl-builder': invalid user rm: cannot remove `>': Is a directory gclcvs.sh Installing clc as /usr/lib/gcl-2.7.0/unixport/saved_clc_gcl > ... GCL (GNU Common Lisp) 2.7.0 ANSI Dec 23 2005 04:17:17 Source License: LGPL(gcl,gmp,pargcl), GPL(unexec,bfd) Binary License: GPL due to GPL'ed components: (READLINE BFD UNEXEC) Modifications of this banner must retain notice of a compatible license Dedicated to the memory of W. Schelter Use (help) to get some basic information on how to use GCL. > #<"COMMON-LISP" package> COMMON-LISP> NIL COMMON-LISP> #<"COMMON-LISP-USER" package> > Loading /usr/share/common-lisp/source/common-lisp-controller/common-lisp-controller.lisp Finished loading /usr/share/common-lisp/source/common-lisp-controller/common-lisp-controller.lisp T > #<"COMMON-LISP-CONTROLLER" package> COMMON-LISP-CONTROLLER>Segmentation violation: c stack ok:signalling error/usr/lib/common-lisp/bin/gclcvs.sh: line 58: 6462 Segmentation fault $gcl_bin <8------>8------>8------>8------>8------>8------>8------>8------>8------ # dpkg --purge gclcvs (Reading database ... 263914 files and directories currently installed.) Removing gclcvs ... gclcvs.sh Uninstalling clc and restoring pristine orig image ... rm: cannot remove `>': Is a directory gclcvs.sh Uninstalling clc and restoring pristine orig image ... rm: cannot remove `>': Is a directory remove/gclcvs: purging byte-compiled files for emacs21 remove/gclcvs: purging byte-compiled files for xemacs21 Purging configuration files for gclcvs ... ------>8------>8------>8------>8------>8------>8------>8------>8------>8------ -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages gclcvs depends on: ii debconf [debconf-2.0] 1.5.2 Debian configuration management sy ii gcc 4:4.1.1-5 The GNU C compiler ii libc6 2.3.6-15 GNU C Library: Shared libraries ii libgmp3c2 2:4.2.1+dfsg-3 Multiprecision arithmetic library ii libncurses5 5.5-2 Shared libraries for terminal hand ii libreadline5 5.1-7 GNU readline and history libraries ii libx11-6 2:1.0.0-7 X11 client-side library ii tcl8.4 8.4.12-1.1 Tcl (the Tool Command Language) v8 ii tk8.4 8.4.12-1 Tk toolkit for Tcl and X11, v8.4 - gclcvs recommends no packages. From fahree at gmail.com Thu Aug 10 02:48:19 2006 From: fahree at gmail.com (=?ISO-8859-1?Q?Far=E9?=) Date: Wed, 9 Aug 2006 22:48:19 -0400 Subject: [cl-debian] Re: cl-launch in debian In-Reply-To: <653bea160608022032l30a191c5w365b2e872ad37cd1@mail.gmail.com> References: <653bea160608022032l30a191c5w365b2e872ad37cd1@mail.gmail.com> Message-ID: <653bea160608091948m29480131h210441cb58fcf7d6@mail.gmail.com> Dear all,, I have a cl-launch 1.84 in http://fare.tunes.org/files/cl-launch/ ECL is now fully supported, including for image-dumping (with ugly kluges). But until the ECL debian package is fixed to use ECL's asdf and to not mess up with *load-verbose*, you need to export ECL=/usr/lib/ecl/ecl-original for cl-launch to work properly. Also a few minor bugs were fixed, including some debian issues since previous debian package 1.80. I assumed Rene and Peter were my Uploaders. If not, the control file should be changed appropriately by my mysterious mentor to reveal himself. [ Fran?ois-Ren? ?VB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] I'd rather write programs that write programs than write programs -- Dick Sites From aman.ehsan at afghan-wireless.com Thu Aug 10 06:00:50 2006 From: aman.ehsan at afghan-wireless.com (Amanullah Ehsan) Date: Thu, 10 Aug 2006 10:30:50 +0430 Subject: [cl-debian] IP Blakclisted Message-ID: <3645DB021B475E47803A8DDEEF18143A4DEB84@mail.afghan-wireless.com> My IP is blacklisted in blars.org database there is no contact information available in the web site any one can help me getting contact information. Aman -------------- next part -------------- An HTML attachment was scrubbed... URL: From edi at agharta.de Thu Aug 10 15:29:28 2006 From: edi at agharta.de (Edi Weitz) Date: Thu, 10 Aug 2006 17:29:28 +0200 Subject: [cl-debian] [ann] [rdnzl-announce] New version 0.10.1 Message-ID: ChangeLog: Version 0.10.1 2006-08-10 DSPEC definitions for LispWorks Download: http://weitz.de/files/RDNZL.tar.gz These changes only affect LispWorks users who want to browse the RDNZL source code. _______________________________________________ rdnzl-announce mailing list rdnzl-announce at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/rdnzl-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From edi at agharta.de Thu Aug 10 15:47:25 2006 From: edi at agharta.de (Edi Weitz) Date: Thu, 10 Aug 2006 17:47:25 +0200 Subject: [cl-debian] [ann] [rdnzl-announce] New version 0.10.2 Message-ID: Sorry, next one... ChangeLog: Version 0.10.2 2006-08-10 More DSPEC definitions for LispWorks Download: http://weitz.de/files/RDNZL.tar.gz These changes only affect LispWorks users. _______________________________________________ rdnzl-announce mailing list rdnzl-announce at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/rdnzl-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From fahree at gmail.com Thu Aug 10 21:44:31 2006 From: fahree at gmail.com (=?UTF-8?Q? Far=C3=A9 ?=) Date: Thu, 10 Aug 2006 17:44:31 -0400 Subject: [cl-debian] Bug#382430: c-l-c installation of ecl does things wrong Message-ID: <653bea160608101444o6eaea720p9e5ad9a5fe370691@mail.gmail.com> Package: ecl Version: 0.9i-2 Severity: normal the c-l-c installation of ecl does a few wrong things: (1) it uses the c-l-c version of asdf and not the ecl-provided one from /usr/lib/ecl/asdf.fas as a result it fails to include the make-build extension from ECL sources ecl-0.9i/contrib/asdf/asdf-ecl.lisp Solution (a) would be to (require 'asdf) from the c-l-c compiled image and not compile it in the c-l-c binary for ecl. Solution (b) would be to include asdf-ecl.lisp in the ecl package, and recompile it together with c-l-c's asdf.lisp when installing c-l-c. (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 ;;; Loading #P"/usr/lib/ecl/cmp.fas" ;;; Loading #P"/usr/lib/ecl/sysfun.lsp" which is quite annoying for programs that need produce controlled output. This is probably caused by the runtime loading of /etc/lispconfig.lisp by c-l-c. This banner should not be printed by quiet ecl scripts. Solution (2a) is to explicitly bind *load-verbose* to nil when loading /etc/lispconfig.lisp. Solution (2b) is to modify the c-l-c ecl startup to somehow hook the value of *load-verbose* on the -q flag. However, this requires modifying or overriding code from ecl-0.9i/src/lsp/cmdline.lsp and maintaining the result. Ouch. Solution (2c) is to hook into ecl's loading of a user resource file and replace it with the loading of a system resource file, say /etc/ecl/rc.lisp that in turn loads /etc/lispconfig.lisp then the user resource file. We would just prepend that path to *lisp-init-file-list* from install-clc.lisp, and writing the proper default code in /etc/ecl/rc.lisp Thus the usual parsing of -q and -norc applies to clc's ecl. (3) compiling configuration files everytime can be a performance issue, in addition to requiring to load the compiler. We could instead have a mechanism such as cl-launch's compile-and-load-file to only recompile when needed (SLIME's doesn't try hard enough for ECL), and put c-l-c cached .fas variants of the files in *lisp-init-file-list* before the source variants. Also, we want it to not require users to do anything special for the fasl to remain in synch with their lisp configuration. Any hackish code should come precompiled as part of install-clc.lisp so as to avoid requiring costly recompilation at runtime when things change. Solution (3a) would be to only do that for the system-wide file, and have that system-wide file include provisions for recompiling itself and then loading the compiled contents, and do the same for lispconfig.lisp and user files. A bit of a hack. Solution (3b) would be to modify or override cmdline.lsp to do the compile-and-load instead of load. Costly to maintain. (4) If we use a compile-and-load-file strategy for (3), then we might share code with cl-launch. This would mean having a dependency on cl-launch. It also means I should change cl-launch to install its file in /usr/share/common-lisp/source/cl-launch instead of /usr/share/common-lisp/cl-launch and produce a cl-launch.asd. I'll do that for cl-launch 1.85. In any cases, problems (1) and (2) both interact badly with cl-launch, and although cl-launch 1.84 now fully supports ECL, debian users need export ECL=/usr/lib/ecl/ecl-original so as to use cl-launch with ECL. I should probably include detection of that executable in cl-launch as a workaround to current breakage, since I already kluge a lot of my way to supporting ECL in cl-launch. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16.9-blefuscu Locale: LANG=en_US.iso-8859-1, LC_CTYPE=en_US.iso-8859-1 (charmap=ISO-8859-1) (ignored: LC_ALL set to e n_US.iso-8859-1) Versions of packages ecl depends on: ii common-lisp-controller 6.1 This is a Common Lisp source and c ii gcc-4.1 4.1.1-9 The GNU C compiler ii libc6 2.3.6-16 GNU C Library: Shared libraries ii libgc-dev 1:6.7-2 conservative garbage collector for ii libgc1c2 1:6.7-2 conservative garbage collector for ii libgmp3-dev 2:4.2.1+dfsg-3 Multiprecision arithmetic library ii libgmp3c2 2:4.2.1+dfsg-3 Multiprecision arithmetic library ii libncurses5-dev 5.5-2 Developer's libraries and docs for ecl recommends no packages. -- no debconf information From pvaneynd at debian.org Fri Aug 11 06:30:36 2006 From: pvaneynd at debian.org (Peter Van Eynde) Date: Fri, 11 Aug 2006 08:30:36 +0200 Subject: [cl-debian] Re: cl-launch in debian In-Reply-To: <653bea160608091948m29480131h210441cb58fcf7d6@mail.gmail.com> References: <653bea160608022032l30a191c5w365b2e872ad37cd1@mail.gmail.com> <653bea160608091948m29480131h210441cb58fcf7d6@mail.gmail.com> Message-ID: <200608110830.40734.pvaneynd@debian.org> From fare at tunes.org Fri Aug 11 22:06:56 2006 From: fare at tunes.org (Francois-Rene Rideau) Date: Fri, 11 Aug 2006 18:06:56 -0400 Subject: [cl-debian] Bug#382582: common-lisp-controller: c-l-c fails to exclude /usr/lib/sbcl and such from cache Message-ID: <20060811220656.27145.67712.reportbug@blefuscu.porte31> Package: common-lisp-controller Version: 6.2 Severity: minor While compiling a program with sbcl and c-l-c, I realized that c-l-c wasn't excluding directories such as /usr/lib/sbcl from its cache, recompiling in-cache fasl's for source code instead of using the precompiled fasl's. Same applies for other lisp implementations. cl-launch fixed a similar with its function exclude-from-cache. Note: if c-l-c ends up using the very same mechanism as cl-launch, it would be nice if the interface was similar enough that cl-launch could just import the relevant symbols in a #+common-lisp-controller. In any case, you're welcome to "borrow" code from cl-launch. PS: I see you depend on a package named realpath. In debian systems, readlink --canonicalize now does the same thing. Of course, in older Linux systems, BSD systems, etc., readlink doesn't have option --canonicalize. Sigh. PPS: unrelatedly, I found more bugs in cl-launch and ECL when using a system, and the bug has a long reach when the system has dependencies. Sigh. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16.9-blefuscu Locale: LANG=en_US.iso-8859-1, LC_CTYPE=en_US.iso-8859-1 (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US.iso-8859-1) Versions of packages common-lisp-controller depends on: ii bash 3.1-5 The GNU Bourne Again SHell ii cl-asdf 1.99-2 Another System Definition Facility ii debconf [debconf-2.0] 1.5.2 Debian configuration management sy ii debianutils 2.16.2 Miscellaneous utilities specific t ii perl 5.8.8-6 Larry Wall's Practical Extraction ii realpath 1.10 Return the canonicalized absolute common-lisp-controller recommends no packages. -- debconf information excluded From kmr at debian.org Sat Aug 12 20:47:13 2006 From: kmr at debian.org (Kevin M. Rosenberg) Date: Sat, 12 Aug 2006 13:47:13 -0700 Subject: [cl-debian] Accepted cl-sql 3.6.4-1 (source all i386) Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Sat, 12 Aug 2006 10:18:05 -0600 Source: cl-sql Binary: cl-sql-sqlite3 cl-sql-oracle cl-sql-aodbc cl-sql-postgresql-socket cl-sql-postgresql cl-sql-odbc cl-sql cl-sql-uffi cl-sql-tests cl-sql-sqlite cl-sql-mysql Architecture: source all i386 Version: 3.6.4-1 Distribution: unstable Urgency: low Maintainer: Kevin M. Rosenberg Changed-By: Kevin M. Rosenberg Description: cl-sql - SQL Interface for Common Lisp cl-sql-aodbc - CLSQL database backend, AODBC cl-sql-mysql - CLSQL database backend, MySQL cl-sql-odbc - CLSQL database backend, ODBC cl-sql-oracle - CLSQL database backend, Oracle cl-sql-postgresql - CLSQL database backend, PostgreSQL cl-sql-postgresql-socket - CLSQL database backend, PostgreSQL cl-sql-sqlite - CLSQL database backend, SQLite cl-sql-sqlite3 - CLSQL database backend, SQLite3 cl-sql-tests - Testing suite for CLSQL cl-sql-uffi - Common UFFI functions for CLSQL database backends Changes: cl-sql (3.6.4-1) unstable; urgency=low . * New upstream Files: 3b833023044e3fd8addaff0f7caf5b66 796 devel extra cl-sql_3.6.4-1.dsc 1150b1cc969e9751497d462765b21040 707984 devel extra cl-sql_3.6.4.orig.tar.gz 2713e1dd5f6a7b548843a5fbdae75a94 11522 devel extra cl-sql_3.6.4-1.diff.gz ac1419bc3e9d8a16b1bcf29e10b4e448 494136 devel extra cl-sql_3.6.4-1_all.deb 6ae924c09b44b010ba8fddf91029424f 37596 devel extra cl-sql-aodbc_3.6.4-1_all.deb ee38b3a8dcbe54fec2b7de7e83b8a2aa 64228 devel extra cl-sql-odbc_3.6.4-1_all.deb 5db5365565f981ded6d1264b4eae438f 42266 devel extra cl-sql-postgresql_3.6.4-1_all.deb 4ad245d4fdde8b46a9231db65e9f648b 46376 devel extra cl-sql-postgresql-socket_3.6.4-1_all.deb b79a23632f34d2fe321c239cbd648d57 42138 devel extra cl-sql-sqlite_3.6.4-1_all.deb 219c3edd5b7ae85b676e6e79d29a30e8 42896 devel extra cl-sql-sqlite3_3.6.4-1_all.deb 8d99709eaef2ad0906eac606460e1b94 58566 contrib/devel extra cl-sql-oracle_3.6.4-1_all.deb 68febdc8d46f81e92eb36aa77736d259 60956 devel extra cl-sql-tests_3.6.4-1_all.deb a75cbcca95b70c16370ad4a860d443bd 40970 devel extra cl-sql-uffi_3.6.4-1_i386.deb 3e3fdbaa0b506fc1a8b35dc8952a2fdf 51270 devel extra cl-sql-mysql_3.6.4-1_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE3jVOES7N8sSjgj4RAsUcAJ0XhvbfCfQ319ErlgA89BTBD4UQtwCfW8p9 hWzDfllFIjGgqi4yqkLepl8= =xTsz -----END PGP SIGNATURE----- Accepted: cl-sql-aodbc_3.6.4-1_all.deb to pool/main/c/cl-sql/cl-sql-aodbc_3.6.4-1_all.deb cl-sql-mysql_3.6.4-1_i386.deb to pool/main/c/cl-sql/cl-sql-mysql_3.6.4-1_i386.deb cl-sql-odbc_3.6.4-1_all.deb to pool/main/c/cl-sql/cl-sql-odbc_3.6.4-1_all.deb cl-sql-oracle_3.6.4-1_all.deb to pool/contrib/c/cl-sql/cl-sql-oracle_3.6.4-1_all.deb cl-sql-postgresql-socket_3.6.4-1_all.deb to pool/main/c/cl-sql/cl-sql-postgresql-socket_3.6.4-1_all.deb cl-sql-postgresql_3.6.4-1_all.deb to pool/main/c/cl-sql/cl-sql-postgresql_3.6.4-1_all.deb cl-sql-sqlite3_3.6.4-1_all.deb to pool/main/c/cl-sql/cl-sql-sqlite3_3.6.4-1_all.deb cl-sql-sqlite_3.6.4-1_all.deb to pool/main/c/cl-sql/cl-sql-sqlite_3.6.4-1_all.deb cl-sql-tests_3.6.4-1_all.deb to pool/main/c/cl-sql/cl-sql-tests_3.6.4-1_all.deb cl-sql-uffi_3.6.4-1_i386.deb to pool/main/c/cl-sql/cl-sql-uffi_3.6.4-1_i386.deb cl-sql_3.6.4-1.diff.gz to pool/main/c/cl-sql/cl-sql_3.6.4-1.diff.gz cl-sql_3.6.4-1.dsc to pool/main/c/cl-sql/cl-sql_3.6.4-1.dsc cl-sql_3.6.4-1_all.deb to pool/main/c/cl-sql/cl-sql_3.6.4-1_all.deb cl-sql_3.6.4.orig.tar.gz to pool/main/c/cl-sql/cl-sql_3.6.4.orig.tar.gz From kmr at debian.org Sat Aug 12 21:32:17 2006 From: kmr at debian.org (Kevin M. Rosenberg) Date: Sat, 12 Aug 2006 14:32:17 -0700 Subject: [cl-debian] Accepted cl-sql 3.6.5-1 (source all i386) Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Sat, 12 Aug 2006 15:18:47 -0600 Source: cl-sql Binary: cl-sql-sqlite3 cl-sql-oracle cl-sql-aodbc cl-sql-postgresql-socket cl-sql-postgresql cl-sql-odbc cl-sql cl-sql-uffi cl-sql-tests cl-sql-sqlite cl-sql-mysql Architecture: source all i386 Version: 3.6.5-1 Distribution: unstable Urgency: low Maintainer: Kevin M. Rosenberg Changed-By: Kevin M. Rosenberg Description: cl-sql - SQL Interface for Common Lisp cl-sql-aodbc - CLSQL database backend, AODBC cl-sql-mysql - CLSQL database backend, MySQL cl-sql-odbc - CLSQL database backend, ODBC cl-sql-oracle - CLSQL database backend, Oracle cl-sql-postgresql - CLSQL database backend, PostgreSQL cl-sql-postgresql-socket - CLSQL database backend, PostgreSQL cl-sql-sqlite - CLSQL database backend, SQLite cl-sql-sqlite3 - CLSQL database backend, SQLite3 cl-sql-tests - Testing suite for CLSQL cl-sql-uffi - Common UFFI functions for CLSQL database backends Changes: cl-sql (3.6.5-1) unstable; urgency=low . * New upstream Files: 2411cc77b73fd4b39e305c4106ac6404 796 devel extra cl-sql_3.6.5-1.dsc b0179cfa49e0ce1c2bb7a9ac02b41edf 708173 devel extra cl-sql_3.6.5.orig.tar.gz 1e427d4f9dc8f4bd19ec9dcad96eb79b 11526 devel extra cl-sql_3.6.5-1.diff.gz 7688c434ae6a8095459f5db9fdceb1dd 494344 devel extra cl-sql_3.6.5-1_all.deb b83873cdf0624c811e8ac4cb22f072ee 37704 devel extra cl-sql-aodbc_3.6.5-1_all.deb 90d1c644391f94cf39ee77995bd7d3c2 64324 devel extra cl-sql-odbc_3.6.5-1_all.deb b0d5eae33d273587796519ca296e8e19 42376 devel extra cl-sql-postgresql_3.6.5-1_all.deb ed052adb7f55277259848fef14408d85 46488 devel extra cl-sql-postgresql-socket_3.6.5-1_all.deb ed29da7accb6b6e2b5efeb92697cbe0d 42240 devel extra cl-sql-sqlite_3.6.5-1_all.deb a1690934af466475864e84795785790c 42994 devel extra cl-sql-sqlite3_3.6.5-1_all.deb 35e38030e4c19b0ccf96214c387fa960 58668 contrib/devel extra cl-sql-oracle_3.6.5-1_all.deb 26d82ce5798a77b4fc5d515d70bc0ad6 61074 devel extra cl-sql-tests_3.6.5-1_all.deb 5646e2803a49112b4724a5060ddc274a 41064 devel extra cl-sql-uffi_3.6.5-1_i386.deb ff6fa5f1e0be6d7809cf4509b8f41ded 51370 devel extra cl-sql-mysql_3.6.5-1_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE3kYOES7N8sSjgj4RApqLAJ91uhf0ikIk9hTc8r+rV8YAe7/ijwCfY/OE Usn4x/0+wW/p+4v3+wqLppU= =fJQN -----END PGP SIGNATURE----- Accepted: cl-sql-aodbc_3.6.5-1_all.deb to pool/main/c/cl-sql/cl-sql-aodbc_3.6.5-1_all.deb cl-sql-mysql_3.6.5-1_i386.deb to pool/main/c/cl-sql/cl-sql-mysql_3.6.5-1_i386.deb cl-sql-odbc_3.6.5-1_all.deb to pool/main/c/cl-sql/cl-sql-odbc_3.6.5-1_all.deb cl-sql-oracle_3.6.5-1_all.deb to pool/contrib/c/cl-sql/cl-sql-oracle_3.6.5-1_all.deb cl-sql-postgresql-socket_3.6.5-1_all.deb to pool/main/c/cl-sql/cl-sql-postgresql-socket_3.6.5-1_all.deb cl-sql-postgresql_3.6.5-1_all.deb to pool/main/c/cl-sql/cl-sql-postgresql_3.6.5-1_all.deb cl-sql-sqlite3_3.6.5-1_all.deb to pool/main/c/cl-sql/cl-sql-sqlite3_3.6.5-1_all.deb cl-sql-sqlite_3.6.5-1_all.deb to pool/main/c/cl-sql/cl-sql-sqlite_3.6.5-1_all.deb cl-sql-tests_3.6.5-1_all.deb to pool/main/c/cl-sql/cl-sql-tests_3.6.5-1_all.deb cl-sql-uffi_3.6.5-1_i386.deb to pool/main/c/cl-sql/cl-sql-uffi_3.6.5-1_i386.deb cl-sql_3.6.5-1.diff.gz to pool/main/c/cl-sql/cl-sql_3.6.5-1.diff.gz cl-sql_3.6.5-1.dsc to pool/main/c/cl-sql/cl-sql_3.6.5-1.dsc cl-sql_3.6.5-1_all.deb to pool/main/c/cl-sql/cl-sql_3.6.5-1_all.deb cl-sql_3.6.5.orig.tar.gz to pool/main/c/cl-sql/cl-sql_3.6.5.orig.tar.gz From kapustin at gorodok.net Sun Aug 13 09:13:03 2006 From: kapustin at gorodok.net (alexey) Date: Sun, 13 Aug 2006 16:13:03 +0700 Subject: [cl-debian] Bug#382770: Can not get access to SBCL documentation through "info" command Message-ID: Package: sbcl-doc Version: 0.9.14.0-2 Hello. I cann't get access to SBCL documentation through "info" command. If I run "info sbcl" from shell prompt, then man page appears. If I run "info" from shell prompt and click to sbcl link, then get this message: Cannot find node 'Top'. If I run emacs, execute "C-h i" and click to sbcl link, then this message appears: Can't find sbcl.info-1 or any compressed version of it Package sbcl.info.gz exist: ls -l /usr/share/info/ | grep -i sbcl -rw-r--r-- 1 root root 4527 2006-07-06 04:34 sbcl.info.gz System information: Debian Release: testing/unstable Kernel: Linux 2.6.16-2-686 From kmr at debian.org Mon Aug 14 06:32:09 2006 From: kmr at debian.org (Kevin M. Rosenberg) Date: Sun, 13 Aug 2006 23:32:09 -0700 Subject: [cl-debian] Accepted cl-uffi 1.5.15-1 (source all i386) Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Mon, 14 Aug 2006 00:21:47 -0600 Source: cl-uffi Binary: cl-uffi-tests cl-uffi Architecture: source all i386 Version: 1.5.15-1 Distribution: unstable Urgency: low Maintainer: Kevin M. Rosenberg Changed-By: Kevin M. Rosenberg Description: cl-uffi - Universal Foreign Function Library for Common Lisp cl-uffi-tests - Regression tests for UFFI Common Lisp Library Changes: cl-uffi (1.5.15-1) unstable; urgency=low . * New upstream Files: ff3800ea05853908d24b57c845aa778b 636 devel optional cl-uffi_1.5.15-1.dsc 45599c279cdb7eb76182a7fea556be83 95104 devel optional cl-uffi_1.5.15.orig.tar.gz 4bf6452359223ec958f6f56b06a9114f 7799 devel optional cl-uffi_1.5.15-1.diff.gz 41e499777e0a5015ca164eec544daabc 63476 devel optional cl-uffi_1.5.15-1_all.deb 441144af81020f1388b7df871bcc5d99 24912 devel optional cl-uffi-tests_1.5.15-1_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE4BezES7N8sSjgj4RAr8rAJ9iI45vMeJpEmG2kAmCLinK8t/NwQCggtUM 2Hiy3gIsvJ0jfC3VTwoVeFo= =QSK6 -----END PGP SIGNATURE----- Accepted: cl-uffi-tests_1.5.15-1_i386.deb to pool/main/c/cl-uffi/cl-uffi-tests_1.5.15-1_i386.deb cl-uffi_1.5.15-1.diff.gz to pool/main/c/cl-uffi/cl-uffi_1.5.15-1.diff.gz cl-uffi_1.5.15-1.dsc to pool/main/c/cl-uffi/cl-uffi_1.5.15-1.dsc cl-uffi_1.5.15-1_all.deb to pool/main/c/cl-uffi/cl-uffi_1.5.15-1_all.deb cl-uffi_1.5.15.orig.tar.gz to pool/main/c/cl-uffi/cl-uffi_1.5.15.orig.tar.gz From kmr at debian.org Mon Aug 14 07:17:04 2006 From: kmr at debian.org (Kevin M. Rosenberg) Date: Mon, 14 Aug 2006 00:17:04 -0700 Subject: [cl-debian] Accepted cl-sql 3.6.6-1 (source all i386) Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Mon, 14 Aug 2006 00:53:43 -0600 Source: cl-sql Binary: cl-sql-sqlite3 cl-sql-oracle cl-sql-aodbc cl-sql-postgresql-socket cl-sql-postgresql cl-sql-odbc cl-sql cl-sql-uffi cl-sql-tests cl-sql-sqlite cl-sql-mysql Architecture: source all i386 Version: 3.6.6-1 Distribution: unstable Urgency: low Maintainer: Kevin M. Rosenberg Changed-By: Kevin M. Rosenberg Description: cl-sql - SQL Interface for Common Lisp cl-sql-aodbc - CLSQL database backend, AODBC cl-sql-mysql - CLSQL database backend, MySQL cl-sql-odbc - CLSQL database backend, ODBC cl-sql-oracle - CLSQL database backend, Oracle cl-sql-postgresql - CLSQL database backend, PostgreSQL cl-sql-postgresql-socket - CLSQL database backend, PostgreSQL cl-sql-sqlite - CLSQL database backend, SQLite cl-sql-sqlite3 - CLSQL database backend, SQLite3 cl-sql-tests - Testing suite for CLSQL cl-sql-uffi - Common UFFI functions for CLSQL database backends Changes: cl-sql (3.6.6-1) unstable; urgency=low . * New upstream Files: e1efa58fbc129da6a1f227c90693d887 796 devel extra cl-sql_3.6.6-1.dsc fc60d1e1aad5a95bfdebb5c9ae209132 708207 devel extra cl-sql_3.6.6.orig.tar.gz 0a243bf553a71b7c01b107f198826fba 11530 devel extra cl-sql_3.6.6-1.diff.gz a7f86d3f9c6871d77fd8c903c11fbd54 494430 devel extra cl-sql_3.6.6-1_all.deb 517ef949e7968bdc7e2153ad73befffe 37758 devel extra cl-sql-aodbc_3.6.6-1_all.deb c4d8d4d4b06e9e4d86d528aaf8ed2506 64402 devel extra cl-sql-odbc_3.6.6-1_all.deb 02cbaac83e661100d27139ec3dd7a466 42434 devel extra cl-sql-postgresql_3.6.6-1_all.deb 2823e0e2018d385c8b3eb6593ed1d627 46544 devel extra cl-sql-postgresql-socket_3.6.6-1_all.deb 1634c7a35b434be169fd8bee902d45e4 42298 devel extra cl-sql-sqlite_3.6.6-1_all.deb 98d10754ed24795597a483beba34b706 43066 devel extra cl-sql-sqlite3_3.6.6-1_all.deb 3ce90947dcf9ebff87237f606bb4d1d2 58722 contrib/devel extra cl-sql-oracle_3.6.6-1_all.deb bb25726953e6b08b8f7de0deef1a51a9 61110 devel extra cl-sql-tests_3.6.6-1_all.deb 4afcd6365e42328ab87e9c1c43eb40e6 41140 devel extra cl-sql-uffi_3.6.6-1_i386.deb 8a2fb06f3cbe2dba25c29570aee46b88 51448 devel extra cl-sql-mysql_3.6.6-1_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE4B9PES7N8sSjgj4RAqVfAJwOn/kjAlzDNFVObQhVE+41NwlMrwCbBLCH 4oVsh2iwepl7DJwiSEQQl3A= =lpu8 -----END PGP SIGNATURE----- Accepted: cl-sql-aodbc_3.6.6-1_all.deb to pool/main/c/cl-sql/cl-sql-aodbc_3.6.6-1_all.deb cl-sql-mysql_3.6.6-1_i386.deb to pool/main/c/cl-sql/cl-sql-mysql_3.6.6-1_i386.deb cl-sql-odbc_3.6.6-1_all.deb to pool/main/c/cl-sql/cl-sql-odbc_3.6.6-1_all.deb cl-sql-oracle_3.6.6-1_all.deb to pool/contrib/c/cl-sql/cl-sql-oracle_3.6.6-1_all.deb cl-sql-postgresql-socket_3.6.6-1_all.deb to pool/main/c/cl-sql/cl-sql-postgresql-socket_3.6.6-1_all.deb cl-sql-postgresql_3.6.6-1_all.deb to pool/main/c/cl-sql/cl-sql-postgresql_3.6.6-1_all.deb cl-sql-sqlite3_3.6.6-1_all.deb to pool/main/c/cl-sql/cl-sql-sqlite3_3.6.6-1_all.deb cl-sql-sqlite_3.6.6-1_all.deb to pool/main/c/cl-sql/cl-sql-sqlite_3.6.6-1_all.deb cl-sql-tests_3.6.6-1_all.deb to pool/main/c/cl-sql/cl-sql-tests_3.6.6-1_all.deb cl-sql-uffi_3.6.6-1_i386.deb to pool/main/c/cl-sql/cl-sql-uffi_3.6.6-1_i386.deb cl-sql_3.6.6-1.diff.gz to pool/main/c/cl-sql/cl-sql_3.6.6-1.diff.gz cl-sql_3.6.6-1.dsc to pool/main/c/cl-sql/cl-sql_3.6.6-1.dsc cl-sql_3.6.6-1_all.deb to pool/main/c/cl-sql/cl-sql_3.6.6-1_all.deb cl-sql_3.6.6.orig.tar.gz to pool/main/c/cl-sql/cl-sql_3.6.6.orig.tar.gz From rm at seid-online.de Tue Aug 15 16:56:20 2006 From: rm at seid-online.de (Ralf Mattes) Date: Tue, 15 Aug 2006 16:56:20 -0000 Subject: Bug#360561: [cl-debian] Bug#360561: cmucl: CMUCL does not run under kernel version 2.6.16 In-Reply-To: <200607261748.23377.pvaneynd@debian.org> References: <87hd166hgr.fsf@geddis.org> <200607261412.42448.pvaneynd@debian.org> <87k660cttl.fsf_-_@geddis.org> <200607261748.23377.pvaneynd@debian.org> Message-ID: <1153939686.10378.10.camel@localhost.localdomain> On Wed, 2006-07-26 at 17:48 +0200, Peter Van Eynde wrote: > [... schnip ...] > I can see what the solution would be but there are technical and cultural > problems with it, basicly the debian package would be 'different' from a > normal cmucl and this is often enough reason to distrust bug reports from > debian users. > This is a _very_ good point! > > > I'm open to suggestions on what I should 'require'. ;-) > > > > Well, hopefull this is only a short-term issue. I don't really know the > > Debian package syntax, but can't you can something like "requires > > linux-image-2.4, or linux-image-2.6 with version <= 2.6.15"? > > This would only require a specific version of the kernel to be installed, > there is no general way to say 'this package only runs with kernels < 2.6.15 > and > 2.7.17-5 (I hope). Well, isn't this a job for the 'Conflicts' section. Of course this would only protect the user from installing a not-working kernel image but those who compile their own kernels should know what they do. Cheers, Ralf Mattes > Groetjes, Peter > From don at geddis.org Tue Aug 15 15:31:52 2006 From: don at geddis.org (Don Geddis) Date: Tue, 15 Aug 2006 08:31:52 -0700 Subject: Bug#360561: [cl-debian] Bug#360561: cmucl: CMUCL does not run under kernel version 2.6.16 In-Reply-To: <1153939686.10378.10.camel@localhost.localdomain> (Ralf Mattes's message of "Wed, 26 Jul 2006 20:48:06 +0200") References: <87hd166hgr.fsf@geddis.org> <200607261412.42448.pvaneynd@debian.org> <87k660cttl.fsf_-_@geddis.org> <200607261748.23377.pvaneynd@debian.org> <1153939686.10378.10.camel@localhost.localdomain> Message-ID: <87zme6ypzr.fsf@geddis.org> > On Wed, 2006-07-26 at 17:48 +0200, Peter Van Eynde wrote: >> I can see what the solution would be but there are technical and cultural >> problems with it, basicly the debian package would be 'different' from a >> normal cmucl and this is often enough reason to distrust bug reports from >> debian users. Ralf Mattes wrote on Wed, 26 Jul 2006: > This is a _very_ good point! In this case, upstream has fixed this bug (for all platforms). In a (near-term) future release [19d?], the memory layout is more logical, and cmucl should no longer have this conflict with the debian kernel. In addition, since the change affects all platforms, there doesn't need to be any fear that the debian package is "different" from a "normal" cmucl. -- Don _______________________________________________________________________________ Don Geddis http://don.geddis.org/ don at geddis.org I made dinner. We didn't have any Hamburger, so it's just Helper. -- "Gabe", Penny Arcade From edi at agharta.de Wed Aug 16 12:31:35 2006 From: edi at agharta.de (Edi Weitz) Date: Wed, 16 Aug 2006 14:31:35 +0200 Subject: [cl-debian] [ann] [tbnl-announce] New version 0.9.11 Message-ID: ChangeLog: Version 0.9.11 2006-08-16 Added note about SBCL problems Download: http://weitz.de/files/tbnl.tar.gz This is just a documentation update. No need to download it, if you have it working. Cheers, 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 fahree at gmail.com Thu Aug 17 09:17:16 2006 From: fahree at gmail.com (=?ISO-8859-1?Q?Far=E9?=) Date: Thu, 17 Aug 2006 05:17:16 -0400 Subject: [cl-debian] Re: cl-launch in debian In-Reply-To: <200608110830.40734.pvaneynd@debian.org> References: <653bea160608022032l30a191c5w365b2e872ad37cd1@mail.gmail.com> <653bea160608091948m29480131h210441cb58fcf7d6@mail.gmail.com> <200608110830.40734.pvaneynd@debian.org> Message-ID: <653bea160608170217t108928c7o2b54506c69deaa26@mail.gmail.com> I'm glad to announce cl-launch 1.86, which I'm sad to say fixes brown bag bugs (most importantly including command-line arguments not being recomputed anymore when using dumped images), and revises its claim of complete support for image-dumping with ECL (see discussion on the ECL mailing-list). An important new feature is a more complete automated test coverage, that now includes image-dumping in the tested combinations -- this allowed me to catch all the above bugs and more. In other news, I revived the limited support for gcl 2.6 (no asdf, no image dumping). The gcl 2.7 in debian is hosed on too many levels for me to try do anything more about it. As usual, the relevant files are available on http://fare.tunes.org/files/cl-launch/ Peter Van Eynde wrote: > The package looks good, I had 5 minutes so I rebuild and uploaded it. It was actually quite buggy. 1.86 shall improve on the quality with its more complete integrated regression test suite. And so I feel entitled to stealing 5 more of your minutes. > I thought it was using ECL's asdf. Could you open wishlist bugs against ECL so > I don't forget to fix this? I did, and offered several solutions to this problem. However, I realized that ECL's c::builder also had problems with pathnames and with libraries, making it unsuitable as is for use by cl-launch. The ECL guys don't seem to care enough to fix it, and frankly neither do I. Sigh. >> I assumed Rene and Peter were my Uploaders. If not, the control file >> should be changed appropriately by my mysterious mentor to reveal >> himself. > > Boe! :-) > Whoa, what a surprise. You scared me! Thanks a lot for all your hard work, [ Fran?ois-Ren? ?VB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] The American businessmen, as a class, have demonstrated the greatest productive genius and the most spectacular achievements ever recorded in the economic history of mankind. What reward did they receive from our culture and its intellectuals? The position of a hated, persecuted minority. The position of a scapegoat for the evils of the bureaucrats. -- Ayn Rand From kristian at cavatina.no Sun Aug 20 21:21:32 2006 From: kristian at cavatina.no (Kristian Berge Nessa) Date: Sun, 20 Aug 2006 21:21:32 +0000 Subject: Bug#361275: [cl-debian] Bug#361275: cl-swank: swank-loader looks for a ChangeLog file that doesn't exist In-Reply-To: <200604101257.19717.pvaneynd@debian.org> References: <18589991.1144424195495.JavaMail.root@ps18> <200604101257.19717.pvaneynd@debian.org> Message-ID: <200608202121.32126.kristian@cavatina.no> Mandag 10 april 2006 10:57 skreiv du: > On Friday 07 April 2006 17:36, stfn.sbtn at tiscali.it wrote: > > I'm trying to run slime from emacs in the usual way with M-x slime. > > I get in the *inferior-lisp* buffer: > > [1]> ;; Loading file /usr/share/common-lisp/source/slime/swank-loader. > > lisp ... > > *** - FILE-WRITE-DATE: file #P"/usr/share/common- > > lisp/source/slime/ChangeLog" does not exist > > This is strange as we create a ChangeLog file in the appropriate elc > directory when installing for a emacs variant. > See /usr/lib/emacsen-common/packages/install/slime: > ... swank-loader.lisp looks for the ChangeLog in its own source directory; #P"/usr/share/common-lisp/source/slime" and not in the elisp directory, where the symbolic link is created by the aforementioned script. This "works" in CMUCL & derivatives only because the function (file-write-date) returns nil if its argument does not point to a valid file, unlike CLISP which signals (file-error). > (...) Does anyone else has this > problem? Yes! :) I believe a symbolic link to the changelog from /usr/share/common-lisp/source/slime/ChangeLog would fix this bug. Regards, Kristian Berge Nessa Cavatina Software AS From noreply at henning.makholm.net Sun Aug 20 21:08:33 2006 From: noreply at henning.makholm.net (Debian testing watch) Date: Sun, 20 Aug 2006 15:08:33 -0600 Subject: [cl-debian] sbcl 1:0.9.15.0-1 MIGRATED to testing Message-ID: FYI: The status of the sbcl source package in Debian's testing distribution has changed. Previous version: 1:0.9.14.0-2 Current version: 1:0.9.15.0-1 -- 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 Aug 20 21:08:09 2006 From: noreply at henning.makholm.net (Debian testing watch) Date: Sun, 20 Aug 2006 15:08:09 -0600 Subject: [cl-debian] cl-sdl 1:0.2.2-4 MIGRATED to testing Message-ID: FYI: The status of the cl-sdl source package in Debian's testing distribution has changed. Previous version: 1:0.2.2-3 Current version: 1:0.2.2-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 Sun Aug 20 21:08:10 2006 From: noreply at henning.makholm.net (Debian testing watch) Date: Sun, 20 Aug 2006 15:08:10 -0600 Subject: [cl-debian] common-lisp-controller 6.2 MIGRATED to testing Message-ID: FYI: The status of the common-lisp-controller source package in Debian's testing distribution has changed. Previous version: 6.1 Current version: 6.2 -- This email is automatically generated; henning at makholm.net is responsible. See http://people.debian.org/~henning/trille/ for more information. From kevinl at tamu.edu Sun Aug 20 23:25:26 2006 From: kevinl at tamu.edu (Kevin L) Date: Sun, 20 Aug 2006 18:25:26 -0500 Subject: [cl-debian] Bug#383957: cl-statistics does not compile in SBCL Message-ID: <44E8EF66.1040108@tamu.edu> Package: cl-statistics The Debian patch to cl-statistics (cl-statistics_20050224-1.diff.gz ) produces invalid Lisp code after applied to cl-statistics.lisp. Example: ----snip-----snip----- v v v v v v v (defpackage :statistics (:nicknames :stats) (:use :common-lisp) (:export #:mean #:median #:mode #:geometric-mean #:range #:percentile #:variance #:standard-deviation #:sd #:coefficient-of-variation #:standard-error-of-the-mean #:permutations #:choose #:binomial-probability #:binomial-cumulative-probability #:binomial-ge-probability #:poisson-probability #:poisson-cumulative-probability #:poisson-ge-probability #:poisson-cdf #:normal-pdf #:convert-to-standard-normal #:phi #:z #:t-distribution #:chi-square #:chi-square-cdf #:binomial-probability-ci #:poisson-mu-ci #:normal-mean-ci #:normal-mean-ci-on-sequences #:normal-variance-ci #:normal-variance-ci-on-sequence #:normal-sd-ci #:normal-sd-ci-on-sequence #:z-test #:z-test-on-sequence #:t-test-one-sample #:t-test-one-sample-on-sequence #:t-test-paired #:t-test-paired-on-sequences #:t-test-two-sample #:t-test-two-sample-on-sequences #:chi-square-test-one-sample #:f-test #:binomial-test-one-sample #:binomial-test-two-sample #:fisher-exact-test #:mcnemars-test #:poisson-test-one-sample #:sign-test #:sign-test-on-sequences #:wilcoxon-signed-rank-test #:wilcoxon-signed-rank-test-on-sequences #:chi-square-test-rxc #:chi-square-test-for-trend #:t-test-one-sample-sse #:t-test-two-sample-sse #:t-test-paired-sse #:binomial-test-one-sample-sse #:binomial-test-two-sample-sse #:binomial-test-paired-sse #:correlation-sse #:linear-regression #:correlation-coefficient #:correlation-test-two-sample #:correlation-test-two-sample-on-sequences #:spearman-rank-correlation #:t-significance #:f-significance #:random-sample #:random-pick #:test-variables #:bin-and-count #:fishers-z-transform #:mean-sd-n #:square #:round-float #:random-normal)) (declaim (optimize (debug 3) (speed 3) (safety 1) (compilation-speed 0))) (in-package :statistics) ;; |KMR| add dummy routine for missing function (defmacro test-variables (&rest dummy) ) ;; |KMR| move to top of file to prevent some functions from not having ;; this pre-declared ;; SQUARE (defmacro square (x) `(* ,x ,x)) ************* ) ;end eval-when ^ ^ ^ ^ ^ ^ ^ v v v v v v v ^ ^ ^ ^ ^ ^ ^ ----snip-----snip----- These lines of "v v v v v v v", "^ ^ ^ ^ ^ ^ ^", etc. cause SBCL to fail: ----snip-----snip----- ; compiling file "/usr/share/common-lisp/source/cl-statistics/cl-statistics.lisp" (written 18 JUN 2006 02:55:05 PM): ; compiling (DECLAIM (OPTIMIZE # ...)) ; compiling (DEFPACKAGE :STATISTICS ...) ; compiling (IN-PACKAGE :STATISTICS) ; compiling (DEFMACRO TEST-VARIABLES ...) ; compiling (DEFMACRO SQUARE ...) ; compiling (DEFMACRO UNDERFLOW-GOES-TO-ZERO ...) ; compiling V debugger invoked on a SIMPLE-ERROR in thread #: Error during processing of --eval option (LOAD #P"spacebox/spacebox.lisp"): The variable V is unbound. Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [RETRY ] Retry performing # on #. 1: [ACCEPT ] Continue, treating # on # as having been successful. 2: [CONTINUE] Ignore and continue with next --eval option. 3: [ABORT ] Skip rest of --eval options. 4: Skip to toplevel READ/EVAL/PRINT loop. 5: [QUIT ] Quit SBCL (calling #'QUIT, killing the process). ((LAMBDA (SB-IMPL::E)) #) 0] ----snip-----snip----- $ dpkg --status cl-statistics Package: cl-statistics Status: install ok installed Priority: optional Section: devel Installed-Size: 156 Maintainer: Peter Van Eynde Architecture: all Version: 20050224-1 Depends: common-lisp-controller (>= 5.11) Description: Common Lisp Statistics Package cl-statistics provides numerous statistical functions for use in Common Lisp programs. From zedek at gnu.org Mon Aug 21 18:03:09 2006 From: zedek at gnu.org (Xavier Maillard) Date: Mon, 21 Aug 2006 20:03:09 +0200 Subject: [cl-debian] Bug#384071: stumpwm: Please update to a more recent cvs checkout Message-ID: <20060821180309.26966.43188.reportbug@zogzog.gnu-rox.org> Package: stumpwm Version: 1:20060513-1 Severity: wishlist -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-zedek Locale: LANG=fr_FR at euro, LC_CTYPE=fr_FR at euro (charmap=ISO-8859-15) Versions of packages stumpwm depends on: ii cl-clx-sbcl 0.7.2-1 An X11 Common Lisp client library ii cl-port 20060408-1 Common Lisp Object Collections Por ii common-lisp-controller 6.2 This is a Common Lisp source and c stumpwm recommends no packages. -- no debconf information From kevinl at tamu.edu Mon Aug 21 21:08:26 2006 From: kevinl at tamu.edu (Kevin L) Date: Mon, 21 Aug 2006 16:08:26 -0500 Subject: [cl-debian] Bug#360561: So what is a user supposed to do? Message-ID: <44EA20CA.8020402@tamu.edu> I just "upgraded" from Sarge to testing and CMUCL is now dead. If this is fixed upstream, when is the fix going into testing? Is an end-user just supposed to compile their own kernel in the meantime? From jdunrue at gmail.com Wed Aug 23 00:16:08 2006 From: jdunrue at gmail.com (Jack Unrue) Date: Tue, 22 Aug 2006 18:16:08 -0600 Subject: [cl-debian] [ann] [graphic-forms-announce] version 0.5.0 released Message-ID: I'd like to announce that release 0.5.0 of Graphic-Forms, a Common Lisp library for Windows GUI programming, is now available. This is an alpha release, meaning that the feature set and API have not yet stabilized. For information on what's new in this release: http://awayrepl.blogspot.com/2006/08/graphic-forms-version-050-released.html The README.txt file in the release zip file also has important information. Download the release zip file here: http://prdownloads.sourceforge.net/graphic-forms/graphic-forms-0.5.0.zip?download The project website is: http://common-lisp.net/project/graphic-forms/ _______________________________________________ graphic-forms-announce mailing list graphic-forms-announce at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/graphic-forms-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From edi at agharta.de Wed Aug 23 11:13:02 2006 From: edi at agharta.de (Edi Weitz) Date: Wed, 23 Aug 2006 13:13:02 +0200 Subject: [cl-debian] [ann] [tbnl-announce] New Hunchentoot release 0.1.5 Message-ID: ChangeLog: Version 0.1.5 2006-08-23 Connection headers are separated by commas, not semicolons Version 0.1.4 2006-08-22 Refactored streams.lisp to appease LW compiler (thanks to Martin Simmons) Changed handling of version string Changed package handling in system definition (thanks to Christophe Rhodes) Download: http://weitz.de/files/hunchentoot.tar.gz Cheers, 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 owner at bugs.debian.org Wed Aug 23 14:48:26 2006 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Wed, 23 Aug 2006 07:48:26 -0700 Subject: [cl-debian] Processed: Re: Bug#384071: stumpwm: Please update to a more recent cvs checkout In-Reply-To: <87y7tfa6r4.fsf@gismo.pca.it> References: <87y7tfa6r4.fsf@gismo.pca.it> Message-ID: Processing commands for control at bugs.debian.org: > tags 384071 + pending Bug#384071: stumpwm: Please update to a more recent cvs checkout 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 Wed Aug 23 14:03:59 2006 From: luca at pca.it (Luca Capello) Date: Wed, 23 Aug 2006 16:03:59 +0200 Subject: [cl-debian] Bug#384071: stumpwm: Please update to a more recent cvs checkout In-Reply-To: <20060821180309.26966.43188.reportbug@zogzog.gnu-rox.org> (Xavier Maillard's message of "Mon, 21 Aug 2006 20:03:09 +0200") References: <20060821180309.26966.43188.reportbug@zogzog.gnu-rox.org> Message-ID: <87y7tfa6r4.fsf@gismo.pca.it> tags 384071 + pending thanks Hello Xavier! On Mon, 21 Aug 2006 20:03:09 +0200, Xavier Maillard wrote: > Version: 1:20060513-1 > Severity: wishlist I was waiting for the upload of 1:20060513-2, which corrects small Debian-related issues and the I'd upload a new CVS checkout, which is necessary because of the (long-awaited) support for modifiers other than Ctrl. I'm testing on my Debian a checkout made 2 days ago and I'm planning to ask to my sponsor to upload it next week (thus the pending tag). Thx, bye, Gismo / Luca -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: not available URL: From fahree at gmail.com Wed Aug 23 15:30:46 2006 From: fahree at gmail.com (=?UTF-8?Q? Far=C3=A9 ?=) Date: Wed, 23 Aug 2006 11:30:46 -0400 Subject: Bug#384071: [cl-debian] Bug#384071: stumpwm: Please update to a more recent cvs checkout In-Reply-To: <87y7tfa6r4.fsf@gismo.pca.it> References: <20060821180309.26966.43188.reportbug@zogzog.gnu-rox.org> <87y7tfa6r4.fsf@gismo.pca.it> Message-ID: <653bea160608230830l5bf1a90rc9ac826b1dfa5713@mail.gmail.com> Will you also include a cl-launch script to make stumpwm runnable easily from the command-line? As I said in a previous mail, you should use (after testing) something like BINARY=/usr/bin/stumpwm IMAGE=/usr/lib/sbcl/stumpwm.core SYSTEMS=/usr/share/common-lisp/systems LISPS="sbcl" DUMP="--dump ${IMAGE}" cl-launch --lisp "${LISPS}" \ --path ${SYSTEMS} --no-include \ --system stumpwm \ --init '(stumpwm:stumpwm (cl-launch:getenv "DISPLAY"))' \ --wrap 'LISP=sbcl SBCL=/usr/bin/sbcl SBCL_OPTIONS=" " STY=' \ --output ${BINARY} \ ${DUMP} [ Fran?ois-Ren? ?VB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Mathematics is the Queen of Science but she isn't very Pure; she keeps having babies by handsome young upstarts and various frog princes. --Donald Kingsbury (In "psychohistorical crisis", 2001) On 23/08/06, Luca Capello wrote: > I was waiting for the upload of 1:20060513-2, which corrects small > Debian-related issues and the I'd upload a new CVS checkout, which is > necessary because of the (long-awaited) support for modifiers other > than Ctrl. > > I'm testing on my Debian a checkout made 2 days ago and I'm planning > to ask to my sponsor to upload it next week (thus the pending tag). From camm at enhanced.com Wed Aug 23 22:02:53 2006 From: camm at enhanced.com (Camm Maguire) Date: Wed, 23 Aug 2006 15:02:53 -0700 Subject: [cl-debian] Accepted gcl 2.6.7-18 (source i386 all) Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Wed, 23 Aug 2006 14:19:51 -0400 Source: gcl Binary: gcl-doc gcl Architecture: source i386 all Version: 2.6.7-18 Distribution: unstable Urgency: low Maintainer: Camm Maguire Changed-By: Camm Maguire Description: gcl - GNU Common Lisp compiler gcl-doc - Documentation for GNU Common Lisp Changes: gcl (2.6.7-18) unstable; urgency=low . * remove emacs build dependency * synch xgcl-2 with Novak edits * fix build errors * Remove power of two limit to MAXPAGE;fix X lib paths * configure cleanup * delete-file works on directories;build xgcl the old way;latest xgcl from Gordon Novak Files: 45ce0cc3bbb21a493d9f928b3d799d5b 730 interpreters optional gcl_2.6.7-18.dsc 4c7096813288c42a9dc97585bb2e32f3 14457684 interpreters optional gcl_2.6.7-18.diff.gz 3df9a7fe5a1e420e40a62b488810d72c 764604 doc optional gcl-doc_2.6.7-18_all.deb bd01e801582cfe986c4314bafb060491 28804580 interpreters optional gcl_2.6.7-18_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQFE7MhuczG1wFfwRdwRAsqHAKCytWe0qxvEPnxa9FGwNnqVd8QQ3ACeO7Lt ytg7xVRjS7UYPYl6ocd3Gdw= =DVLt -----END PGP SIGNATURE----- Accepted: gcl-doc_2.6.7-18_all.deb to pool/main/g/gcl/gcl-doc_2.6.7-18_all.deb gcl_2.6.7-18.diff.gz to pool/main/g/gcl/gcl_2.6.7-18.diff.gz gcl_2.6.7-18.dsc to pool/main/g/gcl/gcl_2.6.7-18.dsc gcl_2.6.7-18_i386.deb to pool/main/g/gcl/gcl_2.6.7-18_i386.deb From luca at pca.it Wed Aug 23 21:21:04 2006 From: luca at pca.it (Luca Capello) Date: Wed, 23 Aug 2006 23:21:04 +0200 Subject: Bug#384071: [cl-debian] Bug#384071: stumpwm: Please update to a more recent cvs checkout References: <20060821180309.26966.43188.reportbug@zogzog.gnu-rox.org> <87y7tfa6r4.fsf@gismo.pca.it> <653bea160608230830l5bf1a90rc9ac826b1dfa5713@mail.gmail.com> Message-ID: <87zmdv6tdr.fsf@gismo.pca.it> Hello Far?! On Wed, 23 Aug 2006 17:30:46 +0200, Far? wrote: > Will you also include a cl-launch script to make stumpwm runnable > easily from the command-line? I'm still sceptic about it, not because cl-launch, but because stumpwm is something surely not "easy" (check bug #356948 [1] for more informations). Moreover, I think we need to find a common way to specify cl-launch files. For example, stumpwm can be loaded through CMUCL or SBCL, thus the script in /usr/bin/stumpwm cannot have the SBCL option hardcoded (because files in /usr should not be edited by the administrator). Thus, we would need something in /etc/cl-launch/, but this needs a bit of brainstorming, before ;-) > As I said in a previous mail, you should use (after testing) > something like Thank you for the hint, I put it into the StumpWM ToDo list, to be considered as soon as we will have solved the "problems" above. However, I, for myself, prefer to load every time a fresh SBCL instead of a dumped imaged. I guess we need to provide both solutions. Thx, bye, Gismo / Luca Footnotes: [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=356948 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: not available URL: From zedek at gnu.org Wed Aug 23 22:50:35 2006 From: zedek at gnu.org (Xavier Maillard) Date: Thu, 24 Aug 2006 00:50:35 +0200 Subject: Bug#384071: [cl-debian] Bug#384071: stumpwm: Please update to a more recent cvs checkout In-Reply-To: <87zmdv6tdr.fsf@gismo.pca.it> (message from Luca Capello on Wed, 23 Aug 2006 23:21:04 +0200) References: <20060821180309.26966.43188.reportbug@zogzog.gnu-rox.org> <87y7tfa6r4.fsf@gismo.pca.it> <653bea160608230830l5bf1a90rc9ac826b1dfa5713@mail.gmail.com> <87zmdv6tdr.fsf@gismo.pca.it> Message-ID: > As I said in a previous mail, you should use (after testing) > something like Thank you for the hint, I put it into the StumpWM ToDo list, to be considered as soon as we will have solved the "problems" above. However, I, for myself, prefer to load every time a fresh SBCL instead of a dumped imaged. I guess we need to provide both solutions. Is not this too long each time ? I was quite sceptic about dumping an image too but it really speeds things up (a lot) at startup. Xavier From zedek at gnu.org Wed Aug 23 22:53:17 2006 From: zedek at gnu.org (Xavier Maillard) Date: Thu, 24 Aug 2006 00:53:17 +0200 Subject: Bug#384071: [cl-debian] Bug#384071: stumpwm: Please update to a more recent cvs checkout In-Reply-To: <87zmdv6tdr.fsf@gismo.pca.it> (message from Luca Capello on Wed, 23 Aug 2006 23:21:04 +0200) References: <20060821180309.26966.43188.reportbug@zogzog.gnu-rox.org> <87y7tfa6r4.fsf@gismo.pca.it> <653bea160608230830l5bf1a90rc9ac826b1dfa5713@mail.gmail.com> <87zmdv6tdr.fsf@gismo.pca.it> Message-ID: Moreover, I think we need to find a common way to specify cl-launch files. For example, stumpwm can be loaded through CMUCL or SBCL, thus the script in /usr/bin/stumpwm cannot have the SBCL option hardcoded (because files in /usr should not be edited by the administrator). You can normally pass --lisp "sbcl cmucl clisp" as an argument thus you can easily set LISPS="list of CL implentations separated by spaces". I personally used to use this when on Gentoo GNU/Linux: cl-launch --output ~/bin/mystumpwm --lisp "sbcl clisp" \ --system stumpwm --init '(stumpwm:stumpwm ":0")' Xavier From christian.lynbech at ericsson.com Thu Aug 24 12:47:15 2006 From: christian.lynbech at ericsson.com (Christian Lynbech) Date: Thu, 24 Aug 2006 14:47:15 +0200 Subject: [cl-debian] Bug#384457: common-lisp-controller: Reconfiguration of ASDF is too intrusive Message-ID: Package: common-lisp-controller Version: 6.2 Severity: normal In order for CLC to store fasls in /var/cache, it adds a method to `asdf:output-files' with some dire effects on the user environment. Either the fasl root configuration should be organised to be active only when compiling from within `clc-require' or there should at least be some way to disable/reconfigure the redirection of fasl files. The problem is that when doing any normal ASDF compilation in an CLC6 enabled lisp (at least verified in CMUCL, package version 19c-release-20051115-2), the fasl files all end up in /var/cache as well. This means the annoyance of it being more difficult to remove all fasls in order to recompile compared to when the fasls appear in the local directory. More seriously, it means that some packages will fail to build. If one downloads the latest mcclim snapshot and tries to build the Listener application, it fails due to the inability to find some xpm files: ;; Loading #P"/var/cache/common-lisp-controller/416/cmucl/local/net/daphne/usr/local/home/tedchly/Tools/UPSTREAM/mcclim/Apps/Listener/icons.x86f". ; Compilation unit aborted. Error in batch processing: File-error in function LISP::FD-OPEN: Error opening #P"/var/cache/common-lisp-controller/416/cmucl/local/net/daphne/usr/local/home/tedchly/Tools/UPSTREAM/mcclim/Apps/Listener/icons/folder.xpm", No such file or directory. A problem that would not have hit if one could have compiled this in place rather than redirecting fasls to /var/cache. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.5-7.151-default Locale: LANG=C, LC_CTYPE=da_DK (charmap=ISO-8859-1) Versions of packages common-lisp-controller depends on: ii bash 3.1-5 The GNU Bourne Again SHell ii cl-asdf 1.99-3 Another System Definition Facility ii debconf [debconf-2.0] 1.5.3 Debian configuration management sy ii debianutils 2.17 Miscellaneous utilities specific t ii perl 5.8.8-6.1 Larry Wall's Practical Extraction ii realpath 1.10 Return the canonicalized absolute common-lisp-controller recommends no packages. From owner at packages.qa.debian.org Thu Aug 24 14:25:31 2006 From: owner at packages.qa.debian.org (owner at packages.qa.debian.org) Date: Thu, 24 Aug 2006 09:25:31 -0500 Subject: [cl-debian] Re: Web subscription for cl-launch package Message-ID: An embedded and charset-unspecified text was scrubbed... Name: not available URL: From pts at qa.debian.org Thu Aug 24 14:25:30 2006 From: pts at qa.debian.org (Debian Package Tracking System) Date: Thu, 24 Aug 2006 09:25:30 -0500 Subject: [cl-debian] CONFIRM 489307121e704c3e661c334f9ecd2f34 Message-ID: Hello, you asked to be subscribed to the "mailing list"[1] for the Debian source package called cl-launch. To complete this process, you have to reply to this mail by including this command : CONFIRM 489307121e704c3e661c334f9ecd2f34 On any modern mailer, you just have to hit reply and send the mail. If you don't understand why you got this mail, please ignore it, you won't be subscribed to anything unless you confirm it. If you have any problem with this service, please contact owner at packages.qa.debian.org. Thanks, [1] This list receives all the bug reports (and the corresponding logs) for the package "cl-launch" that are sent to the Debian Bug Tracking System. http://packages.qa.debian.org/cl-launch From owner at packages.qa.debian.org Thu Aug 24 15:08:18 2006 From: owner at packages.qa.debian.org (owner at packages.qa.debian.org) Date: Thu, 24 Aug 2006 10:08:18 -0500 Subject: [cl-debian] Re: subscribe cl-launch cl-debian@common-lisp.net In-Reply-To: <87sljmgpu4.fsf@gismo.pca.it> References: <87sljmgpu4.fsf@gismo.pca.it> Message-ID: An embedded and charset-unspecified text was scrubbed... Name: not available URL: From luca at pca.it Thu Aug 24 15:08:27 2006 From: luca at pca.it (Luca Capello) Date: Thu, 24 Aug 2006 17:08:27 +0200 Subject: [cl-debian] CONFIRM 489307121e704c3e661c334f9ecd2f34 In-Reply-To: (Debian Package Tracking System's message of "Thu, 24 Aug 2006 09:25:30 -0500") References: Message-ID: <8764gigoic.fsf@gismo.pca.it> Hello! On Thu, 24 Aug 2006 16:25:30 +0200, Debian Package Tracking System wrote: > you asked to be subscribed to the "mailing list"[1] for the Debian > source package called cl-launch. To complete this process, you > have to reply to this mail by including this command : Sorry, I messed up with the Mailman interface... :-( Thx, bye, Gismo / Luca -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: not available URL: From luca at pca.it Thu Aug 24 14:31:24 2006 From: luca at pca.it (Luca Capello) Date: Thu, 24 Aug 2006 16:31:24 +0200 Subject: Bug#384071: [cl-debian] Bug#384071: stumpwm: Please update to a more recent cvs checkout References: <20060821180309.26966.43188.reportbug@zogzog.gnu-rox.org> <87y7tfa6r4.fsf@gismo.pca.it> <653bea160608230830l5bf1a90rc9ac826b1dfa5713@mail.gmail.com> <87zmdv6tdr.fsf@gismo.pca.it> Message-ID: <87u042i4sj.fsf@gismo.pca.it> Hello Xavier! On Thu, 24 Aug 2006 00:50:35 +0200, Xavier Maillard wrote: >> Thank you for the hint, I put it into the StumpWM ToDo list, to be >> considered as soon as we will have solved the "problems" above. >> However, I, for myself, prefer to load every time a fresh SBCL >> instead of a dumped imaged. I guess we need to provide both >> solutions. > > Is not this too long each time ? I was quite sceptic about dumping > an image too but it really speeds things up (a lot) at startup. Well, I never tested a dumped image and in my case I don't care at all about the startup speed, because as I'm a massive user of suspend-to-disk (sometime suspend-to-ram, too), I don't reboot my laptop (and consequently my X) so often. Moreover, as I track the CVS version, I don't need to dump a new image every time there's a new commit ;-) [OK, StumpWM has not a lot of commits, but just to explain you my idea] As I already stated, IMHO we should provide both solutions, maybe triggered by a command-line option ? Far?, what do you think about it? Thx, bye, Gismo / Luca -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: not available URL: From zedek at gnu.org Thu Aug 24 16:10:17 2006 From: zedek at gnu.org (Xavier Maillard) Date: Thu, 24 Aug 2006 18:10:17 +0200 Subject: [cl-debian] CONFIRM 489307121e704c3e661c334f9ecd2f34 In-Reply-To: <8764gigoic.fsf@gismo.pca.it> (message from Luca Capello on Thu, 24 Aug 2006 17:08:27 +0200) References: <8764gigoic.fsf@gismo.pca.it> Message-ID: Sorry, I messed up with the Mailman interface... :-( No problem :) Xavier From zedek at gnu.org Thu Aug 24 16:08:28 2006 From: zedek at gnu.org (Xavier Maillard) Date: Thu, 24 Aug 2006 18:08:28 +0200 Subject: Bug#384071: [cl-debian] Bug#384071: stumpwm: Please update to a more recent cvs checkout In-Reply-To: <87u042i4sj.fsf@gismo.pca.it> (message from Luca Capello on Thu, 24 Aug 2006 16:31:24 +0200) References: <20060821180309.26966.43188.reportbug@zogzog.gnu-rox.org> <87y7tfa6r4.fsf@gismo.pca.it> <653bea160608230830l5bf1a90rc9ac826b1dfa5713@mail.gmail.com> <87zmdv6tdr.fsf@gismo.pca.it> <87u042i4sj.fsf@gismo.pca.it> Message-ID: Yo Luca, From: Luca Capello > Is not this too long each time ? I was quite sceptic about dumping > an image too but it really speeds things up (a lot) at startup. Well, I never tested a dumped image and in my case I don't care at all about the startup speed, because as I'm a massive user of suspend-to-disk (sometime suspend-to-ram, too), I don't reboot my laptop (and consequently my X) so often. Lucky you. Here too I massively use s2d but stumpwm (or lisp implementation) often freezes here ;) [snip] As I already stated, IMHO we should provide both solutions, maybe triggered by a command-line option ? Far=C3=A9, what do you think about it? I am not against that idea. Maybe just adding this information into README.Debian can be enough or just display something when installing the Debian package ? Oh and by the way, do you maintaint a Debian repository where we could apt-get stumpwm "beta package" ? Xavier From fahree at gmail.com Thu Aug 24 16:50:31 2006 From: fahree at gmail.com (=?UTF-8?Q? Far=C3=A9 ?=) Date: Thu, 24 Aug 2006 12:50:31 -0400 Subject: Bug#384071: [cl-debian] Bug#384071: stumpwm: Please update to a more recent cvs checkout In-Reply-To: References: <20060821180309.26966.43188.reportbug@zogzog.gnu-rox.org> <87y7tfa6r4.fsf@gismo.pca.it> <653bea160608230830l5bf1a90rc9ac826b1dfa5713@mail.gmail.com> <87zmdv6tdr.fsf@gismo.pca.it> <87u042i4sj.fsf@gismo.pca.it> Message-ID: <653bea160608240950w567fd6deu3c2e872c267a51a8@mail.gmail.com> We could very well have several versions of stumpwm generated by cl-launch, and a master-script that accepts options and picks the right one depending on those options, and/or a /etc/alternatives/ thingie to select which version to pick. Personally, I when I use stumpwm, I don't usually dump image, because I re-launch it with twiddled sources more often than I start it from stable sources. [ Fran?ois-Ren? ?VB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Merely having an open mind is nothing; the object of opening the mind, as of opening the mouth, is to shut it again on something solid. -- G.K. Chesterton On 24/08/06, Xavier Maillard wrote: > Yo Luca, > > From: Luca Capello > > > Is not this too long each time ? I was quite sceptic about dumping > > an image too but it really speeds things up (a lot) at startup. > > Well, I never tested a dumped image and in my case I don't care at > all about the startup speed, because as I'm a massive user of > suspend-to-disk (sometime suspend-to-ram, too), I don't reboot my > laptop (and consequently my X) so often. > > Lucky you. Here too I massively use s2d but stumpwm (or lisp > implementation) often freezes here ;) > > [snip] > > As I already stated, IMHO we should provide both solutions, maybe > triggered by a command-line option ? Far=C3=A9, what do you think about > it? > > I am not against that idea. Maybe just adding this information into > README.Debian can be enough or just display something when installing > the Debian package ? > > Oh and by the way, do you maintaint a Debian repository where we could > apt-get stumpwm "beta package" ? > > Xavier From edi at agharta.de Fri Aug 25 09:48:53 2006 From: edi at agharta.de (Edi Weitz) Date: Fri, 25 Aug 2006 11:48:53 +0200 Subject: [cl-debian] [ann] [rdnzl-announce] New release 0.10.3 Message-ID: ChangeLog: Version 0.10.3 2006-08-25 Added Excel example Fixed bug in AREF* Changed package handling in system definition (thanks to Christophe Rhodes) Download: http://weitz.de/files/RDNZL.tar.gz Cheers, Edi. _______________________________________________ rdnzl-announce mailing list rdnzl-announce at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/rdnzl-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From owner at packages.qa.debian.org Fri Aug 25 21:19:24 2006 From: owner at packages.qa.debian.org (owner at packages.qa.debian.org) Date: Fri, 25 Aug 2006 16:19:24 -0500 Subject: [cl-debian] You are now subscribed to cl-launch In-Reply-To: <87ac5sa59a.fsf@gismo.pca.it> References: <87ac5sa59a.fsf@gismo.pca.it> Message-ID: An embedded and charset-unspecified text was scrubbed... Name: not available URL: From luca at pca.it Sat Aug 26 01:08:13 2006 From: luca at pca.it (Luca Capello) Date: Sat, 26 Aug 2006 03:08:13 +0200 Subject: [cl-debian] Bug#384697: cl-launch: need to modify script variables without touching the script Message-ID: <87u040483m.fsf@gismo.pca.it> Package: cl-launch Version: 1.85-1 Severity: wishlist Hello, the background of this wishlist can be found on bug #384071 [1], I created a new bug because I think the discussion was becoming specific to CL-Launch and no more to StumpWM. BTW, Xavier, I Cc:ed you because you were deeply involved in the discussion, I hope you don't mind :-) On Thu, 24 Aug 2006 00:53:17 +0200, Xavier Maillard wrote: >> Moreover, I think we need to find a common way to specify cl-launch >> files. For example, stumpwm can be loaded through CMUCL or SBCL, >> thus the script in /usr/bin/stumpwm cannot have the SBCL option >> hardcoded (because files in /usr should not be edited by the >> administrator). > > You can normally pass --lisp "sbcl cmucl clisp" as an argument thus > you can easily set LISPS="list of CL implentations separated by > spaces". I'm aware of this, but the main problem here is the following. At package building time, I create the /usr/bin/stumpwm script with cl-launch --output ./stumpwm --lisp "sbcl clisp" \ --system stumpwm --init '(stumpwm:stumpwm ":0")' But with this solution, as the StumpWM maintainer I'm giving a preference to SBCL (because it's the first in the list). As by the Debian Policy not the administrator neither the end-user have the rights to modify files in /usr, but only in /etc (because only modifications done in the latter are preserved during package upgrades), if someone wants to start StumpWM through CMUCL needs to copy /usr/bin/stumpwm somewhere and modify the $LISPS variable. Thus, I think we need to find a general and user-specific solution: something like a /etc/cl-launchrc and ~/.cl-launchrc files, where for every CL-Launch binary script (e.g. /usr/bin/stumpwm) one can override variables (especially $LISPS). Thus, any maintainer that wants to provide CL-Launch binary scripts could specify every supported Common Lisp implementation, then the administrator or the end-user can adjust to his needs. Obviously, someone may prefer to copy /usr/bin/stumpwm into ~/bin, but I'm not for "polluting" $HOME with multiple copies of /usr/bin/ files which differ only for a line (yes, I'm a bit paranoid). Thx, bye, Gismo / Luca -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-rc4 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages cl-launch depends on: ii common-lisp-controller 6.2 This is a Common Lisp source and c cl-launch recommends no packages. -- no debconf information Footnotes: [1] http://bugs.debian.org/384071 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: not available URL: From fahree at gmail.com Sat Aug 26 04:08:39 2006 From: fahree at gmail.com (=?UTF-8?Q? Far=C3=A9 ?=) Date: Sat, 26 Aug 2006 00:08:39 -0400 Subject: [cl-debian] Bug#384697: cl-launch: need to modify script variables without touching the script In-Reply-To: <87u040483m.fsf@gismo.pca.it> References: <87u040483m.fsf@gismo.pca.it> Message-ID: <653bea160608252108u7378ef3m4444c328b5a02754@mail.gmail.com> On 25/08/06, Luca Capello wrote: > Package: cl-launch > Version: 1.85-1 > Severity: wishlist I'm not sure we either need or want a /etc/cl-launchrc or a ~/.cl-launchrc. After all, the user (or root) may already export the variable $LISP to override things at runtime (or at dump time), whatever the --lisp or $LISPS variable be, unless explicitly prevented with a --wrap argument (or a resetting of $LISP), and I think that's all we need. As for stumpwm, note that I prefer the more versatile --init argument: '(stumpwm:stumpwm (cl-launch:getenv "DISPLAY"))' to a hardcoded :0. If multiple dumped versions are wanted, they should each have a different name, and the main script would select amongst them. Finally, there are embarassing bugs in cl-launch 1.85, and I'd appreciate it if one of my sponsors would have the time upload 1.86 to unstable. [ Fran?ois-Ren? ?VB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] You're currently going through a difficult transition period called "Life." From fahree at gmail.com Sat Aug 26 04:08:39 2006 From: fahree at gmail.com (=?UTF-8?Q? Far=C3=A9 ?=) Date: Sat, 26 Aug 2006 00:08:39 -0400 Subject: [cl-debian] Bug#384697: cl-launch: need to modify script variables without touching the script In-Reply-To: <87u040483m.fsf@gismo.pca.it> References: <87u040483m.fsf@gismo.pca.it> Message-ID: <653bea160608252108u7378ef3m4444c328b5a02754@mail.gmail.com> On 25/08/06, Luca Capello wrote: > Package: cl-launch > Version: 1.85-1 > Severity: wishlist I'm not sure we either need or want a /etc/cl-launchrc or a ~/.cl-launchrc. After all, the user (or root) may already export the variable $LISP to override things at runtime (or at dump time), whatever the --lisp or $LISPS variable be, unless explicitly prevented with a --wrap argument (or a resetting of $LISP), and I think that's all we need. As for stumpwm, note that I prefer the more versatile --init argument: '(stumpwm:stumpwm (cl-launch:getenv "DISPLAY"))' to a hardcoded :0. If multiple dumped versions are wanted, they should each have a different name, and the main script would select amongst them. Finally, there are embarassing bugs in cl-launch 1.85, and I'd appreciate it if one of my sponsors would have the time upload 1.86 to unstable. [ Fran?ois-Ren? ?VB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] You're currently going through a difficult transition period called "Life." From aurel32 at debian.org Sat Aug 26 13:02:56 2006 From: aurel32 at debian.org (Aurelien Jarno) Date: Sat, 26 Aug 2006 15:02:56 +0200 Subject: [cl-debian] Bug#384758: FTBFS: build-depends on removed package lesstif-dev Message-ID: <20060826130256.23821.62477.reportbug@bode.aurel32.net> Package: cmucl Version: cmucl_19c-release-20051115-2 Severity: serious Tags: etch sid Justification: fails to build from source >From my build log: > Automatic build of cmucl_19c-release-20051115-2 on testbuild by sbuild/i386 85 > Build started at 20060826-1357 > ****************************************************************************** > Checking available source versions... > Fetching source files... > Reading package lists... > Building dependency tree... > Need to get 6161kB of source archives. > Get:1 http://debian.aurel32.net sid/main cmucl 19c-release-20051115-2 (dsc) [745B] > Get:2 http://debian.aurel32.net sid/main cmucl 19c-release-20051115-2 (tar) [4654kB] > Get:3 http://debian.aurel32.net sid/main cmucl 19c-release-20051115-2 (diff) [1506kB] > Fetched 6161kB in 0s (7685kB/s) > Download complete and in download only mode > ** Using build dependencies supplied by package: > Build-Depends: debhelper (>= 4.1.16), lesstif-dev, tetex-extra, cmucl (>= 19c-pre1-20051019-1), hevea, tidy, > +a2ps, x-dev, gcc-3.4, bc > Checking for already installed source dependencies... > debhelper: missing > Using default version 5.0.37.3 > lesstif-dev: missing > tetex-extra: missing > cmucl: missing > Using default version 19c-release-20051115-2 > hevea: missing > tidy: missing > a2ps: missing > x-dev: missing > gcc-3.4: missing > bc: missing > Checking for source dependency conflicts... > /usr/bin/sudo /usr/bin/apt-get --purge $CHROOT_OPTIONS -q -y install debhelper lesstif-dev tetex-extra > +cmucl hevea tidy a2ps x-dev gcc-3.4 bc > Reading package lists... > Building dependency tree... > Package lesstif-dev is not available, but is referred to by another package. > This may mean that the package is missing, has been obsoleted, or > is only available from another source > However the following packages replace it: > lesstif2-dev > E: Package lesstif-dev has no installation candidate > apt-get failed. > Package installation failed > Trying to reinstall removed packages: > Trying to uninstall newly installed packages: > Source-dependencies not satisfied; skipping cmucl > ****************************************************************************** > Finished at 20060826-1357 > Build needed 00:00:00, 0k disk space -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-amd64-k8-smp Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8) From pc at p-cos.net Sat Aug 26 15:14:43 2006 From: pc at p-cos.net (Pascal Costanza) Date: Sat, 26 Aug 2006 17:14:43 +0200 Subject: [cl-debian] [ann] [closer-announce] New releases in the Closer project. Message-ID: <4D842F02-9A6C-4AEE-890F-3648CF7B2A23@p-cos.net> Hi everyone, I have just uploaded new versions of all packages in the Closer project. They are all tagged with new version numbers, and tar balls of the new versions are also available. Please see http://common- lisp.net/project/closer for more details. Pascal -- Pascal Costanza, mailto:pc at p-cos.net, http://p-cos.net Vrije Universiteit Brussel, Programming Technology Lab Pleinlaan 2, B-1050 Brussel, Belgium _______________________________________________ closer-announce mailing list closer-announce at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/closer-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From luca at pca.it Sat Aug 26 16:50:40 2006 From: luca at pca.it (Luca Capello) Date: Sat, 26 Aug 2006 18:50:40 +0200 Subject: [cl-debian] Bug#384697: cl-launch: need to modify script variables without touching the script References: <87u040483m.fsf@gismo.pca.it> <653bea160608252108u7378ef3m4444c328b5a02754@mail.gmail.com> Message-ID: <874pvz1lwf.fsf@gismo.pca.it> tags 384697 + patch thanks Hello Far?! On Sat, 26 Aug 2006 06:08:39 +0200, Far? wrote: > I'm not sure we either need or want a /etc/cl-launchrc or a > ~/.cl-launchrc. I still think that's the way to go, but obviously we need more feedbacks from the other CL-Debian developers/users (especially Peter and Ren?). Xavier, this is the reason I explicitly cc:ed you again, I hope you don't mind :-) The attached patch is a very simple support for ~/.cl-launchrc, based on the CL-Launch available in Debian, thus 1.85-1. To apply it: $ [save the patch somewhere] $ cp /usr/share/common-lisp/source/cl-launch/wrapper.sh ~/ $ patch wrapper.sh < /path/to/the/patch $ [modify your CL-Launch script to call include ~/wrapper.sh instead of the /usr/share/common-lisp/source/cl-launch/wrapper.sh] ~/.cl-launchrc is a shell file, with the following structure: [value of $SOFTWARE_SYSTEM in the CL-Launch script] = \ [Common Lisp implementation to be used] I assume that the value of $SOFTWARE_SYSTEM will always be the name of the script, i.e. /usr/bin/$SOFTWARE_SYSTEM. Thus, for StumpWM would be something like the following: stumpwm=sbcl ATM the patch is quite dirty, because it uses grep and the BASH parameter substitution to assign the value, while the same function should be very simple as: check_lisp_variable () { test -r /etc/cl-launchrc && . /etc/cl-launchrc test -r "$HOME/.cl-launchrc" && . "$HOME/.cl-launchrc" test -n ${SOFTWARE_SYSTEM} && LISP=${SOFTWARE_SYSTEM} } The last line is obviously fault, what I'd like to do is: if the variable called with the name of the value of $SOFTWARE_SYSTEM is not-empty set the LISP variable to that value Unfortunately, I don't know how to do it in shell language, I quickly and unsuccessfully read `man bash`, so I post here in case someone with more shell skills would help. > After all, the user (or root) may already export the variable $LISP > to override things at runtime (or at dump time), whatever the --lisp > or $LISPS variable be, unless explicitly prevented with a --wrap > argument (or a resetting of $LISP), and I think that's all we need. If we ship a CL-Launch script I'd like to avoid special forms like: $ LISP=sbcl /usr/bin/stumpwm $ /usr/bin/stumpwm --lisp sbcl > As for stumpwm, note that I prefer the more versatile --init > argument: > '(stumpwm:stumpwm (cl-launch:getenv "DISPLAY"))' > to a hardcoded :0. OK, I noticed it and I completely agree, as this is The Right Thing?, because we can't assume $DISPLAY always :0.0. > If multiple dumped versions are wanted, they should each have a > different name, and the main script would select amongst them. Well, for sure I'm not going to support multiple versions (would be them dumped images or not). IMHO, if a Debian package ships a CL-Launch script at /usr/bin/$SOFTWARE_SYSTEM, this should be the more generic possible, i.e. $LISPS should contains all the Common Lisp implementation that the _Debian package_ support. Thx, bye, Gismo / Luca -------------- next part -------------- A non-text attachment was scrubbed... Name: home_cl-launchrc_gismo-20060826.patch Type: text/x-patch Size: 595 bytes Desc: very brutal ~/.cl-launchrc support URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: not available URL: From owner at bugs.debian.org Sat Aug 26 17:18:29 2006 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sat, 26 Aug 2006 10:18:29 -0700 Subject: [cl-debian] Processed: Re: Bug#384697: cl-launch: need to modify script variables without touching the script In-Reply-To: <874pvz1lwf.fsf@gismo.pca.it> References: <874pvz1lwf.fsf@gismo.pca.it> Message-ID: Processing commands for control at bugs.debian.org: > tags 384697 + patch Bug#384697: cl-launch: need to modify script variables without touching the script 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 zedek at gnu.org Sun Aug 27 22:41:49 2006 From: zedek at gnu.org (Xavier Maillard) Date: Mon, 28 Aug 2006 00:41:49 +0200 Subject: Bug#384697: [cl-debian] Bug#384697: cl-launch: need to modify script variables without touching the script In-Reply-To: <653bea160608252108u7378ef3m4444c328b5a02754@mail.gmail.com> (fahree@gmail.com) References: <87u040483m.fsf@gismo.pca.it> <653bea160608252108u7378ef3m4444c328b5a02754@mail.gmail.com> Message-ID: I'm not sure we either need or want a /etc/cl-launchrc or a ~/.cl-launchrc. After all, the user (or root) may already export the variable $LISP to override things at runtime (or at dump time), whatever the --lisp or $LISPS variable be, unless explicitly prevented with a --wrap argument (or a resetting of $LISP), and I think that's all we need. I second this. As for stumpwm, note that I prefer the more versatile --init argument: '(stumpwm:stumpwm (cl-launch:getenv "DISPLAY"))' to a hardcoded :0. Oh nice enhancement ! I did not know I could do this. Thank you. -- Xavier From edi at agharta.de Mon Aug 28 08:58:49 2006 From: edi at agharta.de (Edi Weitz) Date: Mon, 28 Aug 2006 10:58:49 +0200 Subject: [cl-debian] [ann] [tbnl-announce] New releases TBNL 0.10.0 / Hunchentoot 0.2.0 Message-ID: TBNL: ----- ChangeLog: Version 0.10.0 2006-08-28 Based LispWorks version of TBNL on Hunchentoot infrastructure Added "easy" handlers Exported GET-BACKTRACE (suggested by Erik Enge) Download: http://weitz.de/files/tbnl.tar.gz Hunchentoot: ------------ ChangeLog: Version 0.2.0 2006-08-28 Serves as infrastructure for TBNL now (to replace KMRCL) For HTTP/1.1 only send 'Keep-Alive' headers if explicitely requested Download: http://weitz.de/files/hunchentoot.tar.gz LispWorks users please note that Hunchentoot is now a mandatory installation if you want to use TBNL - it replaces KMRCL. You can still use TBNL as before, but the installation procedure has changed a bit - see documentation. For other Lisps the installation hasn't changed. Please note that this infrastructure change and the new "easy" handlers should be considered experimental. Please report problems to the mailing list. Thanks. Have fun, 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 owner at bugs.debian.org Mon Aug 28 16:48:50 2006 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Mon, 28 Aug 2006 09:48:50 -0700 Subject: [cl-debian] Bug#382145: marked as done (gcl_2.6.7-17(ia64/unstable): FTBFS: "Can't allocate.") References: <54irkc7r00.fsf@intech19.enhanced.com> <20060809084630.GI5985@mmjgroup.com> Message-ID: Your message dated 28 Aug 2006 12:40:47 -0400 with message-id <54irkc7r00.fsf at intech19.enhanced.com> and subject line Bug#382145: gcl_2.6.7-17(ia64/unstable): FTBFS: "Can't allocate." 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: lamont at debian.org Subject: gcl_2.6.7-17(ia64/unstable): FTBFS: "Can't allocate." Date: Wed, 9 Aug 2006 02:46:30 -0600 Size: 2409 URL: -------------- next part -------------- An embedded message was scrubbed... From: Camm Maguire Subject: Re: Bug#382145: gcl_2.6.7-17(ia64/unstable): FTBFS: "Can't allocate." Date: 28 Aug 2006 12:40:47 -0400 Size: 2801 URL: From noreply at henning.makholm.net Mon Aug 28 21:08:10 2006 From: noreply at henning.makholm.net (Debian testing watch) Date: Mon, 28 Aug 2006 15:08:10 -0600 Subject: [cl-debian] cl-uffi 1.5.15-1 MIGRATED to testing Message-ID: FYI: The status of the cl-uffi source package in Debian's testing distribution has changed. Previous version: 1.5.14-1 Current version: 1.5.15-1 -- 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 Mon Aug 28 21:08:10 2006 From: noreply at henning.makholm.net (Debian testing watch) Date: Mon, 28 Aug 2006 15:08:10 -0600 Subject: [cl-debian] cl-sql 3.6.6-1 MIGRATED to testing Message-ID: FYI: The status of the cl-sql source package in Debian's testing distribution has changed. Previous version: 3.6.3-1 Current version: 3.6.6-1 -- This email is automatically generated; henning at makholm.net is responsible. See http://people.debian.org/~henning/trille/ for more information. From uwe at hermann-uwe.de Tue Aug 29 10:11:31 2006 From: uwe at hermann-uwe.de (Uwe Hermann) Date: Tue, 29 Aug 2006 12:11:31 +0200 Subject: [cl-debian] Bug#385126: warning: file `/usr/share/doc/gcl-doc/dwdoc/index.html' does not exist at /usr/sbin/install-docs line 718, line 15. Message-ID: <20060829101131.GA6649@aragorn> Package: gcl-doc Version: 2.6.7-18 Severity: normal Not sure how critical this is, but I got this when doing a dist-upgrade recently: warning: file `/usr/share/doc/gcl-doc/dwdoc/index.html' does not exist at /usr/sbin/install-docs line 718, line 15. warning: file `/usr/share/doc/gcl-doc/dwdoc/index.html' does not exist at /usr/sbin/install-docs line 718, line 15. HTH, Uwe. -- Uwe Hermann http://www.hermann-uwe.de http://www.it-services-uh.de | http://www.crazy-hacks.org http://www.holsham-traders.de | http://www.unmaintained-free-software.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From der_julian at web.de Sun Aug 27 16:20:27 2006 From: der_julian at web.de (Julian Stecklina) Date: Sun, 27 Aug 2006 18:20:27 +0200 Subject: [cl-debian] [ann] [blitzblog-announce] Ports to CMUCL and SBCL Message-ID: <44F1C64B.70909@web.de> Hello, I have ported blitzblog to CMUCL and SBCL in addition to the existing Allegro CL port. XML-RPC is not yet ported, so the Emacs blogging interface does not work at the moment. Dump and restore of the blog database (which is needed if I change the database backend) does also still need work and does not work on non-ACL. Regards, Julian _______________________________________________ blitzblog-announce mailing list blitzblog-announce at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/blitzblog-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From kmr at debian.org Tue Aug 29 15:17:04 2006 From: kmr at debian.org (Kevin M. Rosenberg) Date: Tue, 29 Aug 2006 08:17:04 -0700 Subject: [cl-debian] Accepted cl-sql 3.6.7-1 (source all i386) Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Tue, 29 Aug 2006 09:04:41 -0600 Source: cl-sql Binary: cl-sql-sqlite3 cl-sql-oracle cl-sql-aodbc cl-sql-postgresql-socket cl-sql-postgresql cl-sql-odbc cl-sql cl-sql-uffi cl-sql-tests cl-sql-sqlite cl-sql-mysql Architecture: source all i386 Version: 3.6.7-1 Distribution: unstable Urgency: low Maintainer: Kevin M. Rosenberg Changed-By: Kevin M. Rosenberg Description: cl-sql - SQL Interface for Common Lisp cl-sql-aodbc - CLSQL database backend, AODBC cl-sql-mysql - CLSQL database backend, MySQL cl-sql-odbc - CLSQL database backend, ODBC cl-sql-oracle - CLSQL database backend, Oracle cl-sql-postgresql - CLSQL database backend, PostgreSQL cl-sql-postgresql-socket - CLSQL database backend, PostgreSQL cl-sql-sqlite - CLSQL database backend, SQLite cl-sql-sqlite3 - CLSQL database backend, SQLite3 cl-sql-tests - Testing suite for CLSQL cl-sql-uffi - Common UFFI functions for CLSQL database backends Changes: cl-sql (3.6.7-1) unstable; urgency=low . * New upstream Files: ba2795c9bb38d97d00502527771a0153 796 devel extra cl-sql_3.6.7-1.dsc 74e589f2c1359b0b7062dcf9d1d771fe 708224 devel extra cl-sql_3.6.7.orig.tar.gz d0143326c16880c9f47146c017d6541d 11538 devel extra cl-sql_3.6.7-1.diff.gz 59a965082d74c1de916781cd043bc8a8 494444 devel extra cl-sql_3.6.7-1_all.deb 768f0ef828a5e40a1e7d2a6d4a869870 37790 devel extra cl-sql-aodbc_3.6.7-1_all.deb 8347a52bf96032e3fc142a5b83636019 64430 devel extra cl-sql-odbc_3.6.7-1_all.deb 2e7f9457579dc31e2b4472b8b8b192a7 42448 devel extra cl-sql-postgresql_3.6.7-1_all.deb 2f99746bb078922df1f6b589dcd793b8 46578 devel extra cl-sql-postgresql-socket_3.6.7-1_all.deb c2031e0ff15dae4149da1cefd74dbf81 42322 devel extra cl-sql-sqlite_3.6.7-1_all.deb ec29ec0e2969987cef624cd10b59b930 43088 devel extra cl-sql-sqlite3_3.6.7-1_all.deb 9961020f6d68175af0bf6e589ccd311e 58762 contrib/devel extra cl-sql-oracle_3.6.7-1_all.deb 48744cb5f7b0529e6b370c446a4b19f0 61148 devel extra cl-sql-tests_3.6.7-1_all.deb bbdd74e018a8f9501d30ba184eebbee4 41154 devel extra cl-sql-uffi_3.6.7-1_i386.deb aa6a4e113566b776ab348e19229e7124 51460 devel extra cl-sql-mysql_3.6.7-1_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE9FgBES7N8sSjgj4RAgCcAJ9ps1DXkUFgQhpbMYSxolDv74Vl/QCeO4FX SDbMGPTs3g/rE2O/RMZJmOQ= =7F/9 -----END PGP SIGNATURE----- Accepted: cl-sql-aodbc_3.6.7-1_all.deb to pool/main/c/cl-sql/cl-sql-aodbc_3.6.7-1_all.deb cl-sql-mysql_3.6.7-1_i386.deb to pool/main/c/cl-sql/cl-sql-mysql_3.6.7-1_i386.deb cl-sql-odbc_3.6.7-1_all.deb to pool/main/c/cl-sql/cl-sql-odbc_3.6.7-1_all.deb cl-sql-oracle_3.6.7-1_all.deb to pool/contrib/c/cl-sql/cl-sql-oracle_3.6.7-1_all.deb cl-sql-postgresql-socket_3.6.7-1_all.deb to pool/main/c/cl-sql/cl-sql-postgresql-socket_3.6.7-1_all.deb cl-sql-postgresql_3.6.7-1_all.deb to pool/main/c/cl-sql/cl-sql-postgresql_3.6.7-1_all.deb cl-sql-sqlite3_3.6.7-1_all.deb to pool/main/c/cl-sql/cl-sql-sqlite3_3.6.7-1_all.deb cl-sql-sqlite_3.6.7-1_all.deb to pool/main/c/cl-sql/cl-sql-sqlite_3.6.7-1_all.deb cl-sql-tests_3.6.7-1_all.deb to pool/main/c/cl-sql/cl-sql-tests_3.6.7-1_all.deb cl-sql-uffi_3.6.7-1_i386.deb to pool/main/c/cl-sql/cl-sql-uffi_3.6.7-1_i386.deb cl-sql_3.6.7-1.diff.gz to pool/main/c/cl-sql/cl-sql_3.6.7-1.diff.gz cl-sql_3.6.7-1.dsc to pool/main/c/cl-sql/cl-sql_3.6.7-1.dsc cl-sql_3.6.7-1_all.deb to pool/main/c/cl-sql/cl-sql_3.6.7-1_all.deb cl-sql_3.6.7.orig.tar.gz to pool/main/c/cl-sql/cl-sql_3.6.7.orig.tar.gz From florent at sarcelle.net Tue Aug 29 15:49:08 2006 From: florent at sarcelle.net (Florent Bayle) Date: Tue, 29 Aug 2006 17:49:08 +0200 Subject: [cl-debian] Bug#385176: gcl: FTBFS: bashisms in build scripts In-Reply-To: References: Message-ID: <200608291749.13930.florent@sarcelle.net> Package: gcl Version: 2.6.7-18 Severity: important Justification: Policy 10.4 Hi, There was a problem while autobuilding your package: > Automatic build of gcl_2.6.7-18 on saturne by sbuild/amd64 85 > Build started at 20060828-1534 > ****************************************************************************** [...] > /usr/bin/fakeroot debian/rules clean > rm -f ${debian/control.rm%.rm} > /bin/sh: Syntax error: Bad substitution > make: *** [debian/control.rm] Error 2 > ****************************************************************************** > Build finished at 20060828-1536 > FAILED [dpkg-buildpackage died] ${debian/control.rm%.rm} is not POSIX, and this make the build fail if you're not using bash as sh. -- Florent -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From camm at enhanced.com Tue Aug 29 22:02:42 2006 From: camm at enhanced.com (Camm Maguire) Date: Tue, 29 Aug 2006 15:02:42 -0700 Subject: [cl-debian] Accepted gclcvs 2.7.0-55 (source i386 all) Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Tue, 29 Aug 2006 13:30:41 -0400 Source: gclcvs Binary: gclcvs gclcvs-doc Architecture: source i386 all Version: 2.7.0-55 Distribution: unstable Urgency: low Maintainer: Camm Maguire Changed-By: Camm Maguire Description: gclcvs - GNU Common Lisp compiler, CVS snapshot gclcvs-doc - Documentation for GNU Common Lisp, CVS snapshot Closes: 338613 342967 347560 358309 382247 Changes: gclcvs (2.7.0-55) unstable; urgency=low . * New cvs snapshot * new release Closes: #382247, Closes: #358309, Closes: #338613,Closes: #347560 * Try not depending on specific gcc, Closes: #342967. Files: 1afb7f8c951b47322b11c0b00f138bd1 734 interpreters optional gclcvs_2.7.0-55.dsc cf1aa25e7332c0b868115eb64a7ce1bb 23438989 interpreters optional gclcvs_2.7.0-55.tar.gz a7bce5442a71ef4ee55a528b84f0ae35 3365588 doc optional gclcvs-doc_2.7.0-55_all.deb f0bd5bb2b83d44485fc730a23bd2bf8f 49602556 interpreters optional gclcvs_2.7.0-55_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQFE9K4QczG1wFfwRdwRAjyUAJ9dKWe0x5SIc0e0Xuku2LHoNeHnKgCgu6+b KUGVxbReFhRA8cxRbbU9wfQ= =q3Dj -----END PGP SIGNATURE----- Accepted: gclcvs-doc_2.7.0-55_all.deb to pool/main/g/gclcvs/gclcvs-doc_2.7.0-55_all.deb gclcvs_2.7.0-55.dsc to pool/main/g/gclcvs/gclcvs_2.7.0-55.dsc gclcvs_2.7.0-55.tar.gz to pool/main/g/gclcvs/gclcvs_2.7.0-55.tar.gz gclcvs_2.7.0-55_i386.deb to pool/main/g/gclcvs/gclcvs_2.7.0-55_i386.deb From luca at pca.it Tue Aug 29 21:10:14 2006 From: luca at pca.it (Luca Capello) Date: Tue, 29 Aug 2006 23:10:14 +0200 Subject: [cl-debian] Bug#384697: cl-launch: need to modify script variables without touching the script In-Reply-To: <874pvz1lwf.fsf@gismo.pca.it> (Luca Capello's message of "Sat, 26 Aug 2006 18:50:40 +0200") References: <87u040483m.fsf@gismo.pca.it> <653bea160608252108u7378ef3m4444c328b5a02754@mail.gmail.com> <874pvz1lwf.fsf@gismo.pca.it> Message-ID: <877j0rs0y1.fsf@gismo.pca.it> Hello! On Sat, 26 Aug 2006 18:50:40 +0200, Luca Capello wrote: > ATM the patch is quite dirty, because it uses grep and the BASH > parameter substitution to assign the value, while the same function > should be very simple as: > > check_lisp_variable () { > test -r /etc/cl-launchrc && . /etc/cl-launchrc > test -r "$HOME/.cl-launchrc" && . "$HOME/.cl-launchrc" > test -n ${SOFTWARE_SYSTEM} && LISP=${SOFTWARE_SYSTEM} > } > > The last line is obviously fault, what I'd like to do is: It was quite simple, just putting two ! (and I'd like to thanks __dave at irc.freenode.net for his support). The attached patch is tested on cl-launch_1.85-1, but it's generated against cl-launch_1.86 as at [1]. Comments? Thx, bye, Gismo / Luca Footnotes: [1] http://fare.tunes.org/files/cl-launch/ -------------- next part -------------- A non-text attachment was scrubbed... Name: cl-launch.sh_add-cl-launchrc-support_gismo-20060829.patch Type: text/x-patch Size: 596 bytes Desc: add support for /etc/cl-launchrc and $HOME/.cl-launchrc URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: not available URL: From owner at bugs.debian.org Tue Aug 29 23:07:21 2006 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Tue, 29 Aug 2006 16:07:21 -0700 Subject: [cl-debian] Bug#358309: marked as done (FTBFS: error: request for member '_mp_a' in something not a structure or union) References: <20060322044506.GA6059@deprecation.cyrius.com> Message-ID: Your message dated Tue, 29 Aug 2006 15:02:42 -0700 with message-id and subject line Bug#358309: fixed in gclcvs 2.7.0-55 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: Martin Michlmayr Subject: FTBFS: undefined reference to 'init_gcl_cmpfun' Date: Wed, 22 Mar 2006 04:45:06 +0000 Size: 6957 URL: -------------- next part -------------- An embedded message was scrubbed... From: Camm Maguire Subject: Bug#358309: fixed in gclcvs 2.7.0-55 Date: Tue, 29 Aug 2006 15:02:42 -0700 Size: 3176 URL: From fahree at gmail.com Tue Aug 29 22:13:47 2006 From: fahree at gmail.com (=?UTF-8?Q? Far=C3=A9 ?=) Date: Tue, 29 Aug 2006 18:13:47 -0400 Subject: [cl-debian] Bug#384697: cl-launch: need to modify script variables without touching the script In-Reply-To: <877j0rs0y1.fsf@gismo.pca.it> References: <87u040483m.fsf@gismo.pca.it> <653bea160608252108u7378ef3m4444c328b5a02754@mail.gmail.com> <874pvz1lwf.fsf@gismo.pca.it> <877j0rs0y1.fsf@gismo.pca.it> Message-ID: <653bea160608291513t7cd02683i29f38d0d372baf45@mail.gmail.com> On 29/08/06, Luca Capello wrote: >> check_lisp_variable () { >> test -r /etc/cl-launchrc && . /etc/cl-launchrc >> test -r "$HOME/.cl-launchrc" && . "$HOME/.cl-launchrc" >> test -n ${SOFTWARE_SYSTEM} && LISP=${SOFTWARE_SYSTEM} >> } I have several issues with such a patch: (1) I took enough pain to get cl-launch running on a wide variety of shells (bash, zsh, posh, dash...) and I won't accept any bash-ism. Eval is OK. (2) since we're using eval I'd rather the variable be named LISP_stumpwm or something like that. (3) this patch just won't work when we're in --dump mode, since it very wrongly overrides the $LISP from the dumped image. A script generated with --dump should NOT read any kind of cl-launchrc. (4) If you hack cl-launch, you might want to run cl-launch -l "clisp sbcl cmucl gcl" -B tests from a temporary directory (complete with all installed and supported implementations). This will run the self-test. [ Fran?ois-Ren? ?VB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Amateurs talk strategy. Professionals talk logistics. - old military saying From owner at bugs.debian.org Tue Aug 29 23:07:08 2006 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Tue, 29 Aug 2006 16:07:08 -0700 Subject: [cl-debian] Bug#342967: marked as done (Package explicitely build-depends on g++-3.4) References: <200512112354.jBBNsUGu022906@bolero.cs.tu-berlin.de> Message-ID: Your message dated Tue, 29 Aug 2006 15:02:42 -0700 with message-id and subject line Bug#342967: fixed in gclcvs 2.7.0-55 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: Matthias Klose Subject: Package explicitely build-depends on g++-3.4 Date: Mon, 12 Dec 2005 00:54:30 +0100 (MET) Size: 2754 URL: -------------- next part -------------- An embedded message was scrubbed... From: Camm Maguire Subject: Bug#342967: fixed in gclcvs 2.7.0-55 Date: Tue, 29 Aug 2006 15:02:42 -0700 Size: 3201 URL: From luca at pca.it Tue Aug 29 21:24:01 2006 From: luca at pca.it (Luca Capello) Date: Tue, 29 Aug 2006 23:24:01 +0200 Subject: Bug#384071: [cl-debian] Bug#384071: stumpwm: Please update to a more recent cvs checkout References: <20060821180309.26966.43188.reportbug@zogzog.gnu-rox.org> <87y7tfa6r4.fsf@gismo.pca.it> <653bea160608230830l5bf1a90rc9ac826b1dfa5713@mail.gmail.com> <87zmdv6tdr.fsf@gismo.pca.it> <87u042i4sj.fsf@gismo.pca.it> Message-ID: <87zmdnqlqm.fsf@gismo.pca.it> Hello Xavier! On Thu, 24 Aug 2006 18:08:28 +0200, Xavier Maillard wrote: > From: Luca Capello >> As I already stated, IMHO we should provide both solutions, maybe >> triggered by a command-line option ? Far=C3=A9, what do you think >> about it? > > I am not against that idea. Maybe just adding this information into > README.Debian can be enough or just display something when installing > the Debian package ? This could be an idea, at least until bug #384697 [1] won't be solved. Moreover, this could be an improvement for bug #356948 [2]. > Oh and by the way, do you maintaint a Debian repository where we > could apt-get stumpwm "beta package" ? Actually no, but you can track the darcs repository at [3]. Thx, bye, Gismo / Luca Footnotes: [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384697 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=356948 [3] http://cl-debian.alioth.debian.org/repository/lcapello/stumpwm -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: not available URL: From owner at bugs.debian.org Tue Aug 29 23:07:06 2006 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Tue, 29 Aug 2006 16:07:06 -0700 Subject: [cl-debian] Bug#338613: marked as done (The clc-dumped image's name is wrong--a bug in gclcvs.sh) References: <4374B23F.8010009@gmail.com> Message-ID: Your message dated Tue, 29 Aug 2006 15:02:42 -0700 with message-id and subject line Bug#338613: fixed in gclcvs 2.7.0-55 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: "Chun Tian (binghe)" Subject: The clc-dumped image's name is wrong--a bug in gclcvs.sh Date: Fri, 11 Nov 2005 23:01:19 +0800 Size: 3584 URL: -------------- next part -------------- An embedded message was scrubbed... From: Camm Maguire Subject: Bug#338613: fixed in gclcvs 2.7.0-55 Date: Tue, 29 Aug 2006 15:02:42 -0700 Size: 3201 URL: From owner at bugs.debian.org Tue Aug 29 23:07:44 2006 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Tue, 29 Aug 2006 16:07:44 -0700 Subject: [cl-debian] Bug#382247: marked as done (gclcvs segfaults during c-l-c initialization) References: <20060809175753.7138.52653.reportbug@lux> Message-ID: Your message dated Tue, 29 Aug 2006 15:02:42 -0700 with message-id and subject line Bug#382247: fixed in gclcvs 2.7.0-55 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: Francois-Rene Rideau Subject: gclcvs segfaults during c-l-c initialization Date: Wed, 09 Aug 2006 13:57:53 -0400 Size: 6810 URL: -------------- next part -------------- An embedded message was scrubbed... From: Camm Maguire Subject: Bug#382247: fixed in gclcvs 2.7.0-55 Date: Tue, 29 Aug 2006 15:02:42 -0700 Size: 3201 URL: From owner at bugs.debian.org Tue Aug 29 23:07:14 2006 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Tue, 29 Aug 2006 16:07:14 -0700 Subject: [cl-debian] Bug#347560: marked as done (gclcvs: incorrect purge) References: <1136989947.3776.12.camel@note.consulting.net.nz> Message-ID: Your message dated Tue, 29 Aug 2006 15:02:42 -0700 with message-id and subject line Bug#347560: fixed in gclcvs 2.7.0-55 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: Adam Warner Subject: gclcvs: incorrect purge Date: Thu, 12 Jan 2006 03:32:27 +1300 Size: 2581 URL: -------------- next part -------------- An embedded message was scrubbed... From: Camm Maguire Subject: Bug#347560: fixed in gclcvs 2.7.0-55 Date: Tue, 29 Aug 2006 15:02:42 -0700 Size: 3201 URL: From fahree at gmail.com Tue Aug 29 23:38:30 2006 From: fahree at gmail.com (=?UTF-8?Q? Far=C3=A9 ?=) Date: Tue, 29 Aug 2006 19:38:30 -0400 Subject: [cl-debian] Bug#384697: cl-launch: need to modify script variables without touching the script In-Reply-To: <653bea160608291513t7cd02683i29f38d0d372baf45@mail.gmail.com> References: <87u040483m.fsf@gismo.pca.it> <653bea160608252108u7378ef3m4444c328b5a02754@mail.gmail.com> <874pvz1lwf.fsf@gismo.pca.it> <877j0rs0y1.fsf@gismo.pca.it> <653bea160608291513t7cd02683i29f38d0d372baf45@mail.gmail.com> Message-ID: <653bea160608291638n8ec9a17k4110c46be4310bfb@mail.gmail.com> Due to popular request, I am working on an optional /etc/cl-launchrc feature for cl-launch. Because I allow a --no-rc option (that is enabled by default for me, you can use --rc by default), the contents of these file will be read *after* the option processing. A cl-launchrc file may contain statements such as: system_preferred_lisps stumpwm cmucl sbcl clisp system_preferred_lisps exscribe clisp cmucl Then remains the question of whether or not the statements should override a user-specified --lisps option. My current feeling is "yes, but issue a warning on stderr". Also, the preferrence happens at script-creation time. At runtime, the variable $LISP is still all that matters -- should it not? [ Fran?ois-Ren? ?VB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Clairvoyant, n.: A person, commonly a woman, who has the power of seeing that which is invisible to her patron -- namely, that he is a blockhead. -- Ambrose Bierce From fahree at gmail.com Wed Aug 30 01:38:43 2006 From: fahree at gmail.com (=?UTF-8?Q? Far=C3=A9 ?=) Date: Tue, 29 Aug 2006 21:38:43 -0400 Subject: [cl-debian] Bug#384697: cl-launch: need to modify script variables without touching the script In-Reply-To: <653bea160608291638n8ec9a17k4110c46be4310bfb@mail.gmail.com> References: <87u040483m.fsf@gismo.pca.it> <653bea160608252108u7378ef3m4444c328b5a02754@mail.gmail.com> <874pvz1lwf.fsf@gismo.pca.it> <877j0rs0y1.fsf@gismo.pca.it> <653bea160608291513t7cd02683i29f38d0d372baf45@mail.gmail.com> <653bea160608291638n8ec9a17k4110c46be4310bfb@mail.gmail.com> Message-ID: <653bea160608291838v591cc74bn921d420f72a1eba3@mail.gmail.com> I put on my site a cl-launch 1.87 deb that I believe fixes 384697. Testers: Please test. Uploaders: please upload. [ Fran?ois-Ren? ?VB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] If Java had true garbage collection, most programs would delete themselves upon execution. -- Robert Sewell On 29/08/06, Far? wrote: > Due to popular request, I am working on an optional /etc/cl-launchrc > feature for cl-launch. > Because I allow a --no-rc option (that is enabled by default for me, > you can use --rc by default), the contents of these file will be read > *after* the option processing. > > A cl-launchrc file may contain statements such as: > system_preferred_lisps stumpwm cmucl sbcl clisp > system_preferred_lisps exscribe clisp cmucl > > Then remains the question of whether or not the statements should > override a user-specified --lisps option. My current feeling is "yes, > but issue a warning on stderr". > > Also, the preferrence happens at script-creation time. At runtime, the > variable $LISP is still all that matters -- should it not? > > [ Fran?ois-Ren? ?VB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] > Clairvoyant, n.: > A person, commonly a woman, who has the power of seeing that > which is invisible to her patron -- namely, that he is a blockhead. > -- Ambrose Bierce From camm at enhanced.com Wed Aug 30 17:47:37 2006 From: camm at enhanced.com (Camm Maguire) Date: Wed, 30 Aug 2006 10:47:37 -0700 Subject: [cl-debian] Accepted gcl 2.6.7-19 (source i386 all) Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Wed, 30 Aug 2006 12:13:46 -0400 Source: gcl Binary: gcl-doc gcl Architecture: source i386 all Version: 2.6.7-19 Distribution: unstable Urgency: low Maintainer: Camm Maguire Changed-By: Camm Maguire Description: gcl - GNU Common Lisp compiler gcl-doc - Documentation for GNU Common Lisp Closes: 376806 385126 385176 Changes: gcl (2.6.7-19) unstable; urgency=low . * xgcl upgrade * parse_number from cvs head with *read-base* fixes * fix object_to_string * install xgcl-2/sysdef.lisp * fix info dir and emacs site lisp dir installation * New xgcl readme * Remove bashism from debian/rules, Closes: #376806, Closes: #385176. * Fix dwdoc doc-base error, Closes: #385126 Files: 46c87a3636575468cb0e29ddc9785a25 730 interpreters optional gcl_2.6.7-19.dsc 7eab9ae87e72e895f7576ff547172219 14454630 interpreters optional gcl_2.6.7-19.diff.gz 5cc18a8ca4cf56d9e6cad51ef40420a3 765938 doc optional gcl-doc_2.6.7-19_all.deb bf24989f8b3dda32e70d8c8e421f1173 28807156 interpreters optional gcl_2.6.7-19_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQFE9ceBczG1wFfwRdwRAvaEAJ40WAXKYQqcTRG4yj7x2jG78xE6NgCcDQ+F jZ1K8F8/Dozltoa05wVe5vQ= =dntv -----END PGP SIGNATURE----- Accepted: gcl-doc_2.6.7-19_all.deb to pool/main/g/gcl/gcl-doc_2.6.7-19_all.deb gcl_2.6.7-19.diff.gz to pool/main/g/gcl/gcl_2.6.7-19.diff.gz gcl_2.6.7-19.dsc to pool/main/g/gcl/gcl_2.6.7-19.dsc gcl_2.6.7-19_i386.deb to pool/main/g/gcl/gcl_2.6.7-19_i386.deb From owner at bugs.debian.org Wed Aug 30 18:05:06 2006 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Wed, 30 Aug 2006 11:05:06 -0700 Subject: [cl-debian] Bug#385126: marked as done (warning: file `/usr/share/doc/gcl-doc/dwdoc/index.html' does not exist at /usr/sbin/install-docs line 718, line 15.) References: <20060829101131.GA6649@aragorn> Message-ID: Your message dated Wed, 30 Aug 2006 10:47:37 -0700 with message-id and subject line Bug#385126: fixed in gcl 2.6.7-19 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: Uwe Hermann Subject: warning: file `/usr/share/doc/gcl-doc/dwdoc/index.html' does not exist at /usr/sbin/install-docs line 718, line 15. Date: Tue, 29 Aug 2006 12:11:31 +0200 Size: 2574 URL: -------------- next part -------------- An embedded message was scrubbed... From: Camm Maguire Subject: Bug#385126: fixed in gcl 2.6.7-19 Date: Wed, 30 Aug 2006 10:47:37 -0700 Size: 3254 URL: From owner at bugs.debian.org Wed Aug 30 18:05:02 2006 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Wed, 30 Aug 2006 11:05:02 -0700 Subject: [cl-debian] Bug#376806: marked as done (gcl: FTBFS: bashisms in debian/rules) References: <20060705080634.GJ24203@abydos.adm.naquadah.org> Message-ID: Your message dated Wed, 30 Aug 2006 10:47:37 -0700 with message-id and subject line Bug#376806: fixed in gcl 2.6.7-19 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: Julien Danjou Subject: gcl: FTBFS: bashisms in debian/rules Date: Wed, 5 Jul 2006 10:06:34 +0200 Size: 2982 URL: -------------- next part -------------- An embedded message was scrubbed... From: Camm Maguire Subject: Bug#376806: fixed in gcl 2.6.7-19 Date: Wed, 30 Aug 2006 10:47:37 -0700 Size: 3254 URL: From owner at bugs.debian.org Wed Aug 30 18:05:10 2006 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Wed, 30 Aug 2006 11:05:10 -0700 Subject: [cl-debian] Bug#385176: marked as done (gcl: FTBFS: bashisms in build scripts) References: <200608291749.13930.florent@sarcelle.net> Message-ID: Your message dated Wed, 30 Aug 2006 10:47:37 -0700 with message-id and subject line Bug#385176: fixed in gcl 2.6.7-19 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: Florent Bayle Subject: gcl: FTBFS: bashisms in build scripts Date: Tue, 29 Aug 2006 17:49:08 +0200 Size: 2532 URL: -------------- next part -------------- An embedded message was scrubbed... From: Camm Maguire Subject: Bug#385176: fixed in gcl 2.6.7-19 Date: Wed, 30 Aug 2006 10:47:37 -0700 Size: 3229 URL: From edi at agharta.de Wed Aug 30 22:35:13 2006 From: edi at agharta.de (Edi Weitz) Date: Thu, 31 Aug 2006 00:35:13 +0200 Subject: [cl-debian] [ann] [tbnl-announce] New versions 0.10.1 (TBNL) and 0.2.2 (Hunchentoot) Message-ID: TBNL: ----- ChangeLog: Version 0.10.1 2006-08-31 Only LispWorks: Set read timeout to NIL if connected to mod_lisp Download: http://weitz.de/files/tbnl.tar.gz Hunchentoot: ------------ ChangeLog: Version 0.2.2 2006-08-31 Skip START-OUTPUT advice completely if working for TBNL Version 0.2.1 2006-08-28 Added write timeouts for LW 5.0 Updated LW links in documentation Download: http://weitz.de/files/hunchentoot.tar.gz Cheers, 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 kmr at debian.org Wed Aug 30 23:32:04 2006 From: kmr at debian.org (Kevin M. Rosenberg) Date: Wed, 30 Aug 2006 16:32:04 -0700 Subject: [cl-debian] Accepted cl-sql 3.7.0-1 (source all i386) Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Wed, 30 Aug 2006 04:03:18 -0600 Source: cl-sql Binary: cl-sql-sqlite3 cl-sql-oracle cl-sql-aodbc cl-sql-postgresql-socket cl-sql-postgresql cl-sql-odbc cl-sql cl-sql-uffi cl-sql-tests cl-sql-sqlite cl-sql-mysql Architecture: source all i386 Version: 3.7.0-1 Distribution: unstable Urgency: low Maintainer: Kevin M. Rosenberg Changed-By: Kevin M. Rosenberg Description: cl-sql - SQL Interface for Common Lisp cl-sql-aodbc - CLSQL database backend, AODBC cl-sql-mysql - CLSQL database backend, MySQL cl-sql-odbc - CLSQL database backend, ODBC cl-sql-oracle - CLSQL database backend, Oracle cl-sql-postgresql - CLSQL database backend, PostgreSQL cl-sql-postgresql-socket - CLSQL database backend, PostgreSQL cl-sql-sqlite - CLSQL database backend, SQLite cl-sql-sqlite3 - CLSQL database backend, SQLite3 cl-sql-tests - Testing suite for CLSQL cl-sql-uffi - Common UFFI functions for CLSQL database backends Changes: cl-sql (3.7.0-1) unstable; urgency=low . * New upstream Files: fd0770da4b7cd2f184a6878623c3666e 796 devel extra cl-sql_3.7.0-1.dsc 516b465bebef0512f7280ceafce0f07a 736284 devel extra cl-sql_3.7.0.orig.tar.gz 9a0871c5123078921d80b7934b987c87 11554 devel extra cl-sql_3.7.0-1.diff.gz 886db09d26c8d0c930f5dcdbc35184ae 522588 devel extra cl-sql_3.7.0-1_all.deb 12e008e34f9b926027fcdbca7036695a 38134 devel extra cl-sql-aodbc_3.7.0-1_all.deb 62d235ffacbee704ac05c2f47899a505 64796 devel extra cl-sql-odbc_3.7.0-1_all.deb d8c8c4607e561a4d215e68d972c79e7c 42810 devel extra cl-sql-postgresql_3.7.0-1_all.deb c74f4eb82cb9c24b60da859e6bb473d8 46924 devel extra cl-sql-postgresql-socket_3.7.0-1_all.deb 1d848cfdd4c5f21a28fbf3b8677dee8f 42680 devel extra cl-sql-sqlite_3.7.0-1_all.deb c06b048fd8ac208607e3799a8c3eea83 43446 devel extra cl-sql-sqlite3_3.7.0-1_all.deb b60d875d7f9678e204c046c6d35731e4 59118 contrib/devel extra cl-sql-oracle_3.7.0-1_all.deb fd3c70c4936ffcbaccffea7778e07ebd 61504 devel extra cl-sql-tests_3.7.0-1_all.deb 3f23f91c5f499095235297eacd52f141 41534 devel extra cl-sql-uffi_3.7.0-1_i386.deb 5e7fe976277dd156341a84e86ac33b24 51816 devel extra cl-sql-mysql_3.7.0-1_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE9hyiES7N8sSjgj4RAgtxAJ49A83RCSgHbUUjnw4EaY07lxCmpgCghD74 6Sze9R+1nBOl5xsHVcxdA6o= =vvTf -----END PGP SIGNATURE----- Accepted: cl-sql-aodbc_3.7.0-1_all.deb to pool/main/c/cl-sql/cl-sql-aodbc_3.7.0-1_all.deb cl-sql-mysql_3.7.0-1_i386.deb to pool/main/c/cl-sql/cl-sql-mysql_3.7.0-1_i386.deb cl-sql-odbc_3.7.0-1_all.deb to pool/main/c/cl-sql/cl-sql-odbc_3.7.0-1_all.deb cl-sql-oracle_3.7.0-1_all.deb to pool/contrib/c/cl-sql/cl-sql-oracle_3.7.0-1_all.deb cl-sql-postgresql-socket_3.7.0-1_all.deb to pool/main/c/cl-sql/cl-sql-postgresql-socket_3.7.0-1_all.deb cl-sql-postgresql_3.7.0-1_all.deb to pool/main/c/cl-sql/cl-sql-postgresql_3.7.0-1_all.deb cl-sql-sqlite3_3.7.0-1_all.deb to pool/main/c/cl-sql/cl-sql-sqlite3_3.7.0-1_all.deb cl-sql-sqlite_3.7.0-1_all.deb to pool/main/c/cl-sql/cl-sql-sqlite_3.7.0-1_all.deb cl-sql-tests_3.7.0-1_all.deb to pool/main/c/cl-sql/cl-sql-tests_3.7.0-1_all.deb cl-sql-uffi_3.7.0-1_i386.deb to pool/main/c/cl-sql/cl-sql-uffi_3.7.0-1_i386.deb cl-sql_3.7.0-1.diff.gz to pool/main/c/cl-sql/cl-sql_3.7.0-1.diff.gz cl-sql_3.7.0-1.dsc to pool/main/c/cl-sql/cl-sql_3.7.0-1.dsc cl-sql_3.7.0-1_all.deb to pool/main/c/cl-sql/cl-sql_3.7.0-1_all.deb cl-sql_3.7.0.orig.tar.gz to pool/main/c/cl-sql/cl-sql_3.7.0.orig.tar.gz From robin at debian.org Thu Aug 31 07:08:36 2006 From: robin at debian.org (Robin) Date: Thu, 31 Aug 2006 12:08:36 +0500 Subject: [cl-debian] Bug#385490: [wishlist] FFI module should be made to work on more architectures Message-ID: <20060831070836.GB7423@robin-laptop> Package: clisp Version: 1:2.33.2-10 The FFI module is no longer being built on a wide number of architectures; for some architectures this is a regression. The mcvs package actually relies on the FFI module and consequently fails to build from source on all of these platforms. As per earlier conversations with the clisp maintainer, we have decided to file a wishlist bug against clisp to capture the request for FFI. It is understood that not all architectures are as widely-used as before anymore and it may be hard to get the brainpower together to take a look at some of these architectures and do the work necessary to make FFI buildable and working again. The architectures were FFI built before but where it is no longer working are: ia64, mipsel, s390 and sparc. -- From camm at enhanced.com Thu Aug 31 21:48:04 2006 From: camm at enhanced.com (Camm Maguire) Date: Thu, 31 Aug 2006 14:48:04 -0700 Subject: [cl-debian] Accepted gcl 2.6.7-20 (source i386 all) Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Thu, 31 Aug 2006 15:14:18 -0400 Source: gcl Binary: gcl-doc gcl Architecture: source i386 all Version: 2.6.7-20 Distribution: unstable Urgency: low Maintainer: Camm Maguire Changed-By: Camm Maguire Description: gcl - GNU Common Lisp compiler gcl-doc - Documentation for GNU Common Lisp Changes: gcl (2.6.7-20) unstable; urgency=low . * fix ia64 build Files: 65069288fa7db736a9dcdbe49cf3901c 730 interpreters optional gcl_2.6.7-20.dsc 1a00542bf831ec18b75a61cee32c8521 14454782 interpreters optional gcl_2.6.7-20.diff.gz f49ec49912838ee5c04f025d2e84657c 765974 doc optional gcl-doc_2.6.7-20_all.deb 1db74d8d9155471c089ff7f2021526cf 29159616 interpreters optional gcl_2.6.7-20_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQFE90x5czG1wFfwRdwRAm4kAKDBmmCfThOy7pHJUEXkilktOxqTzwCfWLMb ylM7NahIBChfUWtUF0HqzFg= =Z6KY -----END PGP SIGNATURE----- Accepted: gcl-doc_2.6.7-20_all.deb to pool/main/g/gcl/gcl-doc_2.6.7-20_all.deb gcl_2.6.7-20.diff.gz to pool/main/g/gcl/gcl_2.6.7-20.diff.gz gcl_2.6.7-20.dsc to pool/main/g/gcl/gcl_2.6.7-20.dsc gcl_2.6.7-20_i386.deb to pool/main/g/gcl/gcl_2.6.7-20_i386.deb From eenge at common-lisp.net Mon Aug 14 14:20:04 2006 From: eenge at common-lisp.net (Erik Enge) Date: Mon, 14 Aug 2006 14:20:04 -0000 Subject: [cl-debian] [ann] [clhp-announce] Last chance: move your files off of common-lisp.net FTP, please. Message-ID: <20060814141930.C0F8B5E0C7@common-lisp.net> See http://common-lisp.net/pipermail/users/2006-August/000006.html for more information. Thanks. _______________________________________________ clhp-announce site list clhp-announce at common-lisp.net http://common-lisp.net/mailman/listinfo/clhp-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements