From: Marius Bakke <mbakke@fastmail.com>
To: ng0 <ng0@pragmatique.xyz>, 27212@debbugs.gnu.org
Subject: bug#27212: 203a9455c4695152fc5d0085bffeead9ce3216c2 broke system boot
Date: Sat, 03 Jun 2017 19:01:10 +0200 [thread overview]
Message-ID: <8737bh0zvt.fsf@fastmail.com> (raw)
In-Reply-To: <20170603165321.iocqorc25mmvjhjf@abyayala>
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
ng0 <ng0@pragmatique.xyz> writes:
> Otherwise perfectly working systems I have *all* break after
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=203a9455c4695152fc5d0085bffeead9ce3216c2
>
> and the last thing they display before guile repl is the
> message in that commit.
>
> Yes, I use labels. No, I don't use complicated setups.
> Please test such changes before applying them in the wild..
> I just hope this happened here and the break is a mistake.
I *just* noticed the same thing. I also tried reverting this commit, but
that just entered a (re)boot loop. Not sure what's up, but two of my
GuixSD systems are affected.
On my way out now, but will investigate more tomorrow. CC Danny in case
of insight (which report by Chris did this address?).
Older generations are fine.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-06-03 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 16:53 bug#27212: 203a9455c4695152fc5d0085bffeead9ce3216c2 broke system boot ng0
2017-06-03 17:01 ` Marius Bakke [this message]
2017-06-03 17:30 ` ng0
2017-06-03 18:00 ` bug#27212: [PATCH] file-systems: Improve error handling in the iso9660 case - fixes boot problem Danny Milosavljevic
2017-06-03 18:25 ` Danny Milosavljevic
2017-06-03 19:45 ` Leo Famulari
2017-06-03 19:57 ` Jelle Licht
2017-06-03 20:11 ` Danny Milosavljevic
2017-06-03 20:12 ` Danny Milosavljevic
2017-06-03 19:38 ` bug#27212: 203a9455c4695152fc5d0085bffeead9ce3216c2 broke system boot jah
2017-06-04 11:14 ` ng0
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=8737bh0zvt.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=27212@debbugs.gnu.org \
--cc=ng0@pragmatique.xyz \
/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).