[EPEL-devel] Fedora EPEL 7 updates-testing report

2022-09-26 Thread updates 
The following Fedora EPEL 7 Security updates need testing:
 Age  URL
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-1b4c7ee66c   
knot-resolver-5.5.3-1.el7


The following builds have been pushed to Fedora EPEL 7 updates-testing

perl-DateTimeX-Easy-0.091-1.el7

Details about builds:



 perl-DateTimeX-Easy-0.091-1.el7 (FEDORA-EPEL-2022-05fe5e5848)
 Parse a date/time string using the best method available

Update Information:

This release improves a documentation.

ChangeLog:

* Mon Sep 26 2022 Petr Pisar  - 0.091-1
- 0.091 bump

References:

  [ 1 ] Bug #2129398 - perl-DateTimeX-Easy-0.091 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2129398


___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@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.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] Fedora EPEL 8 updates-testing report

2022-09-26 Thread updates 
The following Fedora EPEL 8 Security updates need testing:
 Age  URL
  12  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-9d8794e452   
ImageMagick-6.9.12.63-1.el8
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-6a12c208cf   
snakeyaml-1.32-1.el8
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-4c26d6c15b   
knot-resolver-5.5.3-1.el8


The following builds have been pushed to Fedora EPEL 8 updates-testing

chromium-105.0.5195.125-2.el8
perl-DateTimeX-Easy-0.091-1.el8

Details about builds:



 chromium-105.0.5195.125-2.el8 (FEDORA-EPEL-2022-9f67252d52)
 A WebKit (Blink) powered web browser that Google doesn't want you to use

Update Information:

Update to chromium-105.0.5195.125. Fixes the following security issues:
CVE-2022-2007 CVE-2022-2008 CVE-2022-2010 CVE-2022-2011 CVE-2022-2603
CVE-2022-2604 CVE-2022-2605 CVE-2022-2606 CVE-2022-2607 CVE-2022-2608
CVE-2022-2609 CVE-2022-2610 CVE-2022-2611 CVE-2022-2612 CVE-2022-2613
CVE-2022-2614 CVE-2022-2615 CVE-2022-2616 CVE-2022-2617 CVE-2022-2618
CVE-2022-2619 CVE-2022-2620 CVE-2022-2621 CVE-2022-2622 CVE-2022-2623
CVE-2022-2624 CVE-2022-2852 CVE-2022-2854 CVE-2022-2855 CVE-2022-2857
CVE-2022-2858 CVE-2022-2853 CVE-2022-2856 CVE-2022-2859 CVE-2022-2860
CVE-2022-2861 CVE-2022-3038 CVE-2022-3039 CVE-2022-3040 CVE-2022-3041
CVE-2022-3042 CVE-2022-3043 CVE-2022-3044 CVE-2022-3045 CVE-2022-3046
CVE-2022-3071 CVE-2022-3047 CVE-2022-3048 CVE-2022-3049 CVE-2022-3050
CVE-2022-3051 CVE-2022-3052 CVE-2022-3053 CVE-2022-3054 CVE-2022-3055
CVE-2022-3056 CVE-2022-3057 CVE-2022-3058 CVE-2022-3075 CVE-2022-3195
CVE-2022-3196 CVE-2022-3197 CVE-2022-3198 CVE-2022-3199 CVE-2022-3200
CVE-2022-3201  You may also notice that there is not an EL7 build. This is due
to newer Chromium having a dependency that is not available in EL7/EPEL7. As
soon as that package arrives in EPEL7, I will start making EL7 builds again.

ChangeLog:

* Fri Sep 23 2022 Tom Callaway  - 105.0.5195.125-2
- apply upstream fix for wayland menu misplacement bug
* Mon Sep 19 2022 Tom Callaway  - 105.0.5195.125-1
- update to 105.0.5195.125
* Thu Sep  1 2022 Tom Callaway  - 105.0.5195.52-1
- update to 105.0.5195.52
* Thu Aug 18 2022 Tom Callaway  - 104.0.5112.101-1
- update to 104.0.5112.101
* Wed Jul 20 2022 Fedora Release Engineering  - 
103.0.5060.114-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild

References:

  [ 1 ] Bug #2095757 - CVE-2022-2007 chromium-browser: Use after free in WebGPU
