As the person in charge of maintaining updates for the rh-* SCLs, I can say that I'm not shipping/caring about these once they are marked as EOL; so from my POV, they can be removed if it is not desirable to have them in the repositories. That being said, there is a possibility that a inter-SCL dependency will break, as have happened last summer with rh-ror42 (maintained at the time) and rh-nodejs4 (EOL). Since upstream does not remove the unmaintained packages from the repos, such dependencies won't be discovered until someone does remove them. Basically, I'm in favor of removing the EOL SCLs, but it might break non-EOL collections, which will take some time to fix. -- Jan Staněk Associate Software Engineer, Core Services Red Hat Czech jstanek at redhat.com IM: jstanek -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20190514/bafcb2ea/attachment-0008.sig>