RHEL 6.10 was released today and building CentOS 6.10 has just started. This would be an excellent time to remove any EOL software you may have floating around on mirror.centos.org.
SIGs should explicitly state which content they want copied over from 6.9 to 6.10.
I'd imagine that for example openstack-juno could be dropped because it went EOL in 2015-12-07 (so actually prior to CentOS 6.8's release..). Is there some other content that could be dropped?
If SIGs want to transfer some of their packages from 6.9 to 6.10, please let hughesjr know. You can probably simply reply to this message to let people know of your decision. Content to be transferred over to 6.10 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/6.9/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 6.9, including any EOL content, will be archived to vault.centos.org, and that content will be available in the vault indefinitely. The 6.9 directory on mirror.centos.org will be emptied some time after 6.10 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 6.10 when that time comes. Making the decisions now would save a bit of time at 6.10 release time.
cloud/x86_64/openstack-juno cloud/x86_64/openstack-juno/common sclo/x86_64/rh/devassist09 sclo/x86_64/rh/devtoolset-3 sclo/x86_64/rh/devtoolset-4 sclo/x86_64/rh/devtoolset-6 sclo/x86_64/rh/devtoolset-7 sclo/x86_64/rh/git19 sclo/x86_64/rh/httpd24 sclo/x86_64/rh/mariadb55 sclo/x86_64/rh/maven30 sclo/x86_64/rh/mongodb24 sclo/x86_64/rh/mysql55 sclo/x86_64/rh/nginx16 sclo/x86_64/rh/nodejs010 sclo/x86_64/rh/perl516 sclo/x86_64/rh/php54 sclo/x86_64/rh/php55 sclo/x86_64/rh/postgresql92 sclo/x86_64/rh/python27 sclo/x86_64/rh/python33 sclo/x86_64/rh/rh-git29 sclo/x86_64/rh/rh-java-common sclo/x86_64/rh/rh-mariadb100 sclo/x86_64/rh/rh-mariadb101 sclo/x86_64/rh/rh-mariadb102 sclo/x86_64/rh/rh-maven33 sclo/x86_64/rh/rh-mongodb26 sclo/x86_64/rh/rh-mongodb30upg sclo/x86_64/rh/rh-mongodb32 sclo/x86_64/rh/rh-mongodb34 sclo/x86_64/rh/rh-mysql56 sclo/x86_64/rh/rh-mysql57 sclo/x86_64/rh/rh-nginx18 sclo/x86_64/rh/rh-nginx110 sclo/x86_64/rh/rh-nodejs4 sclo/x86_64/rh/rh-nodejs6 sclo/x86_64/rh/rh-passenger40 sclo/x86_64/rh/rh-perl520 sclo/x86_64/rh/rh-perl524 sclo/x86_64/rh/rh-php56 sclo/x86_64/rh/rh-php70 sclo/x86_64/rh/rh-postgresql94 sclo/x86_64/rh/rh-postgresql95 sclo/x86_64/rh/rh-postgresql96 sclo/x86_64/rh/rh-python34 sclo/x86_64/rh/rh-python35 sclo/x86_64/rh/rh-python36 sclo/x86_64/rh/rh-redis32 sclo/x86_64/rh/rh-ror41 sclo/x86_64/rh/rh-ror42 sclo/x86_64/rh/rh-ror50 sclo/x86_64/rh/rh-ruby22 sclo/x86_64/rh/rh-ruby23 sclo/x86_64/rh/rh-ruby24 sclo/x86_64/rh/rh-scala210 sclo/x86_64/rh/rh-thermostat16 sclo/x86_64/rh/rh-varnish4 sclo/x86_64/rh/ror40 sclo/x86_64/rh/ruby193 sclo/x86_64/rh/ruby200 sclo/x86_64/rh/thermostat1 sclo/x86_64/rh/v8314 sclo/x86_64/sclo/sclo-git25 sclo/x86_64/sclo/sclo-git212 sclo/x86_64/sclo/sclo-httpd24more sclo/x86_64/sclo/sclo-php54 sclo/x86_64/sclo/sclo-php55 sclo/x86_64/sclo/sclo-php56 sclo/x86_64/sclo/sclo-php70 sclo/x86_64/sclo/sclo-python27 sclo/x86_64/sclo/sclo-python34 sclo/x86_64/sclo/sclo-python35 sclo/x86_64/sclo/sclo-ror42 sclo/x86_64/sclo/sclo-subversion19 storage/x86_64/gluster-3.6 storage/x86_64/gluster-3.7 storage/x86_64/gluster-3.8 storage/x86_64/gluster-3.9 storage/x86_64/gluster-3.10 storage/x86_64/gluster-3.12 storage/x86_64/gluster-3.13 storage/x86_64/gluster-4.0 storage/x86_64/gluster-4.1 virt/x86_64/xen-44 virt/x86_64/xen-46 virt/x86_64/xen-48
Anssi Johansson kirjoitti 19.6.2018 klo 13.48:
RHEL 6.10 was released today and building CentOS 6.10 has just started. This would be an excellent time to remove any EOL software you may have floating around on mirror.centos.org.
SIGs should explicitly state which content they want copied over from 6.9 to 6.10.
I'd imagine that for example openstack-juno could be dropped because it went EOL in 2015-12-07 (so actually prior to CentOS 6.8's release..). Is there some other content that could be dropped?
If SIGs want to transfer some of their packages from 6.9 to 6.10, please let hughesjr know. You can probably simply reply to this message to let people know of your decision. Content to be transferred over to 6.10 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/6.9/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 6.9, including any EOL content, will be archived to vault.centos.org, and that content will be available in the vault indefinitely. The 6.9 directory on mirror.centos.org will be emptied some time after 6.10 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 6.10 when that time comes. Making the decisions now would save a bit of time at 6.10 release time.
cloud/x86_64/openstack-juno cloud/x86_64/openstack-juno/common sclo/x86_64/rh/devassist09 sclo/x86_64/rh/devtoolset-3 sclo/x86_64/rh/devtoolset-4 sclo/x86_64/rh/devtoolset-6 sclo/x86_64/rh/devtoolset-7 sclo/x86_64/rh/git19 sclo/x86_64/rh/httpd24 sclo/x86_64/rh/mariadb55 sclo/x86_64/rh/maven30 sclo/x86_64/rh/mongodb24 sclo/x86_64/rh/mysql55 sclo/x86_64/rh/nginx16 sclo/x86_64/rh/nodejs010 sclo/x86_64/rh/perl516 sclo/x86_64/rh/php54 sclo/x86_64/rh/php55 sclo/x86_64/rh/postgresql92 sclo/x86_64/rh/python27 sclo/x86_64/rh/python33 sclo/x86_64/rh/rh-git29 sclo/x86_64/rh/rh-java-common sclo/x86_64/rh/rh-mariadb100 sclo/x86_64/rh/rh-mariadb101 sclo/x86_64/rh/rh-mariadb102 sclo/x86_64/rh/rh-maven33 sclo/x86_64/rh/rh-mongodb26 sclo/x86_64/rh/rh-mongodb30upg sclo/x86_64/rh/rh-mongodb32 sclo/x86_64/rh/rh-mongodb34 sclo/x86_64/rh/rh-mysql56 sclo/x86_64/rh/rh-mysql57 sclo/x86_64/rh/rh-nginx18 sclo/x86_64/rh/rh-nginx110 sclo/x86_64/rh/rh-nodejs4 sclo/x86_64/rh/rh-nodejs6 sclo/x86_64/rh/rh-passenger40 sclo/x86_64/rh/rh-perl520 sclo/x86_64/rh/rh-perl524 sclo/x86_64/rh/rh-php56 sclo/x86_64/rh/rh-php70 sclo/x86_64/rh/rh-postgresql94 sclo/x86_64/rh/rh-postgresql95 sclo/x86_64/rh/rh-postgresql96 sclo/x86_64/rh/rh-python34 sclo/x86_64/rh/rh-python35 sclo/x86_64/rh/rh-python36 sclo/x86_64/rh/rh-redis32 sclo/x86_64/rh/rh-ror41 sclo/x86_64/rh/rh-ror42 sclo/x86_64/rh/rh-ror50 sclo/x86_64/rh/rh-ruby22 sclo/x86_64/rh/rh-ruby23 sclo/x86_64/rh/rh-ruby24 sclo/x86_64/rh/rh-scala210 sclo/x86_64/rh/rh-thermostat16 sclo/x86_64/rh/rh-varnish4 sclo/x86_64/rh/ror40 sclo/x86_64/rh/ruby193 sclo/x86_64/rh/ruby200 sclo/x86_64/rh/thermostat1 sclo/x86_64/rh/v8314 sclo/x86_64/sclo/sclo-git25 sclo/x86_64/sclo/sclo-git212 sclo/x86_64/sclo/sclo-httpd24more sclo/x86_64/sclo/sclo-php54 sclo/x86_64/sclo/sclo-php55 sclo/x86_64/sclo/sclo-php56 sclo/x86_64/sclo/sclo-php70 sclo/x86_64/sclo/sclo-python27 sclo/x86_64/sclo/sclo-python34 sclo/x86_64/sclo/sclo-python35 sclo/x86_64/sclo/sclo-ror42 sclo/x86_64/sclo/sclo-subversion19 storage/x86_64/gluster-3.6 storage/x86_64/gluster-3.7 storage/x86_64/gluster-3.8 storage/x86_64/gluster-3.9 storage/x86_64/gluster-3.10 storage/x86_64/gluster-3.12 storage/x86_64/gluster-3.13 storage/x86_64/gluster-4.0 storage/x86_64/gluster-4.1 virt/x86_64/xen-44 virt/x86_64/xen-46 virt/x86_64/xen-48
*tap* *tap* *tap* Is this thing on? I haven't seen any reactions to this email yet.
On Tue, Jun 19, 2018 at 01:48:34PM +0300, Anssi Johansson wrote:
RHEL 6.10 was released today and building CentOS 6.10 has just started. This would be an excellent time to remove any EOL software you may have floating around on mirror.centos.org.
SIGs should explicitly state which content they want copied over from 6.9 to 6.10.
I'd imagine that for example openstack-juno could be dropped because it went EOL in 2015-12-07 (so actually prior to CentOS 6.8's release..). Is there some other content that could be dropped?
If SIGs want to transfer some of their packages from 6.9 to 6.10, please let hughesjr know. You can probably simply reply to this message to let people know of your decision. Content to be transferred over to 6.10 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/6.9/extras/x86_64/Packages/ , perhaps some of those could be trimmed as well.
All versions of centos-release-gluster310 and lower can be removed. Ideally centos-release-gluster-legacy gets included before that time (tagged in the CBS already, waiting for Johnny finishing some 6.10 work).
storage/x86_64/gluster-3.6 storage/x86_64/gluster-3.7 storage/x86_64/gluster-3.8 storage/x86_64/gluster-3.9 storage/x86_64/gluster-3.10
.. (skipping 3.12)
storage/x86_64/gluster-3.13 storage/x86_64/gluster-4.0
These are now unmaintained as other Long Term Maintenance releases are available (3.12 and 4.1). The repositories can be removed.
Thanks! Niels
I believe the following SCLs can be dropped now, since they are EOL:
sclo/x86_64/rh/devassist09 sclo/x86_64/rh/devtoolset-3 sclo/x86_64/rh/devtoolset-4 sclo/x86_64/rh/git19 sclo/x86_64/rh/mariadb55 sclo/x86_64/rh/maven30 sclo/x86_64/rh/mongodb24 sclo/x86_64/rh/mysql55 sclo/x86_64/rh/nginx16 sclo/x86_64/rh/nodejs010 sclo/x86_64/rh/perl516 sclo/x86_64/rh/php54 sclo/x86_64/rh/php55 sclo/x86_64/rh/postgresql92 sclo/x86_64/rh/python33 sclo/x86_64/rh/rh-mariadb100 sclo/x86_64/rh/rh-maven33 sclo/x86_64/rh/rh-mongodb26 sclo/x86_64/rh/rh-mongodb30upg sclo/x86_64/rh/rh-mysql56 sclo/x86_64/rh/rh-nodejs4 sclo/x86_64/rh/rh-passenger40 sclo/x86_64/rh/rh-perl520 sclo/x86_64/rh/rh-php56 sclo/x86_64/rh/rh-postgresql94 sclo/x86_64/rh/rh-python34 sclo/x86_64/rh/rh-ror41 sclo/x86_64/rh/rh-ruby22 sclo/x86_64/rh/rh-thermostat16 sclo/x86_64/rh/ror40 sclo/x86_64/rh/ruby193 sclo/x86_64/rh/ruby200 sclo/x86_64/rh/thermostat1 sclo/x86_64/rh/v8314 sclo/x86_64/sclo/sclo-php54 sclo/x86_64/sclo/sclo-php55 sclo/x86_64/sclo/sclo-php56 sclo/x86_64/sclo/sclo-python34
Honza
On 06/19/2018 12:48 PM, Anssi Johansson wrote:
RHEL 6.10 was released today and building CentOS 6.10 has just started. This would be an excellent time to remove any EOL software you may have floating around on mirror.centos.org.
SIGs should explicitly state which content they want copied over from 6.9 to 6.10.
I'd imagine that for example openstack-juno could be dropped because it went EOL in 2015-12-07 (so actually prior to CentOS 6.8's release..). Is there some other content that could be dropped?
If SIGs want to transfer some of their packages from 6.9 to 6.10, please let hughesjr know. You can probably simply reply to this message to let people know of your decision. Content to be transferred over to 6.10 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/6.9/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 6.9, including any EOL content, will be archived to vault.centos.org, and that content will be available in the vault indefinitely. The 6.9 directory on mirror.centos.org will be emptied some time after 6.10 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 6.10 when that time comes. Making the decisions now would save a bit of time at 6.10 release time.
cloud/x86_64/openstack-juno cloud/x86_64/openstack-juno/common sclo/x86_64/rh/devassist09 sclo/x86_64/rh/devtoolset-3 sclo/x86_64/rh/devtoolset-4 sclo/x86_64/rh/devtoolset-6 sclo/x86_64/rh/devtoolset-7 sclo/x86_64/rh/git19 sclo/x86_64/rh/httpd24 sclo/x86_64/rh/mariadb55 sclo/x86_64/rh/maven30 sclo/x86_64/rh/mongodb24 sclo/x86_64/rh/mysql55 sclo/x86_64/rh/nginx16 sclo/x86_64/rh/nodejs010 sclo/x86_64/rh/perl516 sclo/x86_64/rh/php54 sclo/x86_64/rh/php55 sclo/x86_64/rh/postgresql92 sclo/x86_64/rh/python27 sclo/x86_64/rh/python33 sclo/x86_64/rh/rh-git29 sclo/x86_64/rh/rh-java-common sclo/x86_64/rh/rh-mariadb100 sclo/x86_64/rh/rh-mariadb101 sclo/x86_64/rh/rh-mariadb102 sclo/x86_64/rh/rh-maven33 sclo/x86_64/rh/rh-mongodb26 sclo/x86_64/rh/rh-mongodb30upg sclo/x86_64/rh/rh-mongodb32 sclo/x86_64/rh/rh-mongodb34 sclo/x86_64/rh/rh-mysql56 sclo/x86_64/rh/rh-mysql57 sclo/x86_64/rh/rh-nginx18 sclo/x86_64/rh/rh-nginx110 sclo/x86_64/rh/rh-nodejs4 sclo/x86_64/rh/rh-nodejs6 sclo/x86_64/rh/rh-passenger40 sclo/x86_64/rh/rh-perl520 sclo/x86_64/rh/rh-perl524 sclo/x86_64/rh/rh-php56 sclo/x86_64/rh/rh-php70 sclo/x86_64/rh/rh-postgresql94 sclo/x86_64/rh/rh-postgresql95 sclo/x86_64/rh/rh-postgresql96 sclo/x86_64/rh/rh-python34 sclo/x86_64/rh/rh-python35 sclo/x86_64/rh/rh-python36 sclo/x86_64/rh/rh-redis32 sclo/x86_64/rh/rh-ror41 sclo/x86_64/rh/rh-ror42 sclo/x86_64/rh/rh-ror50 sclo/x86_64/rh/rh-ruby22 sclo/x86_64/rh/rh-ruby23 sclo/x86_64/rh/rh-ruby24 sclo/x86_64/rh/rh-scala210 sclo/x86_64/rh/rh-thermostat16 sclo/x86_64/rh/rh-varnish4 sclo/x86_64/rh/ror40 sclo/x86_64/rh/ruby193 sclo/x86_64/rh/ruby200 sclo/x86_64/rh/thermostat1 sclo/x86_64/rh/v8314 sclo/x86_64/sclo/sclo-git25 sclo/x86_64/sclo/sclo-git212 sclo/x86_64/sclo/sclo-httpd24more sclo/x86_64/sclo/sclo-php54 sclo/x86_64/sclo/sclo-php55 sclo/x86_64/sclo/sclo-php56 sclo/x86_64/sclo/sclo-php70 sclo/x86_64/sclo/sclo-python27 sclo/x86_64/sclo/sclo-python34 sclo/x86_64/sclo/sclo-python35 sclo/x86_64/sclo/sclo-ror42 sclo/x86_64/sclo/sclo-subversion19 storage/x86_64/gluster-3.6 storage/x86_64/gluster-3.7 storage/x86_64/gluster-3.8 storage/x86_64/gluster-3.9 storage/x86_64/gluster-3.10 storage/x86_64/gluster-3.12 storage/x86_64/gluster-3.13 storage/x86_64/gluster-4.0 storage/x86_64/gluster-4.1 virt/x86_64/xen-44 virt/x86_64/xen-46 virt/x86_64/xen-48 _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Anssi Johansson kirjoitti 19.6.2018 klo 13.48:
RHEL 6.10 was released today and building CentOS 6.10 has just started. This would be an excellent time to remove any EOL software you may have floating around on mirror.centos.org.
SIGs should explicitly state which content they want copied over from 6.9 to 6.10.
[snip]
Thanks for the lists. Outside this mailing list thread, I have received information that cloud/x86_64/openstack-juno and virt/x86_64/xen-44 can be archived and not copied over to 6.10. The respective centos-release-* packages will also be removed from extras. I think we've now gathered enough information about SIG content for this release cycle.
Note that a similar process is likely to happen for the next point releases as well. So when RHEL 7.6 gets released, SIGs should have a look at the packages they ship and inform us which packages are still supported and which ones should be dropped. Doing this within around a week of RHEL's point release would give us sufficient time to arrange for the SIG bits to be included in the respective CentOS 7.6.19xx point release.
Thanks!
-
Anssi Johansson -
Honza Horak -
Niels de Vos