You haven't provided any details about those "other applications" breaking. Please show us the evidence i.e. log files, crash reports, backtraces, etc.

Edit: I see new comment here [1] about an API break. So yeah, not good.

[1] https://gitlab.gnome.org/GNOME/gupnp-igd/-/merge_requests/9

For example gajim, or dino.

Sorry for the minimal bug report, here a longer version

These are libs that provide introspection, there is something like a API version there. Im not actually too knowledgeable about the wording.

The problem is you cannot load 2 different versions into the same process.

So gajim depends on libsoup2 which has API version 2.4

gupnp-idg master depends on gupnp 1.6 which depends on libsoup3 API version 3.0

but the official released version of gupnp-idg depends on gupnp < 1.5 which dependend on libsoup2

i hope this makes the situation more clear, what needs to happen here in my opinion is the same which was done for libsoup

this package needs to be downgraded again to the official released version
and a new package has to be added with a different version number

Example libsoup

https://archlinux.org/packages/extra/x86_64/libsoup/
https://archlinux.org/packages/extra/x86_64/libsoup3/

There is a open MR on the gupnp-idg tracker, which sets the introspection version to 1.6, see my initial post with the issue link

> So gajim depends on libsoup2

gajim libsoup issue was previously reported here  FS#76305  and fixed. And again, dino was also fixed here  FS#76317 . What version of gajim and dino are you running? Please clarify.

dino ported to libsoup3, so yeah that works around the problem, but its a workaround for a packaging error or developer error (not upgrading the version), so i would not consider that a "fix" because its not a bug in dino to begin with.

because i had no time, and we directly imported gupnp-idg for a small functionality i removed the code in Gajim, to work around the issue, because porting to libsoup3 is a big effort.
this "fix" now lets the application start again at least, and so probably the reporters considers it fixed.

But then users discovered that other dependencies of gajim also depend on gupnp-idg.

We depend on Farstream -> libnice -> gupnp-idg

Means everytime someone uses the audio call feature gajim crashes.
Disabling farstream and with that our audio call feature is not an option.

so essentially now all applications that use farstream or libnice and use libsoup2 are broken.

Its clear to me that the root cause for this is, that the package maintainer did not discover the api break, because the developers didnt make it clear.
So now that it is clear, lets fix it at the root.

Ok, it sounds like a royal mess :( Let's see if the PM has any thoughts...