Bug#840111: stumpwm: please make the build reproducible

> "CL" == Chris Lamb writes: CL> There hasn't seem to be any update on this bug in 37 days, in CL> which time the Reproducible Builds effort has come on a long CL> way. :) CL> Would you consider applying this patch and uploading? I'm sorry, I missed the bug. Thank you for t

Re: slime does not compile for emacs25.1

> "GH" == Gijs Hillenius writes: GH> I noticed that slime is not available in Emacs25, which landed GH> in Debian. Should I file a bug? Am asking because Slime GH> recommends Emacs24, so that would explain it. Indeed, the dependency has to be updated with every major Emacs versio

Bug#788523: slime: ASDF fails to compile

Is this bug still present with slime 2.15-1 in current unstable? It doesn't look like a SLIME bug, but let's check. ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listin

Bug#781118: [slime] Purging the package leaves behind a confguration file causing problems for local slime installation

> "MV" == Martin Vlk writes: MV> I tried installing slime again and curiously, it doesn't install MV> that file (/etc/emacs/site-start.d/50slime.el) at all. It looks like something strange happens on your computer. The file is present in the package (you can check it with dpkg) and

Bug#781118: [slime] Purging the package leaves behind a confguration file causing problems for local slime installation

> "MV" == Martin Vlk writes: MV> Hi, when the slime package is uninstalled and purged, it leaves MV> behind the "/etc/emacs/site-start.d/50slime.el" config file. I can't reproduce the bug -- whatever I do the file disappears after purge. On both wheezy and current sid. Can you stil

Re: RFS: cl-launch (updated package)

> "F" == Faré writes: F> I am looking for a sponsor for the new version 4.1.3-1 of my F> package "cl-launch". Uploaded. ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.debian.org/c

Re: RFS: cl-launch (updated package)

> "F" == Faré writes: F> I am looking for a sponsor for the new version 4.1.2-2 of my F> package "cl-launch". Uploaded. -- http://www.zamazal.org ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http:

Re: RFS: cl-launch (updated package)

> "F" == Faré writes: F> I am looking for a sponsor for the new version 4.1.1-1 of my F> package "cl-launch". Uploaded (to experimental as we are in freeze now). -- http://www.zamazal.org ___ pkg-common-lisp-devel mailing list pkg-commo

Bug#766944: slime: Emacs"M-x slime"+sbcl fails with "Package SWANK-REPL does not exist." if cl-swank cache not deleted

Thanks for help, I could reproduce the bug again and it fixes it. Since this bug makes slime package unusable for some users, I'll raise its priority and request to unblock it for testing. Please test the new version (2.10-3). ___ pkg-common-lisp-devel

Bug#766944: slime: Emacs"M-x slime"+sbcl fails with "Package SWANK-REPL does not exist." if cl-swank cache not deleted

I could see the bug too and it was reproducible but after some experiments it suddenly disappeared for reasons unknown to me and it hasn't appeared again since then. Apparently it has something to do with the load ordering of contrib modules, maybe in slime--setup-contribs in slime.el. I might tr

Re: RFS: Please upload cl-asdf package

Done. The package didn't build, so I had to add a small patch — apparently the last line in Makefile should start with a tab instead of spaces. ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.deb

CLISP and Stumpwm (was: stumpwm REMOVED from testing)

So what to do with CLISP and testing? It seems CLISP is prevented from entering testing due to bugs #751005 and #752726, i.e. segfaults on certain architectures. I'm afraid I'm unable to help with that. Is anybody going to handle the problems? If not then Stumpwm package should remove its depen

Re: stumpwm REMOVED from testing

On 26. srpna 2014 18:39:16 CEST, Debian testing watch wrote: >FYI: The status of the stumpwm source package >in Debian's testing distribution has changed. > > Previous version: 2:0.9.8-5 > Current version: (not in testing) > Hint: ># get

Bug#754177: stumpwm does not work if `cl-asdf' is not installed.

