From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>,
Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Missing dependency for emacs-magit
Date: Fri, 18 Feb 2022 05:51:19 +0100 [thread overview]
Message-ID: <32058b309b3742abf844283d3b49827815279f65.camel@gmail.com> (raw)
In-Reply-To: <f5d36e50-73b1-d755-1d24-321b297caeaa@posteo.de>
Am Freitag, dem 18.02.2022 um 01:10 +0000 schrieb Zelphir Kaltstahl:
> [...]
>
> Since there was some verification thing with the `guix gc --
> verify=contents` command, I will run `guix gc`, delete the whole guix
> profile, recreate the profile, and then check again.
>
> ~~~~
> $ guix gc
> ...
> $ rm -rf ~/.guix-extra-profiles/emacs-test-profile
> ...
> $ guix package --manifest="${GUIX_EXTRA_PROFILES}"/emacs-profile-
> manifest.scm --profile="${GUIX_EXTRA_PROFILES}"/emacs-profile
> ...
> $ /bin/bash /home/user/emacs.sh
> ...
> $ guix package --list-profiles
> /home/user/.guix-extra-profiles/emacs-profile
> /home/user/.config/guix/current
> /home/user/.guix-profile
> ~~~~
>
> (Note, that I have removed the "-test" part of the name. At some
> point I hope for this all to work and then I don't want the "-test"
> thing to still remain.)
> The script contains:
>
> ~~~~
> #!/usr/bin/env bash
>
> set -Eeuxo pipefail
>
> # source the environment
> GUIX_PROFILE="${GUIX_EXTRA_PROFILES}/emacs-profile"
> . "${GUIX_PROFILE}/etc/profile"
>
> # run emacs
> env XMODIFIERS='' emacs
> ~~~~
>
> Anything else I can try?
Note that --verify=contents only prints out the warnings that something
is wrong, but does not fix them. Since repairing the store is
potentially dangerous, you need to --verify=contents,repair as
superuser. I'm not sure if your sequence of commands actually led to
garbage-collection of the damaged magit.
Cheers
next prev parent reply other threads:[~2022-02-18 4:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 23:51 Missing dependency for emacs-magit Zelphir Kaltstahl
2022-02-14 2:50 ` Michael Rohleder
2022-02-14 18:41 ` Zelphir Kaltstahl
2022-02-14 19:33 ` Liliana Marie Prikler
2022-02-15 9:45 ` Zelphir Kaltstahl
2022-02-15 19:54 ` Liliana Marie Prikler
2022-02-16 22:23 ` Zelphir Kaltstahl
2022-02-17 17:49 ` Liliana Marie Prikler
2022-02-17 19:26 ` Ricardo Wurmus
2022-02-18 1:10 ` Zelphir Kaltstahl
2022-02-18 4:51 ` Liliana Marie Prikler [this message]
2022-02-19 2:34 ` Zelphir Kaltstahl
2022-02-19 7:30 ` Liliana Marie Prikler
2022-02-19 15:43 ` Zelphir Kaltstahl
2022-02-19 16:04 ` Liliana Marie Prikler
2022-02-22 9:34 ` Zelphir Kaltstahl
2022-02-22 10:39 ` Liliana Marie Prikler
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=32058b309b3742abf844283d3b49827815279f65.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
--cc=zelphirkaltstahl@posteo.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.