guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: core-updates freeze


From: Marius Bakke
Subject: Re: core-updates freeze
Date: Fri, 12 Jul 2019 17:20:44 +0200
User-agent: Notmuch/0.29.1 (https://notmuchmail.org) Emacs/26.2 (x86_64-pc-linux-gnu)

Kei Kebreau <address@hidden> writes:

> Ludovic Courtès <address@hidden> writes:
>
>> Hello!
>>
>> Marius Bakke <address@hidden> skribis:
>>
>>> The core-updates branch is now (almost!) ready for prime time.
>>
>> Yay!
>>
>>> This is turning out to be one of the biggest merges ever[*], currently
>>> representing 433 commits from 15 people, with commits dating back to
>>> September last year(!).
>>
>> Ouch!  This is both impressive and… frightening.  :-)
>>
>>> Some of the highlights from this branch include:
>>>
>>> * jannekes long-awaited new reduced binary seeds for i686 and x86_64
>>> * GCC7 is now the default compiler
>>> * The 'CMake' package comes with full documentation
>>> * OpenSSL 1.1 is now the default 'openssl' package
>>> * GNOME 3.30
>>> * glibc 2.29, binutils 2.32, gettext 0.20, bash 5.0.7, gawk 5.0.1, ...
>>
>> Exciting!
>>
>>> To give everyone a little time to brush up any last-minute patches, as
>>> well as let the CI catch up with 'master' and 'staging', I suggest we
>>> set a final date for starting the full CI build on *July 9th*, i.e six
>>> days from now.  At which point the branch becomes bugfix-only, no new
>>> updates or features.
>>>
>>> July 9th incidentally gives us just enough time to get Python 3.7.4 too,
>>> which comes with desirable security and OpenSSL 1.1 compatibility fixes.
>>
>> July 9th is now behind us, where are we?  I’m currently running:
>>
>>   guix pull --branch=core-updates -p /tmp/core-updates
>>
>> so I can give it a shot with my profile and my system.
>>
>> Is there anything people should pay attention to, or any specific tests
>> we should make?
>>
>> Thank you!
>>
>> Ludo’.
>
> I must say, the GNOME 3.30 changes haven't been pushed to core-updates
> yet.  There were a number of issues with the updated GNOME desktop as I
> last built it.  For example, the displayed time was incorrect, and the
> "night light" feature didn't work.  Other issues included failing tests
> that I couldn't figure out and just disabled to get the building to
> finish.

I think many of the failing tests should be fixed with commit
ee46474d54a661e87cd501c3fde6e572b3423a60.

Wrt the time zone issue, it appears recent Glib refuses to function if
/etc/localtime is not a symbolic link, reminiscent of 
<https://issues.guix.gnu.org/issue/35746>:

https://gitlab.gnome.org/GNOME/glib/blob/glib-2-60/glib/gtimezone.c#L443

I'm not sure what we should do about it.  Thoughts?

Kei: Does it work if you 'echo Your/Timezone > /etc/timezone' ?
Alternatively, you could make /etc/localtime a symbolic link to
$tzdata/share/zoneinfo/Your/Timezone, though that will not persist a
reboot.

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]