Hi,
On Wed, Jun 7, 2023, at 09:19, Sune Vuorela wrote:
> lisp runtie. unsure why restricted
>> cmucl deb lisp optional arch=i386
>> cmucl-clm deb lisp optional arch=i386
cmucl contains a compiler and is self hosting (the compiler is used to create
the new version of the environment). x86 is th
Package: wnpp
Severity: wishlist
Owner: Peter Van Eynde <[EMAIL PROTECTED]>
* Package name: cl-chunga
Version : 0.2.0
Upstream Author : Dr. Edmund Weitz
* URL : http://weitz.de/chunga/
* License : BSD
Programming Lang: Common Lisp
Description : Po
Package: wnpp
Severity: wishlist
Owner: Peter Van Eynde <[EMAIL PROTECTED]>
* Package name: cl-cffi
Version : 20061013
Upstream Author : James Bielman
* URL : http://common-lisp.net/project/cffi/
* License : BSD
Programming Lang: Common Lisp
Descr
Package: wnpp
Severity: wishlist
Owner: Peter Van Eynde <[EMAIL PROTECTED]>
* Package name: cl-plus-ssl
Version : 20060904
Upstream Author : various
* URL : http://common-lisp.net/project/cl-plus-ssl/
* License : Lisp LGPL
Programming Lang: Commo
Package: wnpp
Severity: wishlist
Owner: Peter Van Eynde <[EMAIL PROTECTED]>
* Package name: cl-hunchentoot
Version : 0.4.4
Upstream Author : Dr. Edmund Weitz
* URL : http://weitz.de/hunchentoot/
* License : BSD
Programming Lang: Common Lisp
Descr
Package: wnpp
Severity: wishlist
Owner: Peter Van Eynde <[EMAIL PROTECTED]>
* Package name: cl-trivial-https
Version : 20051125
Upstream Author : Brian Mastenbrook / David Lichteblau
* URL : http://common-lisp.net/project/cl-plus-ssl/
* License
On Sunday 08 October 2006 01:52, Debian Project Secretary wrote:
>
> - - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
> c2d43675-9efa-4809-a4aa-af042b62786e
> [ 2 ] Choice 1: Release Etch even with kernel firmware issues
> [ 1 ] Choice 2: Special exception to DFSG2 for fi
On Sunday 01 October 2006 01:05, Debian Project Secretary wrote:
>
> - - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
> 22fc4edd-1f6c-454f-b204-6aa0bad0ce1d
> [ ] Choice 1: DFSG #2 applies to all programmatic works
> [ 1 ] Choice 2: Further discussion
> - - -=-=-=-=-=-
>
> - - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
> 22fc4edd-1f6c-454f-b204-6aa0bad0ce1d
> [ ] Choice 1: DFSG #2 applies to all programmatic works
> [ 1 ] Choice 2: Further discussion
> - - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
pgpJ
Alle Thursday 03 August 2006 13:42, Otavio Salvador ha scritto:
> Alexander Sack <[EMAIL PROTECTED]> writes:
>
> > Anyway, as a side note on this thread: *darcs is just far t
> > slow* for decent maintenance of large pieces of software. I tried once
> > to create a mozilla repository, do some
Package: wnpp
Severity: wishlist
Owner: Peter Van Eynde <[EMAIL PROTECTED]>
* Package name: cl-kpax
Version : 20051222
Upstream Author : Sven Van Caekenberghe
* URL : http://homepage.mac.com/svc/kpax/
* License : LLGPL
Description : A Commo
Package: wnpp
Severity: wishlist
Owner: Peter Van Eynde <[EMAIL PROTECTED]>
* Package name: cl-s-http-server
Version : 20051218
Upstream Author : Sven Van Caekenberghe
* URL : http://homepage.mac.com/svc/s-http-server/
* License : LLGPL
Description
Package: wnpp
Severity: wishlist
Owner: Peter Van Eynde <[EMAIL PROTECTED]>
* Package name: cl-s-utils
Version : 20051212
Upstream Author : Sven Van Caekenberghe
* URL : http://homepage.mac.com/svc/s-utils/
* License : LLGPL
Description : A collect
Package: wnpp
Severity: wishlist
Owner: Peter Van Eynde <[EMAIL PROTECTED]>
* Package name: cl-s-sysdeps
Version : 20051122
Upstream Author : Sven Van Caekenberghe
* URL : http://homepage.mac.com/svc/s-sysdeps/
* License : LLGPL
Description
Package: wnpp
Severity: wishlist
Owner: Peter Van Eynde <[EMAIL PROTECTED]>
* Package name: cl-s-base64
Version : 20051102
Upstream Author : Sven Van Caekenberghe
* URL : http://homepage.mac.com/svc/s-base64/
* License : LLGPL
Description : A Commo
On Monday 21 November 2005 12:07, Ingo Juergensmann wrote:
> I could give you an account on a sparc machine with unstable chroot, but
> that's a non-debian.org machine, so it's mostly usuable for debugging and
> not for a build of an binary upload.
Thanks, but as the main goal is creating a new de
Hello,
I would need to have access to a sid chroot on sparc to build sbcl by hand,
but vore seems to be unreachable by me. The machine page [1] shows no
indication of problems, it is outdated?
Groetjes, Peter
1: http://db.debian.org/machines.cgi?host=vore
--
signature -at- pvaneynd.mailworks
Hello,
Mea culpa. I did a stupid thing with sbcl: in version 1:0.9.6.0-1 I used the
following construction:
Package: sbcl
Depends: sbcl-common (= ${Source-Version}), ${shlibs:Depends}
...
Package: sbcl-common
Now it turns out that the buildd network cannot build new packages[1]:
|The followin
On Wednesday 21 September 2005 15:49, René van Bevern wrote:
> > A lot of packages install stuff in the user directory.
>
> I doubt that any package does this.
1/[EMAIL PROTECTED]:~ :( $ grep '^/home/' /var/lib/dpkg/info/*.list
1/[EMAIL PROTECTED]:~ :( $
None on my system.
> Not by packages or
Package: wnpp
Severity: wishlist
Owner: Peter Van Eynde <[EMAIL PROTECTED]>
* Package name: cl-lw-compat
Version : 0.2
Upstream Author : Pascal Costanza
* URL : http://common-lisp.net/project/closer/
* License : MIT-style
Description : Lis
Package: wnpp
Severity: wishlist
Owner: Peter Van Eynde <[EMAIL PROTECTED]>
* Package name: cl-closer-mop
Version : 0.2
Upstream Author : Pascal Costanza
* URL : http://common-lisp.net/project/closer/
* License : MIT-style
Description :
Package: wnpp
Severity: wishlist
Owner: Peter Van Eynde <[EMAIL PROTECTED]>
* Package name: cl-utilities
Version : 1.1
Upstream Author : Peter Scott
* URL : http://common-lisp.net/project/cl-utilities/
* License : public domain
Description : a
Hello,
While this is getting a little off topic, I just wanted to correct a
common misconception.
Wouter Verhelst wrote:
>>I'm not sure what you mean by this; do you mean packages with circular
>>dependencies which must be bootstrapped manually? If so, this is generally
>>handled by our buildd a
Hello,
Daniel Holbach wrote:
> I set up http://www.ubuntulinux.org/wiki/UniverseNewPackages some time
...
> Ideally, both, the Debian maintainer and the Ubuntu maintainer should
> work together and make it an absolutely rocking package with no flaws
> and a perfectly crafted packaging system.
A
Package: wnpp
Severity: wishlist
Owner: Peter Van Eynde <[EMAIL PROTECTED]>
* Package name: cl-rfc2388
Version : x.y.z
Upstream Author : Name <[EMAIL PROTECTED]>
* URL : http://www.example.org/
* License : (GPL, LGPL, BSD, MIT/X, etc.)
Descript
Raul Miller wrote:
On Fri, Dec 17, 2004 at 10:39:26AM +0100, Peter Van Eynde wrote:
The API is known, otherwise there would be no Linux driver.
The API that is programmed by the firmware -- which you shouldn't confuse
with the API used by the driver that downloads the firmware -- is not
kno
Brian Thomas Sniffen wrote:
Peter Van Eynde <[EMAIL PROTECTED]> writes:
Is your name input for a state-machine?
You should see what it does to TECO. My name is a killing word.
:-)
>>[data == software ?]
Bingo. Debian had this debate last year. There was a giant vote over
it.
John Goerzen wrote:
On Thu, Dec 16, 2004 at 10:43:37PM +0100, Wouter Verhelst wrote:
Thus, the answer to the failure of the LSB is not "the Free Software
people should be more helpful to the non-free people"; the correct
answer is "the non-free people should be more helpful to the Free
Software peo
Matthew Palmer wrote:
Should I go on?
No, I think you've adequately demonstrated that you don't have the foggiest
idea what you're talking about.
Ok. I'm game. Why? Where is the error my in applying your rules?
Groetjes, Peter
Raul Miller wrote:
Fundamentally, the DFSG is aimed at making sure that we can provide the
software that we can support. Restrictions that leave us writing an
opaque blob of bits which drives an unknown API very much put us into
a context where we can't know that we're doing the right thing.
The A
Glenn Maynard wrote:
Hmm. A few places to draw the "dependency from driver to firmware"
line seem to be:
1: a dependency exists if the driver needs access to a copy of the firmware
(for devices that need the firmware uploaded on every boot);
2: a dependency exists if the hardware needs firmware at
Brian Thomas Sniffen wrote:
Some firmware is part of the hardware. Some isn't. It's easy to tell
-- either it's in the hardware or it isn't. Of course, the name
"firmware" should make it clear that this is an often ambiguous line.
But this does seem to be a good practical place: can anybody with
Brian Thomas Sniffen wrote:
Peter Van Eynde <[EMAIL PROTECTED]> writes:
And now you consider it software just because the method of storage is
different? How can the nature of the bytes change because they are
stored on a disk?
The nature of the bytes do not change. But my name, distribute
Brian Thomas Sniffen wrote:
No; the hardware is damaged. No driver can drive that. The driver
you have is a driver for Foomatic Quxer cards. You don't have a
Foomatix Quxer; you have a broken pile of junk.
So here you argue that because the firmware is gone the hardware is broken,
correct?
...
Package: wnpp
Version: N/A; reported 2002-11-08
Severity: wishlist
* Package name: cl-pg
Version : 0.14
Upstream Author : Eric Marsden <[EMAIL PROTECTED]>
* URL : http://www.chez.com/emarsden/downloads/
* License : LGPL
Description : Common Lisp library th
On Thu, Feb 11, 1999 at 08:49:06PM -0500, Branden Robinson wrote:
> Package: cmucl-clx
> Version: 2.4.9
>
> On Fri, Feb 12, 1999 at 12:04:19AM +0100, Pierre Mai wrote:
> > This has in fact already happened some time ago, as can be witnessed
> > by CLX, which is an implementation of the X protocol
36 matches
Mail list logo
