unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Sent <richard@freakingpenguin.com>
To: 62890@debbugs.gnu.org
Subject: bug#62890: StumpWM with --no-grafts and System/Home mismatches
Date: Fri, 12 Jan 2024 16:02:13 -0500	[thread overview]
Message-ID: <1e0e77cc4d8f9b49c181d8eff6ee2bdd@freakingpenguin.com> (raw)
In-Reply-To: <GV1P193MB23106F1D18FD3516594772CBDF9F9@GV1P193MB2310.EURP193.PROD.OUTLOOK.COM>

I've noticed the same behavior and was able to resolve it by adding 
--no-grafts whenever I reconfigure my system and home profiles. Likely 
just the former is necessary, but I haven't tested it.

I've also noticed this behavior (SBCL trying to place .fasl in 
/gnu/store) once when I pulled, reconfigured system, and didn't 
reconfigure home. I have my setup configured such that StumpWM is 
installed at the system level, while contrib packages are installed via 
guix home.

I ran a git bisect and continually reconfigured my system to try and 
narrow down what commit it was, and was able to isolate it to either an 
xorgproto or Mesa update. Home was built before (49a7a95ba4) the commit, 
System after (d55a4431f3). The offending commit in this particular case 
lies somewhere between d55a4431f3 and 17c3a3bfff. (This probably isn't 
actually a bug, but I'm posting it in case anyone else runs into a 
similar issue in the future.)

If anyone else has a similar setup, encounters this issue, and already 
uses --no-grafts, be sure both the system and home profiles are built 
with the same version of Guix.

Richard Sent




  parent reply	other threads:[~2024-01-12 21:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-16 22:32 bug#62890: StumpWM fails to start - Read only file system Kjartan Óli Águstsson
2023-04-24 12:57 ` Guillaume Le Vaillant
2023-04-25  9:35   ` Guillaume Le Vaillant
2024-01-12 21:02 ` Richard Sent [this message]
2024-05-03  2:30 ` bug#62890: Specific graft that's at fault Richard Sent
2024-05-27  6:54 ` bug#62890: Likely cause found, excess library grafting Richard Sent
2024-05-27  7:05   ` bug#62890: StumpWM fails to start - Read only file system Richard Sent

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=1e0e77cc4d8f9b49c181d8eff6ee2bdd@freakingpenguin.com \
    --to=richard@freakingpenguin.com \
    --cc=62890@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).