From Newsgroup: alt.os.linux.slackware

Hello,

I noticed in the current changelog that, for at least three years, it's
been using snapshots of the unreleased 2.50 version. I don't run
current, myself, and my Lisp usage is so rudimentary that the version
likely wouldn't matter at all. Still, I'm curious if anyone knows the background for this change. 2.49 does date back to 2010, but I see other projects sticking with that.

Regards,
Mike Sm.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.slackware

On Wed, 11 Jun 2025 20:59:57 -0400, Mike Small wrote:

I noticed in the current changelog that, for at least three years, it's
been using snapshots of the unreleased 2.50 version. I don't run
current, myself, and my Lisp usage is so rudimentary that the version
likely wouldn't matter at all. Still, I'm curious if anyone knows the background for this change. 2.49 does date back to 2010, but I see other projects sticking with that.

Looking at the ChangeLog when clisp 2.50 was introduced would make me
guess that upgrading to that "beta" version was needed to support a new version of libunistring:

-8<-----------------------------------------------
+--------------------------+
Wed Oct 19 20:06:33 UTC 2022
a/aaa_libraries-15.1-x86_64-11.txz: Rebuilt.
Upgraded: libcap.so.2.66, liblzma.so.5.2.7, libpopt.so.0.0.2,
libexpat.so.1.8.9, libglib-2.0.so.0.7200.4, libgmodule-2.0.so.0.7200.4,
libgobject-2.0.so.0.7200.4, libgthread-2.0.so.0.7200.4,
libhistory.so.8.2,
libreadline.so.8.2.
Added: libunistring.so.2.1.0, libunistring.so.5.0.0.
Removed: libffi.so.7.1.0.
a/gettext-0.21.1-x86_64-2.txz: Rebuilt.
ap/lsof-4.96.4-x86_64-1.txz: Upgraded.
ap/man-pages-6.01-noarch-1.txz: Upgraded. d/clisp-2.50_20220927_acb1266ee-x86_64-1.txz: Upgraded.
Compiled against libunistring-1.1.
d/gettext-tools-0.21.1-x86_64-2.txz: Rebuilt.
Recompiled against libunistring-1.1.
d/guile-3.0.8-x86_64-3.txz: Rebuilt.
Recompiled against libunistring-1.1.
kde/kguiaddons-5.99.0-x86_64-2.txz: Rebuilt.
[PATCH] systemclipboard: Don't signal data source cancellation.
Thanks to marav.
l/libidn2-2.3.3-x86_64-2.txz: Rebuilt.
l/libpsl-0.21.1-x86_64-5.txz: Rebuilt.
Recompiled against libunistring-1.1.
l/libunistring-1.1-x86_64-1.txz: Upgraded.
Shared library .so-version bump.
n/bind-9.18.8-x86_64-1.txz: Upgraded.
n/gnutls-3.7.8-x86_64-2.txz: Rebuilt.
Recompiled against libunistring-1.1.
n/samba-4.17.1-x86_64-1.txz: Upgraded.
This update fixes the following security issue:
Bad password count not incremented atomically.
For more information, see:
https://bugzilla.samba.org/show_bug.cgi?id=14611
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-20251
(* Security fix *)
n/wget-1.21.3-x86_64-2.txz: Rebuilt.
Recompiled against libunistring-1.1.
x/imake-1.0.9-x86_64-1.txz: Upgraded.
x/xcb-util-errors-1.0.1-x86_64-1.txz: Upgraded. x/xcb-util-image-0.4.1-x86_64-1.txz: Upgraded. x/xcb-util-keysyms-0.4.1-x86_64-1.txz: Upgraded. x/xcb-util-renderutil-0.3.10-x86_64-1.txz: Upgraded. x/xcb-util-wm-0.4.2-x86_64-1.txz: Upgraded.
+--------------------------+
-8<-----------------------------------------------

However, the libunistring explanation is only a guess from my side, maybe version 2.49 would also work with the new libunistring and the upgrade to
2.50 was a mistake?

regards Henrik
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.slackware

Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> writes:
...

been using snapshots of the unreleased 2.50 version. I don't run
current, myself, and my Lisp usage is so rudimentary that the version
likely wouldn't matter at all. Still, I'm curious if anyone knows the
background for this change. 2.49 does date back to 2010, but I see other
projects sticking with that.

