Hey all, In order to make sure SIG content is "fresh", whenever a new version of CentOS comes out, content is discarded automatically unless SIG chairs specifically request it to be moved over. At the moment, Xen has three repos that are under consideration to be moved up: virt/x86_64/xen-46 virt/x86_64/xen-48 virt/x86_64/xen-410 I'll request xen-48 and xen-410 to be updated for sure, but I wanted to gauge how much interest there was in xen-46. If you have strong feelings about xen-46, let me know (and perhaps consider volunteering to maintain the packages). Thanks, -George ---------- Forwarded message --------- From: Anssi Johansson <avij at centosproject.org> Date: Thu, Nov 1, 2018 at 9:02 AM Subject: [CentOS-devel] SIGs: Possibility to drop EOL content at 7.6.1810 release time To: The CentOS developers mailing list. <centos-devel at centos.org> So here we go again. As one of the virtues of a programmer is laziness, I'll just cut&paste the previous email with some modifications. You know the drill. RHEL 7.6 was released a few days ago and building CentOS 7.6.1810 has just started. This would be an excellent time to remove any EOL software you may have floating around on mirror.centos.org. mirror.centos.org should have only supported packages available. SIGs should explicitly state which content they want copied over from 7.5.1804 to 7.6.1810. I'd imagine that for example ceph-jewel could be dropped because it went EOL in July 2018. Is there some other content that could be dropped? If you are planning to keep content available that has gone EOL upstream, you must commit to backport any required security fixes to it. If SIGs want to transfer some of their packages from 7.5.18004 to 7.6.1810, please let hughesjr know. You can probably simply reply to this message to let people know of your decision. It is possible that some other SIG depends on your packages that are going to be removed. In that case the other SIG should probably update their packages to depend on supported versions. 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. cloud/x86_64/openstack-ocata cloud/x86_64/openstack-pike cloud/x86_64/openstack-queens cloud/x86_64/openstack-rocky configmanagement/x86_64/ansible26 configmanagement/x86_64/yum4 dotnet nfv/x86_64/fdio/vpp/vpp-1710 nfv/x86_64/fdio/vpp/vpp-1801 nfv/x86_64/fdio/vpp/vpp-1804 nfv/x86_64/fdio/vpp/vpp-1807 opstools/x86_64/common opstools/x86_64/fluentd opstools/x86_64/logging opstools/x86_64/perfmon opstools/x86_64/sensu paas/x86_64/openshift-origin paas/x86_64/openshift-origin13 paas/x86_64/openshift-origin14 paas/x86_64/openshift-origin15 paas/x86_64/openshift-origin36 paas/x86_64/openshift-origin37 paas/x86_64/openshift-origin38 paas/x86_64/openshift-origin39 paas/x86_64/openshift-origin310 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/go-toolset-7 sclo/x86_64/rh/httpd24 sclo/x86_64/rh/llvm-toolset-7 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/passenger40 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/python34 sclo/x86_64/rh/rh-eclipse46 sclo/x86_64/rh/rh-git29 sclo/x86_64/rh/rh-haproxy18 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-maven35 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-mongodb36 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-nginx112 sclo/x86_64/rh/rh-nodejs4 sclo/x86_64/rh/rh-nodejs6 sclo/x86_64/rh/rh-nodejs8 sclo/x86_64/rh/rh-perl520 sclo/x86_64/rh/rh-perl524 sclo/x86_64/rh/rh-perl526 sclo/x86_64/rh/rh-php56 sclo/x86_64/rh/rh-php70 sclo/x86_64/rh/rh-php71 sclo/x86_64/rh/rh-postgresql10 sclo/x86_64/rh/rh-postgresql94 sclo/x86_64/rh/rh-postgresql95 sclo/x86_64/rh/rh-postgresql96 sclo/x86_64/rh/rh-python35 sclo/x86_64/rh/rh-python36 sclo/x86_64/rh/rh-redis32 sclo/x86_64/rh/rh-ror42 sclo/x86_64/rh/rh-ror50 sclo/x86_64/rh/rh-ruby23 sclo/x86_64/rh/rh-ruby24 sclo/x86_64/rh/rh-ruby25 sclo/x86_64/rh/rh-scala210 sclo/x86_64/rh/rh-thermostat16 sclo/x86_64/rh/rh-varnish4 sclo/x86_64/rh/rh-varnish5 sclo/x86_64/rh/ror40 sclo/x86_64/rh/ror41 sclo/x86_64/rh/ruby193 sclo/x86_64/rh/ruby200 sclo/x86_64/rh/ruby22 sclo/x86_64/rh/rust-toolset-7 sclo/x86_64/rh/thermostat1 sclo/x86_64/rh/v8314 sclo/x86_64/sclo/sclo-cassandra3 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-php71 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 sclo/x86_64/sclo/vagrant1 storage/x86_64/ceph-jewel storage/x86_64/ceph-luminous storage/x86_64/gluster-3.10 storage/x86_64/gluster-3.12 storage/x86_64/gluster-4.0 storage/x86_64/gluster-4.1 storage/x86_64/gluster-5 virt/x86_64/azure virt/x86_64/kubernetes19 virt/x86_64/kubernetes110 virt/x86_64/kvm-common virt/x86_64/libvirt-latest virt/x86_64/ovirt-4.2 virt/x86_64/xen-46 virt/x86_64/xen-48 virt/x86_64/xen-410 In addition to those, ovirt-4.1 should have already been removed, but it is still available in the altarch branch for aarch64 and ppc64le. This is an error, which will hopefully get fixed this round. _______________________________________________ CentOS-devel mailing list CentOS-devel at centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Pasi Kärkkäinen
2019-Feb-09 16:39 UTC
[CentOS-virt] CentOS 7.6 and Xen 4.6 / centos-release-xen broken
Hello George, On Thu, Nov 01, 2018 at 12:06:49PM +0000, George Dunlap wrote:> Hey all, > > In order to make sure SIG content is "fresh", whenever a new version > of CentOS comes out, content is discarded automatically unless SIG > chairs specifically request it to be moved over. > > At the moment, Xen has three repos that are under consideration to be moved up: > > virt/x86_64/xen-46 > virt/x86_64/xen-48 > virt/x86_64/xen-410 > > I'll request xen-48 and xen-410 to be updated for sure, but I wanted > to gauge how much interest there was in xen-46. If you have strong > feelings about xen-46, let me know (and perhaps consider volunteering > to maintain the packages). >It seems currently "centos-release-xen" package is broken in CentOS7, it points to xen-46 repo, which isn't available anymore in CentOS 7.6: http://mirror.centos.org/centos/7/virt/x86_64/ -> xen-48/ -> xen-410/ # yum clean all # yum search centos-release-xen .. centos-release-xen.x86_64 : CentOS Virt SIG Xen repo configs centos-release-xen-48.x86_64 : CentOS Virt Sig Xen repo configs for Xen 4.8 centos-release-xen-common.x86_64 : CentOS Virt Sig Xen support files .. # yum install centos-release-xen # cat /etc/yum.repos.d/CentOS-Xen.repo # CentOS-Xen.repo # # Please see http://wiki.centos.org/QaWiki/Xen4 for more # information [centos-virt-xen-46] name=CentOS-$releasever - xen baseurl=http://mirror.centos.org/centos/$releasever/virt/$basearch/xen-46 gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization [centos-virt-xen-46-testing] name=CentOS-$releasever - xen - testing baseurl=http://buildlogs.centos.org/centos/$releasever/virt/$basearch/xen-46 gpgcheck=0 enabled=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization I guess two things should happen in CentOS7: 1) Publish centos-release-xen-410 package 2) Update centos-release-xen package to point to.. 410 ? Thanks, -- Pasi> Thanks, > -George >
Pasi Kärkkäinen
2019-Feb-09 16:50 UTC
[CentOS-virt] CentOS 7.6 and Xen 4.6 / centos-release-xen broken
Hi, On Sat, Feb 09, 2019 at 06:39:59PM +0200, Pasi K?rkk?inen wrote:> Hello George, > > On Thu, Nov 01, 2018 at 12:06:49PM +0000, George Dunlap wrote: > > Hey all, > > > > In order to make sure SIG content is "fresh", whenever a new version > > of CentOS comes out, content is discarded automatically unless SIG > > chairs specifically request it to be moved over. > > > > At the moment, Xen has three repos that are under consideration to be moved up: > > > > virt/x86_64/xen-46 > > virt/x86_64/xen-48 > > virt/x86_64/xen-410 > > > > I'll request xen-48 and xen-410 to be updated for sure, but I wanted > > to gauge how much interest there was in xen-46. If you have strong > > feelings about xen-46, let me know (and perhaps consider volunteering > > to maintain the packages). > > > > It seems currently "centos-release-xen" package is broken in CentOS7, > it points to xen-46 repo, which isn't available anymore in CentOS 7.6: > > http://mirror.centos.org/centos/7/virt/x86_64/ > > -> xen-48/ > -> xen-410/ > > > # yum clean all > # yum search centos-release-xen > .. > centos-release-xen.x86_64 : CentOS Virt SIG Xen repo configs > centos-release-xen-48.x86_64 : CentOS Virt Sig Xen repo configs for Xen 4.8 > centos-release-xen-common.x86_64 : CentOS Virt Sig Xen support files > .. > > # yum install centos-release-xen > # cat /etc/yum.repos.d/CentOS-Xen.repo > > # CentOS-Xen.repo > # > # Please see http://wiki.centos.org/QaWiki/Xen4 for more > # information > > [centos-virt-xen-46] > name=CentOS-$releasever - xen > baseurl=http://mirror.centos.org/centos/$releasever/virt/$basearch/xen-46 > gpgcheck=1 > enabled=1 > gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization > > [centos-virt-xen-46-testing] > name=CentOS-$releasever - xen - testing > baseurl=http://buildlogs.centos.org/centos/$releasever/virt/$basearch/xen-46 > gpgcheck=0 > enabled=0 > gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization > > > I guess two things should happen in CentOS7: > > 1) Publish centos-release-xen-410 package >Ah, actually it's there already in xen-48 and xen-410 dirs, but not in CentOS extras.> 2) Update centos-release-xen package to point to.. 410 ? >So it seems the "centos-release-xen" package in "extras" repo has the xen-46 reference in it. So we should update the package in extras. Thanks, -- Pasi> > Thanks, > > -- Pasi > > > Thanks, > > -George > > >