On Jan 18, 2026, at 4:58 PM, Roland Rosenfeld <user-237a1e03bc39@xymon.invalid> wrote:
Hi Mark!
On Sun, 18 Jan 2026, Mark Felder via Xymon wrote:
It would be great to have a 4.3.31 without architectural changes
but with the current painpoints fixed.
I agree. I think 4.3.31 as our test run should be a roll up of
patches collected by distros and other small patches that have been
floating around which don't risk changing behavior or build
dependencies. That would exclude the PCRE2 change for this release
as we don't know how this will affect non-Linux/BSD platforms. It
should be fine as PCRE2 has been around a long time, but nobody has
ever tried to build it on e.g., Solaris yet
But not upgrading to PCRE2 but staying with the old library, which was
last updated 2021-06-22 (8.45) and is now officially "no longer being
actively maintained" (see https://www.pcre.org/ <https:// www.pcre.org/>) means, that RHEL 10
and Debian 13 (trixie) are no longer supported, since these do no
longer ship the old pcre library.
BTW: pcre2 was first released in 2015, so I expect that every OS
should be able to build/ship this in more than 10 years.
I have to admit, that I didn't try this out on Solaris yet, but is
there really anybody running a xymon server on Solaris nowadays? If
you only need the client (with conftype "server"), no pcre is needed
at all (only for the client with conftype "client"), so for most
users, who only need a client on a "special" OS, this shouldn't be an
issue.
A short search showed me, that pcre2 seems to be available on Solaris
10 and 11: https://www.opencsw.org/package/pcre2/ <https:// www.opencsw.org/package/pcre2/> (but I didn't try
this out myself, since I'm very happy to have shut down all Solaris
boxes last year and so I no longer have to pray, if one of them hicks
up and nobody is there to fix it).
Greetings
Roland
PS: Do you also see my mails on the ML "From: Roland Rosenfeld
<user-237a1e03bc39@xymon.invalid>"?
While I see most postings in the ML as "From: Some Name as xymon
<xymon@xymon.com>", I see myself (and some others) with their real
addresses (and get DMARC warnings, because the list breaks DKIM
(by adding a signature) and SPF (since the list server isn't
permitted for spinnaker.de)...