October 2005 - cl-debian@common-lisp.net - mailman3.common-lisp.net

[cl-debian] Bug#330468: sbcl: Can't start sbcl with kernel 2.4.27-2-686
by Didier Verna 28 Jun '07

28 Jun '07

Package: sbcl Version: 1:0.9.4.65-1 Severity: grave Hi ! When I try to launch SBCL, I get the following message: ,---- | fatal error encountered in SBCL pid 10204(tid 16384): | This version of sbcl is compiled with threading support, but your kernel is | too old to support this. Please use a more recent kernel or a version of sbcl | without threading support. `----- ... which I consider a bug since the Debian package installed just fine, and there don't seem to be an alternative sbcl package usable for me. I don't want to use a 2.6 kernel on my machine. So what should I do ? Thanks ! -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.27-2-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages sbcl depends on: ii common-lisp-controller 4.18 This is a Common Lisp source and c ii libc6 2.3.5-6 GNU C Library: Shared libraries an ii sbcl-common 1:0.9.4.65-1 Architecture independent files for Versions of packages sbcl recommends: ii binfmt-support 1.2.6 Support for extra binary formats -- no debconf information

4 4

[cl-debian] Bug#323274: wishlist: packaging of SBCL sources; recording of source-definitions for lisp forms
by Sean Champ 08 Jul '06

08 Jul '06

Package: sbcl Version: 1:0.9.3.0-2 Severity: wishlist [*] Introduction Today, I was trying to use SLIME's `slime-edit-definition', in order to learn a bit more about what is defined in SBCL. However, on a number of forms, when I tried to view their definitions, SBCL produced messages like Error: Source filename not recorded for ... That was so, on (DEFGENERIC STREAM-LINE-COLUMN) (METHOD STREAM-LINE-COLUMN (FUNDAMENTAL-CHARACTER-OUTPUT-STREAM)) Yet, for (METHOD STREAM-LINE-COLUMN (SWANK-BACKEND::SLIME-OUTPUT-STREAM)) SBCL is able to determine where that method is defined -- presumably, given that the sources for that method's definition are available on the local system, and given that the code would have been compiled with an DEBUG OPTIMIZE of quality 2 or greater [incidental ref: SBCL manual, Source Location Availability], and given the nature of it, a method definition, such that the source location would be recoded, for it. [*] The Request I do not mean to ask overmuch, but if there would be an opportunity that the SBCL sources would be made available in a Debian package, and if SBCL -- in its availability with Debian -- would be available as being compiled, with such an OPTIMIZE DEBUG proclamation that SBCL would record the source defintions of appropriate forms, then I am sure it would be of help, for many users of SBCL (at the very least, for our becoming acquainted with the SBCL source-code) Though I realize that I may try to address this request, directly upon the Debian source package for SBCL, yet it might take me some while, as to produce anything useful of it. Also, I would only be able to address it for x86 architectures. Regardless, I have thought that this should be addressed as a wishlist item, about the Debian SBCL release. While I realize that it would probably result in some change in the performance of SBCL, if it would be compiled with such a DEBUG quality as would be needed for it to record source locations, yet it may be of use, to who would intend to see the definition of a form, within the SBCL sources. As such, it may be of help, towards the continuing development of SBCL. [*] Addressing Attendant Concerns If it would serve to ease any concern about performance, then to have the matter brought to any reader's attention: Anyone might derive a package for a particularly optimized SBCL, deriving the package upon the Debian SBCL packages -- editing the debian/* files, as to adapt the commands for the compilation, and to adjust package-names, in order to avoid naming conflicts -- then, of course, running debuild and/or any more of the pacakge-buiding tools. Hopefully, such would not result in a bewildering array of SBCL packags, but hey, "what can one say". Thank you. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.11.8 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages sbcl depends on: ii common-lisp-controller 4.12 This is a Common Lisp source and c ii libc6 2.3.5-3 GNU C Library: Shared libraries an ii sbcl-common 1:0.8.21.16-2 Architecture independent files for -- debconf information excluded

