Policies don't mean mistakes won't happen. A mistake happened and A) We are trying to clean it up as soon as possible [1] B) We are trying to work with mbs and infrastructure to make sure this can't happen in the future. I'm sorry this is so short on details, but I need to either write a short email now, or a long email later. Hopefully others can fill in the details. Troy [1] https://pagure.io/releng/issue/9554 On Sat, Jun 27, 2020 at 12:41 AM Felix Schwarz <fschwarz@xxxxxxxxxxxxxxxxx> wrote: > > > This morning I got an email notification: > > ================================================================================ > > Package Arch Version Repository Size > > ================================================================================ > Aktualisieren: > > libnghttp2 x86_64 1.41.0-1.module_el8+9071+b2b61c14 epel-modular 78 k > > Enabling module streams: > > nodejs 10 > > > As far as I know "libnghttp2" is provided in CentOS/RHEL base so this modular > package just replaced the previous from CentOS? Also the "nodejs" module got > enabled automatically? > > What is going on here? I thought we had contained the modularity fallout > pretty much with Fedora's (+EPEL's) policies. > > Felix > _______________________________________________ > epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
