From: "André Batista" <nandre@riseup.net>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 74756@debbugs.gnu.org, vivien@planete-kraus.eu,
maxim.cournoyer@gmail.com
Subject: [bug#74756] [PATCH gnome-team 0/3] Update gjs to 1.82.1
Date: Tue, 10 Dec 2024 20:11:35 -0300 [thread overview]
Message-ID: <Z1jKp_C1oROLKD4g@andel> (raw)
In-Reply-To: <cover.1733775119.git.liliana.prikler@gmail.com>
Hi Liliana,
seg 09 dez 2024 às 21:11:59 (1733789519), liliana.prikler@gmail.com enviou:
> Hi Guix,
>
> after updating GNOME Shell to 46 in [1], I noticed that the tools
> dealing with extensions do not work as supposed. According to [2],
> upstream expects gjs versions 1.80 or 1.82 for GNOME 46/47 respectively,
> so let's update it. Unfortunately, this also requires updates of icu4c
> and mozjs, which I'd rather put in the hands of our mozilla team if
> possible.
>
I'm not sure I understood your last sentence above: what do you mean
by "rather put in the hands of our mozilla team"? To build on a
separate branch? To review here the work you've already done? To fix
those FIXMEs that you've worked around for now?
The patches look good to me, but they trigger to many builds for me
to actually test them locally.
Oh and the icu4c one does not apply cleanly on master because there's
a icu4c-75 under what is currently icu4c-73.
Cheers!
next prev parent reply other threads:[~2024-12-10 23:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 20:11 [bug#74756] [PATCH gnome-team 0/3] Update gjs to 1.82.1 Liliana Marie Prikler
2024-12-08 11:19 ` [bug#74756] [PATCH gnome-team 1/3] gnu: Make icu4c 73.1 the default Liliana Marie Prikler
2024-12-09 22:07 ` Mark H Weaver
2024-12-09 19:22 ` [bug#74756] [PATCH gnome-team 2/3] gnu: mozjs: Update to 128.3.1 Liliana Marie Prikler
2024-12-09 19:26 ` [bug#74756] [PATCH gnome-team 3/3] gnu: gjs: Update to 1.82.1 Liliana Marie Prikler
2024-12-10 23:11 ` André Batista [this message]
2024-12-11 18:30 ` [bug#74756] [PATCH gnome-team 0/3] Update gjs " Liliana Marie Prikler
2024-12-11 23:28 ` André Batista
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=Z1jKp_C1oROLKD4g@andel \
--to=nandre@riseup.net \
--cc=74756@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=maxim.cournoyer@gmail.com \
--cc=vivien@planete-kraus.eu \
/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.