From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44537) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d6NAT-0001qY-9r for guix-patches@gnu.org; Thu, 04 May 2017 16:16:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d6NAQ-0006nn-3o for guix-patches@gnu.org; Thu, 04 May 2017 16:16:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:56696) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d6NAP-0006nh-TO for guix-patches@gnu.org; Thu, 04 May 2017 16:16:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1d6NAP-0004H9-L5 for guix-patches@gnu.org; Thu, 04 May 2017 16:16:01 -0400 Subject: bug#26702: [PATCH 1/2] gnu: Add font-cns11643 Resent-Message-ID: From: Alex Kost References: <36cee073-4427-d584-2d9c-c0e2e22fd4ff@openmailbox.org> <87wpa2gcdx.fsf@fastmail.com> <994b0c86-c4ce-8b20-5c02-acf592fdc8bf@openmailbox.org> <87mvawfbps.fsf@fastmail.com> Date: Thu, 04 May 2017 23:15:53 +0300 In-Reply-To: <87mvawfbps.fsf@fastmail.com> (Marius Bakke's message of "Tue, 02 May 2017 00:34:23 +0200") Message-ID: <87fugkcr9i.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Marius Bakke Cc: 26702@debbugs.gnu.org Marius Bakke (2017-05-02 00:34 +0200) wrote: > Brendan Tildesley writes: [...] >> I have confirmed that the new hash represents an update to the font. I >> have thought about hosting this file, but I'm not sure where I can host >> ~300MiB. Also, It means I have to bother updating that file frequently. >> On the other hand if we use upstream, a failing hash typically means >> there is an update. There is unlikely any other Guix user interested in >> these fonts at the present. So I'm not sure what to do. > > Thanks for checking! Where did you take the version number and datestamp > from? Are you willing to help maintain this package? > > The current situation is suboptimal, but I think it's fine if we can > ping you about any problems. What do you think? > > I've committed this for now, let's see how long it holds. I may be able > to provide a fallback mirror in a not-too-distant future, but immediate > suggestions welcome. Hi Marius, I've just found that you pushed this patch but didn't close this "bug thread" (or whatever it should be called). Was it intentional? -- Alex