all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jacob MacDonald <jaccarmac@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix@gnu.org
Subject: Re: Strange behavior around guix package --show
Date: Sat, 21 Dec 2019 15:55:01 -0800	[thread overview]
Message-ID: <CACy6W0C1B+_uOjMHhwdSJGqE+nZFsxYAfiEdybfCF=pk89YGXA@mail.gmail.com> (raw)
In-Reply-To: <87eewxq3lh.fsf@ambrevar.xyz>

Thanks, I'll have to pull down the most recent build when I'm on a more
robust connection. After some more log-reading I think I've narrowed the
problem down, though I'm not sure what the cause is. The root profile and
my user profile are unique (this is probably trivial and intended), but
share all links except one: lib/guix. They each link to a different version
of $HASH-guix-package-cache/lib/guix. Not sure why this happened or what
the impact is, but my best guess at the behavior has to do with that fact,
since according to strace both invocations are reading from the same
compiled .go files. The successful one just reads lisp-xyz much later than
the failing call.

Jacob.

On Sat, Dec 21, 2019 at 4:13 AM Pierre Neidhardt <mail@ambrevar.xyz> wrote:

> Hi,
>
> I don't have an answer, but for what it's worth I've recently moved
> uglify-js to a different module.  This probably has to do with your issue.
>
> --
> Pierre Neidhardt
> https://ambrevar.xyz/
>

  reply	other threads:[~2019-12-21 23:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20 21:21 Strange behavior around guix package --show Jacob MacDonald
2019-12-21 12:12 ` Pierre Neidhardt
2019-12-21 23:55   ` Jacob MacDonald [this message]
2019-12-27  7:28     ` Jacob MacDonald
2019-12-30 16:45       ` Pierre Neidhardt
2019-12-30 16:52         ` Pierre Neidhardt
2020-01-03 13:31           ` Pierre Neidhardt
2020-01-03 14:17             ` Pierre Neidhardt
2020-01-05  8:02               ` Jacob MacDonald
2019-12-30 22:32         ` Ricardo Wurmus
2019-12-30 22:29 ` Ricardo Wurmus
2019-12-31  2:54   ` Jacob MacDonald

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='CACy6W0C1B+_uOjMHhwdSJGqE+nZFsxYAfiEdybfCF=pk89YGXA@mail.gmail.com' \
    --to=jaccarmac@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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.