From: Christopher Baines <mail@cbaines.net>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 70766@debbugs.gnu.org
Subject: [bug#70766] Request to merge "gnome-team" branch
Date: Sun, 26 May 2024 17:51:04 +0100 [thread overview]
Message-ID: <87h6ekfrev.fsf@cbaines.net> (raw)
In-Reply-To: <2ed5b2af9eda9eb0d558608640d65e8f91af6bf2.camel@gmail.com> (Liliana Marie Prikler's message of "Sat, 25 May 2024 16:58:21 +0200")
[-- Attachment #1: Type: text/plain, Size: 1475 bytes --]
Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> Am Freitag, dem 24.05.2024 um 15:14 +0100 schrieb Christopher Baines:
>> Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
>>
>> > Am Freitag, dem 17.05.2024 um 09:11 +0100 schrieb Christopher
>> > Baines:
>> > > gtk is failing to build on aarch64-linux which is blocking lots
>> > > of packages, and the failure looks familiar but I haven't made
>> > > any progress looking at it.
>> >
>> > That looks like trouble. I've fixed up some breaking builds on
>> > x86, but I think we might have to block the merge for now if aarch
>> > can't be fixed.
>>
>> I've now pushed 36e49999227e4f621c211ed5f1a506a3046052df to gnome-
>> team which I hope will fix gtk where it's broken.
>
> QA looks good[1].
Things had flipped to unknown rather than blocked, but I think there
were still some blocked builds, but mostly due to a flaky
python-scikit-image test.
I've now pushed a fix for that to master [1] and rebased
gnome-team. I've also squashed my gtk change in to the gtk update
commit.
2: https://issues.guix.gnu.org/70997
> How do we proceed with the merge? Just `git merge`? Or should we
> rebase on gnome-team and then merge?
Now that I've rebased the branch, it'll take a little while for QA to
check things again, but I don't know of any problems.
To merge it to master, you can either just merge, or rebase and merge
(so that it's a fast forward rebase).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2024-05-26 16:52 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6ekfrev.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.