> "EL" == Emilio Lopes writes: EL> after installing `stumpwm' I could not start the window manager. There EL> was some error message mentioning `asdf', which was *not* installed. EL> Note that `cl-asdf' is not `required' by `stumpwm', just `recommended'. EL> After `cl-asdf'

Bug#754179: stumpwm crashes when window title contains national chars

> "EL" == Emilio Lopes writes: EL> In my case I have the following in my ~/.emacs: EL> (setq-default frame-title-format (list "" "Emacs Macht Alle EL> Computer Sch\366n")) EL> Eval this in an Emacs buffer an watch stumpwm crash: EL> *** - CONVERT-STRING-FROM-BYTE

Bug#704774: stumpwm: libreoffice crashes stumpwm session

While there are some problems with Stumpwm and LibreOffice, the current version doesn't crash on lowriter startup on my system. Is that problem still present with stupmwm 0.9.8 on your system? ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel

Bug#657577: stumpwm: does not work with sbcl

Stumpwm indeed runs with SBCL. Did you read /usr/share/doc/stumpwm/README.Debian and set LISP variable appropriately? ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/lis

Bug#544683: iceweasel crashes stumpwm session when calling image viewer

I review Debian bug reports on stumpwm. Is this bug still present? ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-common-lisp-devel

Bug#705195: stumpwm won't start with cl-clx-sbcl, needs clisp-module-clx

I run Stumpwm with cl-clx-sbcl without problems. Does the problem still exist with stumpwm 0.9.8? ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-common-lis

Bug#585868: stumpwm: crashes on startup

I review old bug reports on stumpwm Debian package. Is this bug still present? ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-common-lisp-devel

Bug#509583: stumpwm does not tolerate non-ascii characters on input

There are actually three bug reports here: - I confirm that non-ASCII input doesn't work in the Stumpwm prompt. - I can't reproduce the problem with set-font, it should work. - I'm afraid the occasional crashes, especially when working with LibreOffice are still present in 0.9.8.

Bug#752726: stumpwm: FTBFS - SIGSEGV cannot be cured.

It looks like a CLISP bug to me, so I've reassigned it to clisp. FWIW, it doesn't crash on my system when built using cowbuilder. ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/

Re: stumpwm package

>>>>> "MZ" == Milan Zamazal writes: MZ> The stumpwm package looks mostly unmaintained. I'd like to MZ> help, is it OK to start working on it and its bugs and adding MZ> myself to Uploaders? No objections, so I updated the package to the curren

Re: RFS: Please upload cl-asdf package

Just a couple of notes: - Please check the package with (current) lintian and fix the reported errors. It complains about too long changelog line 6 and about slightly outdated Standards version. - Could you please update the download location in debian/copyright? After you upload the fixed

Re: RFS: Please upload cl-asdf package

> "RG" == Robert Goldman writes: RG> Please upload the cl-asdf package, after checking that it works RG> fine for you. I'll try to do it soon. ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lis

stumpwm package

The stumpwm package looks mostly unmaintained. I'd like to help, is it OK to start working on it and its bugs and adding myself to Uploaders? ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.debia

Bug#742426: slime: package update fails

> "TB" == Thorsten Bonow writes: TB> updating to the newest version of the slime package failed with TB> the messages attached below. Downgrading to TB> cl-swank_20130626-1_all.deb and slime_20130626-1_all.deb worked. TB> One more thing: I'm using emacs24-lucid and slime

Re: RFS: please upload cl-asdf package

> "F" == Faré writes: F> - dget F> http://mentors.debian.net/debian/pool/main/c/cl-asdf/cl-asdf_3.0.2.4-1.dsc F> I would be glad if someone uploaded these packages for me. Done. ___ pkg-common-lisp-devel mailing list pkg-common-lisp

Bug#720867: /usr/share/emacs24/site-lisp/slime/slime.elc:Error: Don't know how to compile nil

Is the bug still present in slime 20130626-1 (uploaded yesterday to unstable)? I can't reproduce it so I guess it's gone. ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman

Re: RFS: cl-launch, cl-asdf (updated packages)

> "F" == Faré writes: F> Maybe you mean cl-launch -ip '(+ 1 1)' It's the same (as it should by reading the documentation), see below for complete output. Additionally, I was hit by another cl-asdf problem when starting stumpwm (1:20110819.gitca08e08-2): % stumpwm This is SBCL 1.0.

Re: RFS: cl-launch, cl-asdf (updated packages)

cl-launch 3.22 doesn't work for me with sbcl 1.0.57.0-2 from testing: % cl-launch '(+ 1 1)' ... unhandled SB-EXT:NAME-CONFLICT in thread #: USE-PACKAGE # causes name-conflicts in # between the following symbols: ASDF:FIND-SYMBOL*, UIOP/PACKAGE:FIND-SYMBOL* Did I anything wrong

Re: RFS: cl-launch, cl-asdf (updated packages)

> "F" == Faré writes: F> I am looking for a sponsor for F> the new version 3.22-1 of my package "cl-launch", and F> the new version 2:3.0.1-1 of my package "cl-asdf". [...] F> I would be glad if someone uploaded these packages for me. I'll try to do it later today. _

Bug#666648: slime: FTBFS: mkdir: cannot create directory `././sbuild-nonexistent': Permission denied

