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

Dear Guix,

Le dimanche 07 janvier 2024 à 17:53 +0100, Liliana Marie Prikler a
écrit :
> 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:
Oops, I missed that one. Sorry. I checked the list by comparing our
versions to those of the list, but of course, our version of "atkmm" is
reported as 2.36.2, so I did not think further. 

The git log shows various documentation update, build system updates,
and documentation updates between 2.28.1 and 2.28.3.

> #core:calls:44.2:
(as said on IRC, I believe we have Calls already on gnome-team)

> core:font-abattis-cantarell:0.303.1:
I don’t know where this 0.303.1 tag comes from, I can’t see it. It’s
neither a tag nor a gitlab release. There has only been translation
updates for the appstream metadata since our commit.

> core:epiphany:44.7:
We now have it, thank you!

> #core:gnome-logs:43.0:
The day elogind supports the journald API, we will be delighted to have
it (also see https://issues.guix.gnu.org/67338 ).

> #core:gnome-software:44.5:
I thought it was pointless to package it, but see
https://issues.guix.gnu.org/68228 : it is claimed that we can use it to
install flatpaks.

> #core:gnome-tour:44.0:
That’s Rust, unfortunately.

> 
> 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 :)
In my opinion, we should have atkmm:2.28.3, but I see atkmm-2.28 being
used as a propagated-inputs for gtkmm-3, and gtkmm-3 is an input for
inkscape. That’s a world rebuild…

For Cantarell fonts, maybe we should point to the latest commit? That’s
another world rebuild though, and for very little gain as of now.

I’m not sure a flatpak-only gnome software is a hard requirement. It
would be most confusing. Gnome-tour is nice, but I think we can live
without it until we figure out this “rust” stuff.

> 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

You mean, the gnome-shell-extension-* in (gnu packages gnome-xyz)? I
don’t use them (I was told they were frequently broken so I never
bothered to try them!) so I’m not sure I can reliably tell whether they
work correctly.

Best regards,

Vivien


P.S. After a brief period of not being able to send an e-mail, this is
the first I send with my new email-key-rotation-service-type! I hope it
travels safely to your inbox.
https://labo.planete-kraus.eu/email-key-rotation.git/tree/README.org




  reply	other threads:[~2024-01-09 11:11 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
2024-01-09 11:10   ` Vivien Kraus via Bug reports for GNU Guix [this message]
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=12ef074c9aeeb94459a4791ca4d095c368ebdf89.camel@planete-kraus.eu \
    --to=bug-guix@gnu.org \
    --cc=67651@debbugs.gnu.org \
    --cc=liliana.prikler@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.