Needless to say, that such files should *not* be in a release tarball.

Am Do., 28. Aug. 2025 um 23:30 Uhr schrieb Michael Biebl <[email protected]>:
>
> Hi,
>
> I've looked at 
> https://www.rsyslog.com/files/download/rsyslog/rsyslog-8.2508.0.tar.gz
>
> The doc directory (in the release tarball) contains some temporary files like
>
> doc/source/_ext/__pycache__
> doc/source/_ext/__pycache__/rsyslog_lexer.cpython-312.pyc
> doc/source/_ext/__pycache__/edit_on_github.cpython-312.pyc
> doc/source/__pycache__
> doc/source/__pycache__/conf_helpers.cpython-312.pyc
> doc/source/about/ai_first.rst.rej
> doc/source/about/ai_first.rst.orig
> doc/ai/.module_map.yaml.swp
>
> I do not see this in the git repository, so I wonder how the release
> tarball was created. It doesn't look like an automated process.
> Also, a corresponding git tag is missing at
> https://github.com/rsyslog/rsyslog/tags
>
> Regards,
> Michael
>
> Am Di., 26. Aug. 2025 um 20:08 Uhr schrieb Rainer Gerhards via rsyslog
> <[email protected]>:
> >
> > HI all,
> >
> > it is a pleasure for me to announce the possibly largest scheduled
> > stable release we possibly ever made. It's so large that I can provide
> > only a quick overview. For full details pls see:
> >
> >    https://www.rsyslog.com/rsyslog-8-2508-0-2025-08-release-announcement/
> >
> > While it is large, it is well-tested as always. Lots of the commits
> > already run via the daily stable in the field.
> >
> > RHEL & co packages are still in the build process - we had some fuzz with 
> > them.
> >
> > #######################################################
> > Maintaners note: rsyslog-doc has been integrated into the main repo!
> >
> > ** These is no longer a dedicated doc tarball! ** - instead see doc/
> > in main tarball.
> > #######################################################
> >
> > Now to the AI generated summary:
> >
> > ---
> > Date: 2025-08-26
> > Download:
> > https://www.rsyslog.com/files/download/rsyslog/rsyslog-8.2508.0.tar.gz
> > Packages: project builds in progress, expected later today
> >
> > Highlights
> > - Cloud/observability: Prometheus stats; imhttp health; docker
> >   tree merged; omhttp on OMODTX.
> > - Core/networking: tcpsrv refactor; imtcp race fixes; timing
> >   correction.
> > - Security/safety: omelasticsearch 401/403 handling; TLS
> >   diagnostics; PrioritizeSAN; net_ossl leak fix; gtls warn dedup.
> > - Language/pipeline: ${VAR} in backticks; endswith(); headerless
> >   pmrfc3164; new fmpcre; mmaitag PoC.
> > - Inputs/outputs: imfile deleteStateOnFileMove; omazureventhubs
> >   snprintf.
> >
> > Breaking/actionable
> > - Docs live in repo under doc/ (no separate doc tarball).
> > - omsendertrack: use senderid= (was template=); statefile
> >   required. Default senderid yields %fromhost-ip%.
> >
> > AI First
> > - AI-assisted changes pass the same reviews and CI. Low quality
> >   output is rejected.
> >
> > Thanks
> > - Attila Lakatos (cropi), Corey Siltala, Maks Maltsev, xietangxin.
> > ---
> >
> > I hope is useful. Expect much more to come in the next months!
> >
> > Rainer
> > _______________________________________________
> > 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.

Reply via email to