On Tue, Sep 3, 2019, at 10:29, Honza Horak wrote:
A related discussion took place on this mailing-list in May this year, witch a clear agreement that removing EOL content from the SCLo SIG repo is the correct thing to do:
https://lists.centos.org/pipermail/centos-devel/2019-May/017424.html
I'd like to hear jstanek's opinion here as well, because he's handing the SCLo SIG content recently more than myself, but I'm pretty sure the SCLo SIG content mentioned below can be removed from mirrors and just kept in the vault repo.
It just looks like there were some unsuccessful efforts to remove the content before: https://lists.centos.org/pipermail/centos-devel/2018-August/016890.html
so we'll see how it goes this time.
Thanks, Honza
On 9/2/19 5:13 PM, Trevor Hemsley via CentOS-devel wrote:
On 16/08/2019 02:48, Johnny Hughes wrote:
For all the c7 SIGs, if you have content that you want removed (to make inactive) when we create the new 7.7.1908 tree, please let me know here what needs to be removed.
If all files in a specific directory can be removed, you can just list the directory.
You will also obviously need to make any changes to your centos-release-* files to remove those file locations from your repos.
After we release 7.7.1908 .. we will copy over the SIG directories prune the SIG content. The http://mirror.centos.org/centos/7/<repo>/ paths will then be shifted to the new 7.7.1908 tree.
I expect that some time early next week we will release the CR content .. with the full release coming 7 to 14 days after that .. so full release likely some time between 29 August to 6 September 2019.
If you don't tell us to remove content, we will move everything over as is.
I have just done my point-release-expiration-check on all the packages in SCL. I xref'ed this list https://access.redhat.com/support/policy/updates/rhscl with what's actually listed by `yum --disablerepo=* --enablerepo=*scl* list available`
These are the top level packages from that page that are marked as expired with their expiration dates from that page. This list covers more than just the packages I've listed there - for example maven30.x86_64 has 513 maven30* sub-packages and those will all need to be removed.
devassist09.x86_64 Oct 2016 devtoolset-3.x86_64 Oct 2016 devtoolset-4.x86_64 Nov 2017 devtoolset-6.x86_64 Nov 2018 git19.x86_64 Oct 2016 mariadb55.x86_64 Oct 2016 maven30.x86_64 Oct 2016 mongodb24.x86_64 Oct 2016 mysql55.x86_64 Oct 2016 nginx14.x86_64 Oct 2014 nginx16.x86_64 Oct 2016 nodejs010.x86_64 Oct 2016 perl516.x86_64 Oct 2016 php54.x86_64 Oct 2016 php55.x86_64 Oct 2016 postgresql92.x86_64 Oct 2016 python33.x86_64 Oct 2016 rh-eclipse46.x86_64 Nov 2018 rh-git29.x86_64 Nov 2018 rh-mariadb100.x86_64 Apr 2018 rh-mariadb101.x86_64 May 2019 rh-maven33.x86_64 May 2019 rh-mongodb26.x86_64 Apr 2018 rh-mongodb30upg.x86_64 Apr 2018 rh-mongodb32.x86_64 May 2019 rh-mysql56.x86_64 Apr 2018 rh-nginx18.x86_64 Nov 2018 rh-nodejs4.x86_64 May 2018 rh-nodejs6.x86_64 Apr 2019 rh-passenger40.x86_64 Apr 2018 rh-perl520.x86_64 Apr 2018 rh-php56.x86_64 Apr 2018 rh-postgresql94.x86_64 Apr 2018 rh-postgresql95.x86_64 May 2019 rh-python34.x86_64 Apr 2018 rh-python35.x86_64 May 2019 rh-ror41.x86_64 Apr 2018 rh-ruby22.x86_64 Apr 2018 rh-ruby23.x86_64 May 2019 rh-thermostat16.x86_64 Oct 2016 rh-varnish4.x86_64 Nov 2018 ror40.x86_64 Oct 2016 ruby193.x86_64 Oct 2016 ruby200.x86_64 Oct 2016 sclo-ror42.x86_64 May 2019 v8314.x86_64 Apr 2018
Trevor
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
With everything mentioned in this thread I've raised this PR: https://git.centos.org/centos/cbs-content-control/pull-request/9
We can continue taking removal requests here for a little bit longer. If there are any comments on things already removed, that can go in the comments on that PR.
Cheers!
--Brian