Julien, there was a permission issue. For me, this is now fixed. Let me know if you still have issues downloading.
Rainer El mié, 15 oct 2025 a las 12:50, Julien Thomas (<[email protected]>) escribió: > > For information, I just noticed while trying to build that > https://www.liblognorm.com/files/download/liblognorm-2.0.7.tar.gz is a 404. > > Regards, > Julien > > > > On 15/10/2025 09:46, Julien Thomas via rsyslog wrote: > > Thank you. > > > > I saw you also released liblognorm 2.0.7, great if you got a bit of > > time for this project. > > > > Would it be possible to merge those patches, critical to our setups? > > Also that way, with an official release, maybe standard distro-shipped > > debian packages would be updated and usable in production (segfault + > > memory leak). > > > > * > > https://github.com/zenetys/rpm-rsyslog/blob/master/SOURCES/liblognorm-custom-type-memory-leak.patch > > https://github.com/rsyslog/liblognorm/pull/341 (merics) > > https://github.com/rsyslog/liblognorm/pull/343 (ontholerian) > > https://github.com/rsyslog/liblognorm/issues/223 (Amorik) > > > > > > * > > https://github.com/zenetys/rpm-rsyslog/blob/master/SOURCES/liblognorm-string-perm-chars-overflow.patch > > https://github.com/rsyslog/liblognorm/pull/364 > > https://github.com/rsyslog/liblognorm/issues/340 (here referenced > > patch from EHerzog76 is a bit different and drowned with > > non-relevant changes but I think this approach is similar) > > > > That would also allow you to cleanup and some long time issues / pulls ;) > > > > Cheers, > > > > Julien > > > > > > On 15/10/2025 08:37, Rainer Gerhards wrote: > >> It is now present. > >> > >> I do the tagging only after everything went well (because if not I > >> need to make adjustments to lead to code changes). I had to leave > >> earlier yesterday due to my civic duties. So I didn't manage to do it > >> yesterday after the release. > >> > >> Sorry for the disruption. > >> > >> Rainer > >> > >> El mié, 15 oct 2025 a las 8:05, Julien Thomas via rsyslog > >> (<[email protected] <mailto:[email protected]>>) > >> escribió: > >> > >> Hello Florian, > >> > >> Is the tag missing on github repo or am I mistaking? > >> > >> Cheers, > >> Julien > >> > >> > >> > >> > >> Le 14 octobre 2025 18:00:55 GMT+02:00, Florian Riedl via rsyslog > >> <[email protected] <mailto:[email protected]>> a > >> écrit : > >> >We are pleased to announce rsyslog 8.2510.0 (aka 2025.10). > >> > > >> >This release focuses on better Windows Security event parsing, > >> >easier JSON handling, improved compatibility with modern > >> >Elasticsearch and Kafka, and numerous documentation and CI updates. > >> > > >> >Highlights: > >> >- new module mmsnareparse for structured Windows Security event > >> logs > >> >- mmjsonparse: new find-json mode for embedded JSON > >> >- mmjsontransform: experimental module for dotted-key un/flatten > >> >- template: new option.jsonftree for nested JSON output > >> >- omelasticsearch: auto-detect ES/OpenSearch version, typeless by > >> default > >> >- omkafka: restored compatibility with older librdkafka > >> >- imhttp: /health and /metrics endpoints now support Basic Auth > >> >- new message property fromhost-port and clearer imtcp TLS errors > >> >- new RainerScript functions: b64_decode() and toupper() > >> >- build and CI: openEuler 24.03 LTS added, doc spellcheck, > >> security checks > >> >- various bugfixes and refactoring for clarity and stability > >> > > >> >Full details are available at: > >> >https://www.rsyslog.com/rsyslog-8-2510-0-2025-10-released/ > >> > > >> >As always, we recommend testing in a staging environment before > >> >production rollout. Packages for RHEL/CentOS and Ubuntu are readily > >> >available > >> >as well. > >> > > >> >Best regards, > >> >The rsyslog team > >> >_______________________________________________ > >> >rsyslog mailing list > >> >https://lists.adiscon.net/mailman/listinfo/rsyslog > >> >http://www.rsyslog.com/professional-services/ > >> >What's up with rsyslog? Follow https://twitter.com/rgerhards > >> >NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a > >> myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT > >> POST if you DON'T LIKE THAT. > >> _______________________________________________ > >> rsyslog mailing list > >> https://lists.adiscon.net/mailman/listinfo/rsyslog > >> http://www.rsyslog.com/professional-services/ > >> What's up with rsyslog? Follow https://twitter.com/rgerhards > >> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a > >> myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT > >> POST if you DON'T LIKE THAT. > >> > > > > _______________________________________________ > > rsyslog mailing list > > https://lists.adiscon.net/mailman/listinfo/rsyslog > > http://www.rsyslog.com/professional-services/ > > What's up with rsyslog? Follow https://twitter.com/rgerhards > > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a > > myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST > > if you DON'T LIKE THAT. _______________________________________________ rsyslog mailing list https://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
