Bug 2443827 - libsoup3 package provides mingw directories under /usr
Summary: libsoup3 package provides mingw directories under /usr
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libsoup3
Version: 44
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact:
URL:
Whiteboard: AcceptedFreezeException
: 2443002 (view as bug list)
Depends On:
Blocks: BetaFreezeException, F44BetaFreezeException
TreeView+ depends on / blocked
 
Reported: 2026-03-02 14:09 UTC by Michael Catanzaro
Modified: 2026-03-18 00:14 UTC (History)
6 users (show)

Fixed In Version: libsoup3-3.6.6-5.fc44
Clone Of:
Environment:
Last Closed: 2026-03-18 00:14:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michael Catanzaro 2026-03-02 14:09:59 UTC
The libsoup3 package calls %find_lang in the wrong order, resulting in mingw localizations appearing in the main package. This results in the creation of /usr/i686-w64-mingw32 and /usr/x86_64-w64-mingw32.

The fix is:

diff --git a/libsoup3.spec b/libsoup3.spec
index deb949f..10d5bf4 100644
--- a/libsoup3.spec
+++ b/libsoup3.spec
@@ -149,14 +149,14 @@ This is the MinGW build of libsoup3
 %meson_install
 install -m 644 -D tests/libsoup.supp %{buildroot}%{_datadir}/libsoup-3.0/libsoup.supp
 
+%find_lang libsoup-3.0
+
 %if %{with_mingw}
 %mingw_ninja_install
 %mingw_find_lang libsoup-3.0
 %mingw_debug_install_post
 %endif
 
-%find_lang libsoup-3.0
-
 %ifnarch s390x
 %check
 %meson_test

I will request a freeze exception because once the directories are created, RPM will never remove them. So manual intervention is required for anybody who installed the affected versions.

Reproducible: Always

Comment 1 Fedora Blocker Bugs Application 2026-03-02 14:14:59 UTC
Proposed as a Freeze Exception for 44-beta by Fedora user catanzaro using the blocker tracking app because:

 The libsoup3 package calls %find_lang in the wrong order, resulting in mingw localizations appearing in the main package. This results in the creation of /usr/i686-w64-mingw32 and /usr/x86_64-w64-mingw32. I have fixed the bug, but once the directories are created, RPM will never remove them. So it would be nice to fix it before F44 Beta to reduce the number of users who install the affected version. It doesn't cause any functionality problems, but users who don't want the extra directories will have to manually delete them.

Comment 2 Gwyn Ciesla 2026-03-02 15:36:47 UTC
*** Bug 2443002 has been marked as a duplicate of this bug. ***

Comment 3 Michael Catanzaro 2026-03-02 15:53:14 UTC
Created update https://bodhi.fedoraproject.org/updates/FEDORA-2026-eeafb8bdaf but I have failed to attach this bug to the update. The spinner in the web UI keeps spinning after I type the bug number, despite several retries.

Comment 4 Fedora Update System 2026-03-02 16:00:23 UTC
FEDORA-2026-eeafb8bdaf (libsoup3-3.6.6-5.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-eeafb8bdaf

Comment 5 Gwyn Ciesla 2026-03-02 16:00:45 UTC
Thank you! I added the bug.

Comment 6 Lukas Ruzicka 2026-03-02 19:55:47 UTC
Discussed on the Fedora Blocker Review Meeting on March, 2nd 2026 with the resolution.

Accepted Beta FreezeException

See https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2026-03-02/f44-blocker-review.2026-03-02-17.00.log.txt

Comment 7 Fedora Update System 2026-03-03 02:10:58 UTC
FEDORA-2026-eeafb8bdaf has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-eeafb8bdaf`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-eeafb8bdaf

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

Comment 8 Fedora Update System 2026-03-18 00:14:46 UTC
FEDORA-2026-eeafb8bdaf (libsoup3-3.6.6-5.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.


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