From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: Mathieu Othacehe <othacehe@gnu.org>, 59784@debbugs.gnu.org
Subject: bug#59784: [version 1.4.0rc1] Retrying a failed install fails
Date: Sat, 17 Dec 2022 12:01:36 +0100 [thread overview]
Message-ID: <87k02qi99r.fsf@gnu.org> (raw)
In-Reply-To: <871qoz855e.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Fri, 16 Dec 2022 21:28:29 +0100")
Moin!
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>> One finding: when hitting C-c, the dynamic-wind exit handler (the one
>> that restores the database and umounts the cow store) is *not* executed.
>
> Impressive findings.
>
> Now that you found the dynamic-wind’s out-guard does not even run:
It does not run on C-c, but it does run in other cases, typically if you
just press Enter after reading the message that says “command failed,
press Enter”.
I don’t see how to address the C-c issue so we’ll have to live with it.
Longer-term we may have to find a different strategy than the
‘call-with-mnt-container’ trick, but that’s difficult.
> After seeing that you opened a bug#60116 on setsid(), I tested removing
> the setsid call and it had no effect, but if the dynamic-wind’s
> out-guard does not even run, that is to be expected.
Right; #60116 is related, and it’s not great but it’s not critical.
Ludo’.
next prev parent reply other threads:[~2022-12-17 11:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 17:52 bug#59784: [version 1.4.0rc1] Retrying a failed install fails pelzflorian (Florian Pelz)
2022-12-09 9:42 ` Ludovic Courtès
2022-12-09 11:11 ` Ludovic Courtès
2022-12-10 8:39 ` pelzflorian (Florian Pelz)
2022-12-13 9:40 ` Ludovic Courtès
2022-12-13 9:48 ` Ludovic Courtès
2022-12-13 22:22 ` pelzflorian (Florian Pelz)
2022-12-13 23:16 ` Ludovic Courtès
2022-12-14 13:36 ` pelzflorian (Florian Pelz)
2022-12-14 21:47 ` pelzflorian (Florian Pelz)
2022-12-14 23:50 ` Ludovic Courtès
2022-12-15 17:46 ` pelzflorian (Florian Pelz)
2022-12-15 20:44 ` pelzflorian (Florian Pelz)
2022-12-16 16:57 ` Ludovic Courtès
2022-12-16 20:28 ` pelzflorian (Florian Pelz)
2022-12-17 11:01 ` Ludovic Courtès [this message]
2022-12-17 19:36 ` pelzflorian (Florian Pelz)
2022-12-17 16:15 ` Ludovic Courtès
2022-12-17 19:27 ` pelzflorian (Florian Pelz)
2022-12-17 21:30 ` Ludovic Courtès
2022-12-18 0:23 ` Ludovic Courtès
2022-12-16 13:55 ` Maxime Devos
2022-12-16 20:17 ` pelzflorian (Florian Pelz)
2022-12-18 16:41 ` pelzflorian (Florian Pelz)
2022-12-12 12:07 ` pelzflorian (Florian Pelz)
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=87k02qi99r.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=59784@debbugs.gnu.org \
--cc=othacehe@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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.