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: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: rg@raghavgururajan.name, 67582@debbugs.gnu.org
Subject: [bug#67582] [PATCH gnome-team 1/4] gnu: Add python-meson-python.
Date: Sun, 03 Dec 2023 19:41:46 +0100	[thread overview]
Message-ID: <052a685fe0caba9c77c1a03135a28dc03ab42304.camel@gmail.com> (raw)
In-Reply-To: <87il5f2olx.fsf@gmail.com>

Am Sonntag, dem 03.12.2023 um 12:16 -0500 schrieb Maxim Cournoyer:
> Hi,
> 
> Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> 
> > * gnu/packages/python-xyz.scm (python-meson-python): New variable.
> 
> This should go to gnu/packages/python-build.scm.
It should, but it can't, because there are requirements from python-xyz
and I'm not going to move them around on-the-go.

Cheers




  reply	other threads:[~2023-12-03 18:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-02 10:35 [bug#67582] [PATCH gnome-team 0/4] Update python-dbusmock Liliana Marie Prikler
2023-12-01 20:48 ` [bug#67582] [PATCH gnome-team 4/4] Revert "gnu: sysprof: Do not propagate libadwaita." Liliana Marie Prikler
2023-12-01 23:09 ` [bug#67582] [PATCH gnome-team 2/4] gnu: Add python-dbus-python Liliana Marie Prikler
2023-12-03 17:19   ` Maxim Cournoyer
2023-12-03 18:41     ` Liliana Marie Prikler
2023-12-03 19:06       ` Maxim Cournoyer
2023-12-19 22:54         ` bug#67582: " Liliana Marie Prikler
2023-12-01 23:09 ` [bug#67582] [PATCH gnome-team 3/4] gnu: python-dbusmock: Update to 0.30.0 Liliana Marie Prikler
2023-12-01 23:38 ` [bug#67582] [PATCH gnome-team 1/4] gnu: Add python-meson-python Liliana Marie Prikler
2023-12-03 17:16   ` Maxim Cournoyer
2023-12-03 18:41     ` Liliana Marie Prikler [this message]
2023-12-03 19:04       ` Maxim Cournoyer
2023-12-02 14:18 ` [bug#67582] [PATCH gnome-team 0/4] Update python-dbusmock Vivien Kraus via Guix-patches via

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=052a685fe0caba9c77c1a03135a28dc03ab42304.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=67582@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=rg@raghavgururajan.name \
    /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.