[CentOS-devel] SCL packages in CentOS 7 that are expired and EOL

Hi again,
there are few recent bugs kind-of related to this discussion: [1,2].
The short version of both bugs is that some EOL-ed packages contain
packaging mistakes, which can break non-SCL installation when the SCL
repository is enables. As these are EOL, the fix is either to remove
them from the repo, or to patch them "downstream". From my PoV, I would
prefer moving them to the Vault.

Nico Kadel-Garcia wrote:
> Now, with all that in mind: Should there be some kind of comment.
> Should there be some kind of acknowledgement in the CentOS-Vault repo
> along with a pointer to such a repository of "these are so dangerously
> obsolete that we've overridden RHEL's publication of the original sclo
> channel and decided to shut these elsewhere"? What would such a
> channel be called? Would its contents be left permanently in the
> "obsolete" channel?

The last time something similar was discussed, I have tried to add
repository files for SCLo Vault into the centos-release-scl package;
then I was told this is a bad idea (i.e. vault is not mirrored, and
definitely cannot withstand traffic similar to mirrors). I guess the
proper course of action is to document this somewhere, and point people
to that documentation. Also, announcement on CentOS-announce would
probably be in order.

[1]: https://bugs.centos.org/view.php?id=16037
[2]: https://bugs.centos.org/view.php?id=16125
-- 
Jan Staněk
Associate Software Engineer
Red Hat EMEA
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/20190530/37645614/attachment-0004.sig>