unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kei Kebreau <kkebreau@posteo.net>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: 'core-updates' Q4 2019
Date: Thu, 17 Oct 2019 16:44:51 -0400	[thread overview]
Message-ID: <87v9snnlto.fsf@posteo.net> (raw)
In-Reply-To: <87tv8a0x8u.fsf@devup.no> (Marius Bakke's message of "Tue, 15 Oct 2019 18:49:53 +0200")

[-- Attachment #1: Type: text/plain, Size: 1918 bytes --]

Marius Bakke <mbakke@fastmail.com> writes:

> Kei Kebreau <kkebreau@posteo.net> writes:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>>
>>> Hello Kei,
>>>
>>> Kei Kebreau <kkebreau@posteo.net> skribis:
>>>
>>>> I have the GNOME 3.32 branch! I'm building it on top of the new
>>>> core-updates as you read this message. If everything still builds, I'll
>>>> immediately send my changes to the guix-patches mailing list for review
>>>> and testing.
>>>
>>> Shouldn’t you instead base it on ‘master’ or ‘staging’?
>>>
>>> That may allow us to merge it more quickly, especially if these are only
>>> GNOME-related changes.
>>>
>>> Thanks for working on it!
>>>
>>> Ludo’.
>>
>> Hi Ludovic,
>>
>> Taken individually, most changes on the GNOME 3.32 branch could be
>> pushed to master without too much trouble. The only issues are big
>> changes like
>> upgrading Vala. The following changes would cause a large number of
>> rebuilds:
>>
>> At least 300 rebuilds: python-pygobject, gtk+
>>
>> At least 1200 rebuilds: gtk-doc, vala, yelp-tools, python-parameterized,
>> python-check-manifest, python-anytree
>>
>> I'll minimize the changes, isolate what I can, and submit the results
>> for review as time allows!
>
> Thanks!  Sounds like something we can handle in a 'staging' cycle.
>
> By the way, GNOME 3.34 is out, and 3.36 is slated for March.  So I think
> we will finally be able to catch up with GNOME again soon...
>
> (let's focus on 3.32 first though ;-))

I have news! The good part is that I got 54 packages to build on top of
master. The bad part is that when I try to use the resulting packages as
my system configuration, my computer gets stuck in tty1, and attempting
to switch to Xorg on tty7 leaves my screen frozen though the system is
still responsive.

Anyone want to see the 54 patches and possibly help me root around for
the issue?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2019-10-17 20:45 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-08 21:55 'core-updates' Q4 2019 Marius Bakke
2019-10-09 11:53 ` Mathieu Othacehe
2019-10-10 14:32   ` Ludovic Courtès
2019-10-10 15:35     ` Mathieu Othacehe
2019-10-10 21:22     ` Svante Signell
2019-10-11  7:52       ` Ludovic Courtès
2019-10-11 20:42 ` Kei Kebreau
2019-10-12 22:15   ` Ludovic Courtès
2019-10-15  1:28     ` Kei Kebreau
2019-10-15 16:49       ` Marius Bakke
2019-10-17 20:44         ` Kei Kebreau [this message]
2019-10-17 21:29           ` Ricardo Wurmus
2019-10-18  1:53             ` Kei Kebreau
2019-10-18  3:08               ` Ricardo Wurmus
2019-10-19 13:34           ` Timothy Sample
2019-10-20  3:29             ` Kei Kebreau
2019-10-21 13:58               ` pelzflorian (Florian Pelz)
2019-10-22  0:37                 ` Timothy Sample
2019-10-23  3:07                   ` Timothy Sample
2019-10-23  7:49                     ` pelzflorian (Florian Pelz)
2019-10-26 20:26                       ` Kei Kebreau
2019-10-23 17:49                     ` Marius Bakke
2019-10-24  2:07                       ` Timothy Sample
2019-10-24 18:17                         ` Marius Bakke
2019-10-26 21:25                           ` Timothy Sample
2019-11-02  2:27               ` Kei Kebreau
2019-11-04 19:37                 ` Miguel Arruga Vivas
2019-11-05 23:38                   ` Kei Kebreau
2019-11-06 17:46                     ` Leo Famulari
2019-11-07  1:16                       ` Kei Kebreau
2019-11-07  2:58                         ` Timothy Sample
2019-11-08  0:58                     ` Miguel Arruga Vivas
2019-11-23  2:11                       ` Kei Kebreau

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=87v9snnlto.fsf@posteo.net \
    --to=kkebreau@posteo.net \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.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.
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).