https://bugzilla.redhat.com/show_bug.cgi?id=2095757
  [ 2 ] Bug #2095759 - CVE-2022-2008 chromium-browser: Out of bounds memory 
access in WebGL
https://bugzilla.redhat.com/show_bug.cgi?id=2095759
  [ 3 ] Bug #2095760 - CVE-2022-2010 chromium-browser: Out of bounds read in 
compositing
https://bugzilla.redhat.com/show_bug.cgi?id=2095760
  [ 4 ] Bug #2095761 - CVE-2022-2011 chromium-browser: Use after free in ANGLE
https://bugzilla.redhat.com/show_bug.cgi?id=2095761
  [ 5 ] Bug #2114693 - CVE-2022-2603 chromium-browser: Use after free in Omnibox
https://bugzilla.redhat.com/show_bug.cgi?id=2114693
  [ 6 ] Bug #2114694 - CVE-2022-2604 chromium-browser: Use after free in Safe 
Browsing
https://bugzilla.redhat.com/show_bug.cgi?id=2114694
  [ 7 ] Bug #2114695 - CVE-2022-2605 chromium-browser: Out of bounds read in 
Dawn
https://bugzilla.redhat.com/show_bug.cgi?id=2114695
  [ 8 ] Bug #2114696 - CVE-2022-2606 chromium-browser: Use after free in 
Managed devices API
https://bugzilla.redhat.com/show_bug.cgi?id=2114696
  [ 9 ] Bug #2114697 - CVE-2022-2607 chromium-browser: Use after free in Tab 
Strip
https://bugzilla.redhat.com/show_bug.cgi?id=2114697
  [ 10 ] Bug #2114698 - CVE-2022-2608 chromium-browser: Use after free in 
Overview Mode
https://bugzilla.redhat.com/show_bug.cgi?id=2114698
  [ 11 ] Bug #2114699 - CVE-2022-2609 chromium-browser: Use after free in 
Nearby Share
https://bugzilla.redhat.com/show_bug.cgi?id=2114699
  [ 12 ] Bug #2114700 - CVE-2022-2610 chromium-browser: Insufficient policy 
enforcement in Background Fetch
https://bugzilla.redhat.com/show_bug.cgi?id=2114700
  [ 13 ] Bug #2114701 - CVE-2022-2611 chromium-browser: Inappropriate 
implementation in Fullscreen API
https://bugzilla.redhat.com/show_bug.cgi?id=2114701
  [ 14 ] Bug #2114702 - CVE-2022-2612 chromium-browser: Side-channel 
information leakage in Keyboard input
https://bugzilla.redhat.com/show_bug.cgi?id=2114702
  [ 15 ] Bug #2114703 - CVE-2022-2613 chromium-browser: Use after free in Input
https://bugzilla.redhat.com/show_bug.cgi?id=2114703
  [ 16 ] Bug

[EPEL-devel] Re: EPEL RHEL 9 mirror error

2022-09-26 Thread Nick Jahn 
On the security topic, just figured I would share here, as it does go into the 
whole, "make sure your code is signed, and end users don't bypass the security 
checks".

