From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 49475-done@debbugs.gnu.org, 57583@debbugs.gnu.org,
Josselin Poiret <dev@jpoiret.xyz>,
jackhill@jackhill.us, Yusuf Talha <yusuftalha@tuta.io>
Subject: bug#57583: Guix cannot resume after hibernation
Date: Mon, 05 Sep 2022 15:05:16 +0200 [thread overview]
Message-ID: <87wnaiezj2.fsf@nckx> (raw)
In-Reply-To: <87h71m3rx1.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 644 bytes --]
Jack, Yusuf, Ludo',
Yusuf: you could try pulling, reconfiguring, hibernating, and
resuming, if you're brave-ish.
Ludovic Courtès 写道：
> I believe this is fixed by this: […] The patch in question fell
> through the cracks
It should and it had, sorry.
I *dislike* the fact that this makes the resume path no longer
trivially obviously correct — because we now actually do something
potentially useful (and hence, dangerous) during it — but that's
unavoidable I suppose. It's certainly not the fault of this
patch.
Pushed as ec16f88522041dc285a35705ff9ee95672b78143, thanks Jack!
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-09-05 13:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-04 16:37 bug#57583: Guix cannot resume after hibernation Yusuf Talha via Bug reports for GNU Guix
2022-09-04 17:19 ` Josselin Poiret via Bug reports for GNU Guix
2022-09-05 12:38 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-09-05 12:51 ` Ludovic Courtès
2022-09-05 13:05 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2022-12-10 1:11 ` Mekeor Melire
2022-09-05 12:13 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-09-06 2:23 ` bug#57583: Yusuf Talha via Bug reports for GNU Guix
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=87wnaiezj2.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=49475-done@debbugs.gnu.org \
--cc=57583@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=jackhill@jackhill.us \
--cc=ludo@gnu.org \
--cc=me@tobias.gr \
--cc=yusuftalha@tuta.io \
/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.