From: edk@beaver-labs.com
To: 48059@debbugs.gnu.org
Subject: [bug#48059] Acknowledgement ([PATCH] gnu: python-libtmux: Fix build by removing tests broken by tmux update)
Date: Fri, 28 May 2021 09:38:50 +0200 [thread overview]
Message-ID: <87a6ofb94l.fsf@rdklein.fr> (raw)
In-Reply-To: <handler.48059.B.161952974722963.ack@debbugs.gnu.org>
Sorry to be a bother, but could we please merge this ? We depend on this
package and we have to use guix time machine because it is broken. We
would very much like to enjoy the new 1.3 features.
Thanks in advance,
Cheers,
Edouard.
GNU bug Tracking System writes:
> Thank you for filing a new bug report with debbugs.gnu.org.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
> guix-patches@gnu.org
>
> If you wish to submit further information on this problem, please
> send it to 48059@debbugs.gnu.org.
>
> Please do not send mail to help-debbugs@gnu.org unless you wish
> to report a problem with the Bug-tracking system.
next prev parent reply other threads:[~2021-05-28 7:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 13:20 [bug#48059] [PATCH] gnu: python-libtmux: Fix build by removing tests broken by tmux update Edouard Klein
2021-04-27 13:39 ` Tobias Geerinckx-Rice via Guix-patches via
2021-04-27 16:24 ` Edouard Klein
2021-04-27 13:43 ` Tobias Geerinckx-Rice via Guix-patches via
2021-04-27 16:26 ` Edouard Klein
[not found] ` <handler.48059.B.161952974722963.ack@debbugs.gnu.org>
2021-05-28 7:38 ` edk [this message]
2021-05-28 7:56 ` [bug#48059] Acknowledgement ([PATCH] gnu: python-libtmux: Fix build by removing tests broken by tmux update) Maxime Devos
2021-05-28 16:17 ` Edouard Klein
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=87a6ofb94l.fsf@rdklein.fr \
--to=edk@beaver-labs.com \
--cc=48059@debbugs.gnu.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).