Hi,
Tested this and it’s due to the 64t transition. The grovelled data changed:
(sid_armhf-dchroot)pvaneynd@abel:~/sbcl-2.3.7$ diff -u
./crossbuild-runner/backends/arm/stuff-groveled-from-headers.lisp
output/stuff-groveled-from-headers.lisp
---
This looks a lot like a problem between the
`OBSERVED-INTERNAL-REAL-TIME-DELTA-SEC` which is a word and the new 64-bit
counters.
❯ git grep observed-internal-real-time-delta-sec
src/code/thread-structs.lisp: #-64-bit (observed-internal-real-time-delta-sec
0 :type sb-vm:word)
Package: ftp.debian.org
Severity: normal
signature.asc
Description: PGP signature
Hi Adrian,
Thanks for that. I was reading up on this 'source only' uploads. In general I
agree with the idea, however for cmucl when a new major version gets released
the rebuilding of the new version using the old version is non-trivial and not
automated.
So for major releases I do the
Package: zfsutils-linux
Version: 0.7.13-1
Severity: important
Dear Maintainer,
When doing a scrub of my ZFS filesystem with 4.19 I get warnings of hung
processes, followed by the system going catatonic. This happens within
seconds of starting the scrub.
When doing the same operation after
Hello Dmitry,
As mentioned before: the community considers this an 'optional request'
not a requirement. Unless you have further comments I intend to close
this bug in a few weeks.
Best regards, Peter
--
signature -at- pvaneynd.mailworks.org
http://pvaneynd.dreamwidth.org/
God, root, what is
Hello Dmitry,
On 19/04/16 23:18, Dmitry Smirnov wrote:
> But this requirement is not optional. License do not allow us to speculate
> whether they are checking their post box or email and choose whether to
> comply with this requirement...
I checked and nobody is listening anymore at that
Hello Dmitry,
On 16/04/16 04:21, Dmitry Smirnov wrote:
> The following files are licensed under non-DFSG compliant license:
>
> Files:
>
>
Hello Santiago,
> Seems like a missing Build-Depends on hardening-includes, the package
> containing /usr/share/hardening-includes/hardening.make, so it
> should be quite easy to fix.
Turns out it's not so easy after all, I'm still working on it...
> BTW: I wonder why this package does not
Hello Aaron,
> Could you please declare cmucl-source to be Multi-Arch: foreign? As
That's a most excellent idea! Stupid of me of not having thought of this...
> Doing the same for cmucl-docs, which cmucl and cmucl-clm both suggest,
> would be helpful too.
I can do this for cmucl-docs, but
Hello Graham,
On 21/06/15 19:06, Graham Inggs wrote:
Your package depends on libxp. This situation sometimes arises
historically from the time before xprint was considered obsolete, with
Build-depends: libxp-dev being set in the past and then forgotten and
untouched.
In fact upstream set a
Package: libdvdread4
Version: 4.2.0+20120521-2
Severity: normal
Dear Maintainer,
While investigating crashes in another application I noticed they were
caused by libdvdread. Investigating deeper with printfs I would see:
| A path: 0x7fffc8023f90 path_copy: 0x7fffc800b350
| B path:
Hello Jakub,
On 02/01/12 16:44, Jakub Wilk wrote:
Source: cmucl
Version: 20b-1
Severity: serious
Justification: fails to build from source
this is not really correct: in fact cmucl cannot be rebuild from source
in unstable. It worked before :(.
Or are you running stable perhaps?
This must
Hello Michael,
On 17/11/11 18:43, Michael Terry wrote:
I get pretty far these days. I was looking into why it was failing in
Ubuntu and it gets to this point:
./lisp.run -B . -N locale -E UTF-8 -Epathname 1:1 -Emisc 1:1 -norc -m
2MW -lp /home/mterry/clisp-2.49/src/ -x '(and (load
Hello Anne,
On 09/03/11 14:11, Anne C. Hanna wrote:
/usr/lib/clisp-2.49/base/lisp.run: operating system error during load of
initialization file `/usr/lib/clisp-2.49/base/lispinit.mem'
[/build/buildd-clisp_2.49-3+b1-amd64-lEeikj/clisp-2.49/src/spvw_memfile.d:982]
errno = ENOENT: No such file
Hello Desmond and friends,
This bug is due to the fact that the rebuild used dh_lisp 0.7 which
causes the rebuild version not to call the clisp.sh scripts.
So the package is not installed correctly. In fact no rebuild
implementation will work anymore.
This is clearly sub-optimal as this new
Hello,
On 20/02/11 02:53, Wang Lei wrote:
Today after upgrading clisp, stumpwm can't startup. Report no xlib.
This is a problem of stumpwm I fear.
With the new version of clisp clx is no longer build in, you need to
also depend on the module clisp-module-clx. After installing this you
can
Hello Miĥail,
Checking this on 2.49 I cannot reproduce the problem:
Welcome to GNU CLISP 2.49 (2010-07-07) http://clisp.cons.org/
...
...
TEST[14] (length abc)
*** - The value of L should be of type LIST.
The value is: abc
The following restarts are available:
STORE-VALUE:R1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Stef,
On 01/10/10 22:15, stef louise wrote:
This was a little tricky. I successfully built and installed
libsigsegv2_2.8 binary+dev
Then the git build-package was successful, nonetheless it is uninstallable:
# LANG=C dpkg -i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Hector,
On 27/09/10 00:58, Hector Oron wrote:
For 2.49 (latest upstream release), it also fails but on another part, when
building i18n (also reported to upstream) [2]
configure: loading cache ../config.cache
configure: error:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Stef,
On 22/09/10 21:53, stef louise wrote:
I may have some time to check it by the end of the week. I know how to
compile stuff, even quite complex projects, but I'm quite unfamiliar
with git (even though I shouldn't), and I don't know
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Stef,
On 16/09/10 21:57, stef louise wrote:
/usr/share/common-lisp/source/common-lisp-controller/common-lisp-controller.lisp
*** - handle_fault error2 ! address = 0x77dc3ba0 not in
[0x699c60d8,0x69aa3000) !
I have a new clisp version
Hello Sam,
I'm redoing the clisp package from scratch to fix long standing issues like:
* unnecessary dependencies in clisp-dev:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504514
* clisp: base/full in clisp-package
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=177057
* clisp:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Faré,
I'll try to update clc and friends as soon as possible.
On 14/04/10 00:28, Faré wrote:
2- C-L-C needs to (asdf:clear-output-translations) and
(asdf:clear-source-registry) right before it dumps images, for all
implementations.
ok
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
ECL needs a more recent version of libgc, but we only have 7.1 in
experimental so until 446068 and 559345 are fixed in unstable we can
only continue to use the included libgc (and libatomic-ops) version.
If you do have patches that make libgc
Package: common-lisp-controller
Version: 7.0
Severity: important
When using the new clc with clisp you always get a stack overflow on the
first use of clc:clc-require. If you retry it works. For some reason
it loops somewhere it cannot loop.
I need to investigate this in more detail.
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 19/01/10 21:52, James Y Knight wrote:
Only root would be able to use clc-clbuild, right?
Correct. Except for clc-clbuild slime which should start an emacs with
slime running.
This mostly works (I had to do some patched to clbuild itself).
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Christoph,
On 24/01/10 21:48, Christoph Egger wrote:
Downgrading libsigsegv to 2.3-3 does indeed make clisp build
again on kFreeBSD (ignoring the general failure because of
incompatibility with bdb 4.8 which can be solved by using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Faré,
I was actually thinking about this feature of yours in the traffic jam:
instead of /etc/common-lisp/source-registry.conf I would like to see
/etc/common-lisp/source-registry.conf.d
where instead of having one file that you might have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Rafael,
I fear that openvz containers are just not supported upstream. SBCL
needs some pretty unusual low level support and demands a lot of memory
(which it doesn't all use). I don't think it has sense to make custom
patches through Debian, I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Faré,
On 12/01/10 17:46, Faré wrote:
Can you make the path to those files compatible with what I'm
preparing for ASDF?
I've taken a look at the bug and the idea seems to be to have a place to
define the locations of systems in on a system
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello James,
Just FYI I've started working on CLC v7 where this will be a system-wide
setting overrideable with a user-specific configuration file.
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
Hi all,
These bugs only describe expected behavior.
From 6.19 onwards common-lisp-controller is no longer doing this. I will
update the clc documentation and add a NEWS file to point this out more
clearly (I hope).
I've attached the NEWS file for you to review.
Groetjes, Peter
--
signature
Hello all,
Just FYI: cl-babel is now in Debian.
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|
--
To UNSUBSCRIBE, email to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I looked into babel and there is a small license issue to resolve first.
I also am checking all dependencies just to be certain.
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
http://www.livejournal.com/users/pvaneynd/
God, root,
This seems to be because dh_lisp is not setting dependencies correctly,
so babel got removed by accident.
Oops.
We need to check why this is and now check all CL libraries.
Groetjes, Peter
--
signature -at- pvaneynd.mailworks.org
http://www.livejournal.com/users/pvaneynd/
God, root, what is
Hello Raphael,
I don't know what went wrong there, but you're right it is still there,
however in the code you can read:
# Use a simple mkdir command. It is guaranteed to fail if the directory
# already exists. $RANDOM is bash specific and expands to empty in shells
# other than
Hi,
I'm trying but cannot reproduce this anymore with 1:1.0.31.0-2:
2/pvane...@sharrow:~/fakeroot/clean/git/sbcl :) $ sbcl --noinform --eval
'(time (sleep 2))' --eval '(sb-ext:quit)'
; loading system definition from
; /usr/lib/sbcl/sb-bsd-sockets/sb-bsd-sockets.asd into #PACKAGE ASDF0
;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Lucas,
Lucas Nussbaum wrote:
Why are you building in a lenny chroot ?
Because I was testing before with a sid chroot, which worked and I got
confused.
So I redid a build of 9.8.4-1 in a clean chroot and ... it just worked...
Groetjes,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Lucas,
I'm a bit surprised by this FTBFS as ecl is also auto-build for other
platforms. What research did you do in this failure?
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
http://www.livejournal.com/users/pvaneynd/
God,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Lucas,
Lucas Nussbaum wrote:
On 22/09/09 at 18:47 +0200, Peter Van Eynde wrote:
I'm a bit surprised by this FTBFS as ecl is also auto-build for other
platforms. What research did you do in this failure?
I have done no research at all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Barry,
Barry deFreese wrote:
I cannot find a source or binary package cl-f2l. Should this be for
cl-f2cl?
Indeed. Sorry my mistake.
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
http://www.livejournal.com/users/pvaneynd/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Barry,
Barry deFreese wrote:
I'm a bit confused on this one. cl-flexi-streams is a binary package
(and the only binary package) for the flexi-streams source package. It
was recently updated, as was it's reverse depend cl-irc. Should this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello David, Fredrik,
Indeed the clc version 6.18 does not work with older versions of sbcl.
I've had to change the native-file-kind package.
However I've also added a Conflict against sbcl ( 1:1.0.29.0). So
why did it want to install with an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
tag 518605 +confirmed
thanks
Hello Jörg,
Of course you are right, but currently all lisp implementations will
read this file on startup.
We should cleanup this policy and then fix all the lisp
implementations... one day ;-(
Groetjes, Peter
- --
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Barry,
Barry deFreese wrote:
Thanks, does this mean that cl-trivial-gray-streams should stay too
since it is a depends for cl-flexi-streams, or do you think that
dependency can be removed somehow?
Aargh. You're right. We still need
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Barry,
Let me first thank you for all the good work you and your team are
doing! I know I created quite a few RM requests :-(
Barry deFreese wrote:
# Broken Depends:
qbook: cl-qbook
yaclml: cl-yaclml
Luca did a RFA for both of them. I'll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi again,
Barry deFreese wrote:
We are unable to remove cl-rsm-queue currently until the reverse depends
is resolved.
# Broken Depends:
cl-rsm-cache: cl-rsm-cache
cl-rsm-cache has a removal bug filed but it is blocked by:
# Broken
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello all,
Barry deFreese wrote:
We are unable to remove cl-rsm-cache currently until the reverse depends
is resolved.
# Broken Depends:
cl-rsm-genetic-alg: cl-rsm-genetic-alg
I filed 547111 to remove cl-rsm-genetic-alg.
Groetjes, Peter
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello all,
Barry deFreese wrote:
# Broken Depends:
flexi-streams: cl-flexi-streams
I filed #547112 to remove also this package.
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
http://www.livejournal.com/users/pvaneynd/
God, root,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: ftp.debian.org
Severity: normal
For a while now most Common Lisp projects do not do releases anymore,
our plan is to move to proving a cl-build like environment inside debian
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
1 - 100 of 284 matches
Mail list logo
