8:51 a.m.
Hi everyone,
I'm wondering about what will happen next about EPEL:
I mean: will Epel follow Centos Stream and in this case not surely be compatible with RHEL
8 ?, or
will Epel continue to be fully compatible with RHEL 8 and in this case risk to break
compatibility with Centos ?
Or again will there be one repo for RHEL 8 ead another one for Centos Stream ?
Thanks
9:12 a.m.
On Mon, Jun 7, 2021 at 7:01 AM john tatt <zikamev(a)yahoo.com> wrote:
Hi everyone,
I'm wondering about what will happen next about EPEL:
I mean: will Epel follow Centos Stream and in this case not surely be
compatible with RHEL 8 ?, or
will Epel continue to be fully compatible with RHEL 8 and in this case
risk to break compatibility with Centos ?
Or again will there be one repo for RHEL 8 ead another one for Centos
Stream ?
EPEL is built off RHEL, not CentOS, and we plan on continuing that for
normal EPEL.
That will keep it compatible with RHEL, Alma, Rocky, and any other RHEL
rebuild that maintains compatibility.
For CentOS Stream, we are working on epel-next, that will be built off
CentOS Stream and follow that.
epel-next will not be a complete EPEL rebuild, but will layer on top of the
main EPEL repos.
We are very close to having this deployed. In the next couple of weeks
expect an email and documentation to be sent out about epel-next.
Troy
10:52 a.m.
On Mon, Jun 07, 2021 at 01:51:36PM +0000, john tatt wrote:
I mean: will Epel follow Centos Stream and in this case not surely be
compatible with RHEL 8 ?, or
Troy answered the overall questions separately, but... in practice, I expect
this to be a very small issue. How often has it been that RHEL minor updates
have required EPEL packages to be rebuilt, or EPEL packages built on the
latest to not install on older point-releases of RHEL? I'm sure it happens
occasionally, but it's not the typical case.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
11:22 a.m.
I can confirm, this issue affects very few EPEL packages, less than 1%
(excluding packages that don't install on RHEL8 either) [0]. The
numbers were very similar when RHEL was 8.3 and CS8 tracked 8.4
content. Most of those got resolved with the RHEL 8.4 release, but in
exchange CS8 now has that qt5 rebase which is coming in 8.5.
These problems are short lived (~6 months), small in number, and we'll
see even fewer of them over time as RHEL maintainers do fewer rebases
later in the RHEL lifecycle. We also plan to make epel-next a fairly
seamless experience for CS8 users by having epel-release recommend
epel-next-release if centos-stream-release is installed [1].
[0] https://twitter.com/carlwgeorge/status/1396960645250158593
[1] https://src.fedoraproject.org/rpms/epel-release/pull-request/13
On Mon, Jun 7, 2021 at 10:53 AM Matthew Miller <mattdm(a)fedoraproject.org> wrote:
On Mon, Jun 07, 2021 at 01:51:36PM +0000, john tatt wrote:
> I mean: will Epel follow Centos Stream and in this case not surely be compatible
with RHEL 8 ?, or
Troy answered the overall questions separately, but... in practice, I expect
this to be a very small issue. How often has it been that RHEL minor updates
have required EPEL packages to be rebuilt, or EPEL packages built on the
latest to not install on older point-releases of RHEL? I'm sure it happens
occasionally, but it's not the typical case.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
_______________________________________________
epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org
To unsubscribe send an email to epel-devel-leave(a)lists.fedoraproject.org
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@lists.fedoraproj...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
--
Carl George
3:55 p.m.
HiIts very clearThanks to all of you
J
Le lundi 7 juin 2021 à 18:22:52 UTC+2, Carl George <carl(a)redhat.com> a écrit :
I can confirm, this issue affects very few EPEL packages, less than 1%
(excluding packages that don't install on RHEL8 either) [0]. The
numbers were very similar when RHEL was 8.3 and CS8 tracked 8.4
content. Most of those got resolved with the RHEL 8.4 release, but in
exchange CS8 now has that qt5 rebase which is coming in 8.5.
These problems are short lived (~6 months), small in number, and we'll
see even fewer of them over time as RHEL maintainers do fewer rebases
later in the RHEL lifecycle. We also plan to make epel-next a fairly
seamless experience for CS8 users by having epel-release recommend
epel-next-release if centos-stream-release is installed [1].
[0] https://twitter.com/carlwgeorge/status/1396960645250158593
[1] https://src.fedoraproject.org/rpms/epel-release/pull-request/13
On Mon, Jun 7, 2021 at 10:53 AM Matthew Miller <mattdm(a)fedoraproject.org> wrote:
On Mon, Jun 07, 2021 at 01:51:36PM +0000, john tatt wrote:
> I mean: will Epel follow Centos Stream and in this case not surely be compatible
with RHEL 8 ?, or
Troy answered the overall questions separately, but... in practice, I expect
this to be a very small issue. How often has it been that RHEL minor updates
have required EPEL packages to be rebuilt, or EPEL packages built on the
latest to not install on older point-releases of RHEL? I'm sure it happens
occasionally, but it's not the typical case.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
_______________________________________________
epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org
To unsubscribe send an email to epel-devel-leave(a)lists.fedoraproject.org
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@lists.fedoraproj...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
--
Carl George
_______________________________________________
epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org
To unsubscribe send an email to epel-devel-leave(a)lists.fedoraproject.org
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@lists.fedoraproj...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
8:11 a.m.
Dne 07. 06. 21 v 17:52 Matthew Miller napsal(a):
Troy answered the overall questions separately, but... in practice, I
expect
this to be a very small issue.
Small issue in Koji and for Fedora Project itself. But can be bummer when you try to build
your set of packages on top
of EPEL. Or rebuild the EPEL package locally in Mock. Because then you have to do
non-trivial amount of work [1]. And
what is worse - the path has been tested by only few people so far.
[1] https://github.com/rpm-software-management/mock/wiki/Feature-rhelchroots
Miroslav
8:29 a.m.
On 08.06.21 15:11, Miroslav Suchý wrote:
Dne 07. 06. 21 v 17:52 Matthew Miller napsal(a):
> Troy answered the overall questions separately, but... in practice, I
> expect
> this to be a very small issue.
Small issue in Koji and for Fedora Project itself. But can be bummer
when you try to build your set of packages on top of EPEL. Or rebuild
the EPEL package locally in Mock. Because then you have to do
non-trivial amount of work [1]. And what is worse - the path has been
tested by only few people so far.
[1]
https://github.com/rpm-software-management/mock/wiki/Feature-rhelchroots
BTW and JFI:
COPR is preparing rhelchroots - maybe for 2022 Q1 (just speculation)
More here - https://bugzilla.redhat.com/show_bug.cgi?id=1965480
--
Leon
1047
days inactive
1048
days old
epel-devel@lists.fedoraproject.org
6 comments
6 participants
participants (6)
-
Carl George -
john tatt -
Leon Fauster -
Matthew Miller -
Miroslav Suchý -
Troy Dawson