> "CE" == Christoph Egger writes: CE> This one looks like writing to $HOME which is not allowed and CE> will not fail in a cowbuilder environment normally. Would be CE> easy to test building with HOME=/something-not-existing Thanks for explanation, indeed it's the case. I'll try

Bug#666648: slime: FTBFS: mkdir: cannot create directory `././sbuild-nonexistent': Permission denied

> "LN" == Lucas Nussbaum writes: LN> Source: slime LN> Version: 1:20111027-2 LN> Severity: serious LN> Tags: wheezy sid LN> User: debian...@lists.debian.org LN> Usertags: qa-ftbfs-20120331 qa-ftbfs LN> Justification: FTBFS on amd64 LN> Hi, LN> During a re

SLIME git archive on Alioth

I had some time to fix my old fault and make the Debian SLIME git archive on Alioth organized in its original way. This required unclean changes to the archive, namely renaming the branches `master' and `upstream' to `master.diverted' and `upstream.diverted' respectively, and replacing them with n

Re: Mailing list administration

> "LC" == Luca Capello writes: LC> On Wed, 08 Sep 2010 08:31:11 +0200, Peter Van Eynde wrote: >> PS: maybe we also need more 'admin' people for the mailing >> lists. Is someone a volunteer to do this? LC> We need more, yes, especially given the fact that I am slowly LC> f

Re: Uploaded cl-asdf to mentors

> "F" == Faré writes: F> Can you bless it for unstable? Uploaded. Again: You should adhere to new Standards versions. ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailm

Re: uploaded cl-asdf and cl-launch to mentors

Uploaded. BTW, it might be useful to add me to cl-asdf Uploaders. ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-common-lisp-devel

Re: uploaded cl-asdf and cl-launch to mentors

> "F" == Faré writes: F> Note that if you already uploaded anything to any official repo, Not yet. F> LICENSE is created by the Makefile, and I don't know the correct F> way to tell git-buildpackage to ignore it. Isn't it possible to remove it in `clean' target?

Re: uploaded cl-asdf and cl-launch to mentors

> "F" == Faré writes: F> I've just uploaded ASDF 2.005 and CL-Launch 3.001. Some comments: - You should always check current Standards version (and changes) and put it in debian/control. - You should switch to source format 3.0 (probably nothing more than editing debian/source/f

Re: uploaded cl-asdf and cl-launch to mentors

> "F" == Faré writes: F> Can you or someone please update cl-asdf and cl-launch while it's F> still time? Done. ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/

Re: uploaded cl-asdf and cl-launch to mentors

> "F" == Faré writes: F> Problem is, cl-launch 3 depends on asdf 2, so it's not F> immediately helpful to upload cl-launch before asdf is F> updated. That said, cl-launch 2 is probably already broken by F> asdf 1.704, so you may as well upload it now and things will F> ma

