From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Cl=C3=A9ment?= Lassieur Subject: Re: FSDG status of chromium Date: Wed, 26 Sep 2018 10:41:07 +0200 Message-ID: <87zhw4vefw.fsf@lassieur.org> References: <20180925092922.20b2a32d@peers.community> <871s9h2wtu.fsf@lassieur.org> <878t3o8ypl.fsf@igalia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55983) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g55Nl-0003lx-9e for guix-devel@gnu.org; Wed, 26 Sep 2018 04:41:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g55Ng-0005AQ-8K for guix-devel@gnu.org; Wed, 26 Sep 2018 04:41:17 -0400 Received: from mail.lassieur.org ([83.152.10.219]:57126) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1g55Nf-00059T-6j for guix-devel@gnu.org; Wed, 26 Sep 2018 04:41:12 -0400 In-reply-to: <878t3o8ypl.fsf@igalia.com> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Andy Wingo Cc: guix-devel@gnu.org Andy Wingo writes: > On Tue 25 Sep 2018 21:36, Cl=C3=A9ment Lassieur wr= ites: > >> Thank you very much for letting us know about these issues! I'm glad >> Marius put it in a channel then, it was a wise decision. I hope we'll >> make it free at some point, so that it can be integrated into Guix. But >> there is Icecat 60 now (thanks to everyone involved!), so it's not that >> urgent anymore. > > Unless I misunderstand, we have only been notified about the history of > a discussion. Are you aware of any concrete issue that has been raised? > Any non-free file or incompatible in our distribution? I believe the serious issue that has been raised is that we don't communicate well with other FSDG distributions. There are discussions and bugs reported about the fact that Chromium might be non-free, and while we may have fixed those issues, we didn't notify the other people in the community who have the exact same issues. Plus, we may have missed problems that have been raised there.