From: Leo Famulari <leo@famulari.name>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: updating gdk-pixbuf for epiphany
Date: Sat, 1 Apr 2017 14:37:04 -0400 [thread overview]
Message-ID: <20170401183704.GC18851@jasmine> (raw)
In-Reply-To: <87lgrj429s.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
On Sun, Apr 02, 2017 at 10:55:27AM +0200, Ricardo Wurmus wrote:
> Hi,
>
> I’d like to update Epiphany to the latest release but noticed that it
> needs a slightly younger version of gdk-pixbuf. Updating gdk-pixbuf to
> 2.36.6 would result in *many* rebuilds. “guix refresh -l gdk-pixbuf”
> tells me this:
>
> Building the following 324 packages would ensure 630 dependent packages are rebuilt…
>
> So, should this be done in a separate branch along with other GNOME
> updates or can this go to staging after merging core-updates?
We should update all the GNOME stuff, but that requires some focused
work. So, if you or somebody else is up for it, great :) If not, I think
it's fine to put it on a staging branch.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-04-01 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 8:55 updating gdk-pixbuf for epiphany Ricardo Wurmus
2017-04-01 18:37 ` Leo Famulari [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170401183704.GC18851@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).