all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Leo Famulari <leo@famulari.name>, raingloom <raingloom@riseup.net>
Cc: 52073@debbugs.gnu.org
Subject: bug#52073: remove Google support from GVFS?
Date: Wed, 24 Nov 2021 20:38:45 +0100	[thread overview]
Message-ID: <ea09581bb480e6a5cabcec5675de3d03cb128b1f.camel@gmail.com> (raw)
In-Reply-To: <YZ53hAMQmZWTREA8@jasmine.lan>

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





  reply	other threads:[~2021-11-24 20:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24  5:00 bug#52073: remove Google support from GVFS? raingloom
2021-11-24 17:33 ` Leo Famulari
2021-11-24 19:38   ` Liliana Marie Prikler [this message]
2021-12-31 12:24     ` Liliana Marie Prikler
2021-12-31 18:13       ` Leo Famulari
2021-12-31 22:12         ` Mark H Weaver
2021-12-31 22:18           ` Mark H Weaver

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ea09581bb480e6a5cabcec5675de3d03cb128b1f.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=52073@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --cc=raingloom@riseup.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.