[syslog-ng] cleaning up the unofficial rpm repositories

[Nik Ambrosch]

I use the OS-provided syslog-ng version for normal systems but for specific
cases that need a newer version (centralized logging, web servers, etc) I
pin something newer using config management (puppet, chef, etc).  This is
why we mirror the copr repositories.  Considering that fixes are not
back-ported across all of these revisions I feel that one year (or six
revisions) is more than enough.

Your LTS version is usually whatever is maintained by your OS distribution
as opposed to something from the syslog-ng guys, but that's up to them to
decide.


On Thu, Sep 5, 2019 at 10:45 AM Laszlo Budai <laszlo.budai at outlook.com>
wrote:

> Hi!
>
> Don't really see the importance of having separated repositories for each
> syslog-ng version as you don't provide updates... (I mean without
> backporting bugfixes to these repos, this is just a version lock).
>
> But version lock does not require separated repositories: users can pin
> (yum versionlock eg.) a specific version.
>
> The result is the same...
>
> All in all, these repos do not resolve the LTS vs. rolling release issue
> (which is not really liked some of the community members :) ).
>
> L.
>
> ------------------------------
> *From:* syslog-ng <syslog-ng-bounces at lists.balabit.hu> on behalf of Peter
> Czanik (pczanik) <Peter.Czanik at oneidentity.com>
> *Sent:* Thursday, September 5, 2019, 09:14
> *To:* syslog-ng at lists.balabit.hu
> *Subject:* [syslog-ng] cleaning up the unofficial rpm repositories
>
> Hi,
>
> Ever since I started my unofficial rpm packages for (open)SUSE and
> Fedora/RHEL/CentOS I created a new repository for each new release and
> never deleted them. Of course OBS and Copr guys did sometimes clean ups, so
> Fedora and openSUSE packages for long end of life distributions got
> deleted. But for the rest there are still syslog-ng 3.5 packages on-line.
>
> Not everyone likes to update syslog-ng every second month, so I keep the
> current workflow and create a new repo for each new release. This way your
> syslog-ng.conf or package management is not accidentally broken at a random
> time with a new update, you have a chance to test a new release thoroughly
> before upgrading. On the other hand I plan to keep only a year worth of
> releases instead of everything.
>
> Question:
>
>
>    - Is there anyone, who needs packages older than one year? With the
>    one year limit I'd delete anything older than 3.17 and delete 3.17 as well,
>    once 3.24 is out, and so on.
>
> Bye,
>
> Peter Czanik (CzP) <peter.czanik at oneidentity.com>
> Balabit (a OneIdentity company) / syslog-ng upstream
> https://syslog-ng.com/community/
> https://twitter.com/PCzanik
>
>
>
> ______________________________________________________________________________
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation:
> http://www.balabit.com/support/documentation/?product=syslog-ng
> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20190905/42e44399/attachment-0001.html>