https://www.darkreading.com/attacks-breaches/cisa-zoho-manageengine-rce-bug-under-active-exploit
[https://eu-images.contentstack.com/v3/assets/blt66983808af36a8ef/blt834bf7d7c95999a6/628528f3842aa97d937eefa2/CISA_GK_images_Alamy.jpg]
CISA: Zoho ManageEngine RCE Bug Is Under Active 
Exploit
The US Cybersecurity and Infrastructure Security Agency (CISA) is warning that 
a critical Zoho ManageEngine remote code execution (RCE) flaw, first disclosed 
in June, is now under active attack.
www.darkreading.com


Nicholas Jahn
IT professional
A.S. Network Specialist (www.madisoncollege.edu)

From: Troy Dawson 
Sent: Monday, September 26, 2022 12:41 PM
To: EPEL Development List 
Subject: [EPEL-devel] Re: EPEL RHEL 9 mirror error

That is a very good point.
I think the following are better steps
  rpm --import 
https://dl.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL-9
  dnf install 
https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm

Troy
On Mon, Sep 26, 2022 at 10:28 AM Nick Jahn 
mailto:nick.j...@hotmail.com>> wrote:
Wouldn't it be a better option to show in the documentation how to download and 
install the GPG key first, so you don't have to use the nogpgcheck option? 
Security people like secure options better. 

Nicholas Jahn
IT professional
A.S. Network Specialist 
(www.madisoncollege.edu)

From: Troy Dawson mailto:tdaw...@redhat.com>>
Sent: Monday, September 26, 2022 11:46 AM
To: EPEL Development List 
mailto:epel-devel@lists.fedoraproject.org>>
Subject: [EPEL-devel] Re: EPEL RHEL 9 mirror error

I was able to reproduce the error.
If you do a RHEL install, and select a security profile, it will automatically 
turn on gpg checking for everything.[1]
You then get the error you were showing.

To get around this you need to add the --nogpgcheck option

  dnf install --nogpgcheck 
https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm

Thank you for letting us know.  We'll be sure to update the documentation.

Troy

[1] - 
https://www.mankier.com/5/dnf.conf#Options_for_Both_%5BMain%5D_and_Repo-localpkg_gpgcheck


On Mon, Sep 26, 2022 at 7:25 AM Nick Jahn 
mailto:nick.j...@hotmail.com>> wrote:
I will wipe out this VM, and re-install RHEL 9 and see if it happens again. I 
already know it isn't security based issues, as none of my systems caught 
anything (I'm a Security Architect), and I was able to download the GPG key 
using WGET, and install it using RPM --import.

I'm fairly certain the issue was that the GPG key was not getting deployed.

Nicholas Jahn
IT professional
A.S. Network Specialist

[EPEL-devel] Re: EPEL RHEL 9 mirror error

2022-09-26 Thread Troy Dawson 
That is a very good point.
I think the following are better steps
  rpm --import https://dl.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL-9
  dnf install
https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm

Troy
On Mon, Sep 26, 2022 at 10:28 AM Nick Jahn  wrote:

> Wouldn't it be a better option to show in the documentation how to
> download and install the GPG key first, so you don't have to use the
> nogpgcheck option? Security people like secure options better. 
>
> Nicholas Jahn
> IT professional
> A.S. Network Specialist (www.madisoncollege.edu)
> --
> *From:* Troy Dawson 
> *Sent:* Monday, September 26, 2022 11:46 AM
> *To:* EPEL Development List 
> *Subject:* [EPEL-devel] Re: EPEL RHEL 9 mirror error
>
> I was able to reproduce the error.
> If you do a RHEL install, and select a security profile, it will
> automatically turn on gpg checking for everything.[1]
> You then get the error you were showing.
>
> To get around this you need to add the --nogpgcheck option
>
>   dnf install --nogpgcheck
> https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
> 
>
> Thank you for letting us know.  We'll be sure to update the documentation.
>
> Troy
>
> [1] -
> https://www.mankier.com/5/dnf.conf#Options_for_Both_%5BMain%5D_and_Repo-localpkg_gpgcheck
> 
>
>
> On Mon, Sep 26, 2022 at 7:25 AM Nick Jahn  wrote:
>
> I will wipe out this VM, and re-install RHEL 9 and see if it happens
> again. I already know it isn't security based issues, as none of my systems
> caught anything (I'm a Security Architect), and I was able to download the
> GPG key using WGET, and install it using RPM --import.
>
> I'm fairly certain the issue was that the GPG key was not getting
> deployed.
>
> Nicholas Jahn
> IT professional
> A.S. Network Specialist (www.madisoncollege.edu
> 
> )
> --
> *From:* Stephen Smoogen 
> *Sent:* Monday, September 26, 2022 8:59 AM
> *To:* EPEL Development List 
> *Subject:* [EPEL-devel] Re: EPEL RHEL 9 mirror error
>
>
>
> On Mon, 26 Sept 2022 at 09:31, Nick Jahn  wrote:
>
> Tried that, still getting GPG check FAILED. It seems that the security key
> is not getting deployed correctly.
>
> I manually went to the EPEL repo path
> https://dl.fedoraproject.org/pub/epel/
> 
>  and
> found the EPEL 9 Key, downloaded it and installed the key, and now the
> connection is working. The reason I reached out in the first place was to
> let you know that the deployment was not working as designed, as I know the
> EPEL Key is supposed to download and install when you perform the
> installation of the REPO (which was not happening). This needs to be fixed
> or you need to update the documentation to let others know that they need
> to download and install the RPM GPG KEY for EPEL 9 before using the rest of
> the guide..
>
>
> OK I am doing a retest of the instructions with a fresh Alma 9 install.
> I have installed it with minimal functionality and done a `dnf update` to
> get it up to the latest packages.
> Then I have rebooted it and done the following commands:
> ```
> [root@localhost ~]# sudo dnf config-manager --set-enabled crb
> [root@localhost ~]# dnf install
> https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
>

[EPEL-devel] Re: EPEL RHEL 9 mirror error

2022-09-26 Thread Nick Jahn 
Wouldn't it be a better option to show in the documentation how to download and 
install the GPG key first, so you don't have to use the nogpgcheck option? 
Security people like secure options better. ?

Nicholas Jahn
IT professional
A.S. Network Specialist (www.madisoncollege.edu)

From: Troy Dawson 
Sent: Monday, September 26, 2022 11:46 AM
To: EPEL Development List 
Subject: [EPEL-devel] Re: EPEL RHEL 9 mirror error

I was able to reproduce the error.
If you do a RHEL install, and select a security profile, it will automatically 
turn on gpg checking for everything.[1]
You then get the error you were showing.

To get around this you need to add the --nogpgcheck option

  dnf install --nogpgcheck 
https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm

Thank you for letting us know.  We'll be sure to update the documentation.

Troy

[1] - 
https://www.mankier.com/5/dnf.conf#Options_for_Both_%5BMain%5D_and_Repo-localpkg_gpgcheck


On Mon, Sep 26, 2022 at 7:25 AM Nick Jahn 
mailto:nick.j...@hotmail.com>> wrote:
I will wipe out this VM, and re-install RHEL 9 and see if it happens again. I 
already know it isn't security based issues, as none of my systems caught 
anything (I'm a Security Architect), and I was able to download the GPG key 
using WGET, and install it using RPM --import.

I'm fairly certain the issue was that the GPG key was not getting deployed.

Nicholas Jahn
IT professional
A.S. Network Specialist 
(www.madisoncollege.edu)

From: Stephen Smoogen mailto:ssmoo...@redhat.com>>
Sent: Monday, September 26, 2022 8:59 AM
To: EPEL Development List 
mailto:epel-devel@lists.fedoraproject.org>>
Subject: [EPEL-devel] Re: EPEL RHEL 9 mirror error



On Mon, 26 Sept 2022 at 09:31, Nick Jahn 
mailto:nick.j...@hotmail.com>> wrote:
Tried that, still getting GPG check FAILED. It seems that the security key is 
not getting deployed correctly.

I manually went to the EPEL repo path 
https://dl.fedoraproject.org/pub/epel/
 and found the EPEL 9 Key, downloaded it and installed the key, and now the 
connection is working. The reason I reached out in the first place was to let 
you know that the deployment was not working as designed, as I know the EPEL 
Key is supposed to download and install when you perform the installation of 
the REPO (which was not happening). This needs to be fixed or you need to 
update the documentation to let others know that they need to download and 
install the RPM GPG KEY for EPEL 9 before using the rest of the guide..


OK I am doing a retest of the instructions with a fresh Alma 9 install.
I have installed it with minimal functionality and done a `dnf update` to get 
it up to the latest packages.
Then I have rebooted it and done the following commands:
```
[root@localhost ~]# sudo dnf config-manager --set-enabled crb
[root@localhost ~]# dnf install 
https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
AlmaLinux 9 - CRB

[EPEL-devel] Re: EPEL RHEL 9 mirror error

2022-09-26 Thread Troy Dawson 
I was able to reproduce the error.
If you do a RHEL install, and select a security profile, it will
automatically turn on gpg checking for everything.[1]
You then get the error you were showing.

To get around this you need to add the --nogpgcheck option

  dnf install --nogpgcheck
https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm

Thank you for letting us know.  We'll be sure to update the documentation.

Troy

[1] -
https://www.mankier.com/5/dnf.conf#Options_for_Both_%5BMain%5D_and_Repo-localpkg_gpgcheck


On Mon, Sep 26, 2022 at 7:25 AM Nick Jahn  wrote:

> I will wipe out this VM, and re-install RHEL 9 and see if it happens
> again. I already know it isn't security based issues, as none of my systems
> caught anything (I'm a Security Architect), and I was able to download the
> GPG key using WGET, and install it using RPM --import.
>
> I'm fairly certain the issue was that the GPG key was not getting
> deployed.
>
> Nicholas Jahn
> IT professional
> A.S. Network Specialist (www.madisoncollege.edu)
> --
> *From:* Stephen Smoogen 
> *Sent:* Monday, September 26, 2022 8:59 AM
> *To:* EPEL Development List 
> *Subject:* [EPEL-devel] Re: EPEL RHEL 9 mirror error
>
>
>
> On Mon, 26 Sept 2022 at 09:31, Nick Jahn  wrote:
>
> Tried that, still getting GPG check FAILED. It seems that the security key
> is not getting deployed correctly.
>
> I manually went to the EPEL repo path
> https://dl.fedoraproject.org/pub/epel/ and found the EPEL 9 Key,
> downloaded it and installed the key, and now the connection is working. The
> reason I reached out in the first place was to let you know that the
> deployment was not working as designed, as I know the EPEL Key is supposed
> to download and install when you perform the installation of the REPO
> (which was not happening). This needs to be fixed or you need to update the
> documentation to let others know that they need to download and install the
> RPM GPG KEY for EPEL 9 before using the rest of the guide..
>
>
> OK I am doing a retest of the instructions with a fresh Alma 9 install.
> I have installed it with minimal functionality and done a `dnf update` to
> get it up to the latest packages.
> Then I have rebooted it and done the following commands:
> ```
> [root@localhost ~]# sudo dnf config-manager --set-enabled crb
> [root@localhost ~]# dnf install
> https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
> AlmaLinux 9 - CRB
>
> 3.3 MB/s | 2.5 MB 00:00
> Last metadata expiration check: 0:00:01 ago on Mon 26 Sep 2022 09:52:47 AM
> EDT.
> epel-release-latest-9.noarch.rpm
>
>124 kB/s |  18 kB 00:00
> Dependencies resolved.
>
> ==
>  Package Architecture
>  Version  Repository
> Size
>
> ==
> Installing:
>  epel-releasenoarch
>  9-4.el9  @commandline
> 18 k
>
> Transaction Summary
>
> ==
> Install  1 Package
>
> Total size: 18 k
> Installed size: 25 k
> Is this ok [y/N]: y
> Downloading Packages:
> Running transaction check
> Transaction check succeeded.
> Running transaction test
> Transaction test succeeded.
> Running transaction
>   Preparing:
>
>1/1
>   Installing   : epel-release-9-4.el9.noarch
>
>1/1
>   Running scriptlet: epel-release-9-4.el9.noarch
>
>1/1
> Many EPEL packages require the CodeReady Builder (CRB) repository.
> It is recommended that you run /usr/bin/crb enable to enable the CRB
> repository.
>
>   Verifying: epel-release-9-4.el9.noarch
>
>1/1
>
> Installed:
>   epel-release-9-4.el9.noarch
>
>
>
> Complete!
> [root@localhost ~]# dnf install screen
> Last metadata expiration check: 0:00:21 ago on Mon 26 Sep 2022 09:53:52 AM
> EDT.
> Dependencies resolved.
>
> =
>  Package  Architecture
> Version
> Repository  Size
>
>

[EPEL-devel] Re: EPEL RHEL 9 mirror error

2022-09-26 Thread Nick Jahn 
I will wipe out this VM, and re-install RHEL 9 and see if it happens again. I 
already know it isn't security based issues, as none of my systems caught 
anything (I'm a Security Architect), and I was able to download the GPG key 
using WGET, and install it using RPM --import.

I'm fairly certain the issue was that the GPG key was not getting deployed.

Nicholas Jahn
IT professional
A.S. Network Specialist (www.madisoncollege.edu)

From: Stephen Smoogen 
Sent: Monday, September 26, 2022 8:59 AM
To: EPEL Development List 
Subject: [EPEL-devel] Re: EPEL RHEL 9 mirror error



On Mon, 26 Sept 2022 at 09:31, Nick Jahn 
mailto:nick.j...@hotmail.com>> wrote:
Tried that, still getting GPG check FAILED. It seems that the security key is 
not getting deployed correctly.

I manually went to the EPEL repo path https://dl.fedoraproject.org/pub/epel/ 
and found the EPEL 9 Key, downloaded it and installed the key, and now the 
connection is working. The reason I reached out in the first place was to let 
you know that the deployment was not working as designed, as I know the EPEL 
Key is supposed to download and install when you perform the installation of 
the REPO (which was not happening). This needs to be fixed or you need to 
update the documentation to let others know that they need to download and 
install the RPM GPG KEY for EPEL 9 before using the rest of the guide..


OK I am doing a retest of the instructions with a fresh Alma 9 install.
I have installed it with minimal functionality and done a `dnf update` to get 
it up to the latest packages.
Then I have rebooted it and done the following commands:
```
[root@localhost ~]# sudo dnf config-manager --set-enabled crb
[root@localhost ~]# dnf install 
https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
AlmaLinux 9 - CRB   
  
3.3 MB/s | 2.5 MB 00:00
Last metadata expiration check: 0:00:01 ago on Mon 26 Sep 2022 09:52:47 AM EDT.
epel-release-latest-9.noarch.rpm
  
124 kB/s |  18 kB 00:00
Dependencies resolved.
==
 Package Architecture   
   Version  Repository  
 Size
==
Installing:
 epel-releasenoarch 
   9-4.el9  @commandline
 18 k

Transaction Summary
==
Install  1 Package

Total size: 18 k
Installed size: 25 k
Is this ok [y/N]: y
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing:

  1/1
  Installing   : epel-release-9-4.el9.noarch

  1/1
  Running scriptlet: epel-release-9-4.el9.noarch

  1/1
Many EPEL packages require the CodeReady Builder (CRB) repository.
It is recommended that you run /usr/bin/crb enable to enable the CRB repository.

  Verifying: epel-release-9-4.el9.noarch

  1/1

Installed:
  epel-release-9-4.el9.noarch

Complete!
[root@localhost ~]# dnf install screen
Last metadata expiration check: 0:00:21 ago on Mon 26 Sep 2022 09:53:52 AM EDT.
Dependencies resolved.
=
 Package  Architecture  
   Version   Repository 
 Size

[EPEL-devel] Re: EPEL RHEL 9 mirror error

2022-09-26 Thread Stephen Smoogen 
On Mon, 26 Sept 2022 at 09:31, Nick Jahn  wrote:

> Tried that, still getting GPG check FAILED. It seems that the security key
> is not getting deployed correctly.
>
> I manually went to the EPEL repo path
> https://dl.fedoraproject.org/pub/epel/ and found the EPEL 9 Key,
> downloaded it and installed the key, and now the connection is working. The
> reason I reached out in the first place was to let you know that the
> deployment was not working as designed, as I know the EPEL Key is supposed
> to download and install when you perform the installation of the REPO
> (which was not happening). This needs to be fixed or you need to update the
> documentation to let others know that they need to download and install the
> RPM GPG KEY for EPEL 9 before using the rest of the guide..
>
>
OK I am doing a retest of the instructions with a fresh Alma 9 install.
I have installed it with minimal functionality and done a `dnf update` to
get it up to the latest packages.
Then I have rebooted it and done the following commands:
```
[root@localhost ~]# sudo dnf config-manager --set-enabled crb
[root@localhost ~]# dnf install
https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
AlmaLinux 9 - CRB

  3.3 MB/s | 2.5 MB 00:00
Last metadata expiration check: 0:00:01 ago on Mon 26 Sep 2022 09:52:47 AM
EDT.
epel-release-latest-9.noarch.rpm

   124 kB/s |  18 kB 00:00
Dependencies resolved.
==
 Package Architecture
   Version  Repository
  Size
==
Installing:
 epel-releasenoarch
   9-4.el9  @commandline
  18 k

Transaction Summary
==
Install  1 Package

Total size: 18 k
Installed size: 25 k
Is this ok [y/N]: y
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing:

   1/1
  Installing   : epel-release-9-4.el9.noarch

   1/1
  Running scriptlet: epel-release-9-4.el9.noarch

   1/1
Many EPEL packages require the CodeReady Builder (CRB) repository.
It is recommended that you run /usr/bin/crb enable to enable the CRB
repository.

  Verifying: epel-release-9-4.el9.noarch

   1/1

Installed:
  epel-release-9-4.el9.noarch



Complete!
[root@localhost ~]# dnf install screen
Last metadata expiration check: 0:00:21 ago on Mon 26 Sep 2022 09:53:52 AM
EDT.
Dependencies resolved.
=
 Package  Architecture
Version
Repository  Size
=
Installing:
 screen   x86_64
4.8.0-6.el9   epel
  649 k

Transaction Summary
==
Install  1 Package

Total download size: 649 k
Installed size: 957 k
Is this ok [y/N]: y
Downloading Packages:
screen-4.8.0-6.el9.x86_64.rpm

  1.8 MB/s | 649 kB 00:00
--
Total

  1.2 MB/s | 649 kB 00:00
Extra Packages for Enterprise Linux 9 - x86_64

   1.6 MB/s | 1.6 kB 00:00
Importing GPG key 0x3228467C:
 Userid : "Fedora (epel9) "
 Fingerprint: FF8A D134 4597 106E CE81 3B91 8A38 72BF 3228 467C
 From   : /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-9
Is this ok [y/N]: y
Key imported successfully
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing:

   1/1
  Running scriptlet: screen-4.8.0-6.el9.x86_64

   1/1
  Installing   : screen-4.8.0-6.el9.x86_64

   1/1

[EPEL-devel] Re: EPEL RHEL 9 mirror error

2022-09-26 Thread Nick Jahn 
Tried that, still getting GPG check FAILED. It seems that the security key is 
not getting deployed correctly.

I manually went to the EPEL repo path https://dl.fedoraproject.org/pub/epel/ 
and found the EPEL 9 Key, downloaded it and installed the key, and now the 
connection is working. The reason I reached out in the first place was to let 
you know that the deployment was not working as designed, as I know the EPEL 
Key is supposed to download and install when you perform the installation of 
the REPO (which was not happening). This needs to be fixed or you need to 
update the documentation to let others know that they need to download and 
install the RPM GPG KEY for EPEL 9 before using the rest of the guide..

Nicholas Jahn
IT professional
A.S. Network Specialist (www.madisoncollege.edu)

From: Stephen Smoogen 
Sent: Friday, September 23, 2022 3:31 PM
To: EPEL Development List 
Subject: [EPEL-devel] Re: EPEL RHEL 9 mirror error



On Fri, 23 Sept 2022 at 16:28, Nick Jahn 
mailto:nick.j...@hotmail.com>> wrote:
Just deleted the files, and retried it, and now I'm getting this.


# dnf remove epel-release
then
#  dnf install 
https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
 -y

[root@*hiden* yum.repos.d]# dnf install 
https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
 -y
Updating Subscription Management repositories.
created by dnf config-manager from 
https://dl.fedoraproject.org/pub/epel/9/x86_64/

   3.2 MB/s |  10 MB 00:03
Red Hat Enterprise Linux 9 for x86_64 - AppStream (RPMs)

  10 kB/s | 4.1 kB 00:00
Red Hat Enterprise Linux 9 for x86_64 - BaseOS (RPMs)   

  13 kB/s | 4.1 kB 00:00
Red Hat CodeReady Linux Builder for RHEL 9 x86_64 (RPMs)

 8.4 kB/s | 4.0 kB 00:00
epel-release-latest-9.noarch.rpm

  32 kB/s |  18 kB 00:00
Dependencies resolved.
=
 Package   Architecture 
   Version   Repository 
Size
=
Installing:
 epel-release  noarch   
   9-4.el9   @commandline   
18 k

Transaction Summary
=
Install  1 Package

Total size: 18 k
Installed size: 25 k
Downloading Packages:
Public key for epel-release-latest-9.noarch.rpm is not installed
Error: GPG check FAILED


Nicholas Jahn
IT professional
A.S. Network Specialist