Hi All,
I wonder if someone is in the role/position to shed some more light on the topic as announced here https://www.redhat.com/en/blog/furthering-evolution-centos-stream
Any deadlines? Does this target only EL10 or also any current release?
Would be great if some discussion/communication could be happen. Thanks!
On Thu, Jun 22, 2023 at 6:51 AM Leon Fauster via CentOS-devel centos-devel@centos.org wrote:
Hi All,
I wonder if someone is in the role/position to shed some more light on the topic as announced here https://www.redhat.com/en/blog/furthering-evolution-centos-stream
Any deadlines? Does this target only EL10 or also any current release?
It is in effect now for RHEL 8 and 9 and will continue for any future RHEL releases. The development and source code for all of these releases will continue to happen through the CentOS Stream project.
RHEL 7 and CentOS Linux 7 are not affected.
Would be great if some discussion/communication could be happen. Thanks!
If you have more questions, please ask and we can try to address them.
josh
On 22/06/2023 12.56, Josh Boyer wrote:
On Thu, Jun 22, 2023 at 6:51 AM Leon Fauster via CentOS-devel centos-devel@centos.org wrote:
Hi All,
I wonder if someone is in the role/position to shed some more light on the topic as announced here https://www.redhat.com/en/blog/furthering-evolution-centos-stream
Any deadlines? Does this target only EL10 or also any current release?
It is in effect now for RHEL 8 and 9 and will continue for any future RHEL releases. The development and source code for all of these releases will continue to happen through the CentOS Stream project.
RHEL 7 and CentOS Linux 7 are not affected.
Would be great if some discussion/communication could be happen. Thanks!
If you have more questions, please ask and we can try to address them.
I do indeed have a question. The Kmods SIG currently provides artifacts for both CentOS Stream and RHEL. To achieve that we have established some automation using GitLab CI to avoid human interaction as far as possible. For that to work we do need access to the following sources from RHEL (version numbers are just examples):
kernel-5.14.0-284.18.1.el9_2.src.rpm
or
linux-5.14.0-284.18.1.el9_2.tar.xz (which is included in the src.rpm).
So far we have downloaded the tarball from git.centos.org/sources
However, my understanding is that new versions of these files will not be provided anymore. In fact the example listed here (current RHEL 9 kernel) is already not provided anymore.
Is there any way for a CentOS SIG to access these files? Note that it needs to be in a way we can automate the access and even detection of new versions added. Both has been possible so far.
In a later stage we also need access to kernel-devel-5.14.0-284.18.1.el9_2.{aarch64,ppc64le,x86_64}.rpm which we have not been able to retrieve from RHEL directly so far, hence we used one of the RHEL rebuilds as a source. With the unknown future of these, we'd prefer to also have a way to access these directly from RHEL.
Any help in how we can modify our build automation to continue working after the announced changes are very much welcome. In case there are non we'll very likely have to stop producing artifacts for RHEL (but not for CentOS Stream, obviously).
Thanks!
Peter
josh
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Fri, Jun 23, 2023 at 7:47 AM Peter Georg peter.georg@physik.uni-regensburg.de wrote:
On 22/06/2023 12.56, Josh Boyer wrote:
On Thu, Jun 22, 2023 at 6:51 AM Leon Fauster via CentOS-devel centos-devel@centos.org wrote:
Hi All,
I wonder if someone is in the role/position to shed some more light on the topic as announced here https://www.redhat.com/en/blog/furthering-evolution-centos-stream
Any deadlines? Does this target only EL10 or also any current release?
It is in effect now for RHEL 8 and 9 and will continue for any future RHEL releases. The development and source code for all of these releases will continue to happen through the CentOS Stream project.
RHEL 7 and CentOS Linux 7 are not affected.
Would be great if some discussion/communication could be happen. Thanks!
If you have more questions, please ask and we can try to address them.
I do indeed have a question. The Kmods SIG currently provides artifacts for both CentOS Stream and RHEL. To achieve that we have established some automation using GitLab CI to avoid human interaction as far as possible. For that to work we do need access to the following sources from RHEL (version numbers are just examples):
kernel-5.14.0-284.18.1.el9_2.src.rpm
or
linux-5.14.0-284.18.1.el9_2.tar.xz (which is included in the src.rpm).
So far we have downloaded the tarball from git.centos.org/sources
However, my understanding is that new versions of these files will not be provided anymore. In fact the example listed here (current RHEL 9 kernel) is already not provided anymore.
Your understanding is correct.
Is there any way for a CentOS SIG to access these files? Note that it needs to be in a way we can automate the access and even detection of new versions added. Both has been possible so far.
In a later stage we also need access to kernel-devel-5.14.0-284.18.1.el9_2.{aarch64,ppc64le,x86_64}.rpm which we have not been able to retrieve from RHEL directly so far, hence we used one of the RHEL rebuilds as a source. With the unknown future of these, we'd prefer to also have a way to access these directly from RHEL.
Any help in how we can modify our build automation to continue working after the announced changes are very much welcome. In case there are non we'll very likely have to stop producing artifacts for RHEL (but not for CentOS Stream, obviously).
Red Hat has a program for Open Source projects to access RHEL directly. I've copied the Red Hat liaison who should be able to talk with the kmod SIG about this program and see if it's suitable.
We also have EPEL setup to build directly against RHEL, so we may be able to look into the solution it is using. I'm not familiar enough with the infra details to know for sure, but I suspect that would require some rework of various things.
josh
On Fri, Jun 23, 2023 at 7:47 AM Peter Georg peter.georg@physik.uni-regensburg.de wrote:
On 22/06/2023 12.56, Josh Boyer wrote:
On Thu, Jun 22, 2023 at 6:51 AM Leon Fauster via CentOS-devel centos-devel@centos.org wrote:
Hi All,
I wonder if someone is in the role/position to shed some more light
on
the topic as announced here https://www.redhat.com/en/blog/furthering-evolution-centos-stream
Any deadlines? Does this target only EL10 or also any current
release?
It is in effect now for RHEL 8 and 9 and will continue for any future RHEL releases. The development and source code for all of these releases will continue to happen through the CentOS Stream project.
RHEL 7 and CentOS Linux 7 are not affected.
Would be great if some discussion/communication could be happen.
Thanks!
If you have more questions, please ask and we can try to address them.
I do indeed have a question. The Kmods SIG currently provides artifacts for both CentOS Stream and RHEL. To achieve that we have established some automation using GitLab CI to avoid human interaction as far as possible. For that to work we do need access to the following sources from RHEL (version numbers are just examples):
kernel-5.14.0-284.18.1.el9_2.src.rpm
or
linux-5.14.0-284.18.1.el9_2.tar.xz (which is included in the src.rpm).
So far we have downloaded the tarball from git.centos.org/sources
However, my understanding is that new versions of these files will not be provided anymore. In fact the example listed here (current RHEL 9 kernel) is already not provided anymore.
Your understanding is correct.
What I don't understand is this: as a Red Hat customer with paid subscription, I'm still able to download kernel-5.14.0-284.18.1.el9_2.src.rpm, right?
If I do so and extract the kernel-5.14.0-284.18.1.el9_2.src.rpm archive, can I put the resulting files on a public server and let others download the files?
Regards, Simon
On Fri, Jun 23, 2023 at 9:44 AM Simon Matter simon.matter@invoca.ch wrote:
On Fri, Jun 23, 2023 at 7:47 AM Peter Georg peter.georg@physik.uni-regensburg.de wrote:
On 22/06/2023 12.56, Josh Boyer wrote:
On Thu, Jun 22, 2023 at 6:51 AM Leon Fauster via CentOS-devel centos-devel@centos.org wrote:
Hi All,
I wonder if someone is in the role/position to shed some more light
on
the topic as announced here https://www.redhat.com/en/blog/furthering-evolution-centos-stream
Any deadlines? Does this target only EL10 or also any current
release?
It is in effect now for RHEL 8 and 9 and will continue for any future RHEL releases. The development and source code for all of these releases will continue to happen through the CentOS Stream project.
RHEL 7 and CentOS Linux 7 are not affected.
Would be great if some discussion/communication could be happen.
Thanks!
If you have more questions, please ask and we can try to address them.
I do indeed have a question. The Kmods SIG currently provides artifacts for both CentOS Stream and RHEL. To achieve that we have established some automation using GitLab CI to avoid human interaction as far as possible. For that to work we do need access to the following sources from RHEL (version numbers are just examples):
kernel-5.14.0-284.18.1.el9_2.src.rpm
or
linux-5.14.0-284.18.1.el9_2.tar.xz (which is included in the src.rpm).
So far we have downloaded the tarball from git.centos.org/sources
However, my understanding is that new versions of these files will not be provided anymore. In fact the example listed here (current RHEL 9 kernel) is already not provided anymore.
Your understanding is correct.
What I don't understand is this: as a Red Hat customer with paid subscription, I'm still able to download kernel-5.14.0-284.18.1.el9_2.src.rpm, right?
Yes.
If I do so and extract the kernel-5.14.0-284.18.1.el9_2.src.rpm archive, can I put the resulting files on a public server and let others download the files?
The kernel is licensed under the GPL, which grants redistribution rights to all such licensed source code.
josh
On 23/06/2023 16:34, Josh Boyer wrote:
On Fri, Jun 23, 2023 at 9:44 AM Simon Matter simon.matter@invoca.ch wrote:
On Fri, Jun 23, 2023 at 7:47 AM Peter Georg peter.georg@physik.uni-regensburg.de wrote:
On 22/06/2023 12.56, Josh Boyer wrote:
On Thu, Jun 22, 2023 at 6:51 AM Leon Fauster via CentOS-devel centos-devel@centos.org wrote:
Hi All,
I wonder if someone is in the role/position to shed some more light
on
the topic as announced here https://www.redhat.com/en/blog/furthering-evolution-centos-stream
Any deadlines? Does this target only EL10 or also any current
release?
It is in effect now for RHEL 8 and 9 and will continue for any future RHEL releases. The development and source code for all of these releases will continue to happen through the CentOS Stream project.
RHEL 7 and CentOS Linux 7 are not affected.
Would be great if some discussion/communication could be happen.
Thanks!
If you have more questions, please ask and we can try to address them.
I do indeed have a question. The Kmods SIG currently provides artifacts for both CentOS Stream and RHEL. To achieve that we have established some automation using GitLab CI to avoid human interaction as far as possible. For that to work we do need access to the following sources from RHEL (version numbers are just examples):
kernel-5.14.0-284.18.1.el9_2.src.rpm
or
linux-5.14.0-284.18.1.el9_2.tar.xz (which is included in the src.rpm).
So far we have downloaded the tarball from git.centos.org/sources
However, my understanding is that new versions of these files will not be provided anymore. In fact the example listed here (current RHEL 9 kernel) is already not provided anymore.
Your understanding is correct.
What I don't understand is this: as a Red Hat customer with paid subscription, I'm still able to download kernel-5.14.0-284.18.1.el9_2.src.rpm, right?
Yes.
If I do so and extract the kernel-5.14.0-284.18.1.el9_2.src.rpm archive, can I put the resulting files on a public server and let others download the files?
The kernel is licensed under the GPL, which grants redistribution rights to all such licensed source code.
josh
Then maybe the CentOS Project should start a SiG to pull the RHEL sources and populate a repository for everyone to freely access, thus filling the void left by RH's decision to withdraw this?
Or maybe ALMA or Rocky will do it as they will also no doubt be doing something similar in house anyway.
Either way, it sounds like a lot of people need access to these sources in such a way that can be easily integrated into CI/build systems and RH is no longer providing this facility.
Perhaps it would be useful to know the intention behind Red Hat's decision? If this is an unintended consequence of the decision, maybe RH can do something to fix it and provide the sources elsewhere for easily scriptable public consumption. However, if the intention is to deliberately make things harder for the (rebuild) community, then the community will likely need to put in place mitigations themselves.
Phil
On Fri, Jun 23, 2023 at 11:44 AM Phil Perry pperry@elrepo.org wrote:
On 23/06/2023 16:34, Josh Boyer wrote:
On Fri, Jun 23, 2023 at 9:44 AM Simon Matter simon.matter@invoca.ch wrote:
On Fri, Jun 23, 2023 at 7:47 AM Peter Georg peter.georg@physik.uni-regensburg.de wrote:
On 22/06/2023 12.56, Josh Boyer wrote:
On Thu, Jun 22, 2023 at 6:51 AM Leon Fauster via CentOS-devel centos-devel@centos.org wrote: > > Hi All, > > I wonder if someone is in the role/position to shed some more light
on
> the topic as announced here > https://www.redhat.com/en/blog/furthering-evolution-centos-stream > > Any deadlines? Does this target only EL10 or also any current
release?
It is in effect now for RHEL 8 and 9 and will continue for any future RHEL releases. The development and source code for all of these releases will continue to happen through the CentOS Stream project.
RHEL 7 and CentOS Linux 7 are not affected.
> Would be great if some discussion/communication could be happen.
Thanks!
If you have more questions, please ask and we can try to address them.
I do indeed have a question. The Kmods SIG currently provides artifacts for both CentOS Stream and RHEL. To achieve that we have established some automation using GitLab CI to avoid human interaction as far as possible. For that to work we do need access to the following sources from RHEL (version numbers are just examples):
kernel-5.14.0-284.18.1.el9_2.src.rpm
or
linux-5.14.0-284.18.1.el9_2.tar.xz (which is included in the src.rpm).
So far we have downloaded the tarball from git.centos.org/sources
However, my understanding is that new versions of these files will not be provided anymore. In fact the example listed here (current RHEL 9 kernel) is already not provided anymore.
Your understanding is correct.
What I don't understand is this: as a Red Hat customer with paid subscription, I'm still able to download kernel-5.14.0-284.18.1.el9_2.src.rpm, right?
Yes.
If I do so and extract the kernel-5.14.0-284.18.1.el9_2.src.rpm archive, can I put the resulting files on a public server and let others download the files?
The kernel is licensed under the GPL, which grants redistribution rights to all such licensed source code.
josh
Then maybe the CentOS Project should start a SiG to pull the RHEL sources and populate a repository for everyone to freely access, thus filling the void left by RH's decision to withdraw this?
If someone wants to propose that they can. Speaking as an individual Board member, I don't believe I would be in support of such a SIG. I won't speak for the rest of the Board, nor for the Red Hat liaison.
josh
Hi Josh,
On Fri, Jun 23, 2023 at 9:44 AM Simon Matter simon.matter@invoca.ch wrote:
On Fri, Jun 23, 2023 at 7:47 AM Peter Georg peter.georg@physik.uni-regensburg.de wrote:
On 22/06/2023 12.56, Josh Boyer wrote:
On Thu, Jun 22, 2023 at 6:51 AM Leon Fauster via CentOS-devel centos-devel@centos.org wrote:
Hi All,
I wonder if someone is in the role/position to shed some more
light
on
the topic as announced here https://www.redhat.com/en/blog/furthering-evolution-centos-stream
Any deadlines? Does this target only EL10 or also any current
release?
It is in effect now for RHEL 8 and 9 and will continue for any
future
RHEL releases. The development and source code for all of these releases will continue to happen through the CentOS Stream project.
RHEL 7 and CentOS Linux 7 are not affected.
Would be great if some discussion/communication could be happen.
Thanks!
If you have more questions, please ask and we can try to address
them.
I do indeed have a question. The Kmods SIG currently provides
artifacts
for both CentOS Stream and RHEL. To achieve that we have established some automation using GitLab CI to avoid human interaction as far as possible. For that to work we do need access to the following sources from RHEL (version numbers are just examples):
kernel-5.14.0-284.18.1.el9_2.src.rpm
or
linux-5.14.0-284.18.1.el9_2.tar.xz (which is included in the
src.rpm).
So far we have downloaded the tarball from git.centos.org/sources
However, my understanding is that new versions of these files will
not
be provided anymore. In fact the example listed here (current RHEL 9 kernel) is already not provided anymore.
Your understanding is correct.
What I don't understand is this: as a Red Hat customer with paid subscription, I'm still able to download kernel-5.14.0-284.18.1.el9_2.src.rpm, right?
Yes.
If I do so and extract the kernel-5.14.0-284.18.1.el9_2.src.rpm archive, can I put the resulting files on a public server and let others download the files?
The kernel is licensed under the GPL, which grants redistribution rights to all such licensed source code.
josh
Thanks for your answer. I'm still wondering about two things:
1) This comment https://www.theregister.com/2023/06/23/red_hat_centos_move/ says:
The key point being is that to obtain those binaries, customers - as well as developers on free accounts – must agree to a license agreement and are under the terms of a contract, which overrides the GPL license of the code itself.
Is this true? Can anyone set up new rules and just "override" the GPL license?
2) RHEL contains more than "the GPL", fact is it contains source code licensed under a large amount of different licenses. Is it really possible to cover and override all of them so easily?
I'd really like to understand what the new announcement of Red Hat means exactly.
Regards, Simon
On Fri, Jun 23, 2023 at 1:09 PM Simon Matter simon.matter@invoca.ch wrote:
Hi Josh,
On Fri, Jun 23, 2023 at 9:44 AM Simon Matter simon.matter@invoca.ch wrote:
On Fri, Jun 23, 2023 at 7:47 AM Peter Georg peter.georg@physik.uni-regensburg.de wrote:
On 22/06/2023 12.56, Josh Boyer wrote:
On Thu, Jun 22, 2023 at 6:51 AM Leon Fauster via CentOS-devel centos-devel@centos.org wrote: > > Hi All, > > I wonder if someone is in the role/position to shed some more
light
on
> the topic as announced here > https://www.redhat.com/en/blog/furthering-evolution-centos-stream > > Any deadlines? Does this target only EL10 or also any current
release?
It is in effect now for RHEL 8 and 9 and will continue for any
future
RHEL releases. The development and source code for all of these releases will continue to happen through the CentOS Stream project.
RHEL 7 and CentOS Linux 7 are not affected.
> Would be great if some discussion/communication could be happen.
Thanks!
If you have more questions, please ask and we can try to address
them.
I do indeed have a question. The Kmods SIG currently provides
artifacts
for both CentOS Stream and RHEL. To achieve that we have established some automation using GitLab CI to avoid human interaction as far as possible. For that to work we do need access to the following sources from RHEL (version numbers are just examples):
kernel-5.14.0-284.18.1.el9_2.src.rpm
or
linux-5.14.0-284.18.1.el9_2.tar.xz (which is included in the
src.rpm).
So far we have downloaded the tarball from git.centos.org/sources
However, my understanding is that new versions of these files will
not
be provided anymore. In fact the example listed here (current RHEL 9 kernel) is already not provided anymore.
Your understanding is correct.
What I don't understand is this: as a Red Hat customer with paid subscription, I'm still able to download kernel-5.14.0-284.18.1.el9_2.src.rpm, right?
Yes.
If I do so and extract the kernel-5.14.0-284.18.1.el9_2.src.rpm archive, can I put the resulting files on a public server and let others download the files?
The kernel is licensed under the GPL, which grants redistribution rights to all such licensed source code.
josh
Thanks for your answer. I'm still wondering about two things:
- This comment
https://www.theregister.com/2023/06/23/red_hat_centos_move/ says:
The key point being is that to obtain those binaries, customers - as well as developers on free accounts – must agree to a license agreement and are under the terms of a contract, which overrides the GPL license of the code itself.
Is this true? Can anyone set up new rules and just "override" the GPL license?
I would strongly encourage you, as a Red Hat customer, to reach out to Red Hat via the Customer Portal or other contact methods to discuss the Enterprise agreement. Seeking advice on this mailing list or the internet in general about the agreement is probably not in anyone's best interest.
- RHEL contains more than "the GPL", fact is it contains source code
licensed under a large amount of different licenses. Is it really possible to cover and override all of them so easily?
It is quite true that RHEL contains source code under a variety of open source licenses, some of which do not require any typical copyleft provisions at all. That said, Red Hat publishes sources to the Customer Portal for all open source packages even if not required, and the source code is available in CentOS Stream as well.
I'd really like to understand what the new announcement of Red Hat means exactly.
I find the blog post very clear about the change. Red Hat is no longer going to publish sources to git.centos.org and instead refers people to CentOS Stream.
The discussions around terms and conditions of the enterprise agreement are not affected at all by the change described in the blog post. The agreement did not change and any questions on what it entails are the same now as they were last week.
josh
On Fri, Jun 23, 2023 at 9:44 AM Simon Matter simon.matter@invoca.ch wrote:
On Fri, Jun 23, 2023 at 7:47 AM Peter Georg peter.georg@physik.uni-regensburg.de wrote:
On 22/06/2023 12.56, Josh Boyer wrote:
On Thu, Jun 22, 2023 at 6:51 AM Leon Fauster via CentOS-devel centos-devel@centos.org wrote:
Hi All,
I wonder if someone is in the role/position to shed some more light
on
the topic as announced here https://www.redhat.com/en/blog/furthering-evolution-centos-stream
Any deadlines? Does this target only EL10 or also any current
release?
It is in effect now for RHEL 8 and 9 and will continue for any future RHEL releases. The development and source code for all of these releases will continue to happen through the CentOS Stream project.
RHEL 7 and CentOS Linux 7 are not affected.
Would be great if some discussion/communication could be happen.
Thanks!
If you have more questions, please ask and we can try to address them.
I do indeed have a question. The Kmods SIG currently provides artifacts for both CentOS Stream and RHEL. To achieve that we have established some automation using GitLab CI to avoid human interaction as far as possible. For that to work we do need access to the following sources from RHEL (version numbers are just examples):
kernel-5.14.0-284.18.1.el9_2.src.rpm
or
linux-5.14.0-284.18.1.el9_2.tar.xz (which is included in the src.rpm).
So far we have downloaded the tarball from git.centos.org/sources
However, my understanding is that new versions of these files will not be provided anymore. In fact the example listed here (current RHEL 9 kernel) is already not provided anymore.
Your understanding is correct.
What I don't understand is this: as a Red Hat customer with paid subscription, I'm still able to download kernel-5.14.0-284.18.1.el9_2.src.rpm, right?
If I do so and extract the kernel-5.14.0-284.18.1.el9_2.src.rpm archive, can I put the resulting files on a public server and let others download the files?
Regards, Simon
The kernel is GPL, so "yes", as long as you're willing to make any changes you add to the source code available to people who get the binaries. Do review the GPL, it's an interesting license.
On 26/06/2023 11:12, Nico Kadel-Garcia wrote:
On Fri, Jun 23, 2023 at 9:44 AM Simon Matter simon.matter@invoca.ch wrote:
On Fri, Jun 23, 2023 at 7:47 AM Peter Georg peter.georg@physik.uni-regensburg.de wrote:
On 22/06/2023 12.56, Josh Boyer wrote:
On Thu, Jun 22, 2023 at 6:51 AM Leon Fauster via CentOS-devel centos-devel@centos.org wrote:
Hi All,
I wonder if someone is in the role/position to shed some more light
on
the topic as announced here https://www.redhat.com/en/blog/furthering-evolution-centos-stream
Any deadlines? Does this target only EL10 or also any current
release?
It is in effect now for RHEL 8 and 9 and will continue for any future RHEL releases. The development and source code for all of these releases will continue to happen through the CentOS Stream project.
RHEL 7 and CentOS Linux 7 are not affected.
Would be great if some discussion/communication could be happen.
Thanks!
If you have more questions, please ask and we can try to address them.
I do indeed have a question. The Kmods SIG currently provides artifacts for both CentOS Stream and RHEL. To achieve that we have established some automation using GitLab CI to avoid human interaction as far as possible. For that to work we do need access to the following sources from RHEL (version numbers are just examples):
kernel-5.14.0-284.18.1.el9_2.src.rpm
or
linux-5.14.0-284.18.1.el9_2.tar.xz (which is included in the src.rpm).
So far we have downloaded the tarball from git.centos.org/sources
However, my understanding is that new versions of these files will not be provided anymore. In fact the example listed here (current RHEL 9 kernel) is already not provided anymore.
Your understanding is correct.
What I don't understand is this: as a Red Hat customer with paid subscription, I'm still able to download kernel-5.14.0-284.18.1.el9_2.src.rpm, right?
If I do so and extract the kernel-5.14.0-284.18.1.el9_2.src.rpm archive, can I put the resulting files on a public server and let others download the files?
Regards, Simon
The kernel is GPL, so "yes", as long as you're willing to make any changes you add to the source code available to people who get the binaries. Do review the GPL, it's an interesting license.
However, my understanding is that Red Hat are saying or implying that by redistributing the source, you are in breach of their T&C's (not the GPL) and as such they would have the right to terminate your contract meaning you would no longer have access to said sources. (Please review the T&Cs you agreed with Red Hat as a paying customer)
I am not sure if Red Hat's T&Cs are compatible with the GPL which states:
" 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. **You may not impose any further restrictions on the recipients' exercise of the rights granted herein.** You are not responsible for enforcing compliance by third parties to this License."
Red Hat would likely argue that they are not imposing further restrictions to the software licence itself, only on the use of their services by paying customers.
Red Hat would need to clarify their position (and please feel free to correct me if I have misunderstood)
Phil
On Mon, Jun 26, 2023 at 8:15 AM Phil Perry pperry@elrepo.org wrote:
On 26/06/2023 11:12, Nico Kadel-Garcia wrote:
On Fri, Jun 23, 2023 at 9:44 AM Simon Matter simon.matter@invoca.ch wrote:
The kernel is GPL, so "yes", as long as you're willing to make any changes you add to the source code available to people who get the binaries. Do review the GPL, it's an interesting license.
However, my understanding is that Red Hat are saying or implying that by redistributing the source, you are in breach of their T&C's (not the GPL) and as such they would have the right to terminate your contract meaning you would no longer have access to said sources. (Please review the T&Cs you agreed with Red Hat as a paying customer)
Wow. I'm staring at the RHEL 9 kernel, and "rpm -qi output:
License : GPLv2 and Redistributable, no modification permitted
That.... is confusing, and is one of the reasons for the GPLv3. As I understand that particular kernel, it means "you can't modify it and claim new copyrights or licenses". I admit that it's confusing, and a casual reading would discourage people from locally patching and publishing their modified kernels. But I've not published tweaked kernels in years.
On Mon, Jun 26, 2023 at 8:48 AM Nico Kadel-Garcia nkadel@gmail.com wrote:
On Mon, Jun 26, 2023 at 8:15 AM Phil Perry pperry@elrepo.org wrote:
On 26/06/2023 11:12, Nico Kadel-Garcia wrote:
On Fri, Jun 23, 2023 at 9:44 AM Simon Matter simon.matter@invoca.ch wrote:
The kernel is GPL, so "yes", as long as you're willing to make any changes you add to the source code available to people who get the binaries. Do review the GPL, it's an interesting license.
However, my understanding is that Red Hat are saying or implying that by redistributing the source, you are in breach of their T&C's (not the GPL) and as such they would have the right to terminate your contract meaning you would no longer have access to said sources. (Please review the T&Cs you agreed with Red Hat as a paying customer)
Wow. I'm staring at the RHEL 9 kernel, and "rpm -qi output:
License : GPLv2 and Redistributable, no modification permittedThat.... is confusing, and is one of the reasons for the GPLv3. As I understand that particular kernel, it means "you can't modify it and claim new copyrights or licenses". I admit that it's confusing, and a casual reading would discourage people from locally patching and publishing their modified kernels. But I've not published tweaked kernels in years.
It is indeed confusing. The explanation there is that the Linux Kernel source code is published under GPLv2. There are also firmware blobs built into the kernel for legacy reasons (true upstream as well), and those are licensed as redistributable but not modifiable. The RPM License stanza is supposed to represent all licenses included, so you have both listed.
josh
On Fri, Jun 23, 2023 at 9:44 AM Simon Matter simon.matter@invoca.ch wrote:
On Fri, Jun 23, 2023 at 7:47 AM Peter Georg peter.georg@physik.uni-regensburg.de wrote:
On 22/06/2023 12.56, Josh Boyer wrote:
On Thu, Jun 22, 2023 at 6:51 AM Leon Fauster via CentOS-devel centos-devel@centos.org wrote:
Hi All,
I wonder if someone is in the role/position to shed some more
light
on
the topic as announced here https://www.redhat.com/en/blog/furthering-evolution-centos-stream
Any deadlines? Does this target only EL10 or also any current
release?
It is in effect now for RHEL 8 and 9 and will continue for any
future
RHEL releases. The development and source code for all of these releases will continue to happen through the CentOS Stream project.
RHEL 7 and CentOS Linux 7 are not affected.
Would be great if some discussion/communication could be happen.
Thanks!
If you have more questions, please ask and we can try to address
them.
I do indeed have a question. The Kmods SIG currently provides
artifacts
for both CentOS Stream and RHEL. To achieve that we have established some automation using GitLab CI to avoid human interaction as far as possible. For that to work we do need access to the following sources from RHEL (version numbers are just examples):
kernel-5.14.0-284.18.1.el9_2.src.rpm
or
linux-5.14.0-284.18.1.el9_2.tar.xz (which is included in the
src.rpm).
So far we have downloaded the tarball from git.centos.org/sources
However, my understanding is that new versions of these files will
not
be provided anymore. In fact the example listed here (current RHEL 9 kernel) is already not provided anymore.
Your understanding is correct.
What I don't understand is this: as a Red Hat customer with paid subscription, I'm still able to download kernel-5.14.0-284.18.1.el9_2.src.rpm, right?
If I do so and extract the kernel-5.14.0-284.18.1.el9_2.src.rpm archive, can I put the resulting files on a public server and let others download the files?
Regards, Simon
The kernel is GPL, so "yes", as long as you're willing to make any changes you add to the source code available to people who get the binaries. Do review the GPL, it's an interesting license.
I'm not talking about binaries at all. I only say I can get the source in the form of file kernel-5.14.0-284.18.1.el9_2.src.rpm, extract it, and distribute the resulting files to the whole world. I and everybody else can then build binaries from these sources, with or without further changes. Isn't this the whole point of the GPL?
Simon
On 23/06/2023 13:00, Josh Boyer wrote:
On Fri, Jun 23, 2023 at 7:47 AM Peter Georg peter.georg@physik.uni-regensburg.de wrote:
On 22/06/2023 12.56, Josh Boyer wrote:
On Thu, Jun 22, 2023 at 6:51 AM Leon Fauster via CentOS-devel centos-devel@centos.org wrote:
Hi All,
I wonder if someone is in the role/position to shed some more light on the topic as announced here https://www.redhat.com/en/blog/furthering-evolution-centos-stream
Any deadlines? Does this target only EL10 or also any current release?
It is in effect now for RHEL 8 and 9 and will continue for any future RHEL releases. The development and source code for all of these releases will continue to happen through the CentOS Stream project.
RHEL 7 and CentOS Linux 7 are not affected.
Would be great if some discussion/communication could be happen. Thanks!
If you have more questions, please ask and we can try to address them.
I do indeed have a question. The Kmods SIG currently provides artifacts for both CentOS Stream and RHEL. To achieve that we have established some automation using GitLab CI to avoid human interaction as far as possible. For that to work we do need access to the following sources from RHEL (version numbers are just examples):
kernel-5.14.0-284.18.1.el9_2.src.rpm
or
linux-5.14.0-284.18.1.el9_2.tar.xz (which is included in the src.rpm).
So far we have downloaded the tarball from git.centos.org/sources
However, my understanding is that new versions of these files will not be provided anymore. In fact the example listed here (current RHEL 9 kernel) is already not provided anymore.
Your understanding is correct.
Is there any way for a CentOS SIG to access these files? Note that it needs to be in a way we can automate the access and even detection of new versions added. Both has been possible so far.
In a later stage we also need access to kernel-devel-5.14.0-284.18.1.el9_2.{aarch64,ppc64le,x86_64}.rpm which we have not been able to retrieve from RHEL directly so far, hence we used one of the RHEL rebuilds as a source. With the unknown future of these, we'd prefer to also have a way to access these directly from RHEL.
Any help in how we can modify our build automation to continue working after the announced changes are very much welcome. In case there are non we'll very likely have to stop producing artifacts for RHEL (but not for CentOS Stream, obviously).
Red Hat has a program for Open Source projects to access RHEL directly. I've copied the Red Hat liaison who should be able to talk with the kmod SIG about this program and see if it's suitable.
We also have EPEL setup to build directly against RHEL, so we may be able to look into the solution it is using. I'm not familiar enough with the infra details to know for sure, but I suspect that would require some rework of various things.
josh
Hi Peter,
Would it not be easier to build on a RHEL-based build system and then just pull in the Stream specific stuff you need to build against (e.g, Stream kernel / kernel-devel packages) that _are_ publicly available and hence scriptable?
As Josh suggests, this is what projects such as EPEL and ELRepo do. Stream isn't really fit for purpose for developing for RHEL, at least in the kernel space.
Phil
On 23/06/2023 16.07, Phil Perry wrote:
On 23/06/2023 13:00, Josh Boyer wrote:
On Fri, Jun 23, 2023 at 7:47 AM Peter Georg peter.georg@physik.uni-regensburg.de wrote:
On 22/06/2023 12.56, Josh Boyer wrote:
On Thu, Jun 22, 2023 at 6:51 AM Leon Fauster via CentOS-devel centos-devel@centos.org wrote:
Hi All,
I wonder if someone is in the role/position to shed some more light on the topic as announced here https://www.redhat.com/en/blog/furthering-evolution-centos-stream
Any deadlines? Does this target only EL10 or also any current release?
It is in effect now for RHEL 8 and 9 and will continue for any future RHEL releases. The development and source code for all of these releases will continue to happen through the CentOS Stream project.
RHEL 7 and CentOS Linux 7 are not affected.
Would be great if some discussion/communication could be happen. Thanks!
If you have more questions, please ask and we can try to address them.
I do indeed have a question. The Kmods SIG currently provides artifacts for both CentOS Stream and RHEL. To achieve that we have established some automation using GitLab CI to avoid human interaction as far as possible. For that to work we do need access to the following sources from RHEL (version numbers are just examples):
kernel-5.14.0-284.18.1.el9_2.src.rpm
or
linux-5.14.0-284.18.1.el9_2.tar.xz (which is included in the src.rpm).
So far we have downloaded the tarball from git.centos.org/sources
However, my understanding is that new versions of these files will not be provided anymore. In fact the example listed here (current RHEL 9 kernel) is already not provided anymore.
Your understanding is correct.
Is there any way for a CentOS SIG to access these files? Note that it needs to be in a way we can automate the access and even detection of new versions added. Both has been possible so far.
In a later stage we also need access to kernel-devel-5.14.0-284.18.1.el9_2.{aarch64,ppc64le,x86_64}.rpm which we have not been able to retrieve from RHEL directly so far, hence we used one of the RHEL rebuilds as a source. With the unknown future of these, we'd prefer to also have a way to access these directly from RHEL.
Any help in how we can modify our build automation to continue working after the announced changes are very much welcome. In case there are non we'll very likely have to stop producing artifacts for RHEL (but not for CentOS Stream, obviously).
Red Hat has a program for Open Source projects to access RHEL directly. I've copied the Red Hat liaison who should be able to talk with the kmod SIG about this program and see if it's suitable.
We also have EPEL setup to build directly against RHEL, so we may be able to look into the solution it is using. I'm not familiar enough with the infra details to know for sure, but I suspect that would require some rework of various things.
josh
Hi Peter,
Would it not be easier to build on a RHEL-based build system and then just pull in the Stream specific stuff you need to build against (e.g, Stream kernel / kernel-devel packages) that _are_ publicly available and hence scriptable?
Hi Phil,
We are building everything for RHEL against RHEL, everything for Stream we build against Stream. In CBS RHEL build targets have been available for some time by now. I do not know the details, but the setup is probably very similar to the one of EPEL. The actual build is not an issue at all. Access to the files mentioned before is required to prepare the sources of our packages and to detect required rebuilds due to kABI changes. For the former we do require access to the source code of the kernel we want to build against, e.g., linux-5.14.0-284.18.1.el9_2.tar.xz. For the latter we extract Module.symvers of all supported architectures from kernel-devel-5.14.0-284.18.1.el9_2.{aarch64,ppc64le,x86_64}.rpm. 5.14.0-284.18.1.el9_2 being a RHEL kernel it is not available in Stream and hence not publicly available.
As Josh suggests, this is what projects such as EPEL and ELRepo do. Stream isn't really fit for purpose for developing for RHEL, at least in the kernel space.
Phil
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Hi,
I am bex, Brian Exelbierd, the Red Hat liaison that Josh mentioned in another email.
On Fri, Jun 23, 2023 at 4:07 PM Phil Perry pperry@elrepo.org wrote:
On 23/06/2023 13:00, Josh Boyer wrote:
On Fri, Jun 23, 2023 at 7:47 AM Peter Georg peter.georg@physik.uni-regensburg.de wrote:
On 22/06/2023 12.56, Josh Boyer wrote:
On Thu, Jun 22, 2023 at 6:51 AM Leon Fauster via CentOS-devel centos-devel@centos.org wrote:
Hi All,
I wonder if someone is in the role/position to shed some more light on the topic as announced here https://www.redhat.com/en/blog/furthering-evolution-centos-stream
Any deadlines? Does this target only EL10 or also any current release?
It is in effect now for RHEL 8 and 9 and will continue for any future RHEL releases. The development and source code for all of these releases will continue to happen through the CentOS Stream project.
RHEL 7 and CentOS Linux 7 are not affected.
Would be great if some discussion/communication could be happen.
Thanks!
If you have more questions, please ask and we can try to address them.
I do indeed have a question. The Kmods SIG currently provides artifacts for both CentOS Stream and RHEL. To achieve that we have established some automation using GitLab CI to avoid human interaction as far as possible. For that to work we do need access to the following sources from RHEL (version numbers are just examples):
kernel-5.14.0-284.18.1.el9_2.src.rpm
or
linux-5.14.0-284.18.1.el9_2.tar.xz (which is included in the src.rpm).
So far we have downloaded the tarball from git.centos.org/sources
However, my understanding is that new versions of these files will not be provided anymore. In fact the example listed here (current RHEL 9 kernel) is already not provided anymore.
Your understanding is correct.
Is there any way for a CentOS SIG to access these files? Note that it needs to be in a way we can automate the access and even detection of new versions added. Both has been possible so far.
In a later stage we also need access to kernel-devel-5.14.0-284.18.1.el9_2.{aarch64,ppc64le,x86_64}.rpm which we have not been able to retrieve from RHEL directly so far, hence we used one of the RHEL rebuilds as a source. With the unknown future of these, we'd prefer to also have a way to access these directly from RHEL.
Any help in how we can modify our build automation to continue working after the announced changes are very much welcome. In case there are non we'll very likely have to stop producing artifacts for RHEL (but not for CentOS Stream, obviously).
Red Hat has a program for Open Source projects to access RHEL directly. I've copied the Red Hat liaison who should be able to talk with the kmod SIG about this program and see if it's suitable.
We also have EPEL setup to build directly against RHEL, so we may be able to look into the solution it is using. I'm not familiar enough with the infra details to know for sure, but I suspect that would require some rework of various things.
josh
Hi Peter,
Would it not be easier to build on a RHEL-based build system and then just pull in the Stream specific stuff you need to build against (e.g, Stream kernel / kernel-devel packages) that _are_ publicly available and hence scriptable?
As Josh suggests, this is what projects such as EPEL and ELRepo do. Stream isn't really fit for purpose for developing for RHEL, at least in the kernel space.
^^ This
Is the kmod SIG building on CentOS Project infrastructure or external infrastructure? If it is CentOS Project infrastructure then the Infra team will need to help you ensure you have access to the appropriate RHEL builders. The CentOS Project, as a sponsored project of Red Hat, already has access to RHEL.
If you're using external infrastructure, the ROSI program is likely the best way to get you RHEL. If this is your situation can you email rosi-program@redhat.com with your information and situation? Feel free to keep the devel list CC'ed if you wish. That email address goes to me and another Red Hatter, Jason Brooks, who admins the program.
Thank you.
regards,
bex
Phil
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 23/06/2023 16.39, Brian (bex) Exelbierd wrote:
Hi,
I am bex, Brian Exelbierd, the Red Hat liaison that Josh mentioned in another email.
On Fri, Jun 23, 2023 at 4:07 PM Phil Perry <pperry@elrepo.org mailto:pperry@elrepo.org> wrote:
On 23/06/2023 13:00, Josh Boyer wrote: > On Fri, Jun 23, 2023 at 7:47 AM Peter Georg > <peter.georg@physik.uni-regensburg.de <mailto:peter.georg@physik.uni-regensburg.de>> wrote: >> >> On 22/06/2023 12.56, Josh Boyer wrote: >>> On Thu, Jun 22, 2023 at 6:51 AM Leon Fauster via CentOS-devel >>> <centos-devel@centos.org <mailto:centos-devel@centos.org>> wrote: >>>> >>>> Hi All, >>>> >>>> I wonder if someone is in the role/position to shed some more light on >>>> the topic as announced here >>>> https://www.redhat.com/en/blog/furthering-evolution-centos-stream <https://www.redhat.com/en/blog/furthering-evolution-centos-stream> >>>> >>>> Any deadlines? Does this target only EL10 or also any current release? >>> >>> It is in effect now for RHEL 8 and 9 and will continue for any future >>> RHEL releases. The development and source code for all of these >>> releases will continue to happen through the CentOS Stream project. >>> >>> RHEL 7 and CentOS Linux 7 are not affected. >>> >>>> Would be great if some discussion/communication could be happen. Thanks! >>> >>> If you have more questions, please ask and we can try to address them. >> >> I do indeed have a question. The Kmods SIG currently provides artifacts >> for both CentOS Stream and RHEL. To achieve that we have established >> some automation using GitLab CI to avoid human interaction as far as >> possible. For that to work we do need access to the following sources >> from RHEL (version numbers are just examples): >> >> kernel-5.14.0-284.18.1.el9_2.src.rpm >> >> or >> >> linux-5.14.0-284.18.1.el9_2.tar.xz (which is included in the src.rpm). >> >> So far we have downloaded the tarball from git.centos.org/sources <http://git.centos.org/sources> >> >> However, my understanding is that new versions of these files will not >> be provided anymore. In fact the example listed here (current RHEL 9 >> kernel) is already not provided anymore. > > Your understanding is correct. > >> Is there any way for a CentOS SIG to access these files? Note that it >> needs to be in a way we can automate the access and even detection of >> new versions added. Both has been possible so far. >> >> In a later stage we also need access to >> kernel-devel-5.14.0-284.18.1.el9_2.{aarch64,ppc64le,x86_64}.rpm which we >> have not been able to retrieve from RHEL directly so far, hence we used >> one of the RHEL rebuilds as a source. With the unknown future of these, >> we'd prefer to also have a way to access these directly from RHEL. >> >> Any help in how we can modify our build automation to continue working >> after the announced changes are very much welcome. In case there are non >> we'll very likely have to stop producing artifacts for RHEL (but not for >> CentOS Stream, obviously). > > Red Hat has a program for Open Source projects to access RHEL > directly. I've copied the Red Hat liaison who should be able to talk > with the kmod SIG about this program and see if it's suitable. > > We also have EPEL setup to build directly against RHEL, so we may be > able to look into the solution it is using. I'm not familiar enough > with the infra details to know for sure, but I suspect that would > require some rework of various things. > > josh > Hi Peter, Would it not be easier to build on a RHEL-based build system and then just pull in the Stream specific stuff you need to build against (e.g, Stream kernel / kernel-devel packages) that _are_ publicly available and hence scriptable? As Josh suggests, this is what projects such as EPEL and ELRepo do. Stream isn't really fit for purpose for developing for RHEL, at least in the kernel space.^^ This
Is the kmod SIG building on CentOS Project infrastructure or external infrastructure? If it is CentOS Project infrastructure then the Infra team will need to help you ensure you have access to the appropriate RHEL builders. The CentOS Project, as a sponsored project of Red Hat, already has access to RHEL.
Hi bex,
I already mentioned some of the following in another reply, but let me also answer your question:
The kmods SIG is building on CentOS Project infrastructure. We use the RHEL builders available in CBS. However this only gives us access to RHEL for the build itself, but we already need access to the particular files mentioned earlier before the build.
Maybe I'll explain a little more in detail what we need these files for.
kernel-devel-$EVR.{aarch64,ppc64le,x86_64}.rpm: We need these files to extract the Modules.symvers from to compare these to the symbols required by a kernel module. This allows us to detect if a kernel module needs to be rebuilt for a new kernel release.
kernel source: We build several kernel modules which are part of the RHEL kernel but with some features deliberately disabled. For these kernel modules we extract their source code from the kernel source tarball for every new release to ensure that we have the exact same version as provided by RHEL. We then add some additional patches or change compilation configs to enable features disabled in RHEL. This is especially important for kernel modules which have dependencies on other kernel modules or other kernel modules depend on, e.g., mlx4_core.
Do you think the ROSI program is an option in this case? At the end all we need is access to these files, e.g., by being able to download these files from cdn.redhat.com.
Thanks!
Peter
If you're using external infrastructure, the ROSI program is likely the best way to get you RHEL. If this is your situation can you email rosi-program@redhat.com mailto:rosi-program@redhat.com with your information and situation? Feel free to keep the devel list CC'ed if you wish. That email address goes to me and another Red Hatter, Jason Brooks, who admins the program.
Thank you.
regards,
bex
Phil _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org <mailto:CentOS-devel@centos.org> https://lists.centos.org/mailman/listinfo/centos-devel <https://lists.centos.org/mailman/listinfo/centos-devel>-- Don't rush to reply to this email. Enjoy work/life balance. I read email once a day and am in the CE(S)T timezone. If you have an urgent email, ping me, and consider other mediums for urgent messages in the future.
Brian "bex" Exelbierd (he/him/his) Business Strategist for Communities and Developers Linux Business & Ecosystem Strategy, Red Hat Enterprise Linux @bexelbie | http://www.winglemeyer.org http://www.winglemeyer.org bexelbie@redhat.com mailto:bexelbie@redhat.com
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Am 23.06.23 um 16:39 schrieb Brian (bex) Exelbierd:
Hi,
I am bex, Brian Exelbierd, the Red Hat liaison that Josh mentioned in another email.
Hi Brian,
do you plan to update this article
https://developers.redhat.com/blog/2021/02/03/a-guide-for-using-centos-proje...
for 2023?
On 23/06/2023 14.00, Josh Boyer wrote:
On Fri, Jun 23, 2023 at 7:47 AM Peter Georg peter.georg@physik.uni-regensburg.de wrote:
On 22/06/2023 12.56, Josh Boyer wrote:
On Thu, Jun 22, 2023 at 6:51 AM Leon Fauster via CentOS-devel centos-devel@centos.org wrote:
Hi All,
I wonder if someone is in the role/position to shed some more light on the topic as announced here https://www.redhat.com/en/blog/furthering-evolution-centos-stream
Any deadlines? Does this target only EL10 or also any current release?
It is in effect now for RHEL 8 and 9 and will continue for any future RHEL releases. The development and source code for all of these releases will continue to happen through the CentOS Stream project.
RHEL 7 and CentOS Linux 7 are not affected.
Would be great if some discussion/communication could be happen. Thanks!
If you have more questions, please ask and we can try to address them.
I do indeed have a question. The Kmods SIG currently provides artifacts for both CentOS Stream and RHEL. To achieve that we have established some automation using GitLab CI to avoid human interaction as far as possible. For that to work we do need access to the following sources from RHEL (version numbers are just examples):
kernel-5.14.0-284.18.1.el9_2.src.rpm
or
linux-5.14.0-284.18.1.el9_2.tar.xz (which is included in the src.rpm).
So far we have downloaded the tarball from git.centos.org/sources
However, my understanding is that new versions of these files will not be provided anymore. In fact the example listed here (current RHEL 9 kernel) is already not provided anymore.
Your understanding is correct.
Is there any way for a CentOS SIG to access these files? Note that it needs to be in a way we can automate the access and even detection of new versions added. Both has been possible so far.
In a later stage we also need access to kernel-devel-5.14.0-284.18.1.el9_2.{aarch64,ppc64le,x86_64}.rpm which we have not been able to retrieve from RHEL directly so far, hence we used one of the RHEL rebuilds as a source. With the unknown future of these, we'd prefer to also have a way to access these directly from RHEL.
Any help in how we can modify our build automation to continue working after the announced changes are very much welcome. In case there are non we'll very likely have to stop producing artifacts for RHEL (but not for CentOS Stream, obviously).
Red Hat has a program for Open Source projects to access RHEL directly. I've copied the Red Hat liaison who should be able to talk with the kmod SIG about this program and see if it's suitable.
We also have EPEL setup to build directly against RHEL, so we may be able to look into the solution it is using. I'm not familiar enough with the infra details to know for sure, but I suspect that would require some rework of various things.
Just a note of clarification: Building against RHEL is not the issue as RHEL build targets are available in CBS which we already use. We require access to the files mentioned before to prepare the sources and detect required rebuilds to ensure (kABI) compatibility of the artifacts we deliver.
Assuming the program for Open Source projects to access RHEL directly grants us access to cdn.redhat.com for all RHEL versions and at least the aarch64, ppc64le and x86_64 architectures that might work. Obviously we'd have to have a look at how the authentication can be done from within a CI job running on a gitlab.org shared runner.
josh
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
-
Brian (bex) Exelbierd -
Josh Boyer -
Leon Fauster -
Nico Kadel-Garcia -
Peter Georg -
Phil Perry -
Simon Matter