Hi, Could you please branch and build libsoup for EPEL 10 ? It is needed to build another package. Regards, Xavier
Hmm, how do you do that, please? I did not work with EPEL directly by any way yet, this used to be built there automatically, if at all, before. I'm sorry for my ignorance.
Working with EPEL is similar to working with Fedora. You are probably used to rawhide, f41, f40, f39, etc... dist-git branches, it will be exactly the same for epel8, epel9 and epel10 branches. Thus something alike "fedpkg clone libsoup; cd libsoup; fedpkg request-branch epel10; git pull; git checkout epel10; git rebase rawhide; git push; fedpkg build"
Thanks for the commands. It seems complicated on the first look, but it might be just because it's the starter. Thinking of it, an app cannot mix libsoup2 and libsoup3 in runtime, directly or indirectly (brought in through its dependencies, or dependencies of the dependencies,...). It's one of the reasons why the libsoup2 did not make it into the RHEL/EPEL 10, because it can cause breakage for some apps. Could you tell me what app requires it, please? Some apps allow to switch between libsoup and curl usage, I used the switch with syncevolution for example.
This is needed for inkscape, the build request bug for it is: https://bugzilla.redhat.com/show_bug.cgi?id=2315449, as can be seen in the "Blocks" field of this bug. I have no idea if inkscape can be made to use libsoup3 or curl, but indeed your comment about mixing libsoup2/libsoup3 is a good point. Actually, I'm just trying to track dependencies in order to get ImageMagick, and various packages that depends on it, into EPEL 10. I've been building the dependent packages recursively from their rawhide branch to list the missing dependencies, without taking a deep look at every and all of them. It is very much possible I have missed some switches or else that could help lighten/simplify the dependencies chain.
The dependency chain that leads to libsoup 2 is: ImageMagick -> djvulibre -> inkscape -> libsoup2
Interesting Inkscape can use ImageMagick during its build, aka the opposite order of the dependencies. Could it be the inkscape's .spec file was not updated after: https://gitlab.com/inkscape/inkscape/-/commit/a4959939e11b0253fbbaf12c3e1f11490b4328ab ?
This commit is not in the 1.3.x branch of inkscape, it's only available in the unreleased 1.4 branch, but I guess you are pointing in the right direction. Inkscape would need to have at least https://gitlab.com/inkscape/inkscape/-/commit/73c83ef9b8dc3e3dfd0fe24c75356623e7390ebd and https://gitlab.com/inkscape/inkscape/-/commit/a4959939e11b0253fbbaf12c3e1f11490b4328ab backported over 1.3.2 to drop the libsoup2 dependency, if at all possible.
Oh, did they not release it yet? I thought they did, when the commit happened ~6 months ago. I believe it'll be better to not depend on the libsoup2, to avoid problems in the future. I looked into the first commit and I hope I did not overlook anything, but it seems to me the `get_file()` function is not used anywhere. The commit mentions gtk4, which might not be relevant in the 1.3 series, thus maybe if you could try to disable that code, and the libsoup2 usage, in EPEL in a custom downstream patch, then it can prove the libsoup2 is not needed even in the 1.3 series, at least for parts used by the Fedora/EPEL build.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42.