- cl-debian@lists.common-lisp.net - mailman3.common-lisp.net

[cl-debian] cl-asdf 1.99-3 MIGRATED to testing
by Debian testing watch 05 Aug '06

05 Aug '06

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(a)makholm.net is responsible. See http://people.debian.org/~henning/trille/ for more information.

1 0

[cl-debian] cltl 1.0.20 MIGRATED to testing
by Debian testing watch 05 Aug '06

05 Aug '06

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(a)makholm.net is responsible. See http://people.debian.org/~henning/trille/ for more information.

1 0

[cl-debian] Bug#381375: [INTL:pt] Portuguese translation for common-lisp-controller (debconf)
by Rui Branco 04 Aug '06

04 Aug '06

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 <ardoric _at_ gmail.com>. Feel free to use it. For translation updated please contact Ricardo Silva and CC the Portuguese translation team <traduz _at_ debianpt.org> # Portuguese translation for common-lisp-controller debconf messages. # This file is distributed under the same license as the common-lisp-controller package. # Ricardo Silva <ardoric(a)gmail.com>, 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 <ardoric(a)gmail.com>\n" "Language-Team: Native Portuguese <traduz(a)debianpt.org>\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."

1 0

[cl-debian] Bug#368271: No clsql_uffi64.so on amd64, but clsql_uffi.so instead.
by Chun Tian (binghe) 03 Aug '06

03 Aug '06

Package: cl-sql-uffi Version: 3.6.1-1 This bug made me cannot use cl-sql-postgresql correctly. In clsql-uffi-loader.lisp file (in cl-sql-uffi package): (defvar *clsql-uffi-library-filenames* (list #+(or 64bit x86-64) "clsql_uffi64" "clsql_uffi")) It seems that on amd64 it'll load library "clsql_uffi64.so" instead of "clsql_uffi.so", but there's no "clsql_uffi64.so" existed at /usr/lib/clsql or any other directory! So I think this is a trivial bug, should be fixed easily. Thanks very much. Package: cl-sql-uffi Priority: extra Section: devel Installed-Size: 136 Maintainer: Kevin M. Rosenberg <kmr(a)debian.org> Architecture: amd64 Source: cl-sql Version: 3.6.1-1 Depends: cl-uffi (>= 1.5.11), cl-sql (>= 3.6.1-1), libc6 (>= 2.3.5-1) Recommends: cl-sql-backend Filename: pool/main/c/cl-sql/cl-sql-uffi_3.6.1-1_amd64.deb Size: 40316 MD5sum: 6b1b4f56a7a263670dae60a9babb31f0 Description: Common UFFI functions for CLSQL database backends This package provides an interface to several UFFI functions used by multiple CLSQL database backends. CLSQL is a Common Lisp interface to SQL databases. Tag: devel::library, langdevel::lisp, made-of::lang:lisp, works-with::db:sql

2 1

[cl-debian] Re: Using Darcs for Debian package maintenance
by Peter Van Eynde 02 Aug '06

02 Aug '06

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 <foo>-upstream, do a 'get' into a <foo> repository, and do my debian stuff in that <foo> directory. When upstream releases a new version I pull/import this into the <foo>-upstream repository and then pull this into the <foo> 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|

1 0

[cl-debian] Processed: severity of 365230 is serious
by owner＠bugs.debian.org 02 Aug '06

02 Aug '06

Processing commands for control(a)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)

1 0

[cl-debian] Re: [Bese-devel] error starting with ucwctl - problem with cl-launch?
by Luca Capello 01 Aug '06

01 Aug '06

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

1 0

[cl-debian] Bug#270876: FFI is now available again for mips/mipsel
by Thiemo Seufer 30 Jul '06

30 Jul '06

retitle 270876 clisp: FFI not available on arm hppa m68k s390 thanks

1 0

[cl-debian] Bug#362808: clisp still FTBFS on Sparc
by René van Bevern 29 Jul '06

29 Jul '06

found 362808 1:2.39-1 thanks Gna. :-( ----- ;; Loading file clos-class3.lisp ... *** - ALLOCATE-METAOBJECT-INSTANCE: length OOOOOOOO0OOOOOOOO0OOOOOOOO should be of type (INTEGER (0) (OOOOOOOO0OOOOOOOO0OOOOOOOO0OOOOOOOO0OOOOOOOO0OOOOOOOO)) Bye. ----- René -- René van Bevern <rvb(a)debian.org> http://progn.org http://www.debian.org http://www.pro-linux.de Heap exhausted, game over. -- Steel Bank Common Lisp's Garbage Collector running out of memory

2 1

[cl-debian] Bug#365106: xmls bombs on sbcl unicode strings when parsing entities
by Daniel Lakeland 28 Jul '06

28 Jul '06

Package: cl-xmls Version: 1.2-1 " in an xml file I was trying to parse caused SBCL to bomb complaining that """ is not a simple base string. The solution is probably to tell read-stream to coerce ent to 'simple-base-string instead of 'simple-string -- Daniel Lakeland dlakelan(a)street-artists.org http://www.street-artists.org/~dlakelan

2 1