unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Mája Tomášek" <maya.tomasek@disroot.org>
Cc: Alexandros Theodotou <alex@zrythm.org>, 61423@debbugs.gnu.org
Subject: [bug#61423] [PATCH 0/6] gnu: zrythm: Update to 1.0.0-beta.4.5.62
Date: Fri, 03 Mar 2023 11:54:19 +0100	[thread overview]
Message-ID: <87lekexfz8.fsf@gnu.org> (raw)
In-Reply-To: <874jr5vdnt.fsf@disroot.org> ("Mája Tomášek"'s message of "Tue, 28 Feb 2023 19:38:14 +0100")

Hi Mája,

Mája Tomášek <maya.tomasek@disroot.org> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
> Hi Ludo',
>
>> Hi Maya,
>>
>> Could you look into the suggestions Alexandros made (I agree regarding
>> Carla) and send a v2 of the patch series?
>
> Certainly! Should I open it as another patch? I am not certain how these
> things work.

You don’t need to open a new bug.

Instead, create the messages with:

  git format-patch --subject-prefix="PATCH v2" …

and send them all to 61423@debbugs.gnu.org.

> From Antero Mejr (the previous person to update the package):
>> (module-ref (resolve-interface ... 'libbacktrace)
>> was a quick workaround to avoid an cyclical import. It's not ideal and
>> I'm not sure if the maintainers would find it to be acceptable.
>
> Is that line fine? Or should I find some other fix?

No it’s not fine, it should be treated like other packages.

If that causes problem, then we’ll see, but it shouldn’t.

Thanks,
Ludo’.




      reply	other threads:[~2023-03-03 10:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-11 10:35 [bug#61423] [PATCH 0/6] gnu: zrythm: Update to 1.0.0-beta.4.5.62 Maya Tomasek via Guix-patches via
2023-02-11 10:35 ` [bug#61424] [PATCH 1/6] gnu: zrythm: Update to 1.0.0-beta.4.5.1 Maya Tomasek via Guix-patches via
2023-02-11 10:48   ` bug#61424: Closing this as this was a misstake guix-patches--- via
2023-02-11 10:35 ` [bug#61427] [PATCH 2/6] gnu: Add libpanel Maya Tomasek via Guix-patches via
2023-02-11 10:50   ` bug#61427: Closing this as this was a mistake guix-patches--- via
2023-02-11 10:35 ` [bug#61426] [PATCH 3/6] gnu: Add zix Maya Tomasek via Guix-patches via
2023-02-11 10:51   ` bug#61426: Closing this as this was a mistake guix-patches--- via
2023-02-11 10:35 ` [bug#61425] [PATCH 4/6] gnu: carla: Update to 2.6.0 pre-release Maya Tomasek via Guix-patches via
2023-02-11 10:51   ` bug#61425: Closing this as this was a mistake guix-patches--- via
2023-02-11 10:35 ` [bug#61428] [PATCH 5/6] gnu: libaudec: Update to 0.3.4 Maya Tomasek via Guix-patches via
2023-02-11 10:52   ` bug#61428: guix-patches--- via
2023-02-11 10:35 ` [bug#61429] [PATCH 6/6] gnu: zrythm: Update to 1.0.0-beta.4.5.62 Maya Tomasek via Guix-patches via
2023-02-11 10:56   ` bug#61429: Closing this as this was a mistake guix-patches--- via
2023-02-11 11:00 ` [bug#61423] [PATCH 1/6] gnu: zrythm: Update to 1.0.0-beta.4.5.1 Maya Tomasek via Guix-patches via
2023-02-11 11:00   ` [bug#61423] [PATCH 2/6] gnu: Add libpanel Maya Tomasek via Guix-patches via
2023-02-11 11:00   ` [bug#61423] [PATCH 3/6] gnu: Add zix Maya Tomasek via Guix-patches via
2023-02-11 11:00   ` [bug#61423] [PATCH 4/6] gnu: carla: Update to 2.6.0 pre-release Maya Tomasek via Guix-patches via
2023-02-11 11:00   ` [bug#61423] [PATCH 5/6] gnu: libaudec: Update to 0.3.4 Maya Tomasek via Guix-patches via
2023-02-11 11:00   ` [bug#61423] [PATCH 6/6] gnu: zrythm: Update to 1.0.0-beta.4.5.62 Maya Tomasek via Guix-patches via
2023-02-24 23:11 ` [bug#61423] [PATCH 0/6] " Alexandros Theodotou
2023-02-27 14:44   ` Ludovic Courtès
2023-02-28 18:38     ` guix-patches--- via
2023-03-03 10:54       ` Ludovic Courtès [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=87lekexfz8.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=61423@debbugs.gnu.org \
    --cc=alex@zrythm.org \
    --cc=maya.tomasek@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).