From: Leo Famulari <leo@famulari.name>
To: Jason Self <j@jxself.org>
Cc: 34565@debbugs.gnu.org
Subject: bug#34565: ungoogled-chromium contains Widevine DRM
Date: Tue, 19 Feb 2019 02:06:01 -0500 [thread overview]
Message-ID: <20190219070601.GA8273@jasmine.lan> (raw)
In-Reply-To: <1550547897.31222.1.camel@jxself.org>
[-- Attachment #1: Type: text/plain, Size: 426 bytes --]
On Mon, Feb 18, 2019 at 07:44:57PM -0800, Jason Self wrote:
> Unless I am mistaken, ungoogled-chromium is not removing Widevine DRM
> from upstream Chromium. Guix should remove that if upstream won't, as I
> believe this goes against "the distro must contain no DRM..." in the
> FSDG.
Why do you think this is the case? It doesn't work for me on any of the
Widevine demos I can find, unlike an installation of Google Chrome.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-19 7:07 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 [this message]
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
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=20190219070601.GA8273@jasmine.lan \
--to=leo@famulari.name \
--cc=34565@debbugs.gnu.org \
--cc=j@jxself.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).