Hello, Since version 1.50.0, gnome-base/gvfs doesn't have the «http» useflag anymore. It's useful to mount webdav filesystems. [ebuild U ] gnome-base/gvfs-1.50.2::gentoo [1.48.1-r1::gentoo] USE="gnome-keyring gnome-online-accounts mtp nfs policykit systemd udev udisks -afp -archive -bluray -cdda -elogind -fuse -google -gphoto2 (-http*) -ios -samba -test -zeroconf" 0 KiB thanks -- vincent Reproducible: Always Steps to Reproduce: 1.emerge gnome-base/gvfs-1.50.0 Actual Results: /usr/libexec/gvfsd-dav doesn't exist Expected Results: /usr/libexec/gvfsd-dav exists
From profiles/base/package.use.mask: # Matt Turner <mattst88@gentoo.org> (2022-03-25) # Depends on libsoup:3.0 >=gnome-base/gvfs-1.50 http
This also prevents Nautilus from mounting Nextcloud shares when a Nexcloud Online Account is define in GNOME settings and the "files" option is activated. With gnome-base/gvfs-1.48.1-r1 I am able mount my Nextcloud share and with gnome-base/gvfs-1.50.2 Nautilus is failing to mount my Nextcloud share.
This also prevents GNOME from showing album cover image in the playback control widget in the notification area, if this image was provided as a URL address via MPRIS. In my case `gnome-base/gvfs-1.50.2.ebuild` emerges just fine with `http` USE flag unmasked & enabled. I have `net-libs/libsoup-2.74.2` installed and everything is working as expected. These two lines of Python code may serve as a quick test of this functionality: ``` from gi.repository import Gio print(Gio.File.new_for_uri("http://example.org").load_contents(None)) ``` Currently, I don't see any reason why this USE flag should remain masked, but if there is any, please let us know.
It requires libsoup:3.0, which is masked. See https://wiki.gentoo.org/wiki/Project:GNOME/libsoup:3_transition Here's the relevant bit of the diff between 1.48 and 1.50's meson.build: enable_http = get_option('http') if enable_http assert(have_libxml, 'http required but libxml-2.0 not found') - libsoup_dep = dependency('libsoup-2.4', version: '>= 2.58.0') + libsoup_dep = dependency('libsoup-3.0', version: '>= 3.0.0') endif Any help unmasking libsoup:3.0 is welcome.
It should be fine to unmask it and the http flag, because it's a separate /usr/libexec/gvfsd-http process, so not in danger of mixing libsoup:2 and libsoup:3 at runtime. The reason why I p.masked libsoup initially was because I added beta versions for my own development needs, and then it was kept as nothing really needed it, plus it made it not need to worry about the libsoup:2 and libsoup:3 mixing in the same runtime quite yet, when you can't even install libsoup:3. It should be fine to unmask libsoup:3 itself, while keeping libraries (or rather their newer versions) that use libsoup:3 p.masked until we sort things out to not end up with different libsoup versions in the same runtime process, which would just abort out with current libsoup:2 and libsoup:3 versions. So the fun is with things like webkit-gtk and packages that use it; evolution-data-server and packages that use it, and so on. But libsoup:3 itself and gvfs[http] should be good to go imo.
I found it easier to mask the 1.50 version, forcing a downgrade to gvfs-1.48.1-r2 I'm using mate and didn't notice any issue, but the http flag is back with the webdav support.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d4e11da5b7c709d586cb8b853b24c04d95336c38 commit d4e11da5b7c709d586cb8b853b24c04d95336c38 Author: Matt Turner <mattst88@gentoo.org> AuthorDate: 2023-01-01 00:07:43 +0000 Commit: Matt Turner <mattst88@gentoo.org> CommitDate: 2023-01-01 00:07:43 +0000 profiles: Unmask USE=http stable mask on gvfs Closes: https://bugs.gentoo.org/851051 Signed-off-by: Matt Turner <mattst88@gentoo.org> profiles/base/package.use.stable.mask | 4 ---- 1 file changed, 4 deletions(-)
