From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Kost Subject: Re: [PATCH] gnu: font-dejavu: Update to 2.35. Date: Sun, 13 Mar 2016 13:22:18 +0300 Message-ID: <87io0qy8x1.fsf@gmail.com> References: <87r3fhnx7y.fsf@gmail.com> <20160311145653.696d6733@debian-netbook> <874mcdysou.fsf@gnu.org> <87io0s13s9.fsf@gmail.com> <87io0r9f3k.fsf@netris.org> 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]:56967) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1af39x-0000BS-C0 for guix-devel@gnu.org; Sun, 13 Mar 2016 06:22:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1af39u-0003Jj-6V for guix-devel@gnu.org; Sun, 13 Mar 2016 06:22:05 -0400 In-Reply-To: <87io0r9f3k.fsf@netris.org> (Mark H. Weaver's message of "Sat, 12 Mar 2016 23:27:59 -0500") 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-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Mark H Weaver Cc: guix-devel@gnu.org Mark H Weaver (2016-03-13 07:27 +0300) wrote: > Alex Kost writes: > >> Ludovic Court=C3=A8s (2016-03-11 17:50 +0300) wrote: >> >>> Efraim Flashner skribis: >>> >>>> On Fri, 11 Mar 2016 13:08:17 +0300 >>>> Alex Kost wrote: >>>> >>>>> I was going to commit several updates including font-dejavu. Happily, >>>>> with: >>>>> >>>>> guix refresh -l font-dejavu >>>>> >>>>> I found that many things would be rebuilt (including some big ones li= ke >>>>> abiword, libreoffice, gimp, gnome). This happens because 'font-dejav= u' >>>>> is an input of 'cups-filters' which is an input of 'cups' which is an >>>>> input for several things including 'gtk+'. >>>>> >>>>> So my question is: should this update go to master? >>>> >>>> Some of these I push to core-updates. Rebuilding check means rebuildin= g 188 >>>> packages so I pushed it to core-updates. Currently hydra is building o= ut >>>> security updates to take out some of the grafts so not "distracting" h= ydra >>>> with large rebuilds is good(tm). >>> >>> +1 >> >> Sorry, I didn't get it. Should this update be pushed to core-updates? >> But not now? > > I think you should push the update to core-updates at your earliest > convenience :) Thanks, that's what I thought. Pushed to core-updates. --=20 Alex