<div dir="ltr">Evan - run a configuration management agent on your hosts, you can "one click" roll out packages, repos, and config. Some common ones are puppet, chef, terraform, ansible. It's a bit of a time investment at first but an incredible time savings in the long run.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Sep 5, 2019 at 11:06 AM Evan Rempel <<a href="mailto:erempel@uvic.ca">erempel@uvic.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<div class="gmail-m_2783065561331031961moz-cite-prefix"><br>
</div>
<div class="gmail-m_2783065561331031961moz-cite-prefix">Agreed. Trying to get 100's of systems
upgraded currently requires a new repo to be added to each host.
Kind of a pain.</div>
<div class="gmail-m_2783065561331031961moz-cite-prefix">
<div class="gmail-m_2783065561331031961moz-cite-prefix">The repo structure currently in place
pushes a bunch of work onto the package consumers, for what I
can see is for no benefit. Just a make work project :-(<br>
</div>
<div class="gmail-m_2783065561331031961moz-cite-prefix"><br>
</div>
As a result, our organization sucks up all of the repos and
combines them together. Deleting your repo does not remove any
packages from my joined repo, so it makes no difference to me.</div>
<br>
<div class="gmail-m_2783065561331031961moz-cite-prefix">Evan.<br>
</div>
<div class="gmail-m_2783065561331031961moz-cite-prefix"><br>
</div>
<div class="gmail-m_2783065561331031961moz-cite-prefix">On 9/5/19 7:45 AM, Laszlo Budai wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div style="font-family:Helvetica,Arial,sans-serif;font-size:12pt;color:rgb(33,33,33);background-color:rgb(255,255,255);text-align:left" dir="ltr">
Hi!</div>
<div style="font-family:Helvetica,Arial,sans-serif;font-size:12pt;color:rgb(33,33,33);background-color:rgb(255,255,255);text-align:left" dir="ltr">
<br>
</div>
<div style="font-family:Helvetica,Arial,sans-serif;font-size:12pt;color:rgb(33,33,33);background-color:rgb(255,255,255);text-align:left" dir="ltr">
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).</div>
<div style="font-family:Helvetica,Arial,sans-serif;font-size:12pt;color:rgb(33,33,33);background-color:rgb(255,255,255);text-align:left" dir="ltr">
<br>
</div>
<div style="font-family:Helvetica,Arial,sans-serif;font-size:12pt;color:rgb(33,33,33);background-color:rgb(255,255,255);text-align:left" dir="ltr">
But version lock does not require separated repositories: <span style="font-size:12pt">users can pin (yum versionlock eg.)
a specific version. </span></div>
<div style="font-family:Helvetica,Arial,sans-serif;font-size:12pt;color:rgb(33,33,33);background-color:rgb(255,255,255);text-align:left" dir="ltr">
<span style="font-size:12pt"><br>
</span></div>
<div style="font-family:Helvetica,Arial,sans-serif;font-size:12pt;color:rgb(33,33,33);background-color:rgb(255,255,255);text-align:left" dir="ltr">
<span style="font-size:12pt">The result is the same... </span></div>
<div style="font-family:Helvetica,Arial,sans-serif;font-size:12pt;color:rgb(33,33,33);background-color:rgb(255,255,255);text-align:left" dir="ltr">
<span style="font-size:12pt"><br>
</span></div>
<div style="font-family:Helvetica,Arial,sans-serif;font-size:12pt;color:rgb(33,33,33);background-color:rgb(255,255,255);text-align:left" dir="ltr">
<span style="font-size:12pt">All in all, these repos do not
resolve the LTS vs. rolling release issue (which is not
really liked some of the community members :) ).</span></div>
<div style="font-family:Helvetica,Arial,sans-serif;font-size:12pt;color:rgb(33,33,33);background-color:rgb(255,255,255);text-align:left" dir="ltr">
<br>
</div>
<div style="font-family:Helvetica,Arial,sans-serif;font-size:12pt;color:rgb(33,33,33);background-color:rgb(255,255,255);text-align:left" dir="ltr">
L.</div>
<div id="gmail-m_2783065561331031961id-7284ed85-1f6a-4cda-8130-a252239c823f" class="gmail-m_2783065561331031961ms-outlook-mobile-reference-message">
<div style="font-family:sans-serif;font-size:13.2pt;color:rgb(0,0,0)"><br>
</div>
<hr style="display:inline-block;width:98%">
<div id="gmail-m_2783065561331031961divRplyFwdMsg" style="font-family:Helvetica,Arial,sans-serif;font-size:12pt;line-height:13pt;color:rgb(0,0,0)">
<strong>From:</strong> syslog-ng
<a class="gmail-m_2783065561331031961moz-txt-link-rfc2396E" href="mailto:syslog-ng-bounces@lists.balabit.hu" target="_blank"><syslog-ng-bounces@lists.balabit.hu></a> on behalf of
Peter Czanik (pczanik) <a class="gmail-m_2783065561331031961moz-txt-link-rfc2396E" href="mailto:Peter.Czanik@oneidentity.com" target="_blank"><Peter.Czanik@oneidentity.com></a><br>
<strong>Sent:</strong> Thursday, September 5, 2019, 09:14<br>
<strong>To:</strong> <a class="gmail-m_2783065561331031961moz-txt-link-abbreviated" href="mailto:syslog-ng@lists.balabit.hu" target="_blank">syslog-ng@lists.balabit.hu</a><br>
<strong>Subject:</strong> [syslog-ng] cleaning up the
unofficial rpm repositories<br>
</div>
<br>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Hi,</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
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.</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
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.</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Question:</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<ul>
<li>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.<br>
</li>
</ul>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Bye,<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div id="gmail-m_2783065561331031961Signature">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<div>
<div>
<div dir="ltr">Peter Czanik (CzP)
<a class="gmail-m_2783065561331031961moz-txt-link-rfc2396E" href="mailto:peter.czanik@oneidentity.com" target="_blank"><peter.czanik@oneidentity.com></a><br>
Balabit (a OneIdentity company) / syslog-ng upstream<br>
<a href="https://syslog-ng.com/community/" target="_blank">https://syslog-ng.com/community/</a><br>
<a href="https://twitter.com/PCzanik" target="_blank">https://twitter.com/PCzanik</a></div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</div>
______________________________________________________________________________<br>
Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" rel="noreferrer" target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" rel="noreferrer" target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" rel="noreferrer" target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a><br>
<br>
</blockquote></div>