From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: font-dejavu: Update to 2.35.
Date: Sat, 12 Mar 2016 11:47:18 +0300 [thread overview]
Message-ID: <87io0s13s9.fsf@gmail.com> (raw)
In-Reply-To: <874mcdysou.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 11 Mar 2016 15:50:41 +0100")
Ludovic Courtès (2016-03-11 17:50 +0300) wrote:
> Efraim Flashner <efraim@flashner.co.il> skribis:
>
>> On Fri, 11 Mar 2016 13:08:17 +0300
>> Alex Kost <alezost@gmail.com> 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 like
>>> abiword, libreoffice, gimp, gnome). This happens because 'font-dejavu'
>>> 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 rebuilding 188
>> packages so I pushed it to core-updates. Currently hydra is building out
>> security updates to take out some of the grafts so not "distracting" hydra
>> with large rebuilds is good(tm).
>
> +1
Sorry, I didn't get it. Should this update be pushed to core-updates?
But not now?
--
Alex
next prev parent reply other threads:[~2016-03-12 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 10:08 [PATCH] gnu: font-dejavu: Update to 2.35 Alex Kost
2016-03-11 12:56 ` Efraim Flashner
2016-03-11 14:50 ` Ludovic Courtès
2016-03-12 8:47 ` Alex Kost [this message]
2016-03-13 4:27 ` Mark H Weaver
2016-03-13 10:22 ` Alex Kost
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87io0s13s9.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.