From: Martin via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Jelle Licht" <jlicht@fsfe.org>,
"Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: 47007@debbugs.gnu.org
Subject: bug#47007: dcb640f02b broke guix environment --container
Date: Tue, 9 Mar 2021 18:26:10 +0000 [thread overview]
Message-ID: <a4bf75ce-e0f3-c026-cafa-db5e4d042fe1@disroot.org> (raw)
In-Reply-To: <867dmgfrlv.fsf@fsfe.org>
Hello,
On 3/9/21 12:18 PM, Jelle Licht wrote:
> FWIW, I only have this issue on Guix System: on my Ubuntu 20.04.2 things
> JustWork(tm)
>
> Thanks for taking a look,
> - Jelle
>
I can confirm similar issues on my Guix Systems from below:
canonical file name: /gnu/store/70rfnrwxxwmipvnfxg54bwyz5rkkl4ps-system
label: GNU with Linux-Libre 5.11.4
configuration file:
/gnu/store/pl31mxphv6hx36ab07j7i1wnv0l4pqp5-configuration.scm
canonical file name: /gnu/store/8cny9lkvclz1wb06rvz6gywlb9nqqb7r-system
label: GNU with Linux-Libre 5.11.3
configuration file:
/gnu/store/pl31mxphv6hx36ab07j7i1wnv0l4pqp5-configuration.scm
However the Guix System on the same hardware with the same basic
configuration but using linux-libre-LTS JustWork(tm) fine:
canonical file name: /gnu/store/p18smv0h2yygdhnc4gxhzjkck9hasmf3-system
label: GNU with Linux-Libre 5.10.13
configuration file:
/gnu/store/pl31mxphv6hx36ab07j7i1wnv0l4pqp5-configuration.scm
Kind regards!
Martin
prev parent reply other threads:[~2021-03-09 21:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 13:34 bug#47007: dcb640f02b broke guix environment --container Jelle Licht
2021-03-09 11:10 ` Ludovic Courtès
2021-03-09 12:18 ` Jelle Licht
2021-03-09 16:17 ` Ludovic Courtès
2021-03-09 21:00 ` Ludovic Courtès
2021-03-09 21:30 ` Andreas Enge
2021-03-10 9:52 ` Jelle Licht
2021-03-09 21:05 ` Andreas Enge
2021-03-10 11:25 ` Ludovic Courtès
2021-03-10 12:27 ` Andreas Enge
2021-03-10 22:24 ` Ludovic Courtès
2021-03-09 18:26 ` Martin via Bug reports for GNU Guix [this message]
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=a4bf75ce-e0f3-c026-cafa-db5e4d042fe1@disroot.org \
--to=bug-guix@gnu.org \
--cc=47007@debbugs.gnu.org \
--cc=jlicht@fsfe.org \
--cc=ludovic.courtes@inria.fr \
--cc=smartin@disroot.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 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.