This is not a bug, I think. It's only warnings appeared when invoking stumpwm. It said:
You are using ASDF version 3.3.1 (probably from (require "asdf") or loaded
by quicklisp) and have an older version of ASDF (and older than 2.27 at
that) registered at #P"/usr/local/lib/common-lisp/asdf/asdf.asd". Having an
ASDF installed and registered is the normal way of configuring ASDF to
upgrade itself, and having an old version registered is a configuration
error. ASDF will ignore this configured system rather than downgrade itself.
In the future, you may want to either: (a) upgrade this configured ASDF to a
newer version, (b) install a newer ASDF and register it in front of the
former in your configuration, or (c) uninstall or unregister this and any
other old version of ASDF from your configuration. Note that the older ASDF
might be registered implicitly through configuration inherited from your
system installation, in which case you might have to specify
:ignore-inherited-configuration in your in your
~/.config/common-lisp/source-registry.conf or other source-registry
configuration file, environment variable or lisp parameter. Indeed, a likely
offender is an obsolete version of the cl-asdf debian or ubuntu package,
that you might want to upgrade (if a recent enough version is available) or
else remove altogether (since most implementations ship with a recent asdf);
if you lack the system administration rights to upgrade or remove this
package, then you might indeed want to either install and register a more
recent version, or use :ignore-inherited-configuration to avoid registering
the old one. Please consult ASDF documentation and/or experts.
WARNING: System definition file #P"/usr/local/lib/common-lisp/cl-ppcre/cl-ppcre.
asd" contains definition for system "cl-ppcre-test". Please only define "cl-ppcr
e" and secondary systems with a name starting with "cl-ppcre/" (e.g. "cl-ppcre/t
est") in that file.
I even don't know if it's related with stumpwm. I run maxima and sbcl, no warnings appear.
Is it possible to eliminate them? Thanks!
Hi. Sorry for the delay. I'll try to figure out what's going on soon(ish).
For what it's worth:
I was hitting a similar issue, and it turned out that the cause was using a locally installed quicklisp, which was newer than that of the package install.
In the post-install notes for sbcl, there is this comment:
For Common Lisp ports requiring the asdf system definition library from
devel/cl-asdf, /usr/local/etc/asdf-init.lisp has been set to load in
/usr/local/etc/sbclrc. If you plan to use Quicklisp, you must remove
this line from /usr/local/etc/sbclrc.
Removing the line as mentioned resolved the issue for me.
I don't install quicklisp. The only common lisp related ports are installed with stumpwm.
If I commented (load "/usr/local/etc/asdf-init.lisp") from /usr/local/etc/sbclrc, stumpwm could not be start normally.
No worries - I've been trying out stumpwm and am new to lisp in general, so I understandably overlooked some things. Looks like I am using the quick-lisp installed version of the package at this point, actually. So I apologize for the extra noise here.
Looking further into this, it looks like the problem might be because SBCL includes an older version of ASDF than is provided with the system?
I don't yet know enough to guess beyond that.