Looking at the ChangeLog when clisp 2.50 was introduced would make me
guess that upgrading to that "beta" version was needed to support a new version of libunistring:

...

d/clisp-2.50_20220927_acb1266ee-x86_64-1.txz: Upgraded.
Compiled against libunistring-1.1.

...

However, the libunistring explanation is only a guess from my side, maybe version 2.49 would also work with the new libunistring and the upgrade to 2.50 was a mistake?

Seems reasonable.

I missed that Debian unstable actually also is taking versions from
upstream's git repo. It's confusing, as Slackware and Debian are using
quite different version number schemes while perhaps taking similar
code, give or take some months:

Slackware current:

Wed Jun 11 22:22:57 UTC 2025
d/clisp-2.50_20250504_f66220939-x86_64-1.txz: Upgraded.

Debian unstable:

Version: 1:2.49.20241228.gitc3ec11b-2

http://deb.debian.org/debian/pool/main/c/clisp/clisp_2.49.20241228.gitc3ec11b-2.dsc

They are in the same branch, I think. If you look in src/version.h in
f66220939 upstream it shows a version with 2.49 in its string, at least
for now, which maybe is why debian included 2.49 in their package version:

#define PACKAGE_VERSION "2.49.95+ (2024-11-03)" https://gitlab.com/gnu-clisp/clisp/-/blob/master/src/version.h?ref_type=heads

NetBSD/pkgsrc still has 2.49 from 2010, not a repo snapshot, as does
Beyond Linux from Scratch. It looks to me like both of them opt not to
link to libunistring, that being an optional dependency. BLfS does link
to libunistring in their guile instructions. pkgsrc's lack of linkage I
show below. So that supports your guess. Maybe they intentionally
avoided it after having problems. pkgsrc libunistring is at version 1.2
now, even newer (and more problematic for clisp 2.49?) than the 1.1
version in the older Slackware current changelog you cited.

% ldd /usr/pkg/lib/clisp/base/lisp.run
/usr/pkg/lib/clisp/base/lisp.run:
-lreadline.8 => /usr/pkg/lib/libreadline.so.8
-lterminfo.2 => /usr/lib/libterminfo.so.2
-lc.12 => /usr/lib/libc.so.12
-lm.0 => /usr/lib/libm.so.0
-lcrypt.1 => /usr/lib/libcrypt.so.1
-lintl.1 => /usr/lib/libintl.so.1
-lavcall.1 => /usr/pkg/lib/libavcall.so.1
-lcallback.1 => /usr/pkg/lib/libcallback.so.1
-lpthread.1 => /usr/lib/libpthread.so.1
-lsigsegv.2 => /usr/pkg/lib/libsigsegv.so.2

Funny, I just noticed I had a newer, git based clisp compiled outside
pkgsrc on NetBSD, myself. I'd forgotten, but it looked like I was
getting segmentation faults from swank when trying to run slime. But I
was taking a git slime, so maybe I was mixing new wine with old
wineskins. I wonder if anyone on slackware hit anything like this with
2.49 or if I just made bad decisions when installing slime on
NetBSD. I'll have to try slime again on Slackware 15.0 with clisp 2.49.

Oh, also interesting, is this clisp (pkgsrc/NetBSD) without libunistring
linked still shows :UNICODE among its features. Skimming the surface of
this I remain puzzled:

*features*

(:READLINE :REGEXP :SYSCALLS :I18N :LOOP :COMPILER :CLOS :MOP :CLISP :ANSI-CL
:COMMON-LISP :LISP=CL :INTERPRETER :SOCKETS :GENERIC-STREAMS
:LOGICAL-PATHNAMES :SCREEN :FFI :GETTEXT :UNICODE :BASE-CHAR=CHARACTER
:WORD-SIZE=64 :PC386 :UNIX)

Regards,

Mike Sm.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.slackware

Mike Small <smallm@panix.com> writes:

Funny, I just noticed I had a newer, git based clisp compiled outside
pkgsrc on NetBSD, myself. I'd forgotten, but it looked like I was
getting segmentation faults from swank when trying to run slime. But I
was taking a git slime, so maybe I was mixing new wine with old
wineskins. I wonder if anyone on slackware hit anything like this
with 2.49 or if I just made bad decisions when installing slime on
NetBSD. I'll have to try slime again on Slackware 15.0 with clisp
2.49.

