[syslog-ng] cleaning up the unofficial rpm repositories

Peter Czanik (pczanik) Peter.Czanik at oneidentity.com
Thu Sep 5 07:26:40 UTC 2019


Hi,

If you prefer twitter polls instead of writing e-mails, here is your chance to cast your vote: https://twitter.com/PCzanik/status/1169511289246404609 🙂

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

________________________________
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 9:13 AM
To: syslog-ng at lists.balabit.hu <syslog-ng at lists.balabit.hu>
Subject: [syslog-ng] cleaning up the unofficial rpm repositories

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.

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://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsyslog-ng.com%2Fcommunity%2F&data=02%7C01%7Cpeter.czanik%40oneidentity.com%7C0f5f7086d6ae4e5762f508d731d0a179%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637032644462488996&sdata=z7w1mBKgI6nWHk60cQs11FkV4%2BS4a3DLIQ41%2Fz%2BO%2FK0%3D&reserved=0>
https://twitter.com/PCzanik<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2FPCzanik&data=02%7C01%7Cpeter.czanik%40oneidentity.com%7C0f5f7086d6ae4e5762f508d731d0a179%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637032644462488996&sdata=5GhpZuPQkdbFyuuP2XeFhH%2FJNYA%2BMPF3v5GNqT1hI1Q%3D&reserved=0>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20190905/ee377796/attachment-0001.html>


More information about the syslog-ng mailing list