From: Maxime Devos <maximedevos@telenet.be>
To: Thiago Jung Bauermann <bauermann@kolabnow.com>
Cc: 56005@debbugs.gnu.org, control@debbugs.gnu.org
Subject: bug#56005: during substitution: write_wait_fd: unimplemented
Date: Tue, 19 Jul 2022 21:50:19 +0200 [thread overview]
Message-ID: <0a1b9cd5-8721-0bde-d20b-389db9b1440d@telenet.be> (raw)
In-Reply-To: <8735f1vi9o.fsf@kolabnow.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 608 bytes --]
reopen 56005
thanks
(not sure if this works because I haven't set up plain-text instead of
HTML yet ...)
On 16-07-2022 05:34, Thiago Jung Bauermann wrote:
> Hello,
>
> This bug was closed, but I couldn't find what was the resolution of the
> problem. Could someone please clarify, for my own education and also so
> that it gets documented in the bug report?
No reason was given at all for closing (normally it says "solved in
commit ..." or "cannot reproduce" or such ...) , so I'd assume that the
wrong bug number was targetted? Tentatively reopening ...
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-07-19 19:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 2:40 bug#56005: exception while downloading substitutes Thiago Jung Bauermann via Bug reports for GNU Guix
2022-06-16 7:58 ` bug#56005: "write_wait_fd: unimplemented" during " Maxime Devos
2022-06-30 11:48 ` bug#56005: In procedure write_wait_fd: unimplemented Attila Lendvai
2022-06-30 11:51 ` bug#56005: during substitution: " Maxime Devos
2022-06-30 11:55 ` Maxime Devos
2022-06-30 11:56 ` Maxime Devos
2022-07-16 3:34 ` Thiago Jung Bauermann via Bug reports for GNU Guix
2022-07-19 19:50 ` Maxime Devos [this message]
2023-04-23 22:27 ` bug#56005: Nathan Dehnel
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=0a1b9cd5-8721-0bde-d20b-389db9b1440d@telenet.be \
--to=maximedevos@telenet.be \
--cc=56005@debbugs.gnu.org \
--cc=bauermann@kolabnow.com \
--cc=control@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).