I forgot that there is a fedora wiki page for installing KDE on RHEL8

https://fedoraproject.org/wiki/SIGs/KDE/EPEL

On Fri, Aug 28, 2020 at 8:05 AM Troy Dawson tdawson@redhat.com wrote:

OK, I forgot that there is one other step. For many EPEL packages (including KDE) you have to also enable the codeready-builder (RHEL) or PowerTools (CentOS)

#### If RHEL 8 do subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms #### If CentOS 8 do dnf config-manager --enable PowerTools #### If CentOS Stream do dnf config-manager --enable Stream-PowerTools

It looks like that should fix your problem.

On Fri, Aug 28, 2020 at 7:58 AM Troy Dawson tdawson@redhat.com wrote:

...

That should be all you need to do. I'll look into that problem. Hopefully it's something quick. If it's not, I'll get you a workaround.

On Fri, Aug 28, 2020 at 7:37 AM Syam Krishnan syamcr@gmail.com wrote:

...

Hi

What is the recommended method to install KDE on RHEL 8?

I tried adding EPEL repo and did:

yum groupinstall "KDE Plasma Workspaces"

But this fails with:

================

Error: Problem 1: conflicting requests

• nothing provides xmessage needed by

plasma-workspace-5.18.4.1-2.el8.x86_64 Problem 2: package sddm-breeze-5.18.4.1-2.el8.noarch requires plasma-workspace = 5.18.4.1-2.el8, but none of the providers can be installed

• conflicting requests
• nothing provides xmessage needed by

plasma-workspace-5.18.4.1-2.el8.x86_64 Problem 3: package plasma-desktop-5.18.4.1-2.el8.1.x86_64 requires plasma-workspace >= 5.18, but none of the providers can be installed

• conflicting requests
• nothing provides xmessage needed by

plasma-workspace-5.18.4.1-2.el8.x86_64 Problem 4: package kde-print-manager-19.12.3-2.el8.x86_64 requires plasma-workspace, but none of the providers can be installed

• conflicting requests
• nothing provides xmessage needed by

plasma-workspace-5.18.4.1-2.el8.x86_64

================

Do I need to do anything else to install KDE off EPEL? or is there another source?

Thanks

Syam _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@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/kde@lists.fedoraproject.org

Any pointers on fixing this?

Syam

On 29/08/20 4:54 pm, Syam Krishnan wrote:

I have hit another problem when trying to install Okteta:

---

Error:  Problem: conflicting requests   - nothing provides gccxml needed by okteta-1:0.26.0-3.el8.1.x86_64

---

I downloaded the source RPMs of this version (0.26.0-3) and a newer version (0.26.4) for Fedora from Koji. The RHEL version spec file has

Requires: gccxml libxslt

While the Fedora version has:

Requires: castxml libxslt

Any idea why this is so?

Thanks,

Syam

Fixed with an updated okteta. It's currently built, but hasn't made it to the epel-testing repo yet. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-67e827b0c7

It will probably make it into epel-testing tomorrow, and then it's a two week wait for testing. They can either wait for it to hit testing and then do dnf enablerepo=epel-testing install okteta or they can follow that link and manually download the fixed package.

On Fri, Sep 4, 2020 at 9:37 AM Troy Dawson tdawson@redhat.com wrote:

Opening a bugzilla would be the first pointer. It makes things like this more trackable.

But looking at the spec file looks like Fedora has a recommends gccxml, while RHEL has a requires. Simple enough fix. Thanks for letting us know.

On Fri, Sep 4, 2020 at 9:08 AM Syam Krishnan syamcr@gmail.com wrote:

...

Any pointers on fixing this?

Syam

On 29/08/20 4:54 pm, Syam Krishnan wrote:

...

I have hit another problem when trying to install Okteta:

---

Error: Problem: conflicting requests

• nothing provides gccxml needed by okteta-1:0.26.0-3.el8.1.x86_64

---

I downloaded the source RPMs of this version (0.26.0-3) and a newer version (0.26.4) for Fedora from Koji. The RHEL version spec file has

Requires: gccxml libxslt

While the Fedora version has:

Requires: castxml libxslt

Any idea why this is so?

Thanks,

Syam

---

kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@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/kde@lists.fedoraproject.org

File against Fedora EPEL

On Fri, Sep 4, 2020, 11:02 PM Syam Krishnan syamcr@gmail.com wrote:

On 04/09/20 10:07 pm, Troy Dawson wrote:

...

Opening a bugzilla would be the first pointer. It makes things like this more trackable.

But looking at the spec file looks like Fedora has a recommends gccxml, while RHEL has a requires. Simple enough fix. Thanks for letting us know.

Thanks a ton for this. I have installed most packages for KDE on RHEL 8. Everything seem to work fine (on my VM). I had to manually build only very few packages - KRename, Kchmviewer and yakuake (all from Fedora koji srpms).

Regarding Bugzilla entry, where exactly do I file this? There's no Okteta product for RHEL. And filing against Fedora is not really correct as it works fine on Fedora. But is that where I should be filing packaging related issues for KDE on RHEL 8 as well?

Thanks,

Syam

---

kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@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/kde@lists.fedoraproject.org

On 28/08/20 8:35 pm, Troy Dawson wrote:

OK, I forgot that there is one other step. For many EPEL packages (including KDE) you have to also enable the codeready-builder (RHEL) or PowerTools (CentOS)

That worked! Thanks a ton.

I have successfully installed Plasma and logged in from GDM.

Is there any specific reason to switch to sddm? or can I live with gdm?

My final objective is to make a custom DVD image that will install KDE Plasma along with several other packages that are useful for a typical workstation at my office. I had done the same for RHEL 5 and 6, with lot of help from Rex Dieter, Than Ngo and some good people from Fedora & KDE IRC groups. To this end, I am not sure how to make sddm come up by default after the install.

And do you all have any suggestions and recommendations for this custom DVD effort?

Thanks,

Syam

On Sat, 29 Aug, 2020, 6:12 pm Rex Dieter, rdieter@math.unl.edu wrote:

Syam Krishnan wrote:

...

I am not sure how to make sddm come up by default after the install.

systemctl enable sddm --force

will enable sddm (and disable any other login manager, like gdm) for the next boot.

Thanks. But that's a manual operation, isn't it? What I want is to have sddm as default (if it's really required for Plasma) right after OS installation from DVD media. Just like how gdm comes up now.

That's why I was wondering if it's OK to have gdm.

Syam