Bug 2532963

Ok, I've requested an epel10 branch and submitted a scratch build:

https://koji.fedoraproject.org/koji/taskinfo?taskID=150245636

Unfortunately, the rawhide version doesn't build out of the box:


DEBUG util.py:535:  No matching package to install: 'dbusmenu-qt5-devel'
DEBUG util.py:535:  No matching package to install: 'kf5-kconfigwidgets-devel'
DEBUG util.py:535:  No matching package to install: 'kf5-kcoreaddons-devel'
DEBUG util.py:535:  No matching package to install: 'kf5-knotifications-devel'
DEBUG util.py:535:  No matching package to install: 'kf5-knotifyconfig-devel'
DEBUG util.py:535:  No matching package to install: 'kf5-ktextwidgets-devel'
DEBUG util.py:535:  No matching package to install: 'kf5-kwidgetsaddons-devel'
DEBUG util.py:535:  No matching package to install: 'kf5-kwindowsystem-devel'
DEBUG util.py:535:  No matching package to install: 'kf5-kxmlgui-devel'
DEBUG util.py:535:  No matching package to install: 'kf5-rpm-macros'
DEBUG util.py:535:  No matching package to install: 'phonon-qt5-devel'
DEBUG util.py:535:  No matching package to install: 'qt5-qtwebkit-devel'
DEBUG util.py:535:  Not all dependencies satisfied
DEBUG util.py:535:  Error: Some packages could not be found.

Hi Georg,

Thank you for trying to build this. 

It looks like the whole kf5 packages aren't available in EPEL 10 anymore. The developers of quassel are working on a port to kf6/qt6, but this isn't ready yet.
I guess packaging all the necessary dependencies from kf5 is a bit too much work.

Maybe it is possible to build just the quasselcore component for EPEL10 without having the kf5 dependencies available? quasselcore is just the server without any GUI.

I can try that in the next few days.

Created attachment 2157782 [details]
New .spec that builds on EL10

Created attachment 2157783 [details]
diff between original .spec and my modifications that make it build on EL10

I looked a bit more into it and the GUI of quassel can actually be built just with QT and without KDE / kf5 integration. This works fine on EL10.
I modified the .spec to check for EL10 and build the basic qt version there.

I attached my new .spec and a diff to the original rawhide one above.

Do the changes look good to you or do you have some improvement suggestions?

FEDORA-EPEL-2026-d0a84c5d7b (quassel-0.14.0-17.el10_4) has been submitted as an update to Fedora EPEL 10.4.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-d0a84c5d7b

Gerd, thanks for the patch, this is a good approach!

I've applied it with only slight modifications:
https://src.fedoraproject.org/rpms/quassel/c/98fc3125cf9a3442633223ad0b22646fb14a921b?branch=rawhide

That means I switched to guards that aren't version specific and explicitly target the epel environment.

Thanks for looking into my patch.

> That means I switched to guards that aren't version specific and explicitly target the epel environment.

No problem, this looks good. I'm not always up to date which kind of version guards are preferred in which case by the packaging guidelines.

I saw that you built the package just for EPEL 10.4. It will be quite some time until the EL 10.4 will be officially released, even EL 10.3 is not out yet. Would it be possible to also build it for EL 10.2 and EL 10.3 or is that something that requires special procedures and work from you?

Yes, epel switched to a dot-release branching scheme some time ago and the 'epel10' branch apparently is already set to 10.4.

This is somewhat similar to what's in Fedora - modulo the dot-releases, i.e. you have epel10/epel10.1/epel10.2/... vs. rawhide/f41/f42/...

If you start with some epel branch late, you miss the earlier branches, unless you request extra branches for the previous dot-releases and build and update for each of them.

Thus, yes, it's extra work.

Anyhow, I've just requested those extra branches and triggered the builds.

For some reason the 10.3 branch build failed with a weird error:

https://koji.fedoraproject.org/koji/taskinfo?taskID=151007600

> FAILED: BuildError: package quassel not in list for tag epel10.3-testing-candidate

FEDORA-EPEL-2026-2d2afb5f66 (quassel-0.14.0-17.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-2d2afb5f66

FEDORA-EPEL-2026-2d2afb5f66 has been pushed to the Fedora EPEL 10.2 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-2d2afb5f66

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-EPEL-2026-d0a84c5d7b has been pushed to the Fedora EPEL 10.4 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-d0a84c5d7b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-EPEL-2026-d0a84c5d7b (quassel-0.14.0-17.el10_4) has been pushed to the Fedora EPEL 10.4 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-EPEL-2026-2d2afb5f66 (quassel-0.14.0-17.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-EPEL-2026-be150e3c07 (quassel-0.14.0-17.el10_3) has been submitted as an update to Fedora EPEL 10.3.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-be150e3c07

FEDORA-EPEL-2026-be150e3c07 has been pushed to the Fedora EPEL 10.3 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-be150e3c07

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Thank you for keeping to push this through, now it looks like the EPEL 10.3 has worked.

Now I can migrate my chat server.

FEDORA-EPEL-2026-be150e3c07 (quassel-0.14.0-17.el10_3) has been pushed to the Fedora EPEL 10.3 stable repository.
If problem still persists, please make note of it in this bug report.