fesco

#3498 Request for exception: libqtxdg 4.3.0 and libfm-qt 2.3.0 for F43
Closed: Accepted by zbyszek. Opened by sfaulken.

Closed: Accepted
Reopen Issue

libqtxdg and libfm-qt both have soname bumps as part of the larger LXQt-2.3.0 update.

These are internal dependencies only to the 2.3.0 update itself:

📦 mustang ~ % dnf rq --whatrequires libqtxdg --releasever=43
Updating and loading repositories:
Repositories loaded.
liblxqt-0:2.2.0-2.fc43.i686
liblxqt-0:2.2.0-2.fc43.x86_64
libqtxdg-devel-0:4.2.0-5.fc43.i686
libqtxdg-devel-0:4.2.0-5.fc43.x86_64
libqtxdg-devel-0:4.2.0-6.fc43.i686
libqtxdg-devel-0:4.2.0-6.fc43.x86_64
lxqt-about-0:2.2.0-2.fc43.x86_64
lxqt-config-0:2.2.0-2.fc43.x86_64
lxqt-notificationd-0:2.2.0-2.fc43.x86_64
lxqt-panel-0:2.2.2-2.fc43.x86_64
lxqt-panel-0:2.2.2-3.fc43.x86_64
lxqt-qtplugin-0:2.2.0-2.fc43.i686
lxqt-qtplugin-0:2.2.0-2.fc43.x86_64
lxqt-qtplugin-0:2.2.0-3.fc43.i686
lxqt-qtplugin-0:2.2.0-3.fc43.x86_64
lxqt-runner-0:2.2.0-2.fc43.x86_64
lxqt-session-0:2.2.0-5.fc43.x86_64
qtxdg-tools-0:4.2.0-2.fc43.x86_64
screengrab-0:3.0.0-2.fc43.x86_64
screengrab-0:3.0.0-3.fc43.x86_64

and

📦 mustang ~ % dnf rq --whatrequires libfm-qt --releasever=43
Updating and loading repositories:
Repositories loaded.
libfm-qt-devel-0:2.2.0-2.fc43.i686
libfm-qt-devel-0:2.2.0-2.fc43.x86_64
libfm-qt-devel-0:2.2.0-3.fc43.i686
libfm-qt-devel-0:2.2.0-3.fc43.x86_64
libfm-qt-l10n-0:2.2.0-2.fc43.noarch
libfm-qt-l10n-0:2.2.0-3.fc43.noarch
lximage-qt-0:2.2.0-2.fc43.x86_64
lxqt-archiver-0:1.2.0-2.fc43.x86_64
pcmanfm-qt-0:2.2.0-2.fc43.x86_64
xdg-desktop-portal-lxqt-0:1.2.0-2.fc43.x86_64
xdg-desktop-portal-lxqt-0:1.2.0-4.fc43.x86_64

Metadata Update from @ngompa:
- Issue tagged with: updates policy exception

I'm guessing this is because LXQt 2.3.0 released just now, right after the Fedora 43 GA?

It seems fine to me to do this, the LXQt desktop is pretty self contained and small. +1

This isn't the first time an LXQt related exception has been requested, is this something you foresee doing again in the future? If so, perhaps it's worth making a permanent exception, so we don't have to process these tickets on a regular basis when we know it's basically the same every time.

Correct. LXQt released their 2.3.0 update on 5 November 2025

These internal soname bumps are fairly common, everytime the LXQT project does one of it's major releases (Twice a year, IIRC)

It appears according to the website, they release in late April and early November generally. Weird, but unfortunately out of alignment with Fedora.

Do you foresee doing this again in the spring? If so, do you want us to consider a permanent exception?

Yes, please, I suspect that at a bare minimum, we will see the soname bump for these same two packages in April, so a Permanent Exception would be much appreciated

Proposal: The LXQt SIG is granted a permanent exception for the LXQt Desktop package set, though this does not obviate the requirement for exception requests involving packages not from the LXQt project.
Edited by ngompa

+1 from me (as proposer)

+1

Proposal: The LXQt SIG is granted a permanent exception for the LXQt Desktop package set, though this does not obviate the requirement for exception requests involving packages not from the LXQt project.

+1

+1

+1

+1

After a week, this is: APPROVED (+6, 0, 0)
It'll be announced in today's agenda mail.

Metadata Update from @zbyszek:
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

This needs documenting.

Metadata Update from @ngompa:
- Issue status updated to: Open (was: Closed)
- Issue tagged with: document it

https://pagure.io/fesco/fesco-docs/pull-request/116

Merged.

Metadata Update from @zbyszek:
- Issue untagged with: document it
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)
Metadata
None

updates policy exception

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.