On 01/11/2018 10:01, Anssi Johansson wrote:
So here we go again. As one of the virtues of a programmer is laziness,
Content to be transferred over to 7.6.1810 can be specified either by directory name, or by individual package names.
There are also various centos-release-* packages in extras, http://mirror.centos.org/centos/7.5.1804/extras/x86_64/Packages/ , perhaps some of those could be trimmed as well.
You should also communicate to your users in advance that the EOL packages will disappear, and if necessary, instruct them to migrate to a newer supported version. Having instructions for that procedure published somewhere would be nice.
The old content under 7.5.1804, including any EOL content, will be archived to vault.centos.org, and that content will be available in the vault indefinitely. The 7.5.1804 directory on mirror.centos.org will be emptied some time after 7.6.1810 is released.
For reference and inspiration, here are some directories from mirror.centos.org, including both up-to-date content and potentially EOL content. SIGs should review the list to make sure these directories can be copied over to 7.6.1810 when that time comes. Making the decisions now would save a bit of time at 7.6.1810 release time.
opstools/x86_64/common opstools/x86_64/fluentd opstools/x86_64/logging opstools/x86_64/perfmon opstools/x86_64/sensu
Hello,
for the opstools SIG I would like to get all the dirs copied over, but NOT:
opstools/x86_64/common/centos-release-opstools opstools/x86_64/common/libuv* opstools/x86_64/common/nodejs* opstools/x86_64/perfmon/phantomjs-1.9.7-3.el7.x86_64.rpm
and only copying over the latest version of a package would be good. There are multiple collectd versions, or 9 skydive versions now accumulated.
Thank you.
Matthias Matthias