From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 38994@debbugs.gnu.org
Subject: [bug#38994] [PATCH core-updates] gnu: glib: Fix g_app_info_get_default_for_type.
Date: Tue, 7 Jan 2020 10:22:49 +0100 [thread overview]
Message-ID: <8a1cd5ae-003b-e912-69ae-a3504c5fc039@web.de> (raw)
In-Reply-To: <20200107004510.176c34d8@scratchpost.org>
On 07.01.20 00:45, Danny Milosavljevic wrote:
>> I would personally like, if we can update to 2.62. Because that is
>> needed for updating gnome to 3.34
>> (https://gitlab.com/jonsger/Guix/commits/wip-gnome-3.34). What do you think?
>
> Sure, why not (on core-updates)? There's glib 2.63 released upstream.
I wonder if uneven release numbers at glib mark development/unstable
releases. As it's the case in the rest of GNOME.
> Right now, core-updates has glib 2.60.6 still (as has master).
>
> If you try to update glib, be advised that core-updates is broken right now[1].
>
> On the other hand that means that we could update glib on core-updates right
> away since core-updates could not built anything using it anyway :P
>
> (The bug upstream is still open, so it will not improve things in that regard)
>
> [1] texlive-bin build error <https://bugs.gnu.org/38999>; texlive is required for glib-with-documentation.
next prev parent reply other threads:[~2020-01-07 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 19:37 [bug#38994] [PATCH core-updates] gnu: glib: Fix g_app_info_get_default_for_type Danny Milosavljevic
2020-01-06 23:04 ` Jonathan Brielmaier
2020-01-06 23:45 ` Danny Milosavljevic
2020-01-07 9:22 ` Jonathan Brielmaier [this message]
2020-01-13 21:50 ` Marius Bakke
2020-01-14 0:59 ` bug#38994: " Danny Milosavljevic
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=8a1cd5ae-003b-e912-69ae-a3504c5fc039@web.de \
--to=jonathan.brielmaier@web.de \
--cc=38994@debbugs.gnu.org \
--cc=dannym@scratchpost.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 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).