2 1

[cl-debian] cl-launch
by Faré 09 Nov '05

09 Nov '05

Because I very much want cl-launch to be more widely used, I've packaged it for debian myself. I'd upload it or whatever, if only I knew how to do that. This is my first attempt at building a debian package, so please tell me what I did wrong, if anything. The URL with everything is http://fare.tunes.org/files/debian/ [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Brevity is the soul of wit. -- Shakespeare

2 4

[cl-debian] [PATCH] Make S-XML a Debian native package
by Luca Capello 06 Nov '05

06 Nov '05

Hello all! I'm sorry for the cross-posting, but this mail concerns both mailing-lists. I'm using S-XML since I debianized it and it works with no particular problem. I can say the same for some friends of mine that install from my Debian package (which is no more publicly available as it should enter Debian official soon, but if someone wants to test it, just drop me a mail). Now, after some discussions in the Debian world about the differents CL packages [1], I'm here to propose a patch that make S-XML a Debian native package. The patch is simply the debian/ folder, which is necessary and sufficient to build a Debian package. Comments or suggestions? Thx, bye, Gismo / Luca [1] http://common-lisp.net/pipermail/cl-debian/2005-March/000000.html

3 7

[cl-debian] ironclad, tbnl, url-rewrite: updates and questions
by Alceste Scalas 06 Nov '05

06 Nov '05

