From: Marius Bakke <mbakke@fastmail.com>
To: Timothy Sample <samplet@ngyro.com>
Cc: guix-devel@gnu.org, help-guix@gnu.org
Subject: Re: core-updates call for testing
Date: Mon, 04 May 2020 17:32:14 +0200 [thread overview]
Message-ID: <87bln31zsx.fsf@devup.no> (raw)
In-Reply-To: <87sggf92jc.fsf@ngyro.com>
[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]
Timothy Sample <samplet@ngyro.com> writes:
> Hi Marius,
>
> Marius Bakke <mbakke@fastmail.com> writes:
>
>> The "core-updates" branch is ready for testing! [...]
>>
>> Please try upgrading your profiles and systems and file bugs for
>> anything that does not work for you. GNOME users in particular are
>> encouraged to try the new GNOME 3.34 and report any regressions.
>
> Just so you know, GNOME 3.34 is working swimmingly for me. So far I am
> a very happy core-updates user. Thank you very much for all your hard
> work!
Great to know, thanks! Credits to Kei for the GNOME 3.34 upgrade. :-)
I think the only remaining blocker is fixing the WebKitGTK+ sandbox
issue in Epiphany: <https://issues.guix.gnu.org/issue/40837>.
Chris also reported an issue with FlighGear. Presumably updating to the
latest version would make it work with the newer Boost. Any takers?
@everyone, please speak up if you find any of your packages failing on
the core-updates branch! The substitute coverage is currently ~90%,
which is better than on 'master'.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2020-05-04 16:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 23:24 core-updates call for testing Marius Bakke
2020-04-24 3:20 ` sirgazil
2020-04-24 12:58 ` sirgazil
2020-04-24 16:25 ` Marius Bakke
2020-04-24 16:54 ` Gábor Boskovits
2020-04-24 19:29 ` sirgazil
2020-04-24 18:08 ` sirgazil
2020-04-24 21:52 ` Marius Bakke
2020-04-24 22:42 ` sirgazil
2020-04-24 18:46 ` sirgazil
2020-04-24 14:40 ` Jack Hill
2020-04-24 20:06 ` Jack Hill
2020-04-25 3:02 ` Jack Hill
2020-04-25 13:24 ` sirgazil
2020-04-25 18:13 ` sirgazil
2020-04-29 11:31 ` Ricardo Wurmus
2020-04-25 18:36 ` sirgazil
2020-04-25 21:19 ` Jack Hill
2020-04-25 21:54 ` sirgazil
2020-04-27 22:09 ` Jack Hill
2020-04-29 6:17 ` Ricardo Wurmus
2020-04-25 18:06 ` Leo Famulari
2020-04-28 13:17 ` Marius Bakke
2020-04-28 12:46 ` Efraim Flashner
2020-04-28 13:12 ` Marius Bakke
2020-05-04 14:51 ` Timothy Sample
2020-05-04 15:32 ` Marius Bakke [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=87bln31zsx.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
--cc=samplet@ngyro.com \
/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.
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).