unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jason Self <j@jxself.org>
To: 34565@debbugs.gnu.org
Subject: bug#34565: ungoogled-chromium contains Widevine DRM
Date: Tue, 19 Feb 2019 21:35:47 -0800	[thread overview]
Message-ID: <1550640947.21795.7.camel@jxself.org> (raw)
In-Reply-To: <20190220051536.GA7782@jasmine.lan>

Leo Famulari wrote:
> To clarify this general point about Guix for anyone who is reading
> along, as a matter of policy the end user does not receive non-free
> source code from Guix.

Right; the source is downloaded from commondatastorage.googleapis.com
but that is a technicality. What I'm saying is that the recipe should
be updated to cause it to download an already-cleaned up version
directly from Guix (it could be hosted somewhere on gnu.org for example
but exactly where can be up for negotiation) and that this excuse of
"they're getting it elsewhere" shouldn't be usable as an excuse to
sidestep the FSDG. It's still causing the user to download the software
due to the recipes provided by Guix.

> The tools provided by Guix to access source code only return source
> code that is freely licensed. If the sources have to be modified to
> ensure this, the unodified source code is not provided to the user. 

It's still being downloaded into their computer and then being cleaned
up after the fact. If there weren't freedom problems with it there
wouldn't be a need for a clean-up program (ungoogled-chromium in this
case) to be running -- as a process on the user's computer -- to do
this.

And in https://www.gnu.org/distros/free-system-distribution-guidelines.
html we have:

"For instance, a free system distribution must not contain browsers that implement EME, the browser functionality designed to load DRM modules."

So that should make it quite clear.

  reply	other threads:[~2019-02-20  5:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19  3:44 bug#34565: ungoogled-chromium contains Widevine DRM Jason Self
2019-02-19  7:06 ` Leo Famulari
2019-02-19 13:28   ` Jason Self
2019-02-19 13:42     ` Julien Lepiller
2019-02-19 14:44       ` Julien Lepiller
2019-02-20  5:42         ` Leo Famulari
2019-02-20  9:22           ` Giovanni Biscuolo
2019-02-20 14:48             ` Marius Bakke
2019-10-12 11:14               ` ng0
2019-10-12 11:32                 ` bug#34565: ungoogled-chromium may contain " Marius Bakke
2019-02-19 14:43     ` bug#34565: ungoogled-chromium contains " Leo Famulari
2019-02-20  0:39       ` Jason Self
2019-02-20  1:12         ` Jason Self
2019-02-20  1:19           ` Jason Self
2019-02-20 13:03             ` Jason Self
2019-02-20 16:18               ` Julien Lepiller
2019-02-20 20:15                 ` Adonay Felipe Nogueira
2019-02-20 21:49                   ` Ricardo Wurmus
2019-02-21  2:19                     ` Jason Self
2019-02-20  5:15           ` Leo Famulari
2019-02-20  5:35             ` Jason Self [this message]
2019-02-20  7:59               ` bug#34565: ungoogled-chromium might contain remnants of " Ricardo Wurmus
2019-02-20 10:09               ` bug#34565: ungoogled-chromium contains " Jelle Licht
2019-02-20 14:37           ` Marius Bakke
2019-02-21  2:43             ` Jason Self
2019-02-21  7:51               ` Marius Bakke

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=1550640947.21795.7.camel@jxself.org \
    --to=j@jxself.org \
    --cc=34565@debbugs.gnu.org \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).