Package Details: stumpwm 1.0.0-5

Git Clone URL: (read-only)
Package Base: stumpwm
Description: A tiling, keyboard-driven window manager written in common lisp
Upstream URL:
Licenses: GPL2
Provides: stumpwm
Submitter: haawda
Maintainer: haawda
Last Packager: haawda
Votes: 3
Popularity: 0.206255
First Submitted: 2017-01-20 22:35
Last Updated: 2017-06-27 14:56

Dependencies (12)

Required by (1)

Sources (1)

Latest Comments

haawda commented on 2017-06-27 14:57

Upstream wishes decoupling of the contribs from the main package.

zonotope commented on 2017-05-06 02:37

@hiberno I ran into the same issue. My problem was caused by the SBCL_HOME environment variable being set to 'NIL'. I solved it by setting the variable to the parent directory of the `sbcl.core` file on my machine, which ended up being `/usr/lib/sbcl`. You can probably find where your sbcl.core file is by running `sudo find / | grep sbcl.core`.

I only consider this to be a workaround though. Something is setting the SBCL_HOME environment variable to 'NIL', but I haven't figured out what that is. A real fix would be to change whatever is setting it to 'NIL' to make it set it to the real value, but setting the variable by hand after the fact allows stump to compile (after ignoring checksums, of course).

hiberno commented on 2017-05-04 10:37

I can't build it, alas, because of the following error with SBCL:

$ sbcl
fatal error encountered in SBCL pid 6365(tid 0x7ffff7fd5fc0):
can't find core file at NIL/sbcl.core

When I do `sbcl --core /usr/lib/sbcl/sbcl.core`, SBCL starts up just fine. I cannot rebuild SBCL from ABS either because of this error. Does anyone here, by chance, know what to do about that? :)

ahmed-shariff commented on 2017-05-04 03:41

When I build the package using MAKEPKG I get the following:

stumpwm-contrib.git ... FAILED
==> ERROR: One or more files did not pass the validity check!

I managed to build the package by setting the md5sums of to 'SKIP'

haawda commented on 2017-02-14 22:56

For me it works, so it is difficult to determine the right one. You could ty to open an issue on github, and ask the maintainers to make a release for the commit that suits to stumpwm 1.0.0. That would help much.

ElNick commented on 2017-02-14 19:18

If the problem is really because stumpwm-contrib.git is too new, it can be fixed by adding git checkout last_known_working_commit in pre-build step

haawda commented on 2017-02-14 11:48

Indeed it was my first wish to bundle thi with a stabel, released Version of the contribs, but I did not find one.

ElNick commented on 2017-02-14 10:04

As of now, build does not compile ending up in a stack overflow. I did not check it (I use stumpwm-git package and it builds ok), but perhaps mixing git version of stumpwm-contrib with a fixed release of stumpwm is not a good idea.

haawda commented on 2017-02-13 17:48

I did so, thanks.

ElNick commented on 2017-02-13 14:25

md5sum for source should probably be set to "SKIP"