Not slackware, but on OpenBSD I have the same problem. Clisp is 2.49
and it crashes with slime, no matter what version. Seems to be a
general problem with 2.49.

Oh, also interesting, is this clisp (pkgsrc/NetBSD) without
libunistring linked still shows :UNICODE among its features. Skimming
the surface of this I remain puzzled:

*features* (:READLINE :REGEXP :SYSCALLS :I18N :LOOP :COMPILER

:CLOS :MOP :CLISP :ANSI-CL
:COMMON-LISP :LISP=CL :INTERPRETER :SOCKETS :GENERIC-STREAMS
:LOGICAL-PATHNAMES :SCREEN :FFI :GETTEXT :UNICODE
:BASE-CHAR=CHARACTER :WORD-SIZE=64 :PC386 :UNIX)

I guess clisp has its own unicode handling routines and just tries to
switch to an external library.

Regards
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.slackware

Joerg Mertens <joerg-mertens@t-online.de> writes:

Mike Small <smallm@panix.com> writes:

Funny, I just noticed I had a newer, git based clisp compiled outside
pkgsrc on NetBSD, myself. I'd forgotten, but it looked like I was
getting segmentation faults from swank when trying to run slime. But I
was taking a git slime, so maybe I was mixing new wine with old
wineskins. I wonder if anyone on slackware hit anything like this
with 2.49 or if I just made bad decisions when installing slime on
NetBSD. I'll have to try slime again on Slackware 15.0 with clisp
2.49.

Not slackware, but on OpenBSD I have the same problem. Clisp is 2.49
and it crashes with slime, no matter what version. Seems to be a
general problem with 2.49.

Thanks, that's good to know.

I tried it on Slackware 15.0 with 2.49, and slime worked fine, but this
was slime 2.28. So a stable release from a couple of years ago.

- Mike Sm.

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.slackware

Mike Small <smallm@panix.com> writes:

Joerg Mertens <joerg-mertens@t-online.de> writes:

Not slackware, but on OpenBSD I have the same problem. Clisp is 2.49
and it crashes with slime, no matter what version. Seems to be a
general problem with 2.49.

Thanks, that's good to know.

I tried it on Slackware 15.0 with 2.49, and slime worked fine, but this
was slime 2.28. So a stable release from a couple of years ago.

Actually, Slackware 15.0 doesn't have the released 2.49 either, but some snapshot, I think. Look at my version number:

% clisp --help | sed -n 2p
Usage: /usr/lib64/clisp-2.49.93+/base/lisp.run [options] [lispfile [argument ...]]

... and then my old .cache directories ...

/home/smallm/.cache/common-lisp:
drwxr-xr-x 4 smallm smallm 4096 Jul 1 20:09 .
drwxr-xr-x 42 smallm smallm 4096 Jul 1 20:06 ..
drwxr-xr-x 3 smallm smallm 4096 Aug 15 2014 clisp-2.49-unix-x64
drwxr-xr-x 3 smallm smallm 4096 Feb 13 2024 clisp-2.49.93+-unix-x64

And if there is any doubt, here is the top of the file from /var/log/packages...

PACKAGE NAME: clisp-2.50_20191103_c26de7873-x86_64-5
COMPRESSED PACKAGE SIZE: 3.0M
UNCOMPRESSED PACKAGE SIZE: 26M
PACKAGE LOCATION: /mnt/slackware64/d/clisp-2.50_20191103_c26de7873-x86_64-5.txz

So I think you have to go back to the 14.2 Changelog to find the
officially released version:

Tue Apr 21 23:44:00 UTC 2015
...
d/clisp-2.49-x86_64-3.txz: Rebuilt.

with the first clisp entry in 15.0's changelog being a snapshot he
"Upgraded" to...

Thu Jan 12 01:15:52 UTC 2017
...
d/clisp-2.49.20161111-x86_64-1.txz: Upgraded.

and the first giving it a 2.50 version number ...

Tue Dec 31 05:17:04 UTC 2019
...
d/clisp-2.50_20191103_c26de7873-x86_64-1.txz: Upgraded.

- Mike Sm.

p.s. Happy Canada Day to whomever
--- Synchronet 3.21d-Linux NewsLink 1.2