From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Missing dependency for emacs-magit
Date: Tue, 22 Feb 2022 09:34:20 +0000 [thread overview]
Message-ID: <984e38b3-4bb5-87b0-e0c8-f7801c26d35c@posteo.de> (raw)
In-Reply-To: <4b646eec73cdb531b85c168e503cbd776e428b08.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3874 bytes --]
Hello!
On 2/19/22 08:30, Liliana Marie Prikler wrote:
> Hi,
>
> Am Samstag, dem 19.02.2022 um 02:34 +0000 schrieb Zelphir Kaltstahl:
>> So I deleted and built the emacs profile again using `guix package --
>> manifest="${GUIX_EXTRA_PROFILES}"/emacs-profile-manifest.scm --
>> profile="${GUIX_EXTRA_PROFILES}"/emacs-profile`.
>>
>> However, no luck. Still magit cannot be loaded. Still saying that:
>>
>> ~~~~
>> Unable to activate package ‘magit’.
>> Required package ‘git-commit-3.3.0’ is unavailable
>> ~~~~
>>
>> Not sure what else I can try.
>> Best regards,
>> Zelphir
> I think there might be something fundamentally wrong here. On a pretty
> recent git checkout (using pre-inst-env) I can `guix shell -C emacs
> emacs-magit -E TERM -- emacs' and inside the spawned emacs (require
> 'magit) works without any issues.
>
> Cheers
I have now tried again with `guix environment` instead of using profiles. I
faced the same issue as with the profile. As soon as emacs-magit is installed
via guix, I get the error in the `*Messages*` buffer. Then I read about `guix
shell` and learned, that it is to replace `guix environment`. Didn't know that.
Guess I should change my usage. So that is what I did next. Changed the `guix
environment` command in my script to `guix shell`.
It should be reproducible using the following steps, unless guix itself has an
issue and creates non-reproducible environments:
`channels.scm` file at `~/.guix-extra-profiles/emacs-env/channels.scm`:
~~~~
(list (channel
(name 'guix)
(url"https://git.savannah.gnu.org/git/guix.git")
(branch "master")
(commit
"b731d34ed796ad3ca1cfba6e08369ffd6dcb57bf")
(introduction
(make-channel-introduction
"9edb3f66fd807b096b48283debdcddccfea34bad"
(openpgp-fingerprint
"BBB0 2DDF 2CEA F6A8 0D1D E643 A2A0 6DF2 A33A 54FA")))))
~~~~
`manifest.scm` file at `~/.guix-extra-profiles/emacs-env/manifest.scm`:
~~~~
(specifications->manifest
'("emacs"
"emacs-auto-complete"
"emacs-company"
"emacs-dockerfile-mode"
"emacs-editorconfig"
"emacs-erlang"
"emacs-exec-path-from-shell"
"emacs-flycheck"
"emacs-geiser"
"emacs-geiser-guile"
"emacs-geiser-racket"
"emacs-goto-chg"
"emacs-jinja2-mode"
"emacs-json-mode"
"emacs-magit"
"emacs-markdown-mode"
"emacs-moe-theme-el"
"emacs-monokai-theme"
"emacs-multiple-cursors"
"emacs-neotree"
"emacs-ob-async"
"emacs-org"
"emacs-ox-gfm"
"emacs-pkg-info"
"emacs-project"
;; "emacs-python-environment"
"emacs-racket-mode"
"emacs-sml-mode"
"emacs-toml-mode"
;; "emacs-typescript-mode"
"emacs-undo-tree"
"emacs-web-mode"
"emacs-yaml-mode"
"emacs-yasnippet"
"guile"
"guile-colorized"
"guile-fslib"
"guile-json"
"guile-readline"
"racket"))
~~~~
`env.sh` script to run Emacs at `~/.guix-extra-profiles/emacs-env/env.sh`:
~~~~
#!/usr/bin/env bash
set -Eeuxo pipefail
DIR="~/.guix-extra-profiles/emacs-env/"
guix time-machine \
--channels="${DIR}/channels.scm" -- \
shell \
--cores=4 \
--manifest="${DIR}/manifest.scm" -- \
emacs
~~~~
With those in place run:
~~~~
bash ~/.guix-extra-profiles/emacs-env/env.sh
~~~~
However, I have now found out, that the `-C` flag is `--container`, which I am
not using! So I tried to use `--container` with the `guix shell` command and,
what a surprise, the error in Emacs disappeared!
Now of course the question is, how does `--container` affect the `emacs-magit`
package? What is Emacs reading, that affects Magit and even prevents it from
loading the dependency `git-commit`?
If I find out more, I'll let you know.
Best regards and thanks for the patience,
Zelphir
--
repositories:https://notabug.org/ZelphirKaltstahl
[-- Attachment #2: Type: text/html, Size: 4802 bytes --]
next prev parent reply other threads:[~2022-02-22 9:38 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
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 [this message]
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
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=984e38b3-4bb5-87b0-e0c8-f7801c26d35c@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=guix-devel@gnu.org \
--cc=liliana.prikler@gmail.com \
/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).