[syslog-ng] Breaking changes between versions

[Peter Czanik (pczanik)]

Hi,

These are releases from many years ago, so I had to check the release notes. Normally there are no breaking changes, and we are careful about backwards compatibility. I could not find anything obvious in the release notes, so I would not expect any issues upgrading. However, as always, testing with production logs is still recommended.

If you are upgrading from one point release to another one, I assume that you use my Copr packages. The versioned repositories are provided for convenience. Larger organizations have problems with the rolling release model, and it makes staying on a fixed syslog-ng release possible. Also, I do not have any influence on how packages are signed, that is something internal to Copr. Normally only the latest syslog-ng Copr repo is actively receiving fixes (syslog-ng48 as of right now). However, we might experiment a bit here, I put this on my ToDo list.

Peter

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

________________________________
From: syslog-ng <syslog-ng-bounces at lists.balabit.hu> on behalf of Faine, Mark R. (MSFC-IS64)[AEGIS] <mark.faine at nasa.gov>
Sent: Thursday, April 17, 2025 19:43
To: Syslog-ng users' and developers' mailing list <syslog-ng at lists.balabit.hu>
Subject: [syslog-ng] Breaking changes between versions

CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe.


I need to go from 3.31.2 to 3.37.1.  Should I expect any breaking changes?



Also, Redhat Insights is reporting that syslog-ng and syslog-ng-logrotate are signed with SHA1, are the newer packages signed with SHA2?

Red Hat recommends that you adopt any of the options below:

  *   Contact vendors of the packages to ask for new builds signed with supported signatures and re-install the new packages,
  *   Resign packages with your own SHA-2 key or completely remove packages until a new build with SHA-2 signature is available from the 3rd-party vendor



Thanks,

Mark












-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20250422/87c834f6/attachment.htm>