I wonder about the current firefox build 91.13.0-1.el9? Its not on the mirrors (comp 20220829) nor in the last prod compose (20220909) / both lists firefox-91.11.0-2.el9 ... Thanks.
-- Leon
Hi,
On Sat, Sep 10, 2022 at 8:46 PM Leon Fauster via CentOS-devel < centos-devel@centos.org> wrote:
I wonder about the current firefox build 91.13.0-1.el9? Its not on the mirrors (comp 20220829) nor in the last prod compose (20220909) / both lists firefox-91.11.0-2.el9 ... Thanks.
For inclusion in the compose, it has to pass testing. Testing is still in progress.
-- Leon
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Regards
On 11/09/2022 08:41, Branislav Náter wrote:
Hi,
On Sat, Sep 10, 2022 at 8:46 PM Leon Fauster via CentOS-devel <centos-devel@centos.org mailto:centos-devel@centos.org> wrote:
I wonder about the current firefox build 91.13.0-1.el9? Its not on the mirrors (comp 20220829) nor in the last prod compose (20220909) / both lists firefox-91.11.0-2.el9 ... Thanks.For inclusion in the compose, it has to pass testing. Testing is still in progress.
I'm just trying to understand how it can still be in testing for Stream when it has clearly passed testing and been released to RHEL? I thought Stream sat 'upstream' of RHEL?
What extra testing is performed for packages in Stream that is not performed for the same packages in RHEL? What tests are failing? Should we be concerned as RHEL users that we are not receiving the full testing experience?
Hi Phil,
On Sun, Sep 11, 2022 at 10:04:55AM +0100, Phil Perry wrote:
On 11/09/2022 08:41, Branislav Náter wrote:
Hi,
On Sat, Sep 10, 2022 at 8:46 PM Leon Fauster via CentOS-devel <centos-devel@centos.org mailto:centos-devel@centos.org> wrote:
I wonder about the current firefox build 91.13.0-1.el9? Its not on the mirrors (comp 20220829) nor in the last prod compose (20220909) / both lists firefox-91.11.0-2.el9 ... Thanks.For inclusion in the compose, it has to pass testing. Testing is still in progress.
I'm just trying to understand how it can still be in testing for Stream when it has clearly passed testing and been released to RHEL? I thought Stream sat 'upstream' of RHEL?
I wonder if this update is made for security reasons. In that case, updates do go to RHEL first.
Davide wrote a nice explainer for the blog: https://blog.centos.org/2022/09/how-updates-work-in-centos/
Best,
Am 12.09.22 um 14:43 schrieb Michel Alexandre Salim:
Hi Phil,
On Sun, Sep 11, 2022 at 10:04:55AM +0100, Phil Perry wrote:
On 11/09/2022 08:41, Branislav Náter wrote:
Hi,
On Sat, Sep 10, 2022 at 8:46 PM Leon Fauster via CentOS-devel <centos-devel@centos.org mailto:centos-devel@centos.org> wrote:
I wonder about the current firefox build 91.13.0-1.el9? Its not on the mirrors (comp 20220829) nor in the last prod compose (20220909) / both lists firefox-91.11.0-2.el9 ... Thanks.For inclusion in the compose, it has to pass testing. Testing is still in progress.
I'm just trying to understand how it can still be in testing for Stream when it has clearly passed testing and been released to RHEL? I thought Stream sat 'upstream' of RHEL?
I wonder if this update is made for security reasons. In that case, updates do go to RHEL first.
Davide wrote a nice explainer for the blog: https://blog.centos.org/2022/09/how-updates-work-in-centos/
How does the definition of "until the embargo expires" looks like (its a const or a var)?
-- Leon
On Sun, Sep 11, 2022 at 2:05 AM Phil Perry pperry@elrepo.org wrote:
On 11/09/2022 08:41, Branislav Náter wrote:
Hi,
On Sat, Sep 10, 2022 at 8:46 PM Leon Fauster via CentOS-devel <centos-devel@centos.org mailto:centos-devel@centos.org> wrote:
I wonder about the current firefox build 91.13.0-1.el9? Its not onthe
mirrors (comp 20220829) nor in the last prod compose (20220909) /both
lists firefox-91.11.0-2.el9 ... Thanks.For inclusion in the compose, it has to pass testing. Testing is still in progress.
I'm just trying to understand how it can still be in testing for Stream when it has clearly passed testing and been released to RHEL? I thought Stream sat 'upstream' of RHEL?
What extra testing is performed for packages in Stream that is not performed for the same packages in RHEL? What tests are failing? Should we be concerned as RHEL users that we are not receiving the full testing experience?
So people know the sequence of events.
firefox-91.13.0-1.el9_0 was built in RHEL 9.0 on 2022-08-18 - The build passed all of it's gating tests. - This was built on a RHEL 9.0 buildroot, and tested on a RHEL 9.0 buildroot - This got pushed to RHEL 9.0 only
firefox-91.13.0-1.el9 was built on CentOS Stream 9 and RHEL 9.1 on 2022-08-25 - This build did not pass it's gating tests - it still hasn't - This was built on a RHEL 9.1 buildroot, and tested on a RHEL 9.1 buildroot - As far as I can tell, it's got the same tests. It's possible that one or more of the tests went from "warn when it fails" to "fail when it fails", but it looks like the tests are the same. - It's also possible that something changed in RHEL 9.1 that is causing the tests to fail. - I'm not on the firefox team, I'm just looking at the gating system, and to be honest, when I look beyond the "passed" - "failed" parts and into the results, I get lost.
From everything I can see, this delay wasn't the result of an embargo,
simply tests not passing.
Troy
On 12/09/2022 15:47, Troy Dawson wrote:
On Sun, Sep 11, 2022 at 2:05 AM Phil Perry <pperry@elrepo.org mailto:pperry@elrepo.org> wrote:
On 11/09/2022 08:41, Branislav Náter wrote: > Hi, > > > On Sat, Sep 10, 2022 at 8:46 PM Leon Fauster via CentOS-devel > <centos-devel@centos.org <mailto:centos-devel@centos.org> <mailto:centos-devel@centos.org <mailto:centos-devel@centos.org>>> wrote: > > I wonder about the current firefox build 91.13.0-1.el9? Its not on the > mirrors (comp 20220829) nor in the last prod compose (20220909) / both > lists firefox-91.11.0-2.el9 ... Thanks. > > > For inclusion in the compose, it has to pass testing. Testing is still > in progress. > > I'm just trying to understand how it can still be in testing for Stream when it has clearly passed testing and been released to RHEL? I thought Stream sat 'upstream' of RHEL? What extra testing is performed for packages in Stream that is not performed for the same packages in RHEL? What tests are failing? Should we be concerned as RHEL users that we are not receiving the full testing experience?So people know the sequence of events.
firefox-91.13.0-1.el9_0 was built in RHEL 9.0 on 2022-08-18
- The build passed all of it's gating tests.
- This was built on a RHEL 9.0 buildroot, and tested on a RHEL 9.0 buildroot
- This got pushed to RHEL 9.0 only
firefox-91.13.0-1.el9 was built on CentOS Stream 9 and RHEL 9.1 on 2022-08-25
- This build did not pass it's gating tests - it still hasn't
- This was built on a RHEL 9.1 buildroot, and tested on a RHEL 9.1 buildroot
- As far as I can tell, it's got the same tests. It's possible that one
or more of the tests went from "warn when it fails" to "fail when it fails", but it looks like the tests are the same.
- It's also possible that something changed in RHEL 9.1 that is causing
the tests to fail.
- I'm not on the firefox team, I'm just looking at the gating system,
and to be honest, when I look beyond the "passed" - "failed" parts and into the results, I get lost.
From everything I can see, this delay wasn't the result of an embargo, simply tests not passing.
Troy
Thank you Troy - great explanation :-)
Regards,
Phil
Am 12.09.22 um 16:47 schrieb Troy Dawson:
On Sun, Sep 11, 2022 at 2:05 AM Phil Perry <pperry@elrepo.org mailto:pperry@elrepo.org> wrote:
On 11/09/2022 08:41, Branislav Náter wrote: > Hi, > > > On Sat, Sep 10, 2022 at 8:46 PM Leon Fauster via CentOS-devel > <centos-devel@centos.org <mailto:centos-devel@centos.org> <mailto:centos-devel@centos.org <mailto:centos-devel@centos.org>>> wrote: > > I wonder about the current firefox build 91.13.0-1.el9? Its not on the > mirrors (comp 20220829) nor in the last prod compose (20220909) / both > lists firefox-91.11.0-2.el9 ... Thanks. > > > For inclusion in the compose, it has to pass testing. Testing is still > in progress. > > I'm just trying to understand how it can still be in testing for Stream when it has clearly passed testing and been released to RHEL? I thought Stream sat 'upstream' of RHEL? What extra testing is performed for packages in Stream that is not performed for the same packages in RHEL? What tests are failing? Should we be concerned as RHEL users that we are not receiving the full testing experience?So people know the sequence of events.
firefox-91.13.0-1.el9_0 was built in RHEL 9.0 on 2022-08-18
- The build passed all of it's gating tests.
- This was built on a RHEL 9.0 buildroot, and tested on a RHEL 9.0 buildroot
- This got pushed to RHEL 9.0 only
firefox-91.13.0-1.el9 was built on CentOS Stream 9 and RHEL 9.1 on 2022-08-25
- This build did not pass it's gating tests - it still hasn't
- This was built on a RHEL 9.1 buildroot, and tested on a RHEL 9.1 buildroot
- As far as I can tell, it's got the same tests. It's possible that one
or more of the tests went from "warn when it fails" to "fail when it fails", but it looks like the tests are the same.
- It's also possible that something changed in RHEL 9.1 that is causing
the tests to fail.
- I'm not on the firefox team, I'm just looking at the gating system,
and to be honest, when I look beyond the "passed" - "failed" parts and into the results, I get lost.
From everything I can see, this delay wasn't the result of an embargo, simply tests not passing.
I had the understanding that those gates are responsible to sync between RHEL/CENTOS build pipelines? Especially for the major version 9 this should be the state or do I misunderstand the workflow?
-- Leon
On Mon, Sep 12, 2022 at 10:22 AM Leon Fauster via CentOS-devel < centos-devel@centos.org> wrote:
Am 12.09.22 um 16:47 schrieb Troy Dawson:
On Sun, Sep 11, 2022 at 2:05 AM Phil Perry <pperry@elrepo.org mailto:pperry@elrepo.org> wrote:
On 11/09/2022 08:41, Branislav Náter wrote: > Hi, > > > On Sat, Sep 10, 2022 at 8:46 PM Leon Fauster via CentOS-devel > <centos-devel@centos.org <mailto:centos-devel@centos.org> <mailto:centos-devel@centos.org <mailto:centos-devel@centos.org>>> wrote: > > I wonder about the current firefox build 91.13.0-1.el9? Its not on the > mirrors (comp 20220829) nor in the last prod compose (20220909) / both > lists firefox-91.11.0-2.el9 ... Thanks. > > > For inclusion in the compose, it has to pass testing. Testing is still > in progress. > > I'm just trying to understand how it can still be in testing forStream
when it has clearly passed testing and been released to RHEL? Ithought
Stream sat 'upstream' of RHEL? What extra testing is performed for packages in Stream that is not performed for the same packages in RHEL? What tests are failing?Should
we be concerned as RHEL users that we are not receiving the full testing experience?So people know the sequence of events.
firefox-91.13.0-1.el9_0 was built in RHEL 9.0 on 2022-08-18
- The build passed all of it's gating tests.
- This was built on a RHEL 9.0 buildroot, and tested on a RHEL 9.0
buildroot
- This got pushed to RHEL 9.0 only
firefox-91.13.0-1.el9 was built on CentOS Stream 9 and RHEL 9.1 on 2022-08-25
- This build did not pass it's gating tests - it still hasn't
- This was built on a RHEL 9.1 buildroot, and tested on a RHEL 9.1
buildroot
- As far as I can tell, it's got the same tests. It's possible that one
or more of the tests went from "warn when it fails" to "fail when it fails", but it looks like the tests are the same.
- It's also possible that something changed in RHEL 9.1 that is causing
the tests to fail.
- I'm not on the firefox team, I'm just looking at the gating system,
and to be honest, when I look beyond the "passed" - "failed" parts and into the results, I get lost.
From everything I can see, this delay wasn't the result of an embargo, simply tests not passing.
I had the understanding that those gates are responsible to sync between RHEL/CENTOS build pipelines? Especially for the major version 9 this should be the state or do I misunderstand the workflow?
-- Leon
Since I don't exactly know what you are picturing as a workflow, I'll step through an average package update on RHEL9.
1 - maintainer (or others) create a merge request into CentOS Stream 9 gitlab area. 2 - the merge request is gated and tested before being merged. 3 - When that merge request gets merged in the Stream 9 gitlab area, it is also synced over to the internal Brew dist-git area. 4 - The maintainer starts the build in CentOS Stream 9. 5 - When that happens, a build starts on the internal Brew systems. 6 - When both builds finish, they are both gated. The testing only happens internally on the Brew build. 7 - When the internal testing passes successfully, then both RHEL and CS builds are moved on. 8 - Internally, an errata is made, or an errata is updated with the new build, and both packages move to -pending. 9 - Composes are created out of the -pending packages.
Early on there was talk about putting gating between CS and RHEL, but that would make the build repo's different, and eventually the CentOS Stream and RHEL builds would diverge.
I've simplified the steps some, and it's possible I didn't explain everything correctly. So if you need me (or others) to explain or expand on some of the steps, let me know.
Troy
Am 13.09.22 um 00:02 schrieb Troy Dawson:
On Mon, Sep 12, 2022 at 10:22 AM Leon Fauster via CentOS-devel <centos-devel@centos.org mailto:centos-devel@centos.org> wrote:
I had the understanding that those gates are responsible to sync between RHEL/CENTOS build pipelines? Especially for the major version 9 this should be the state or do I misunderstand the workflow? -- LeonSince I don't exactly know what you are picturing as a workflow, I'll step through an average package update on RHEL9.
1 - maintainer (or others) create a merge request into CentOS Stream 9 gitlab area. 2 - the merge request is gated and tested before being merged. 3 - When that merge request gets merged in the Stream 9 gitlab area, it is also synced over to the internal Brew dist-git area. 4 - The maintainer starts the build in CentOS Stream 9. 5 - When that happens, a build starts on the internal Brew systems. 6 - When both builds finish, they are both gated. The testing only happens internally on the Brew build. 7 - When the internal testing passes successfully, then both RHEL and CS builds are moved on. 8 - Internally, an errata is made, or an errata is updated with the new build, and both packages move to -pending. 9 - Composes are created out of the -pending packages.
Early on there was talk about putting gating between CS and RHEL, but that would make the build repo's different, and eventually the CentOS Stream and RHEL builds would diverge.
I've simplified the steps some, and it's possible I didn't explain everything correctly. So if you need me (or others) to explain or expand on some of the steps, let me know.
Thanks for depicting the steps. Very much appreciated! I think point 7 is what I meant with synchronization (both ... moved on). The missed thing in my big picture is a explanation why version 91.13.0 is not (at least) in the stream composes. In particular its not about this package but more about the understanding ...
-- Thanks Leon
On Mon, Sep 12, 2022 at 4:10 PM Leon Fauster via CentOS-devel < centos-devel@centos.org> wrote:
Am 13.09.22 um 00:02 schrieb Troy Dawson:
On Mon, Sep 12, 2022 at 10:22 AM Leon Fauster via CentOS-devel <centos-devel@centos.org mailto:centos-devel@centos.org> wrote:
I had the understanding that those gates are responsible to sync between RHEL/CENTOS build pipelines? Especially for the major version 9 this should be the state or do I misunderstand the workflow? -- LeonSince I don't exactly know what you are picturing as a workflow, I'll step through an average package update on RHEL9.
1 - maintainer (or others) create a merge request into CentOS Stream 9 gitlab area. 2 - the merge request is gated and tested before being merged. 3 - When that merge request gets merged in the Stream 9 gitlab area, it is also synced over to the internal Brew dist-git area. 4 - The maintainer starts the build in CentOS Stream 9. 5 - When that happens, a build starts on the internal Brew systems. 6 - When both builds finish, they are both gated. The testing only happens internally on the Brew build. 7 - When the internal testing passes successfully, then both RHEL and CS builds are moved on. 8 - Internally, an errata is made, or an errata is updated with the new build, and both packages move to -pending. 9 - Composes are created out of the -pending packages.
Early on there was talk about putting gating between CS and RHEL, but that would make the build repo's different, and eventually the CentOS Stream and RHEL builds would diverge.
I've simplified the steps some, and it's possible I didn't explain everything correctly. So if you need me (or others) to explain or expand on some of the steps, let me know.
Thanks for depicting the steps. Very much appreciated! I think point 7 is what I meant with synchronization (both ... moved on). The missed thing in my big picture is a explanation why version 91.13.0 is not (at least) in the stream composes. In particular its not about this package but more about the understanding ...
So, I was about to point you to https://composes.stream.centos.org/development/latest-CentOS-Stream/compose/ which is a daily compose of everything with the -gate tag. But, I see that the new firefox isn't there ... soo ... Something is happening differently with this firefox build. I'll do some more digging.
Troy
Am 13.09.22 um 16:27 schrieb Troy Dawson:
On Mon, Sep 12, 2022 at 4:10 PM Leon Fauster via CentOS-devel <centos-devel@centos.org mailto:centos-devel@centos.org> wrote:
Am 13.09.22 um 00:02 schrieb Troy Dawson: > > > On Mon, Sep 12, 2022 at 10:22 AM Leon Fauster via CentOS-devel > <centos-devel@centos.org <mailto:centos-devel@centos.org> <mailto:centos-devel@centos.org <mailto:centos-devel@centos.org>>> wrote: > > > I had the understanding that those gates are responsible to sync > between > RHEL/CENTOS build pipelines? Especially for the major version 9 this > should be the state or do I misunderstand the workflow? > > -- > Leon > > > Since I don't exactly know what you are picturing as a workflow, I'll > step through an average package update on RHEL9. > > 1 - maintainer (or others) create a merge request into CentOS Stream 9 > gitlab area. > 2 - the merge request is gated and tested before being merged. > 3 - When that merge request gets merged in the Stream 9 gitlab area, it > is also synced over to the internal Brew dist-git area. > 4 - The maintainer starts the build in CentOS Stream 9. > 5 - When that happens, a build starts on the internal Brew systems. > 6 - When both builds finish, they are both gated. The testing only > happens internally on the Brew build. > 7 - When the internal testing passes successfully, then both RHEL and CS > builds are moved on. > 8 - Internally, an errata is made, or an errata is updated with the new > build, and both packages move to -pending. > 9 - Composes are created out of the -pending packages. > > Early on there was talk about putting gating between CS and RHEL, but > that would make the build repo's different, and eventually the CentOS > Stream and RHEL builds would diverge. > > I've simplified the steps some, and it's possible I didn't explain > everything correctly. So if you need me (or others) to explain or > expand on some of the steps, let me know. Thanks for depicting the steps. Very much appreciated! I think point 7 is what I meant with synchronization (both ... moved on). The missed thing in my big picture is a explanation why version 91.13.0 is not (at least) in the stream composes. In particular its not about this package but more about the understanding ...So, I was about to point you to https://composes.stream.centos.org/development/latest-CentOS-Stream/compose/ https://composes.stream.centos.org/development/latest-CentOS-Stream/compose/ which is a daily compose of everything with the -gate tag. But, I see that the new firefox isn't there ... soo ... Something is happening differently with this firefox build. I'll do some more digging.
In the meantime I see that that the RHEL Firefox team is putting all effort into the next ESR release (firefox-102.3.0). We all known that CentOS do not provide guarantees for releasesing in timely manner, but it is very unfortunate to not release the builded and gated packages at all. That is a new quality. I'm sure the community would appreciate at least a late version ... Is it possible that the community helps in the testing phase (assuming that was the place of the issue)?
-- Leon
Am 11.09.22 um 09:41 schrieb Branislav Náter:
On Sat, Sep 10, 2022 at 8:46 PM Leon Fauster via CentOS-devel <centos-devel@centos.org mailto:centos-devel@centos.org> wrote:
I wonder about the current firefox build 91.13.0-1.el9? Its not on the mirrors (comp 20220829) nor in the last prod compose (20220909) / both lists firefox-91.11.0-2.el9 ... Thanks.For inclusion in the compose, it has to pass testing. Testing is still in progress.
Hey, sure. It misses the c9s-candidate tag but to make my question more clearly: 91.11. is in the repos, 91.13. builded, but why is 91.12. still not verified and tagged with c9s-pending (as I understand the proccess)?
Would the version in the "middle" be still blocked because of an embargo? Would the newer version not make such embargo immediately obsolete?
https://kojihub.stream.centos.org/koji/packageinfo?packageID=328
-- Thanks Leon
Phill, I don't see firefox-91.13.0-1.el9 in RHEL.
On Sun, Sep 11, 2022 at 1:56 PM Leon Fauster via CentOS-devel < centos-devel@centos.org> wrote:
Am 11.09.22 um 09:41 schrieb Branislav Náter:
On Sat, Sep 10, 2022 at 8:46 PM Leon Fauster via CentOS-devel <centos-devel@centos.org mailto:centos-devel@centos.org> wrote:
I wonder about the current firefox build 91.13.0-1.el9? Its not onthe
mirrors (comp 20220829) nor in the last prod compose (20220909) /both
lists firefox-91.11.0-2.el9 ... Thanks.For inclusion in the compose, it has to pass testing. Testing is still in progress.
Hey, sure. It misses the c9s-candidate tag but to make my question more clearly: 91.11. is in the repos, 91.13. builded, but why is 91.12. still not verified and tagged with c9s-pending (as I understand the proccess)?
Would the version in the "middle" be still blocked because of an embargo? Would the newer version not make such embargo immediately obsolete?
I don't want to speak on behalf of the RHEL Firefox team, but I would guess that they are now focusing on releasing firefox-91.13.0-1.el9 for CentOS (thus skipping 91.12). Sorry to not provide more info.
https://kojihub.stream.centos.org/koji/packageinfo?packageID=328
-- Thanks Leon
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Regards
I have no idea why you are not seeing it, but it's been there for 2 and a half weeks on my installs::
$ rpm -qi firefox Name : firefox Version : 91.13.0 Release : 1.el9_0 Architecture: x86_64 Install Date: Wed 24 Aug 2022 06:19:44 PM EDT Group : Unspecified Size : 277674420 License : MPLv1.1 or GPLv2+ or LGPLv2+ Signature : RSA/SHA256, Mon 22 Aug 2022 03:47:12 AM EDT, Key ID 199e2f91fd431d51 Source RPM : firefox-91.13.0-1.el9_0.src.rpm Build Date : Thu 18 Aug 2022 03:25:16 AM EDT Build Host : x86-64-02.build.eng.rdu2.redhat.com Packager : Red Hat, Inc. http://bugzilla.redhat.com/bugzilla Vendor : Red Hat, Inc. URL : https://www.mozilla.org/firefox/ Summary : Mozilla Firefox Web browser Description : Mozilla Firefox is an open-source web browser, designed for standards compliance, performance and portability.
On 11/09/2022 13:53, Branislav Náter wrote:
Phill, I don't see firefox-91.13.0-1.el9 in RHEL.
On Sun, Sep 11, 2022 at 1:56 PM Leon Fauster via CentOS-devel <centos-devel@centos.org mailto:centos-devel@centos.org> wrote:
Am 11.09.22 um 09:41 schrieb Branislav Náter: > On Sat, Sep 10, 2022 at 8:46 PM Leon Fauster via CentOS-devel > <centos-devel@centos.org <mailto:centos-devel@centos.org> <mailto:centos-devel@centos.org <mailto:centos-devel@centos.org>>> wrote: > > I wonder about the current firefox build 91.13.0-1.el9? Its not on the > mirrors (comp 20220829) nor in the last prod compose (20220909) / both > lists firefox-91.11.0-2.el9 ... Thanks. > > > For inclusion in the compose, it has to pass testing. Testing is still > in progress. > Hey, sure. It misses the c9s-candidate tag but to make my question more clearly: 91.11. is in the repos, 91.13. builded, but why is 91.12. still not verified and tagged with c9s-pending (as I understand the proccess)? Would the version in the "middle" be still blocked because of an embargo? Would the newer version not make such embargo immediately obsolete?I don't want to speak on behalf of the RHEL Firefox team, but I would guess that they are now focusing on releasing firefox-91.13.0-1.el9 for CentOS (thus skipping 91.12). Sorry to not provide more info.
https://kojihub.stream.centos.org/koji/packageinfo?packageID=328 <https://kojihub.stream.centos.org/koji/packageinfo?packageID=328> -- Thanks Leon _______________________________________________ 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>Regards
Branislav Náter Principal Quality Engineer, Stacks QE IRC: bnater at #qa #urt #brno Red Hat Czech s.r.o., Purkyňova 115, 612 00, Brno, Czech Republic redhat.com http://redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted http://redhat.com/trusted
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
-
Branislav Náter -
Leon Fauster -
Michel Alexandre Salim -
Phil Perry -
Trevor Hemsley -
Troy Dawson