Bug 2305929 - EPEL for KDE package issue on RHEL Clone, Rocky 9
Summary: EPEL for KDE package issue on RHEL Clone, Rocky 9
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: epel-release
Version: epel9
Hardware: All
OS: Other
unspecified
medium
Target Milestone: ---
Assignee: Troy Dawson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-08-19 23:42 UTC by chaveze
Modified: 2024-08-30 15:26 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-08-30 15:26:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description chaveze 2024-08-19 23:42:58 UTC
Description of problem: KDE Workspace package for EPEL RHEL9 is failing due to package missing. Reported on Rocky as well.
https://forums.rockylinux.org/t/missing-packages-in-kde/14934

Rocky Linux 9 some of the packages are nowhere to be found in any repository:

abrt-desktop
dnfdragora
k3b-extras-freeworld
kio-gdrive
NetworkManager-config-connectivity-fedora
pinentry-qt
plasma-nm-vpnc

Version-Release number of selected component (if applicable):
RHEL9 and any clone like Rocky9

How reproducible:
All the time

Steps to Reproduce:
1. install sudo dnf groupinstall-y "KDE Plasma Workspaces"
2. Does not error out, just does not install.
3.

Actual results:
the KDE environment should install 

Expected results:


Additional info:

Comment 1 Troy Dawson 2024-08-20 14:16:19 UTC
Looking at the conversation you linked to, you are doing

  dnf group info "KDE (K Desktop Environment)"

There is no group "KDE (K Desktop Environment)" in epel.  There is no group with that name in rocky9 either.  My guess is that you have a custom repo, possibly setup by ansible, with that group name, and it has not been updated.

The epel group name is "KDE Plasma Workspaces" ... and I think you realized that, because what you have in this bug, and what you have in the conversation are two different things.

  dnf group install "KDE Plasma Workspaces"

works just fine on rocky9.

You are also claiming that the packages you have listed are in epel8, but that is not true.  None of them are in epel8, so if they were installing on your rocky8 machines then you must be getting them from a different place than epel.

Look at your rocky8 machines that are working, and look at the dnf configurations in /etc/yum.repos.d/ and figure out what you are really pointing your repos at.

Comment 2 chaveze 2024-08-20 17:40:01 UTC
Same thing happens with "KDE Plasma Workspaces"

No match for group package "plasma-nm-vpnc"
No match for group package "NetworkManager-config-connectivity-fedora"
No match for group package "pinentry-qt"
No match for group package "qt-at-spi"
No match for group package "dnfdragora"
No match for group package "abrt-desktop"
No match for group package "kio-gdrive"
No match for group package "systemd-oomd-defaults"

All my repos are from EPEL and rocky for its RHEL.
Only things I have added are Fastx from Startnet and vavaldi in the future.

/etc/yum.repos.d/
duosecurity.repo  epel-cisco-openh264.repo  epel.repo  epel-testing.repo  rocky-addons.repo  rocky-devel.repo  rocky-extras.repo  rocky-extras.repo.rpmnew  rocky.repo  rocky.repo.rpmnew  starnet.repo  VirtualGL.repo

Comment 3 Troy Dawson 2024-08-20 18:48:16 UTC
My apologies. You are correct.  I missed that when I checked.

I have created a comps pull request that should fix the problem.

https://pagure.io/fedora-comps/pull-request/1009

Comment 4 Timothée Ravier 2024-08-21 10:30:55 UTC
Is there any specific reason for this issue to not be public?

Comment 5 Troy Dawson 2024-08-21 13:40:29 UTC
(In reply to Timothée Ravier from comment #4)
> Is there any specific reason for this issue to not be public?

I didn't realize it wasn't public.  I have removed the tag.

Comment 6 Troy Dawson 2024-08-21 13:42:26 UTC
The pull request has been merged, but the change won't be seen until there is a new epel9 repo created, and it makes it to the mirrors.
That usually takes a day or two.
I'll keep this open until I can verify it's been pushed out and working.

Comment 7 chaveze 2024-08-21 17:36:12 UTC
Hello Troy,

Thank you for the help. I did not know I made it private.
I'll make sure to not do it next time.

Take care,
Erik

Comment 8 Troy Dawson 2024-08-30 15:26:36 UTC
I have verified that the comps change has gone through, and that it fixed the problem.


Note You need to log in before you can comment on or make changes to this bug.