unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 70766@debbugs.gnu.org
Subject: [bug#70766] Request for merging "gnome-team" branch
Date: Wed, 08 May 2024 12:56:36 +0100	[thread overview]
Message-ID: <87v83ofrez.fsf@cbaines.net> (raw)
In-Reply-To: <8158d0e0c7556e04f8356b213900f673c1b90442.camel@gmail.com> (Liliana Marie Prikler's message of "Tue, 07 May 2024 19:34:41 +0200")

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

Liliana Marie Prikler <liliana.prikler@gmail.com> writes:

> Am Samstag, dem 04.05.2024 um 08:41 +0200 schrieb Liliana Marie
> Prikler:
>> Hi Guix,
>>
>> gnome-team currently has some important updates to gtk and webkitgtk
>> that I'd like to see on master.  Unfortunately, CI has yet to rebuild
>> some Java stuff that is ultimately needed by the gnome metapackage.
>
> I locally built gnome and it builds fine; I haven't tested it yet,
> however.

Sounds good, there is the open merge request for core-updates, but I
think it's sensible to not block these changes until after core-updates
is dealt with as I think that is realistically still several weeks away
at least. If anyone thinks differently, we can wait instead, but I'll
mark the request to merge core-updates as being blocked by this issue to
signal this.

This might be getting ahead of ourselves as well, but would you be able
to rebase the branch, ideally on the most recently processed master
commit here [1], as that'll enable QA to work out what has changed on
the branch. This should also get rid of the merge commit on the
gnome-team branch, which I think is something to avoid.

1: https://data.qa.guix.gnu.org/repository/2/branch/master

Thanks,

Chris

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

  reply	other threads:[~2024-05-08 11:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-04  6:41 [bug#70766] Request to merge "gnome-team" branch Liliana Marie Prikler
2024-05-07 17:34 ` [bug#70766] Request for merging " Liliana Marie Prikler
2024-05-08 11:56   ` Christopher Baines [this message]
2024-05-13  9:27 ` [bug#70766] Request to merge " Christopher Baines
2024-05-17  8:11   ` Christopher Baines
2024-05-19  9:37     ` Liliana Marie Prikler
2024-05-24 14:14       ` Christopher Baines
2024-05-25 14:58         ` Liliana Marie Prikler
2024-05-26 16:51           ` Christopher Baines
2024-06-04 20:45             ` Christopher Baines
2024-06-05  4:26               ` Liliana Marie Prikler
2024-06-06 19:59                 ` Christopher Baines
2024-06-06 21:10                   ` bug#70766: " Liliana Marie Prikler

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=87v83ofrez.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=70766@debbugs.gnu.org \
    --cc=liliana.prikler@gmail.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).