I downloaded and installed the source RPM from Terebithia.  The pristine tarball included in that matches the 4.3-master tarball from Sourceforge, in both size and md5sum, and there are a ton of patch files as well.  Some of the patches relate to the backfeed queue, not sure about the remainder.  Possibly the patches are backported from 4.4-alpha?  

I don't know the first thing about making Ubuntu/Debian packages, but I can make RPMs.

Ralph Mitchell

On Sun, Jan 18, 2026 at 8:55 AM Nicola <canne74@gmail.com> wrote:

I agree building for (at least) ubuntu-latest is a good start, but I would also add some RPM variant before publishing

Nicola

Mastodon: @nic@mathstodon.xyz

Il giorno dom 18 gen 2026 alle ore 12:35 Roland Rosenfeld <roland@spinnaker.de> ha scritto:

On Fr, 16 Jan 2026, Bruno Manzoni wrote:

> - Migrate source control from SVN/SourceForge to GitHub as the
>   primary workflow.

This seems to be done in https://github.com/xymon-monitoring/xymon

> - Establish a clean, shared Git workflow with clear governance.

There is much to do, but a first build pipeline (does only a build of
client and server, without creating packages or testing) was suggested
in https://github.com/xymon-monitoring/xymon/pull/4 Maybe some of you
finds time to review this.

> - Incorporate pending patches and publish a new 4.3.x release.

I started with these by creating some merge requests (the most
important and generic patches from the Debian repository), see
https://github.com/xymon-monitoring/xymon/pulls Looking for reviewers
of these.

> - Address technical debt (PCRE2 migration, build warnings,
>   compatibility issues).

A merge request for PCRE2 is in
https://github.com/xymon-monitoring/xymon/pull/5

> FEEDBACK AND INITIATIVES REQUESTED
> - Does the current branch model (`main` = 4.3.x stable, `4.x-master`
>   = 4.4 development) make sense?

For me that's okay.  I'm open for alternative names of '4.x-master'
(maybe 'devel' or the like?), but I don't think that this is really
relevant.

> - What should be prioritized next: patch integration, CI/CD setup,
>   packaging, testing, or documentation?

>From my point of view, patch integration and fixing build warnings and
the like has highest priority.  It would be great to have a 4.3.31
without architectural changes but with the current painpoints fixed.

I noticed that the RPM distributions (Fedora/RedHat/CentOS/SuSE)
currently don't seem to package xymon themselves.  Users of these
distributions have to use packages from J.C.'s
https://terabithia.org/xymon/ 3rd party repository.

But this seems to have stopped beeing updated after fc38, maybe
because of the PCRE2 incompatibility of newer OS distributions?

Without knowing, whether J.C. will continue to update this repository
in the future (his last vital sign on the xymon list was nearly two
years ago), we should think about building/providing at least RPM
packages via pipeline.

One open question to me is, why J.C. (as the person, who released
upstream 4.3.30) applied that many patches in
https://terabithia.org/xymon/f38/SRPMS/xymon-4.3.30-1.fc38.src.rpm,
that do not seem to be applied upstream.  Seems that we should review
them for integration into main, to find out whether they are RPM
specific or whether they are useful for everybody.

Greetings
Roland
_______________________________________________
Xymon mailing list -- xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com

_______________________________________________
Xymon mailing list -- xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com

_______________________________________________
Xymon mailing list -- xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com