Hello, a few updates on the three packages I'm providing (sorry for the late, due to a *very* annoying hard disk crash). Ironclad: * accepted in main; * got the first bug: #335868. Yayyyy! * fixed the bug; * updated the package to the latest upstream release. TBNL: * rejected by ftp-master, due to debian/copyright issues; * fixed the bug; * updated the package to the latest upstream release. URL-REWRITE: * rejected by ftp-master, due to debian/copyright issues; * fixed the bug. My darcs repositories (managed with darcs-buildpackage) are available at the usual location: http://debian.muvara.org/darcs/debs (.deb sources) http://debian.muvara.org/darcs/upstream/ (upstream repos) And now, a few questions... 1. I've noticed that bug reports and ftp-master responses for other cl-debian packages are being sent to this mailing list, too. Is there a way to automate the process for my packages? 2. How should I notify when my repositories have got interesting updates? Is email pestering (like this one) ok? 3. Have you got a procedure for signing the patches being recorded on darcs? (I've used one for Mercurial[1], that *should* be adaptable to darcs); 4. Should a copy of my repositories go under http://cl-debian.alioth.debian.org/ ? If yes, is there anything I should do? Of course, you can point me to any fine manual that I should have read before asking :-) Regards, aleste - - - - References: [1] Mercurial distributed SCM: http://selenic.com/mercurial/ -- Alceste Scalas <alceste(a)muvara.org>

2 2

[cl-debian] Re: [Bese-devel] YACLML: debianization
by Luca Capello 03 Nov '05

03 Nov '05

Hello! I'm sorry for the cross-posting, but the CL-Debian mailing-list is the best place about packaging CL software for Debian. Moreover, I'd like an advice from the Debian people involved in CL before finishing to package Marco's software. And I'm sorry for the long post O:-) On Thu 27 Oct 2005 10:39 +0200, Marco Baringer wrote: > Luca Capello <luca(a)pca.it> writes: > >> 1) Referring to [1], YACLML *depends* on FiveAM if you want to use >> the test suite. So, if we want a single Debian package from >> YACLML, we need to depend on FiveAM. And AFAIK the same happens >> for the documentation, which needs qbook. >> >> The other possibility is to have multiple Debian packages, if >> it's possible (I propend for this one): >> >> cl-yaclml = all the strictly necessary files >> (depends on ASDF, arnesi and iterate, >> suggests cl-yaclml-test and cl-yaclml-doc) >> cl-yaclml-test = test suite >> (depends on cl-yaclml and FiveAM, >> suggests cl-yaclml-doc) >> cl-yaclml-doc = documentation >> (depends on cl-yaclml and qbook, >> suggests cl-yaclml-test) > > is this a normal way of doing things? if so this is what i'd do. While it's an usual thing to split a -doc package, I think that for the test suite there isn't a strict policy. Searching in the package archive gives the following. I sorted out the relevant packages ;-) ===== luca@gismo:~$ apt-cache search test atlas-test - Automatically Tuned Linear Algebra Software,test programs blacs-pvm-test - Basic Linear Algebra Comm. Subprograms - Test files for PVM blas-test - Basic Linear Algebra Subroutines, testing programs lapack-test - a library of linear algebra routines - testing programs lapack3-test - library of linear algebra routines 3 - testing programs refblas3-test - Basic Linear Algebra Subroutines 3, testing programs ultrapossum-test - UltraPossum SI Testing Framework xmldiff-test - xmldiff's test files blacs-lam-test - Basic Linear Algebra Comm. Subprograms - Test files for LAM blacs-mpich-test - Basic Linear Algebra Comm. Subprograms - Test files for MPICH blacs-test-common - Test data for BLACS testers cl-ansi-tests - Conformance tests for ANSI Common Lisp cl-uffi-tests - Regression tests for UFFI Common Lisp Library clamav-testfiles - use these files to test that your Antivirus program works ltp-commands-test - Command tests for the Linux Test Project ltp-disc-test - Disk I/O tests for the Linux Test Project ltp-kernel-test - kernel tests for the Linux Test Project ltp-misc-test - Misc. tests for the Linux Test Project ltp-network-test - Network tests for the Linux Test Project pylint-test - pylint's test files scalapack-lam-test - Scalable Linear Algebra Package - Test files for LAM scalapack-mpich-test - Scalable Linear Algebra Package - Test files for MPICH scalapack-pvm-test - Scalable Linear Algebra Package - Test files for PVM scalapack-test-common - Test data for ScaLAPACK testers typo3-testsite - A site package to show the abilities of TYPO3 zope-testcase - unit testing framework and test case for Zope parmetis-test - Parallel Graph Partitioning and Sparse Matrix Ordering Tests atlas3-test - Automatically Tuned Linear Algebra Software,test programs axiom-test - A general purpose computer algebra system: regression test inputs cl-sql-tests - Testing suite for CLSQL maxima-test - A fairly complete computer algebra system-- test suite php-simpletest - Unit testing and web testing framework for PHP sqlrelay-test - SQL Relay tests webauth-tests - Tests for the WebAuth authentication modules luca@gismo:~$ ===== Basically and AFAIK, we can decide whatever we want. Considering the space occupied by each package, we have (I just removed _darcs/ folder in each package): ===== luca@gismo:~/Hacking/cl-debian/repository$ du -h arnesi-test/ 16K arnesi-test/docs 68K arnesi-test/src/call-cc 312K arnesi-test/src 48K arnesi-test/t 396K arnesi-test/ luca@gismo:~/Hacking/cl-debian/repository$ du -h fiveam-test/ 68K fiveam-test/src 16K fiveam-test/t 104K fiveam-test/ luca@gismo:~/Hacking/cl-debian/repository$ du -h qbook-test/ 44K qbook-test/src 60K qbook-test/ luca@gismo:~/Hacking/cl-debian/repository$ du -h yaclml-test/ 24K yaclml-test/src/tags 64K yaclml-test/src/tal 128K yaclml-test/src 8.0K yaclml-test/t/root-a 12K yaclml-test/t/root-b 52K yaclml-test/t 196K yaclml-test/ luca@gismo:~/Hacking/cl-debian/repository$ ===== The simple solution will be to strictly depend on every software needed to *completely* use the package we're installing. So, YACLML should depends on ASDF/Common-Lisp-Controller, arnesi and iterate (to compile), plus FiveAM (for the test suite) and qbook (for the docs). This will lead to about 170K more space on disk (FiveAM and qbook), which is quite nothing :-) Obviously, if the dependencies for the /extra/ packages will grow in size (the test suite and the docs are not *strictly* necessary), we can split the package in the future. Now, reconsidering what I just wrote, I think that the simple solution is the best ATM. Suggestions? Peter, your opinion? Thx, bye, Gismo / Luca

