Hi
Ok that makes sense.
Thank you
Le Wed Feb 03 2021 17:48:32 GMT+0100 (CET), Troy Dawson <tdawson@xxxxxxxxxx> a écrit :
On Wed, Feb 3, 2021 at 3:16 AM john tatt <zikamev@xxxxxxxxx> wrote:
>
> Hi
> So if I understand well, an EPEL package could have to be desinstalled just because an update in Stream make it not compatible any more ?
> Strange
>
Yes and no
Yes - If you are running CentOS Stream, and don't have the epel-next
repo enabled.
No - If you are running RHEL, Rocky, Alma, or even CentOS Stream with
epel-next enabled.
>
> Le Mon Feb 01 2021 17:49:41 GMT+0100 (CET), Stephen John Smoogen <smooge@xxxxxxxxx> a écrit :
>
>
>
>
> On Mon, 1 Feb 2021 at 11:00, Filip Bartmann <filbar@xxxxxxxxxx> wrote:
>
> Hello,
> what version of RedHat will EPEL now follow? Centos Stream or oficial RedHat and Rocky based on stable RHEL?
>
>
>
> The main EPEL packages have always been compiled against the official Red Hat Enterprise Linux current package set. There is an initiative to have a set of packages built against CentOS Stream to deal with .next issues we see when RHEL updates from say 8.3 to 8.4.
>
>
>
>
> Thanks,
> Filip Bartmann
> _______________________________________________
> 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
>
>
>
> --
> Stephen J Smoogen.
>
>
> _______________________________________________
> 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
_______________________________________________
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
>
> Hi
> So if I understand well, an EPEL package could have to be desinstalled just because an update in Stream make it not compatible any more ?
> Strange
>
Yes and no
Yes - If you are running CentOS Stream, and don't have the epel-next
repo enabled.
No - If you are running RHEL, Rocky, Alma, or even CentOS Stream with
epel-next enabled.
>
> Le Mon Feb 01 2021 17:49:41 GMT+0100 (CET), Stephen John Smoogen <smooge@xxxxxxxxx> a écrit :
>
>
>
>
> On Mon, 1 Feb 2021 at 11:00, Filip Bartmann <filbar@xxxxxxxxxx> wrote:
>
> Hello,
> what version of RedHat will EPEL now follow? Centos Stream or oficial RedHat and Rocky based on stable RHEL?
>
>
>
> The main EPEL packages have always been compiled against the official Red Hat Enterprise Linux current package set. There is an initiative to have a set of packages built against CentOS Stream to deal with .next issues we see when RHEL updates from say 8.3 to 8.4.
>
>
>
>
> Thanks,
> Filip Bartmann
> _______________________________________________
> 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
>
>
>
> --
> Stephen J Smoogen.
>
>
> _______________________________________________
> 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
_______________________________________________
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
