unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Sat, 19 Feb 2022 17:04:45 +0100	[thread overview]
Message-ID: <2cef25951227410fe7412ac320498aac1a93eead.camel@gmail.com> (raw)
In-Reply-To: <9aca6d8a-1a73-71be-fbd0-5105d572d1b4@posteo.de>

Hi,

Am Samstag, dem 19.02.2022 um 15:43 +0000 schrieb Zelphir Kaltstahl:
> [...]
> Given that I did the guix pull yesterday/today and that the store
> inconsistencies disappeared with that, I have to assume the
> following:
> 
> (1) Either my guix installation is broken somehow, although I never
> messed around in the store and only have quite basic usage using
> environments and profiles (actually haven't touched profiles in a
> while and this is the first time in a long time that I have thought I
> should make a profile for something, instead of merely an
> environment), or (2) the command `guix shell -C emacs
> emacs-magit -E TERM -- emacs` does something different, than the
> command, which I use to make a profile and that therefore the results
> are different.
> 
> If (1) is the case, then I guess there has to be a bug somewhere in
> guix package manager, which messed things up, since I only use very
> few basic commands of guix to install packages, use environments and
> profiles. It's not like I go into the store and mess around in the
> folders ^^'
> 
> If (2) is the case, then I am simply not knowledgeable about guix to
> say what that difference might be.
Note that your profile is a normal directory.  You can ls the files and
everything, so you should be able to find out whether git-commit.el is
broken or any other file is broken, and you should also be able to diff
one version of magit against another.

> I am not sure I really want to somehow remove guix and then reinstall
> it again, because everything else seems to work just fine.
> 
> Not sure what to do now. I might have to abandon the project of
> getting reproducible emacs setup using guix again, or simply cannot
> use guix' profile functionality for that.
I'm not sure if Emacs itself is fully reproducible (there has been a
bug in its build IIRC), but I doubt that this is the change you're
seeing.  Note that Guix is not fully resilient against power outages
(despite what John said in his presentation); I personally had empty
files after power outages on two separate machines, which I do
attribute to the file system/disk rather than Guix however.

Cheers.


  reply	other threads:[~2022-02-19 16:12 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 [this message]
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

  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=2cef25951227410fe7412ac320498aac1a93eead.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 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).