From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Aleksej <lesikedelweiss@disroot.org>, 72202@debbugs.gnu.org
Subject: [bug#72202] [PATCH 00/38] Start work on GNOME 46
Date: Fri, 09 Aug 2024 23:39:06 +0200 [thread overview]
Message-ID: <f5e8f63d64a8de4c4c461d035c91792c64d4fba6.camel@gmail.com> (raw)
In-Reply-To: <61D3B702-3AE7-4FC8-9409-DB3299F7F214@disroot.org>
Am Freitag, dem 09.08.2024 um 04:55 +0300 schrieb Aleksej:
> Hi! It's my first time using Guix, so sorry if I'm doing the wrong
> thing now. Is there any work going on packaging GNOME 46? Or maybe we
> could wait until GNOME 47? Are there any major issues now, that stop
> us from upgrade?
Apart from Rust being Rust (not sure whether the rust-team branch has
what we need to package the new Rust-based applications), GNOME 46
already requires some deep dependency upgrades that will more or less
rebuild the world (tending towards more here).
You can check out the gnome-team branch and try to build some
applications or a full vm (I haven't tried that latter one yet, given
that important packages are still stuck on their 44 versions).
Upstream declares their versions in [1] – we sadly don't have a
buildstream importer yet and need to update the packages by hand.
Cheers
[1] https://gitlab.gnome.org/GNOME/gnome-build-meta/
prev parent reply other threads:[~2024-08-09 21:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 22:38 [bug#72202] [PATCH 00/38] Start work on GNOME 46 Liliana Marie Prikler
2024-07-17 20:13 ` [bug#72202] [PATCH 25/38] gnu: gtksourceview: Update to 5.12.1 Liliana Marie Prikler
2024-07-17 20:14 ` [bug#72202] [PATCH 26/38] gnu: gnome-text-editor: Update to 46.3 Liliana Marie Prikler
2024-07-17 20:21 ` [bug#72202] [PATCH 27/38] gnu: gnome-user-docs: Update to 46.1 Liliana Marie Prikler
2024-07-17 20:41 ` [bug#72202] [PATCH 28/38] gnu: gnome-weather: Update to 46.0 Liliana Marie Prikler
2024-07-19 9:04 ` [bug#72202] [PATCH 31/38] gnu: sushi: " Liliana Marie Prikler
2024-07-19 9:09 ` [bug#72202] [PATCH 33/38] gnu: sysprof: " Liliana Marie Prikler
2024-07-19 9:19 ` [bug#72202] [PATCH 35/38] gnu: gnome-chess: Update package style Liliana Marie Prikler
2024-07-19 9:48 ` [bug#72202] [PATCH 36/38] gnu: evolution-data-server: Update to 3.52.3 Liliana Marie Prikler
2024-07-19 9:48 ` [bug#72202] [PATCH 37/38] gnu: evolution: " Liliana Marie Prikler
2024-07-19 9:53 ` [bug#72202] [PATCH 38/38] gnu: gnome-mahjongg: Update to 3.40.1 Liliana Marie Prikler
2024-07-21 14:13 ` [bug#72202] [PATCH 00/38] Start work on GNOME 46 Liliana Marie Prikler
2024-08-09 1:55 ` Aleksej via Guix-patches via
2024-08-09 21:39 ` Liliana Marie Prikler [this message]
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=f5e8f63d64a8de4c4c461d035c91792c64d4fba6.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=72202@debbugs.gnu.org \
--cc=lesikedelweiss@disroot.org \
/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).