2 3

[cl-debian] Accepted sbcl 1:0.9.6.0-2 (source i386 all)
by Peter Van Eynde 31 Oct '05

31 Oct '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Mon, 31 Oct 2005 07:51:51 +0100 Source: sbcl Binary: sbcl sbcl-common Architecture: source i386 all Version: 1:0.9.6.0-2 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde <pvaneynd(a)debian.org> Changed-By: Peter Van Eynde <pvaneynd(a)debian.org> Description: sbcl - A development environment for Common Lisp sbcl-common - Architecture independent files for SBCL Changes: sbcl (1:0.9.6.0-2) unstable; urgency=low . * move locale stuff later in the debian/rules file, as to avoid perl warnings. * use the current gcc for compilation, it should 'just work' Files: b89b38498405385c0b854de533a0a6a5 669 devel optional sbcl_0.9.6.0-2.dsc ca958206def9d77d918c776b9e8f4b44 20273 devel optional sbcl_0.9.6.0-2.diff.gz f0deba2331a59b2664238051524d4eb0 3968524 devel optional sbcl-common_0.9.6.0-2_all.deb 4e1d719ffa2df15d67a67068a5a20320 9141498 devel optional sbcl_0.9.6.0-2_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDZnAP11ldN0tyliURAo/XAKC9MQ7aQwUOXYHXmXJ9sW5gpJoXVACgnXry lsgKpCYJos3RAVV0I6Gv8Jk= =e8+y -----END PGP SIGNATURE----- Accepted: sbcl-common_0.9.6.0-2_all.deb to pool/main/s/sbcl/sbcl-common_0.9.6.0-2_all.deb sbcl_0.9.6.0-2.diff.gz to pool/main/s/sbcl/sbcl_0.9.6.0-2.diff.gz sbcl_0.9.6.0-2.dsc to pool/main/s/sbcl/sbcl_0.9.6.0-2.dsc sbcl_0.9.6.0-2_i386.deb to pool/main/s/sbcl/sbcl_0.9.6.0-2_i386.deb

1 0

[cl-debian] Accepted cl-sql 3.3.3-1 (source all i386)
by kmr＠debian.org 31 Oct '05

