Hi,

It took a bit longer than expected (three conferences and holidays), but at least I can be sure that 3.24.1 really works nice and stable 🙂 My syslog-ng-stable RPM repositories are now upgraded to 3.24.1:

As this is the first update in these repositories, I'm very interested in any feedback -- both negative and positive -- you have with these repositories!

By the time of this writing I already tested the update on CentOS 7, but I'm still waiting for the openSUSE build to finish.

Bye,

Peter Czanik (CzP) <peter.czanik@oneidentity.com>
Balabit (a OneIdentity company) / syslog-ng upstream
https://syslog-ng.com/community/
https://twitter.com/PCzanik


From: Peter Czanik (pczanik)
Sent: Thursday, September 12, 2019 11:46
To: syslog-ng@lists.balabit.hu <syslog-ng@lists.balabit.hu>
Subject: syslog-ng-stable RPM repo
 
Hi,

Until now I had a single request for a syslog-ng-stable repo, which always contains the latest stable release of syslog-ng. But the discussion about my cleanup plans brought up the topic again, and Bazsi wrote me, that there were more such requests coming from the Splunk Slack channel. So I did it:

In theory it should be the exact copy of my unofficial 3.23.1 packages and some fixes backported for openSUSE Tumbleweed.

New syslog-ng versions will first appear in versioned repositories, as usual. I plan to push packages to the stable repo only after a week or two delay, so there is time find major bugs, have a .2 release if necessary.

Once we have more experience that it works as expected, I'll update my blogs and the syslog-ng website. Until that I'm waiting for your feedback, especially once 3.24.1 comes out.

Peter

Peter Czanik (CzP) <peter.czanik@oneidentity.com>
Balabit (a OneIdentity company) / syslog-ng upstream
https://syslog-ng.com/community/
https://twitter.com/PCzanik