bug#52073: remove Google support from GVFS?

bug#52073: remove Google support from GVFS?

[raingloom]

I'd love to say it's because I want the package to be more in line with
libre software guidelines, but honestly I just don't want WebKitGTK as
a transitive input. A few weeks ago I had to remove GVFS from my system
because WebKitGTK was failing to build.

Then again if I had to connect to Google Drive or Picasa or whatever
I'd rather do it through libre software, so maybe it should stay.

Too bad we still don't have package options.

So, what do yall think, should I just create a custom package on my own
channel that disables all that junk, or is this something everyone
wants?

ps.: if any GVFS devs are reading this, the bug that caused me to
almost delete my entire file system is still unaddressed. :)
https://gitlab.gnome.org/GNOME/gvfs/-/issues/202
https://gitlab.gnome.org/GNOME/gvfs/-/issues/364

bug#52073: remove Google support from GVFS?

[Leo Famulari]

On Wed, Nov 24, 2021 at 06:00:15AM +0100, raingloom wrote:
> I'd love to say it's because I want the package to be more in line with
> libre software guidelines, but honestly I just don't want WebKitGTK as
> a transitive input. A few weeks ago I had to remove GVFS from my system
> because WebKitGTK was failing to build.

Can you explain the connection between libre software guidelines (FSDG),
GVFS, and WebKitGTK?

If the problem was simply that the WebKitGTK package was broken for a
few days, I'm sorry, that was my mistake.

> Then again if I had to connect to Google Drive or Picasa or whatever
> I'd rather do it through libre software, so maybe it should stay.

GNU's position is that services are not "free" or "nonfree" in the way
that software is. So, it shouldn't be a problem that Guix packages can
use 3rd party services.

https://www.gnu.org/philosophy/network-services-arent-free-or-nonfree.en.html

bug#52073: remove Google support from GVFS?

[Liliana Marie Prikler]

