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: Wed, 20 Feb 2019 05:03:31 -0800	[thread overview]
Message-ID: <1550667811.25277.1.camel@jxself.org> (raw)
In-Reply-To: <1550625587.14780.2.camel@jxself.org>

[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]

Jason Self wrote:
> I should probably add on that this position comes from my interaction
> with the FSF in 2010: When LibreWRT was founded in 2010 (before it
> later merged into libreCMC) we submitted a similar question to the
> FSF,as to if it was sufficient for the LibreWRT build scripts (which
> would be run by the person building the firmware image from source
> and would have completely automated, just like how someone might
> instruct Guix to build from source) to download Linux and then run
> the Linux-libre deblobbing scripts on it vs having the build scripts
> instead download tarballs that were already cleaned up. I can't seem
> to find the email from back then but the response was that we needed
> to use already cleaned-up tarballs, not ask the user to clean up the
> software afterward even if automated. So that was what we did. Guix
> should do something similar.

I haven't been able to find this conversation in my email. As it seems
to be directly relevant to Guix, since it seems to also be the exact
same method they use, I have emailed the FSF asking if they can locate
this in their ticketing system and to re-send the conversation to me.
More to come.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2019-02-20 15:28 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 [this message]
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=1550667811.25277.1.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).