31 Oct '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Sun, 30 Oct 2005 21:20:34 -0700 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.3.3-1 Distribution: unstable Urgency: low Maintainer: Kevin M. Rosenberg <kmr(a)debian.org> Changed-By: Kevin M. Rosenberg <kmr(a)debian.org> 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.3.3-1) unstable; urgency=low . * New upstream Files: 3740d6bd253a8aeea6c452efb7ab71ea 796 devel extra cl-sql_3.3.3-1.dsc 60104720e54f61c23cf53b9aaf7e0f8b 701247 devel extra cl-sql_3.3.3.orig.tar.gz 662cda6c474ed7cbf9c13349f7716ed0 10931 devel extra cl-sql_3.3.3-1.diff.gz b69fa702cdee2f9c65fdc103761bf8c9 489242 devel extra cl-sql_3.3.3-1_all.deb 9402cfb1d34176b2e7c664e833b0b18b 35214 devel extra cl-sql-aodbc_3.3.3-1_all.deb ee4b5b14a64652fdc278cd5805b5defc 61166 devel extra cl-sql-odbc_3.3.3-1_all.deb 5d95a44caa99620eb493ddc57d08b626 39984 devel extra cl-sql-postgresql_3.3.3-1_all.deb c9ea6d1579c67e2e66c3e962920bb542 44118 devel extra cl-sql-postgresql-socket_3.3.3-1_all.deb 2307163fc3dcb3c734f5c9db287b1161 39822 devel extra cl-sql-sqlite_3.3.3-1_all.deb d7f98741367be64717978815ced0c8be 40630 devel extra cl-sql-sqlite3_3.3.3-1_all.deb 9abbf600fd52871b679d83b3a7b8f936 56222 contrib/devel extra cl-sql-oracle_3.3.3-1_all.deb 56af9f341d8fe5a56550bd2ca9495104 58452 devel extra cl-sql-tests_3.3.3-1_all.deb 665481190f86cd6a7951ad3ea546308a 38642 devel extra cl-sql-uffi_3.3.3-1_i386.deb 3b3e1629fe9f1cd594304fd4a73eec3e 48950 devel extra cl-sql-mysql_3.3.3-1_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDZaFnES7N8sSjgj4RAsVLAJsGx4flYLxmnPbyqHb4mYivXbd32wCeI1T6 O2iSvWEAaInYmyGL0nNuXhU= =2PCq -----END PGP SIGNATURE----- Accepted: cl-sql-aodbc_3.3.3-1_all.deb to pool/main/c/cl-sql/cl-sql-aodbc_3.3.3-1_all.deb cl-sql-mysql_3.3.3-1_i386.deb to pool/main/c/cl-sql/cl-sql-mysql_3.3.3-1_i386.deb cl-sql-odbc_3.3.3-1_all.deb to pool/main/c/cl-sql/cl-sql-odbc_3.3.3-1_all.deb cl-sql-oracle_3.3.3-1_all.deb to pool/contrib/c/cl-sql/cl-sql-oracle_3.3.3-1_all.deb cl-sql-postgresql-socket_3.3.3-1_all.deb to pool/main/c/cl-sql/cl-sql-postgresql-socket_3.3.3-1_all.deb cl-sql-postgresql_3.3.3-1_all.deb to pool/main/c/cl-sql/cl-sql-postgresql_3.3.3-1_all.deb cl-sql-sqlite3_3.3.3-1_all.deb to pool/main/c/cl-sql/cl-sql-sqlite3_3.3.3-1_all.deb cl-sql-sqlite_3.3.3-1_all.deb to pool/main/c/cl-sql/cl-sql-sqlite_3.3.3-1_all.deb cl-sql-tests_3.3.3-1_all.deb to pool/main/c/cl-sql/cl-sql-tests_3.3.3-1_all.deb cl-sql-uffi_3.3.3-1_i386.deb to pool/main/c/cl-sql/cl-sql-uffi_3.3.3-1_i386.deb cl-sql_3.3.3-1.diff.gz to pool/main/c/cl-sql/cl-sql_3.3.3-1.diff.gz cl-sql_3.3.3-1.dsc to pool/main/c/cl-sql/cl-sql_3.3.3-1.dsc cl-sql_3.3.3-1_all.deb to pool/main/c/cl-sql/cl-sql_3.3.3-1_all.deb cl-sql_3.3.3.orig.tar.gz to pool/main/c/cl-sql/cl-sql_3.3.3.orig.tar.gz

1 0

[cl-debian] Re: CONFIRM c1d95668ebfc5e16d25cd0a0f695505e
by owner＠packages.qa.debian.org 30 Oct '05

30 Oct '05

Processing commands for pts(a)qa.debian.org: > Subject: CONFIRM c1d95668ebfc5e16d25cd0a0f695505e cl-debian(a)common-lisp.net has been subscribed to ironclad(a)packages.qa.debian.org. > CONFIRM c1d95668ebfc5e16d25cd0a0f695505e >

1 0

[cl-debian] Re: Web subscription for ironclad package
by owner＠packages.qa.debian.org 30 Oct '05

30 Oct '05

Processing commands for pts(a)qa.debian.org: > Subject: Web subscription for ironclad package > subscribe ironclad cl-debian(a)common-lisp.net A confirmation mail has been sent to cl-debian(a)common-lisp.net. >

1 0