all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Vivien Kraus <vivien@planete-kraus.eu>, 67651@debbugs.gnu.org
Subject: bug#67651: [gnome-team] What should we do with the "gnome" package?
Date: Sun, 07 Jan 2024 17:53:07 +0100	[thread overview]
Message-ID: <47e607ee3184584dea2ab23ca0d517fa44b7076f.camel@gmail.com> (raw)
In-Reply-To: <271383e7dfc7e1beecc0fcebe533f94e9da4d499.camel@planete-kraus.eu>

Am Dienstag, dem 05.12.2023 um 21:55 +0100 schrieb Vivien Kraus:
> Dear guix,
> 
> On the one hand, we have this list of packages:
> https://ftp2.nluug.nl/windowing/gnome/teams/releng/44.6/versions
For the record, we have a new 44 release:
https://ftp2.nluug.nl/windowing/gnome/teams/releng/44.7/versions

I've summarised our TODOs below: Each commented line (preceded by #)
denotes a package that doesn't exist on the gnome-team branch yet.

core:atkmm:2.28.3:
#core:calls:44.2:
core:font-abattis-cantarell:0.303.1:
core:epiphany:44.7:
#core:gnome-logs:43.0:
#core:gnome-software:44.5:
#core:gnome-tour:44.0:

I think we should settle on what to do with the gnome package soon to
not stall the branch even further.  We can already start working
towards GNOME 46 after the merge :)

There is some gnome-adjacent software (particularly extensions, I don't
want all of them to break like they did the last time and the time
before) to have a look at as well before the merge, but it looks like a
nice road ahead.

We can do this!




  parent reply	other threads:[~2024-01-07 16:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 20:55 bug#67651: [gnome-team] What should we do with the "gnome" package? Vivien Kraus via Bug reports for GNU Guix
2023-12-07  7:34 ` Liliana Marie Prikler
2023-12-07 11:25 ` Efraim Flashner
2024-01-07 16:53 ` Liliana Marie Prikler [this message]
2024-01-09 11:10   ` Vivien Kraus via Bug reports for GNU Guix
2024-01-09 19:29     ` Liliana Marie Prikler
2024-02-06 17:04 ` Vivien Kraus via Bug reports for GNU Guix

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=47e607ee3184584dea2ab23ca0d517fa44b7076f.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=67651@debbugs.gnu.org \
    --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.