From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Self Subject: bug#34565: ungoogled-chromium contains Widevine DRM Date: Wed, 20 Feb 2019 05:03:31 -0800 Message-ID: <1550667811.25277.1.camel@jxself.org> References: <1550547897.31222.1.camel@jxself.org> <20190219070601.GA8273@jasmine.lan> <1550582906.5431.7.camel@jxself.org> <20190219144342.GA2688@jasmine.lan> <1550623152.12316.5.camel@jxself.org> <1550625137.14138.3.camel@jxself.org> <1550625587.14780.2.camel@jxself.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-K9avsEVh8YTzFyKp6qqp" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:44251) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gwTnB-0002hn-Rl for bug-guix@gnu.org; Wed, 20 Feb 2019 10:28:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gwTn5-0000au-Ki for bug-guix@gnu.org; Wed, 20 Feb 2019 10:28:10 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:57550) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gwTn5-0000PP-B0 for bug-guix@gnu.org; Wed, 20 Feb 2019 10:28:07 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gwRXe-0007F4-EQ for bug-guix@gnu.org; Wed, 20 Feb 2019 08:04:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <1550625587.14780.2.camel@jxself.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 34565@debbugs.gnu.org --=-K9avsEVh8YTzFyKp6qqp Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=C2=A0question 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. --=-K9avsEVh8YTzFyKp6qqp Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQIcBAABCgAGBQJcbVAkAAoJEJ0NsxtUWjGYn2gP/ixSgVt8SsabNCn8CLnq0wXd cwnudZoYBrvVc26fsO+px1yH+Om24UHXRlwKjfsEnaZEW8G6EUSbYMWbqOxwVvHB ktinWyp0INAriLPsdCy6PgHnOy5rSA0JVLkFTopY4Gfefn4ha/VBmXeedb8uODeZ a1Uaijnr18j6F6Db1Hoe0cLp/9iM2WbpkoQ0SFwdxWCXNRq1w8r/Xd2ZEvds/l+B bWEF1c2Yr0MonG8krXQukfzhgIHEg+f6LUHlO53wr2YQMXYM97H5BF6EKqlSCc6k EEI0FZpCCPpBphDz9DJMh79rqXL6r8XrDJDet7jhVJ20Qg5onJqsaBL6W+chIs3q BmqWuVEHa3nvURerNBEMgZiPDZt0SfbHaZrDxjoA9zUBbKMRm1d4vJtK2NNXauNQ Nc0059VUN2jslCO+AsEL1SCP4C4YRiMxRQGgBbeU8mefDSIM8k3+9N+dQhwESVpU 5i5qRpkngIHf+S8aOA43vDP7bXrupgu9T6awX6og0Ptsw6lxsUihBiX6peVDvYTG ePzyWuQb2XpxGqPkGTVD9ihlaoLRypnY3X7rKwtgRcqb2qm+IsqUs1kuykzuSQqS fz1mLF4Rlbv4Ss7dIeJtz2JgLPX7jUc3GPtpTmNQVG9gXhlrIFqIW64Wcpoyyxpj xyFNQT/BjuAO+3tykA0Q =Lshi -----END PGP SIGNATURE----- --=-K9avsEVh8YTzFyKp6qqp--