[EPEL-devel] Re: EPEL RHEL 9 mirror error
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]<https://www.darkreading.com/attacks-breaches/cisa-zoho-manageengine-rce-bug-under-active-exploit> CISA: Zoho ManageEngine RCE Bug Is Under Active Exploit<https://www.darkreading.com/attacks-breaches/cisa-zoho-manageengine-rce-bug-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<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2FRPM-GPG-KEY-EPEL-9&data=05%7C01%7C%7Cf3aa3ba65e904420853508da9fe6767d%7C84df9e7fe9f640afb435%7C1%7C0%7C637998109485601918%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=mqfDJvfB9kOEtLdghjgS7W2HQCariGG%2BcouPau4xWBI%3D&reserved=0> dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2Fepel-release-latest-9.noarch.rpm&data=05%7C01%7C%7Cf3aa3ba65e904420853508da9fe6767d%7C84df9e7fe9f640afb435%7C1%7C0%7C637998109485601918%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1v8v5xUswULKCFRrZgb15MTVjRNRKImZF6V78SZz4s0%3D&reserved=0> 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<https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.madisoncollege.edu%2F&data=05%7C01%7C%7Cf3aa3ba65e904420853508da9fe6767d%7C84df9e7fe9f640afb435%7C1%7C0%7C637998109485601918%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=r4PPFetthmJBIaffVt%2BN8hPwn%2F3gjrcXBRAVJoTtOpw%3D&reserved=0>) 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<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2Fepel-release-latest-9.noarch.rpm&data=05%7C01%7C%7Cf3aa3ba65e904420853508da9fe6767d%7C84df9e7fe9f640afb435%7C1%7C0%7C637998109485601918%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1v8v5xUswULKCFRrZgb15MTVjRNRKImZF6V78SZz4s0%3D&reserved=0> 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<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.mankier.com%2F5%2Fdnf.conf%23Options_for_Both_%255BMain%255D_and_Repo-localpkg_gpgcheck&data=05%7C01%7C%7Cf3aa3ba65e904420853508da9fe6767d%7C84df9e7fe9f640afb435%7C1%7C0%7C637998109485601918%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=sjT3BPAoKy8HVZ%2F%2FA11uLkd92k3e88kor5ifEfWvYtc%3D&reserved=0> 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
[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 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 > <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2Fepel-release-latest-9.noarch.rpm&data=05%7C01%7C%7C1fa3525287c241393aee08da9fdeb15c%7C84df9e7fe9f640afb435%7C1%7C0%7C637998076116157808%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=C8yD7Qkt%2FE0aJboL0l1g1kUZXvxDEB3011f9UJgCDSk%3D&reserved=0> > > 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 > <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.mankier.com%2F5%2Fdnf.conf%23Options_for_Both_%255BMain%255D_and_Repo-localpkg_gpgcheck&data=05%7C01%7C%7C1fa3525287c241393aee08da9fdeb15c%7C84df9e7fe9f640afb435%7C1%7C0%7C637998076116157808%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=b%2FtrDDAy8c3Iwp%2FC35%2BoYhdCMgCdaHiP%2B72w7vpo5%2Bs%3D&reserved=0> > > > 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 > <https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.madisoncollege.edu%2F&data=05%7C01%7C%7C1fa3525287c241393aee08da9fdeb15c%7C84df9e7fe9f640afb435%7C1%7C0%7C637998076116157808%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8LvzqKw%2B8jI3asDNIbOwK%2B0btNGn%2Fo3Wl%2B2CQdOCqaM%3D&reserved=0> > ) > -- > *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/ > <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2F&data=05%7C01%7C%7C1fa3525287c241393aee08da9fdeb15c%7C84df9e7fe9f640afb435%7C1%7C0%7C637998076116157808%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8tTjjlYs%2FdS0hjcQysjjPjKok1t1KQYJ5vluGqlStOY%3D&reserved=0> > 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 >
[EPEL-devel] Re: EPEL RHEL 9 mirror error
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<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2Fepel-release-latest-9.noarch.rpm&data=05%7C01%7C%7C1fa3525287c241393aee08da9fdeb15c%7C84df9e7fe9f640afb435%7C1%7C0%7C637998076116157808%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=C8yD7Qkt%2FE0aJboL0l1g1kUZXvxDEB3011f9UJgCDSk%3D&reserved=0> 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<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.mankier.com%2F5%2Fdnf.conf%23Options_for_Both_%255BMain%255D_and_Repo-localpkg_gpgcheck&data=05%7C01%7C%7C1fa3525287c241393aee08da9fdeb15c%7C84df9e7fe9f640afb435%7C1%7C0%7C637998076116157808%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=b%2FtrDDAy8c3Iwp%2FC35%2BoYhdCMgCdaHiP%2B72w7vpo5%2Bs%3D&reserved=0> 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<https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.madisoncollege.edu%2F&data=05%7C01%7C%7C1fa3525287c241393aee08da9fdeb15c%7C84df9e7fe9f640afb435%7C1%7C0%7C637998076116157808%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8LvzqKw%2B8jI3asDNIbOwK%2B0btNGn%2Fo3Wl%2B2CQdOCqaM%3D&reserved=0>) 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/<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2F&data=05%7C01%7C%7C1fa3525287c241393aee08da9fdeb15c%7C84df9e7fe9f640afb435%7C1%7C0%7C637998076116157808%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8tTjjlYs%2FdS0hjcQysjjPjKok1t1KQYJ5vluGqlStOY%3D&reserved=0> 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<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2Fepel-release-latest-9.noarch.rpm&data=05%7C01%7C%7C1fa3525287c241393aee08da9fdeb15c%7C84df9e7fe9f640afb435%7C
[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 > 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
[EPEL-devel] Re: EPEL RHEL 9 mirror error
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
[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 = 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 R
[EPEL-devel] Re: EPEL RHEL 9 mirror error
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<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2Fepel-release-latest-9.noarch.rpm&data=05%7C01%7C%7C364dac83e26d4ec49aa008da9da2fe27%7C84df9e7fe9f640afb435%7C1%7C0%7C637995620673023973%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=LlyomfZS%2BdTyQIb4Jefs2H0rNZDpCWjy1hv2XV5e1uw%3D&reserved=0> -y [root@*hiden* yum.repos.d]# dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2Fepel-release-latest-9.noarch.rpm&data=05%7C01%7C%7C364dac83e26d4ec49aa008da9da2fe27%7C84df9e7fe9f640afb435%7C1%7C0%7C637995620673023973%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=LlyomfZS%2BdTyQIb4Jefs2H0rNZDpCWjy1hv2XV5e1uw%3D&reserved=0> -y Updating Subscription Management repositories. created by dnf config-manager from https://dl.fedoraproject.org/pub/epel/9/x86_64/<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2F9%2Fx86_64%2F&data=05%7C01%7C%7C364dac83e26d4ec49aa008da9da2fe27%7C84df9e7fe9f640afb435%7C1%7C0%7C637995620673180192%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZcCDWiYUuZuZ3eCFbTeuMgwvUMTkSNUr66JG9%2F0ryWs%3D&reserved=0> 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 (www.madis
[EPEL-devel] Re: EPEL RHEL 9 mirror error
On Fri, 23 Sept 2022 at 16:28, Nick Jahn 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 (www.madisoncollege.edu) > -------------- > *From:* Stephen Smoogen > *Sent:* Friday, September 23, 2022 2:38 PM > *To:* EPEL Development List > *Subject:* [EPEL-devel] Re: EPEL RHEL 9 mirror error > > > > On Fri, 23 Sept 2022 at 15:09, Nick Jahn wrote: > > Brand new server, followed guide from EPEL setting it up, first added repo > to server. > > > Hmmm, which guide to setting EPEL up has this? The one that should be used > is at https://docs.fedoraproject.org/en-US/epel/#_el9 > <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.fedoraproject.org%2Fen-US%2Fepel%2F%23_el9&data=05%7C01%7C%7C99500550851943e3b74008da9d9b33dd%7C84df9e7fe9f640afb435%7C1%7C0%7C637995587216883570%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=npNYvW%2Bs%2B1pMiZOr7I%2BKELfDPhcYrpKhCZpCCX7qsvY%3D&reserved=0> > and I will sort of copy what it says here: > > ``` > # if you are running Alma/Rocky/EuroLinux you would do > sudo dnf config-manager --set-enabled crb > # else if you are running RHEL9 > sudo subscription-manager repos --enable > codeready-builder-for-rhel-9-$(arch)-rpms > # > dnf install > https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm > <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2Fepel-release-latest-9.noarch.rpm&data=05%7C01%7C%7C99500550851943e3b74008da9d9b33dd%7C84df9e7fe9f640afb435%7C1%7C0%7C637995587216883570%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ujOvC1bFfHJXvnaKgXgXXmQFMjzpYn8YROPbSYvk29g%3D&reserved=0> > > ``` > will install the correct file in /etc/yum.repos.d/ which should have the > correct permissions > > > > > Tried your suggestion, and I get this. > > bash: cd: /etc/yum/repos.d/: No such file or directory > > > That should be /etc/yum.repos.d not /etc/yum/repos.d/ > > > > Nicholas Jahn > IT professional > A.S. Network Specialist (www.madisoncollege.edu > <https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.madisoncollege.edu%2F&data=05%7C01%7C%7C99500550851943e3b74008da9d9b33dd%7C84df9e7fe9f640afb435%7C1%7C0%7C637995587216883570%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=SOX3Gq5b2Hu5PaM5lJvAwiQ3mQuLuc9mLrcUfn8Ppt0%3D&am
[EPEL-devel] Re: EPEL RHEL 9 mirror error
El El vie, 23 de septiembre de 2022 a la(s) 3:30 p.m., Stephen Smoogen < ssmoo...@redhat.com> escribió: > > > On Fri, 23 Sept 2022 at 16:23, Nick Jahn wrote: > >> Yep that is the one, it gave me the repo file that resulted in this. >> >> > OK something is wrong with what you got. I just did it and the file should > look like the following after it was installed: > > ``` > [epel] > name=Extra Packages for Enterprise Linux $releasever - $basearch > # It is much more secure to use the metalink, but if you wish to use a > local mirror > # place its address here. > #baseurl= > https://download.example/pub/epel/$releasever/Everything/$basearch/ > metalink= > https://mirrors.fedoraproject.org/metalink?repo=epel-$releasever&arch=$basearch&infra=$infra&content=$contentdir > enabled=1 > gpgcheck=1 > countme=1 > gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-$releasever > > [epel-debuginfo] > name=Extra Packages for Enterprise Linux $releasever - $basearch - Debug > # It is much more secure to use the metalink, but if you wish to use a > local mirror > # place its address here. > #baseurl= > https://download.example/pub/epel/$releasever/Everything/$basearch/debug/ > metalink= > https://mirrors.fedoraproject.org/metalink?repo=epel-debug-$releasever&arch=$basearch&infra=$infra&content=$contentdir > enabled=0 > gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-$releasever > gpgcheck=1 > > [epel-source] > name=Extra Packages for Enterprise Linux $releasever - $basearch - Source > # It is much more secure to use the metalink, but if you wish to use a > local mirror > # place its address here. > #baseurl= > https://download.example/pub/epel/$releasever/Everything/source/tree/ > metalink= > https://mirrors.fedoraproject.org/metalink?repo=epel-source-$releasever&arch=$basearch&infra=$infra&content=$contentdir > enabled=0 > gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-$releasever > gpgcheck=1 > ``` > > > > >> Nicholas Jahn >> IT professional >> A.S. Network Specialist (www.madisoncollege.edu) >> -- >> *From:* Stephen Smoogen >> *Sent:* Friday, September 23, 2022 2:38 PM >> *To:* EPEL Development List >> *Subject:* [EPEL-devel] Re: EPEL RHEL 9 mirror error >> >> >> >> On Fri, 23 Sept 2022 at 15:09, Nick Jahn wrote: >> >> Brand new server, followed guide from EPEL setting it up, first added >> repo to server. >> >> >> Hmmm, which guide to setting EPEL up has this? The one that should be >> used is at https://docs.fedoraproject.org/en-US/epel/#_el9 >> <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.fedoraproject.org%2Fen-US%2Fepel%2F%23_el9&data=05%7C01%7C%7C99500550851943e3b74008da9d9b33dd%7C84df9e7fe9f640afb435%7C1%7C0%7C637995587216883570%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=npNYvW%2Bs%2B1pMiZOr7I%2BKELfDPhcYrpKhCZpCCX7qsvY%3D&reserved=0> >> and I will sort of copy what it says here: >> >> ``` >> # if you are running Alma/Rocky/EuroLinux you would do >> sudo dnf config-manager --set-enabled crb >> # else if you are running RHEL9 >> sudo subscription-manager repos --enable >> codeready-builder-for-rhel-9-$(arch)-rpms >> # >> dnf install >> https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm >> <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2Fepel-release-latest-9.noarch.rpm&data=05%7C01%7C%7C99500550851943e3b74008da9d9b33dd%7C84df9e7fe9f640afb435%7C1%7C0%7C637995587216883570%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ujOvC1bFfHJXvnaKgXgXXmQFMjzpYn8YROPbSYvk29g%3D&reserved=0> >> >> ``` >> will install the correct file in /etc/yum.repos.d/ which should have the >> correct permissions >> >> >> >> >> Tried your suggestion, and I get this. >> >> bash: cd: /etc/yum/repos.d/: No such file or directory >> >> >> That should be /etc/yum.repos.d not /etc/yum/repos.d/ >> >> >> >> Nicholas Jahn >> IT professional >> A.S. Network Specialist (www.madisoncollege.edu >> <https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.madisoncollege.edu%2F&data=05%7C01%7C%7C99500550851943e3b74008da9d9b33dd%7C84df9e7fe9f640afb435%7C1%7C0%7C637995587216883570%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%
[EPEL-devel] Re: EPEL RHEL 9 mirror error
On Fri, 23 Sept 2022 at 16:23, Nick Jahn wrote: > Yep that is the one, it gave me the repo file that resulted in this. > > OK something is wrong with what you got. I just did it and the file should look like the following after it was installed: ``` [epel] name=Extra Packages for Enterprise Linux $releasever - $basearch # It is much more secure to use the metalink, but if you wish to use a local mirror # place its address here. #baseurl=https://download.example/pub/epel/$releasever/Everything/$basearch/ metalink= https://mirrors.fedoraproject.org/metalink?repo=epel-$releasever&arch=$basearch&infra=$infra&content=$contentdir enabled=1 gpgcheck=1 countme=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-$releasever [epel-debuginfo] name=Extra Packages for Enterprise Linux $releasever - $basearch - Debug # It is much more secure to use the metalink, but if you wish to use a local mirror # place its address here. #baseurl= https://download.example/pub/epel/$releasever/Everything/$basearch/debug/ metalink= https://mirrors.fedoraproject.org/metalink?repo=epel-debug-$releasever&arch=$basearch&infra=$infra&content=$contentdir enabled=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-$releasever gpgcheck=1 [epel-source] name=Extra Packages for Enterprise Linux $releasever - $basearch - Source # It is much more secure to use the metalink, but if you wish to use a local mirror # place its address here. #baseurl= https://download.example/pub/epel/$releasever/Everything/source/tree/ metalink= https://mirrors.fedoraproject.org/metalink?repo=epel-source-$releasever&arch=$basearch&infra=$infra&content=$contentdir enabled=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-$releasever gpgcheck=1 ``` > Nicholas Jahn > IT professional > A.S. Network Specialist (www.madisoncollege.edu) > -- > *From:* Stephen Smoogen > *Sent:* Friday, September 23, 2022 2:38 PM > *To:* EPEL Development List > *Subject:* [EPEL-devel] Re: EPEL RHEL 9 mirror error > > > > On Fri, 23 Sept 2022 at 15:09, Nick Jahn wrote: > > Brand new server, followed guide from EPEL setting it up, first added repo > to server. > > > Hmmm, which guide to setting EPEL up has this? The one that should be used > is at https://docs.fedoraproject.org/en-US/epel/#_el9 > <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.fedoraproject.org%2Fen-US%2Fepel%2F%23_el9&data=05%7C01%7C%7C99500550851943e3b74008da9d9b33dd%7C84df9e7fe9f640afb435%7C1%7C0%7C637995587216883570%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=npNYvW%2Bs%2B1pMiZOr7I%2BKELfDPhcYrpKhCZpCCX7qsvY%3D&reserved=0> > and I will sort of copy what it says here: > > ``` > # if you are running Alma/Rocky/EuroLinux you would do > sudo dnf config-manager --set-enabled crb > # else if you are running RHEL9 > sudo subscription-manager repos --enable > codeready-builder-for-rhel-9-$(arch)-rpms > # > dnf install > https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm > <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2Fepel-release-latest-9.noarch.rpm&data=05%7C01%7C%7C99500550851943e3b74008da9d9b33dd%7C84df9e7fe9f640afb435%7C1%7C0%7C637995587216883570%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ujOvC1bFfHJXvnaKgXgXXmQFMjzpYn8YROPbSYvk29g%3D&reserved=0> > > ``` > will install the correct file in /etc/yum.repos.d/ which should have the > correct permissions > > > > > Tried your suggestion, and I get this. > > bash: cd: /etc/yum/repos.d/: No such file or directory > > > That should be /etc/yum.repos.d not /etc/yum/repos.d/ > > > > Nicholas Jahn > IT professional > A.S. Network Specialist (www.madisoncollege.edu > <https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.madisoncollege.edu%2F&data=05%7C01%7C%7C99500550851943e3b74008da9d9b33dd%7C84df9e7fe9f640afb435%7C1%7C0%7C637995587216883570%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=SOX3Gq5b2Hu5PaM5lJvAwiQ3mQuLuc9mLrcUfn8Ppt0%3D&reserved=0> > ) > -- > *From:* Troy Dawson > *Sent:* Friday, September 23, 2022 1:21 PM > *To:* EPEL Development List > *Subject:* [EPEL-devel] Re: EPEL RHEL 9 mirror error > > On Fri, Sep 23, 2022 at 10:37 AM Nick Jahn wrote: > > Errors during downloading metadata for repository > 'dl.fedoraproject.org_pub_epel_9_x86_64_': > - Status code: 404 for > https://dl.fedoraproject
[EPEL-devel] Re: EPEL RHEL 9 mirror error
Just deleted the files, and retried it, and now I'm getting this. [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 (www.madisoncollege.edu) From: Stephen Smoogen Sent: Friday, September 23, 2022 2:38 PM To: EPEL Development List Subject: [EPEL-devel] Re: EPEL RHEL 9 mirror error On Fri, 23 Sept 2022 at 15:09, Nick Jahn mailto:nick.j...@hotmail.com>> wrote: Brand new server, followed guide from EPEL setting it up, first added repo to server. Hmmm, which guide to setting EPEL up has this? The one that should be used is at https://docs.fedoraproject.org/en-US/epel/#_el9<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.fedoraproject.org%2Fen-US%2Fepel%2F%23_el9&data=05%7C01%7C%7C99500550851943e3b74008da9d9b33dd%7C84df9e7fe9f640afb435%7C1%7C0%7C637995587216883570%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=npNYvW%2Bs%2B1pMiZOr7I%2BKELfDPhcYrpKhCZpCCX7qsvY%3D&reserved=0> and I will sort of copy what it says here: ``` # if you are running Alma/Rocky/EuroLinux you would do sudo dnf config-manager --set-enabled crb # else if you are running RHEL9 sudo subscription-manager repos --enable codeready-builder-for-rhel-9-$(arch)-rpms # dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2Fepel-release-latest-9.noarch.rpm&data=05%7C01%7C%7C99500550851943e3b74008da9d9b33dd%7C84df9e7fe9f640afb435%7C1%7C0%7C637995587216883570%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ujOvC1bFfHJXvnaKgXgXXmQFMjzpYn8YROPbSYvk29g%3D&reserved=0> ``` will install the correct file in /etc/yum.repos.d/ which should have the correct permissions Tried your suggestion, and I get this. bash: cd: /etc/yum/repos.d/: No such file or directory That should be /etc/yum.repos.d not /etc/yum/repos.d/ Nicholas Jahn IT professional A.S. Network Specialist (www.madisoncollege.edu<https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.madisoncollege.edu%2F&data=05%7C01%7C%7C99500550851943e3b74008da9d9b33dd%7C84df9e7fe9f640afb435%7C1%7C0%7C637995587216883570%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=SOX3Gq5b2Hu5PaM5lJvAwiQ3mQuLuc9mLrcUfn8Ppt0%3D&reserved=0>) From: Troy Dawson mailto:tdaw.
[EPEL-devel] Re: EPEL RHEL 9 mirror error
Yep that is the one, it gave me the repo file that resulted in this. Nicholas Jahn IT professional A.S. Network Specialist (www.madisoncollege.edu) From: Stephen Smoogen Sent: Friday, September 23, 2022 2:38 PM To: EPEL Development List Subject: [EPEL-devel] Re: EPEL RHEL 9 mirror error On Fri, 23 Sept 2022 at 15:09, Nick Jahn mailto:nick.j...@hotmail.com>> wrote: Brand new server, followed guide from EPEL setting it up, first added repo to server. Hmmm, which guide to setting EPEL up has this? The one that should be used is at https://docs.fedoraproject.org/en-US/epel/#_el9<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.fedoraproject.org%2Fen-US%2Fepel%2F%23_el9&data=05%7C01%7C%7C99500550851943e3b74008da9d9b33dd%7C84df9e7fe9f640afb435%7C1%7C0%7C637995587216883570%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=npNYvW%2Bs%2B1pMiZOr7I%2BKELfDPhcYrpKhCZpCCX7qsvY%3D&reserved=0> and I will sort of copy what it says here: ``` # if you are running Alma/Rocky/EuroLinux you would do sudo dnf config-manager --set-enabled crb # else if you are running RHEL9 sudo subscription-manager repos --enable codeready-builder-for-rhel-9-$(arch)-rpms # dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2Fepel-release-latest-9.noarch.rpm&data=05%7C01%7C%7C99500550851943e3b74008da9d9b33dd%7C84df9e7fe9f640afb435%7C1%7C0%7C637995587216883570%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ujOvC1bFfHJXvnaKgXgXXmQFMjzpYn8YROPbSYvk29g%3D&reserved=0> ``` will install the correct file in /etc/yum.repos.d/ which should have the correct permissions Tried your suggestion, and I get this. bash: cd: /etc/yum/repos.d/: No such file or directory That should be /etc/yum.repos.d not /etc/yum/repos.d/ Nicholas Jahn IT professional A.S. Network Specialist (www.madisoncollege.edu<https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.madisoncollege.edu%2F&data=05%7C01%7C%7C99500550851943e3b74008da9d9b33dd%7C84df9e7fe9f640afb435%7C1%7C0%7C637995587216883570%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=SOX3Gq5b2Hu5PaM5lJvAwiQ3mQuLuc9mLrcUfn8Ppt0%3D&reserved=0>) From: Troy Dawson mailto:tdaw...@redhat.com>> Sent: Friday, September 23, 2022 1:21 PM To: EPEL Development List mailto:epel-devel@lists.fedoraproject.org>> Subject: [EPEL-devel] Re: EPEL RHEL 9 mirror error On Fri, Sep 23, 2022 at 10:37 AM Nick Jahn mailto:nick.j...@hotmail.com>> wrote: Errors during downloading metadata for repository 'dl.fedoraproject.org_pub_epel_9_x86_64_': - Status code: 404 for https://dl.fedoraproject.org/pub/epel/9/x86_64/repodata/repomd.xml<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2F9%2Fx86_64%2Frepodata%2Frepomd.xml&data=05%7C01%7C%7C99500550851943e3b74008da9d9b33dd%7C84df9e7fe9f640afb435%7C1%7C0%7C637995587216883570%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Gqy5Pc%2FTyhxvloDly7trMNw4WaGeeHFqE7b2pdlN1B0%3D&reserved=0> (IP: 38.145.60.24) Error: Failed to download metadata for repo 'dl.fedoraproject.org_pub_epel_9_x86_64_': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried That URL is wrong, it should be https://dl.fedoraproject.org/pub/epel/9/Everything/x86_64/repodata/repomd.xml<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2F9%2FEverything%2Fx86_64%2Frepodata%2Frepomd.xml&data=05%7C01%7C%7C99500550851943e3b74008da9d9b33dd%7C84df9e7fe9f640afb435%7C1%7C0%7C637995587216883570%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=fXO4z3S00BXHlACh0LRARQjjYNmg%2BmI%2Bqqb1FTLbtB8%3D&reserved=0> Looking at the name, and the URL, that is from a custom repo config file. The easiest way to spot that is the name 'dl.fedoraproject.org_pub_epel_9_x86_64_' It should be "Extra Packages for Enterprise Linux 9 - x86_64" You should contact the machine's administrator. If you are the machine's administrator, then I would search for dl.fedoraproject.org<https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdl.fedoraproject.org%2F&data=05%7C01%7C%7C99500550851943e3b74008da9d9b33dd%7C84df9e7fe9f640afb435%7C1%7C0%7C637995587216883570%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMz
[EPEL-devel] Re: EPEL RHEL 9 mirror error
On Fri, 23 Sept 2022 at 15:09, Nick Jahn wrote: > Brand new server, followed guide from EPEL setting it up, first added repo > to server. > > Hmmm, which guide to setting EPEL up has this? The one that should be used is at https://docs.fedoraproject.org/en-US/epel/#_el9 and I will sort of copy what it says here: ``` # if you are running Alma/Rocky/EuroLinux you would do sudo dnf config-manager --set-enabled crb # else if you are running RHEL9 sudo subscription-manager repos --enable codeready-builder-for-rhel-9-$(arch)-rpms # dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` will install the correct file in /etc/yum.repos.d/ which should have the correct permissions > Tried your suggestion, and I get this. > > bash: cd: /etc/yum/repos.d/: No such file or directory > That should be /etc/yum.repos.d not /etc/yum/repos.d/ > > Nicholas Jahn > IT professional > A.S. Network Specialist (www.madisoncollege.edu) > -- > *From:* Troy Dawson > *Sent:* Friday, September 23, 2022 1:21 PM > *To:* EPEL Development List > *Subject:* [EPEL-devel] Re: EPEL RHEL 9 mirror error > > On Fri, Sep 23, 2022 at 10:37 AM Nick Jahn wrote: > > Errors during downloading metadata for repository > 'dl.fedoraproject.org_pub_epel_9_x86_64_': > - Status code: 404 for > https://dl.fedoraproject.org/pub/epel/9/x86_64/repodata/repomd.xml > <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2F9%2Fx86_64%2Frepodata%2Frepomd.xml&data=05%7C01%7C%7C5e0fadac30354f6b231c08da9d9071b6%7C84df9e7fe9f640afb435%7C1%7C0%7C637995541040102014%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xxgwBSp7Wy7LDD4ZXSCuUV6WE6ff1RnB5etZ0n24MLo%3D&reserved=0> > (IP: 38.145.60.24) > Error: Failed to download metadata for repo > 'dl.fedoraproject.org_pub_epel_9_x86_64_': Cannot download repomd.xml: > Cannot download repodata/repomd.xml: All mirrors were tried > > > That URL is wrong, it should be > https://dl.fedoraproject.org/pub/epel/9/Everything/x86_64/repodata/repomd.xml > <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2F9%2FEverything%2Fx86_64%2Frepodata%2Frepomd.xml&data=05%7C01%7C%7C5e0fadac30354f6b231c08da9d9071b6%7C84df9e7fe9f640afb435%7C1%7C0%7C637995541040258252%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0p7vWej0JwW19EC%2BeD%2Fg1594cQskrlX0fw5d%2Be5FnLY%3D&reserved=0> > > > Looking at the name, and the URL, that is from a custom repo config file. > > The easiest way to spot that is the name > 'dl.fedoraproject.org_pub_epel_9_x86_64_' > It should be "Extra Packages for Enterprise Linux 9 - x86_64" > You should contact the machine's administrator. > If you are the machine's administrator, then I would search for > dl.fedoraproject.org > <https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdl.fedoraproject.org%2F&data=05%7C01%7C%7C5e0fadac30354f6b231c08da9d9071b6%7C84df9e7fe9f640afb435%7C1%7C0%7C637995541040258252%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=TpP8FEIjtIBiDOTHPZYX7QQD98GycO29w7ItNcWsItg%3D&reserved=0> > in a file in /etc/yum.repos.d/ and fix the repo file. > > Troy > > ___ > 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 > -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren ___ 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] Re: EPEL RHEL 9 mirror error
On September 23, 2022 10:00:49 PM GMT+03:00, Nick Jahn wrote: >Brand new server, followed guide from EPEL setting it up, first added repo to >server. > >Tried your suggestion, and I get this. > >bash: cd: /etc/yum/repos.d/: No such file or directory > Troy said "yum.repos.d" wolfy -- >Nicholas Jahn >IT professional >A.S. Network Specialist (www.madisoncollege.edu) > >From: Troy Dawson >Sent: Friday, September 23, 2022 1:21 PM >To: EPEL Development List >Subject: [EPEL-devel] Re: EPEL RHEL 9 mirror error > >On Fri, Sep 23, 2022 at 10:37 AM Nick Jahn >mailto:nick.j...@hotmail.com>> wrote: >Errors during downloading metadata for repository >'dl.fedoraproject.org_pub_epel_9_x86_64_': > - Status code: 404 for > https://dl.fedoraproject.org/pub/epel/9/x86_64/repodata/repomd.xml<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2F9%2Fx86_64%2Frepodata%2Frepomd.xml&data=05%7C01%7C%7C5e0fadac30354f6b231c08da9d9071b6%7C84df9e7fe9f640afb435%7C1%7C0%7C637995541040102014%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xxgwBSp7Wy7LDD4ZXSCuUV6WE6ff1RnB5etZ0n24MLo%3D&reserved=0> > (IP: 38.145.60.24) >Error: Failed to download metadata for repo >'dl.fedoraproject.org_pub_epel_9_x86_64_': Cannot download repomd.xml: Cannot >download repodata/repomd.xml: All mirrors were tried > > >That URL is wrong, it should be >https://dl.fedoraproject.org/pub/epel/9/Everything/x86_64/repodata/repomd.xml<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2F9%2FEverything%2Fx86_64%2Frepodata%2Frepomd.xml&data=05%7C01%7C%7C5e0fadac30354f6b231c08da9d9071b6%7C84df9e7fe9f640afb435%7C1%7C0%7C637995541040258252%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0p7vWej0JwW19EC%2BeD%2Fg1594cQskrlX0fw5d%2Be5FnLY%3D&reserved=0> > >Looking at the name, and the URL, that is from a custom repo config file. > >The easiest way to spot that is the name >'dl.fedoraproject.org_pub_epel_9_x86_64_' >It should be "Extra Packages for Enterprise Linux 9 - x86_64" >You should contact the machine's administrator. >If you are the machine's administrator, then I would search for >dl.fedoraproject.org<https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdl.fedoraproject.org%2F&data=05%7C01%7C%7C5e0fadac30354f6b231c08da9d9071b6%7C84df9e7fe9f640afb435%7C1%7C0%7C637995541040258252%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=TpP8FEIjtIBiDOTHPZYX7QQD98GycO29w7ItNcWsItg%3D&reserved=0> > in a file in /etc/yum.repos.d/ and fix the repo file. > >Troy > ___ 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] Re: EPEL RHEL 9 mirror error
Brand new server, followed guide from EPEL setting it up, first added repo to server. Tried your suggestion, and I get this. bash: cd: /etc/yum/repos.d/: No such file or directory Nicholas Jahn IT professional A.S. Network Specialist (www.madisoncollege.edu) From: Troy Dawson Sent: Friday, September 23, 2022 1:21 PM To: EPEL Development List Subject: [EPEL-devel] Re: EPEL RHEL 9 mirror error On Fri, Sep 23, 2022 at 10:37 AM Nick Jahn mailto:nick.j...@hotmail.com>> wrote: Errors during downloading metadata for repository 'dl.fedoraproject.org_pub_epel_9_x86_64_': - Status code: 404 for https://dl.fedoraproject.org/pub/epel/9/x86_64/repodata/repomd.xml<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2F9%2Fx86_64%2Frepodata%2Frepomd.xml&data=05%7C01%7C%7C5e0fadac30354f6b231c08da9d9071b6%7C84df9e7fe9f640afb435%7C1%7C0%7C637995541040102014%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xxgwBSp7Wy7LDD4ZXSCuUV6WE6ff1RnB5etZ0n24MLo%3D&reserved=0> (IP: 38.145.60.24) Error: Failed to download metadata for repo 'dl.fedoraproject.org_pub_epel_9_x86_64_': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried That URL is wrong, it should be https://dl.fedoraproject.org/pub/epel/9/Everything/x86_64/repodata/repomd.xml<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.fedoraproject.org%2Fpub%2Fepel%2F9%2FEverything%2Fx86_64%2Frepodata%2Frepomd.xml&data=05%7C01%7C%7C5e0fadac30354f6b231c08da9d9071b6%7C84df9e7fe9f640afb435%7C1%7C0%7C637995541040258252%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0p7vWej0JwW19EC%2BeD%2Fg1594cQskrlX0fw5d%2Be5FnLY%3D&reserved=0> Looking at the name, and the URL, that is from a custom repo config file. The easiest way to spot that is the name 'dl.fedoraproject.org_pub_epel_9_x86_64_' It should be "Extra Packages for Enterprise Linux 9 - x86_64" You should contact the machine's administrator. If you are the machine's administrator, then I would search for dl.fedoraproject.org<https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdl.fedoraproject.org%2F&data=05%7C01%7C%7C5e0fadac30354f6b231c08da9d9071b6%7C84df9e7fe9f640afb435%7C1%7C0%7C637995541040258252%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=TpP8FEIjtIBiDOTHPZYX7QQD98GycO29w7ItNcWsItg%3D&reserved=0> in a file in /etc/yum.repos.d/ and fix the repo file. Troy ___ 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] Re: EPEL RHEL 9 mirror error
On Fri, Sep 23, 2022 at 10:37 AM Nick Jahn wrote: > Errors during downloading metadata for repository > 'dl.fedoraproject.org_pub_epel_9_x86_64_': > - Status code: 404 for > https://dl.fedoraproject.org/pub/epel/9/x86_64/repodata/repomd.xml (IP: > 38.145.60.24) > Error: Failed to download metadata for repo > 'dl.fedoraproject.org_pub_epel_9_x86_64_': Cannot download repomd.xml: > Cannot download repodata/repomd.xml: All mirrors were tried > > > That URL is wrong, it should be > https://dl.fedoraproject.org/pub/epel/9/Everything/x86_64/repodata/repomd.xml > Looking at the name, and the URL, that is from a custom repo config file. The easiest way to spot that is the name 'dl.fedoraproject.org_pub_epel_9_x86_64_' It should be "Extra Packages for Enterprise Linux 9 - x86_64" You should contact the machine's administrator. If you are the machine's administrator, then I would search for dl.fedoraproject.org in a file in /etc/yum.repos.d/ and fix the repo file. Troy ___ 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