Am Mittwoch, den 24.11.2021, 12:33 -0500 schrieb Leo Famulari:
> On Wed, Nov 24, 2021 at 06:00:15AM +0100, raingloom wrote:
> > I'd love to say it's because I want the package to be more in line
> > with libre software guidelines, but honestly I just don't want
> > WebKitGTK as a transitive input. A few weeks ago I had to remove
> > GVFS from my system because WebKitGTK was failing to build.
> 
> Can you explain the connection between libre software guidelines
> (FSDG), GVFS, and WebKitGTK?
> 
> If the problem was simply that the WebKitGTK package was broken for a
> few days, I'm sorry, that was my mistake.
Note that WebkitGTK is still broken on i686 (bug#51863).  I could take
some time out of my weekend to fix the issues I raised w.r.t. that
patch or we could apply it as-is (though note that hasty as-is
applications have not worked out too well for us in the recent past). 
I'm not sure whether raingloom is on i686 or x86_64, just wanted to
point that out.

Cheers

bug#52073: remove Google support from GVFS?

[Liliana Marie Prikler]

Hi,

Given that we have GNOME 40/41 on master right now with GVFS supporting
Google as it did before, is this still relevant?

Cheers

bug#52073: remove Google support from GVFS?

[Leo Famulari]

On Fri, Dec 31, 2021 at 01:24:55PM +0100, Liliana Marie Prikler wrote:
> Given that we have GNOME 40/41 on master right now with GVFS supporting
> Google as it did before, is this still relevant?

Since the bug report was a reaction to WebKitGTK being broken, and it's
no longer broken, I'm closing the ticket [0].

When packages break occasionally, we have to decide if we should remove
them from the distro or if we can should try maintain the status quo.

My experience with WebKitGTK is that the build is quite reliable. That's
why I pushed the broken update to begin with: it always worked in the
past. There's no need to rewrite the dependency graph just because I was
lazy and don't have a very fast computer.

[0] Anyone can reopen it by sending a message with "reopen 52073" to
<control@debbugs.gnu.org>.
https://debbugs.gnu.org/server-control.html

bug#52073: remove Google support from GVFS?

[Mark H Weaver]

Hi Leo,

Leo Famulari <leo@famulari.name> writes:

> My experience with WebKitGTK is that the build is quite reliable. That's
> why I pushed the broken update to begin with: it always worked in the
> past.

That might be true of _micro_ version updates of WebKitGTK, but it's
certainly false for non-micro updates.  I thought you would have known
to treat those two kinds of updates differently.

In fact, if you look at the commit log over the last few years, you'll
see that 8 out of the last 10 non-micro updates of WebKitGTK have
required additional changes to the build recipe.

       Mark


commit 3c5e1412e3ef769df8e4826d0aedabaa3aa0d631
Author: Leo Famulari <leo@famulari.name>
Date:   Tue Mar 30 13:30:28 2021 -0400

    gnu: WebKitGTK: Update to 2.32.0 [fixes CVE-2021-{1788,1844,1871}].
    
    * gnu/packages/webkit.scm (webkitgtk): Update to 2.32.0.
    [arguments]: Add -DENABLE_GAMEPAD=OFF to #:configure-flags.

commit e6b6e834903f001d4f2ae9bf0511bf7953c0f80b
Author: Mark H Weaver <mhw@netris.org>
Date:   Sun Sep 20 14:41:29 2020 -0400

    gnu: webkitgtk: Update to 2.30.0.
    
    * gnu/packages/webkit.scm (webkitgtk): Update to 2.30.0.
    [arguments]: Add "-DUSE_SYSTEMD=OFF" to the configure flags.

commit 3c9d89b5e2da2731ccc56a4cb745e1868175db79
Author: Leo Famulari <leo@famulari.name>
Date:   Fri Mar 13 12:32:33 2020 -0400

    gnu: WebKitGTK: Update to 2.28.0 [fixes CVE-2020-10018].
    
    * gnu/packages/webkit.scm (webkitgtk): Update to 2.28.0.

commit 689b44bc3fe50de86c8c8b8c2ac503b2e82d7975
Author: Marius Bakke <marius@gnu.org>
Date:   Thu Sep 26 16:40:18 2019 +0200

    gnu: WebKitGTK: Update to 2.26.1.
    
    * gnu/packages/webkit.scm (webkitgtk-2.24): Rename to ...
    (webkitgtk-2.26): ... this.  Update to 2.26.1.
    [inputs]: Add BUBBLEWRAP, LIBSECCOMP, LIBWPE, WPEBACKEND-FDO, and XDG-DBUS-PROXY.
    * gnu/packages/gnome.scm (eolie, epiphany)[inputs]: Adjust for changed
    variable name.
    * gnu/packages/web-browsers.scm (next-gtk-webkit)[inputs]: Likewise.

commit 72663b48221668f30b7bdcc502c299757a647156
Author: Marius Bakke <marius@gnu.org>
Date:   Wed Mar 13 15:00:03 2019 +0100

    gnu: WebKitGTK: Update to 2.24.0.
    
    * gnu/packages/webkit.scm (webkitgtk-2.22): Rename to ...
    (webkitgtk-2.24): ... this.  Update to 2.24.0.
    [inputs]: Add OPENJPEG.
    * gnu/packages/gnome.scm (eolie, epiphany)[inputs]: Adjust accordingly.
    * gnu/packages/web-browsers.scm (next-gtk-webkit)[inputs]: Likewise.

commit 844cc6f876b8dcadf210398e68b3f3f824cb7144
Author: Mark H Weaver <mhw@netris.org>
Date:   Sat Sep 22 19:17:02 2018 -0400

    gnu: webkitgtk: Add version 2.22.2.
    
    * gnu/packages/webkit.scm (webkitgtk-2.22): New variable.

commit 86c9c0c11819f1e5ec6f821265a0492ddeaf83ee
Author: Tobias Geerinckx-Rice <me@tobias.gr>
Date:   Wed Mar 14 10:24:08 2018 +0100

    gnu: webkitgtk: Update to 2.20.0.
    
    * gnu/packages/webkit.scm (webkitgtk): Update to 2.20.0.
    [arguments]: (Re-)disable WOFF2 web font support.

commit a54bf725fcb35052120d1111c6e82c951d4d7873
Author: Mark H Weaver <mhw@netris.org>
Date:   Fri Sep 15 13:10:56 2017 -0400

    gnu: webkitgtk: Update to 2.18.0.
    
    * gnu/packages/webkit.scm (webkitgtk): Update to 2.18.0.
    [arguments]: Add -DUSE_GSTREAMER_GL=OFF to configure-flags.
    [inputs]: Add libtasn1.

commit c38685524956a9451ce254da80f6819be53ead6c
Author: Leo Famulari <leo@famulari.name>
Date:   Mon Mar 27 12:52:42 2017 -0400

    gnu: webkitgtk: Update to 2.16.0.
    
    WebKitGTK+ 2.16.0 is the first stable release of WebKitGTK+ that uses libgcrypt
    instead of GnuTLS for some cryptographic functions:
    
    <https://bugs.webkit.org/show_bug.cgi?id=163125>
    <http://trac.webkit.org/changeset/208297/webkit>
    
    * gnu/packages/webkit.scm (webkitgtk): Update to 2.16.0.
    [inputs]: Replace gnutls with libgcrypt.

-- 
Disinformation flourishes because many people care deeply about injustice
but very few check the facts.  Ask me about <https://stallmansupport.org>.

bug#52073: remove Google support from GVFS?

[Mark H Weaver]

Earlier, I wrote:
> In fact, if you look at the commit log over the last few years, you'll
> see that 8 out of the last 10 non-micro updates of WebKitGTK have
> required additional changes to the build recipe.

Correction: it's actually 9 out of the last 10.  At first glance, the
following commit looked like a simple update, but in fact it required
additional changes.

       Mark

> commit 844cc6f876b8dcadf210398e68b3f3f824cb7144
> Author: Mark H Weaver <mhw@netris.org>
> Date:   Sat Sep 22 19:17:02 2018 -0400
>
>     gnu: webkitgtk: Add version 2.22.2.
>     
>     * gnu/packages/webkit.scm (webkitgtk-2.22): New variable.

-- 
Disinformation flourishes because many people care deeply about injustice
but very few check the facts.  Ask me about <https://stallmansupport.org>.