Re: uploaded cl-asdf and cl-launch to mentors

> "F" == Faré writes: F> I uploaded packages for cl-asdf 2.004 and cl-launch 3.000 to F> mentors. Can someone with proper privileges give a look and F> bless them? I can handle cl-launch. However this has been uploaded to mentors as a native Debian package (.tar.gz instead of

Bug#588575: SLIME and Swank have version mismatch

The problem seems to be here: (defvar slime-protocol-version nil) (setq slime-protocol-version (eval-when-compile (slime-changelog-date))) When new slime version gets installed before cl-swank, it stores the old cl-swank version into slime-protocol-version. I don't know why eval-when

Bug#568818: Not sure that the cl-swank problem is fixed?

FWIW, slime works for me with sbcl 1:1.0.34.0-1. And (require 'sb-bsd-sockets) works in my sbcl prompt. ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-commo

Bug#568818: Not sure that the cl-swank problem is fixed?

I believe this problem has been fixed in cl-swank 20100220-4 uploaded just a while ago. When it appears in the archive, please test it. ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.debian.or

Taking over slime

I'm (finally) going to take over SLIME Debian packages. Is there anything I should know before doing the work? ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-comm

Re: debs for cl-launch & xcvb

> "F" == Faré writes: F> Can you sponsor the package in debian? Uploaded. F> Also, if you or anyone is maintaining CLC, I'm not. ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.

Re: debs for cl-launch & xcvb

> "F" == Faré writes: F> Will you be a sponsor for my uploads? F> I've uploaded cl-launch_2.22-1 to mentors.debian.net. It could F> probably use some repackaging, such as being put in section lisp F> and updating the list of uploaders. The package looks basically fine, so I

Re: debs for cl-launch & xcvb

> "F" == Faré writes: F> There's a cl-launch in Debian, but it's extremely old (by F> cl-launch standards), and is missing plenty of bug fixes and new F> features It was recently officially acknowledged that many CL packages suffer from this condition due to the complete lack of

Re: pan pan pan

> "PVE" == Peter Van Eynde > writes: PVE> Do you want to take over completely or as part of the PVE> 'packaging team'? I prefer to keep slime formally under the packaging team. Please note I'm unable to join right now, I hope I'll be able to start doing something in September o

Re: pan pan pan

> "RS" == Rupert Swarbrick > writes: RS> Hmm, so as I said (somewhere in this thread), quite a few lisp RS> libraries don't have "proper" releases, or the official releases RS> lag so far behind the scm that they're pretty much irrelevant. It is not that important whether th

Re: pan pan pan

> "RS" == Rupert Swarbrick > writes: RS> I don't think that debian packages are a waste of time. It is not, the problem is who will do the work. I definitely prefer a small set of well working core CL packages over hundreds of obsolete CL packages in a poorly maintained state.

Re: pan pan pan

> "CL" == Christian Lynbech writes: CL> Is there any way non-DD's can help in the short term? Maybe helping to fix open Debian bugs on packages that you are interested in? CL> Longer term, interested paties should of course sign up as DD's Yes, please. ___

Re: pan pan pan

> "PVE" == Peter Van Eynde > writes: PVE> I also think that slime should go. Not that I don't think it is PVE> good package that has its use, but because it is just so tricky PVE> to maintain and I never have understood how to debug those PVE> emacs bugs :-(. If you give

Re: pan pan pan

I'm a DD interested in CL. I maintain (although not very actively) a few Debian CL packages and I'm not going to give up on them, so I need at least common-lisp-controller (in addition to CL implementations) in Debian. I might consider to help more, but the main problem (what a surprise!) is my R

Re: pan pan pan

I'm a DD interested in CL. I maintain (although not very actively) a few Debian CL packages and I'm not going to give up on them, so I need at least common-lisp-controller (in addition to CL implementations) in Debian. I might consider to help more, but the main problem (what a surprise!) is my R