From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Remco van 't Veer <remco@remworks.net>
Cc: 53421@debbugs.gnu.org
Subject: [bug#53421] Acknowledgement ([PATCH 1/1] gnu: sssd: Fix build with samba-4.15.3)
Date: Fri, 21 Jan 2022 22:58:08 +0100 [thread overview]
Message-ID: <877daszr15.fsf@nckx> (raw)
In-Reply-To: <874k5w229i.fsf@remworks.net>
[-- Attachment #1: Type: text/plain, Size: 676 bytes --]
Hullo Remco,
Remco van 't Veer 写道：
> Oeps, #define in config.h.in should be an #undef. Will make a
> v2 and cc
> this issue (not sure what the proper way is).
You have to perform the Ritual Debbugs Dance as documented in the
manual[0].
The bug tracker is very simple and easily confused:
https://issues.guix.gnu.org/53421
https://issues.guix.gnu.org/53422
https://issues.guix.gnu.org/53428
I've merged them all so further action is needed, but please send
further revisions of this patch to 53428@debbugs.gnu.org.
Thanks!
T G-R
[0]:
https://guix.gnu.org/en/manual/devel/en/html_node/Submitting-Patches.html#Submitting-Patches
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-01-21 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 20:47 [bug#53422] [PATCH 0/1] Fix sssd build Remco van 't Veer
2022-01-21 20:47 ` [bug#53421] [PATCH 1/1] gnu: sssd: Fix build with samba-4.15.3 Remco van 't Veer
[not found] ` <handler.53421.B.16427981146461.ack@debbugs.gnu.org>
2022-01-21 21:43 ` [bug#53421] Acknowledgement ([PATCH 1/1] gnu: sssd: Fix build with samba-4.15.3) Remco van 't Veer
2022-01-21 21:58 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2022-01-22 8:30 ` bug#53421: [PATCH 1/1] gnu: sssd: Fix build with samba-4.15.3 Oleg Pykhalov
[not found] ` <handler.53422.B.16427981156468.ack@debbugs.gnu.org>
2022-01-21 21:06 ` bug#53422: Acknowledgement ([PATCH 0/1] Fix sssd build) Remco van 't Veer
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=877daszr15.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=53421@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=remco@remworks.net \
/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.