all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Ada Stevenson <adanskana@gmail.com>
Cc: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>, 70910@debbugs.gnu.org
Subject: bug#70910: xdot has stopped working after update to 1.3
Date: Mon, 13 May 2024 12:18:53 +0200	[thread overview]
Message-ID: <87cypqc8vm.fsf@gnu.org> (raw)
In-Reply-To: <d91ae685-50be-3f3a-324a-dca90e9e5367@gmail.com> (Ada Stevenson's message of "Mon, 13 May 2024 04:44:29 +0000")

Hi Ada,

(Cc: Artyom, who updated xdot in
a47fe0fdc4b13c850da29c0e11ab63d2041534c1.)

Ada Stevenson <adanskana@gmail.com> skribis:

> I was trying to use `xdot` to view to output of `guix graph` (`guix
> graph bash | xdot -`). However, it crashed instantly with the
> following stack trace:
>
>> dot: No such file or directory
>> Traceback (most recent call last):
>>   File
>> "/gnu/store/r9mrqfpci65hsypgm7r5kpzxlm6fcd1l-xdot-1.3/bin/.xdot-real",
>> line 33, in <module>
>>     sys.exit(load_entry_point('xdot==1.3', 'gui_scripts', 'xdot')())

Looks like the problem is that ‘dot’ is not in $PATH in your case.

On my machine, ‘dot’ is in $PATH because I also have it in my profile,
and thus ‘guix graph bash | xdot -’ works fine.

Artyom, I think we should replace the reference to ‘dot’ in the source
with its absolute file name, ‘/gnu/store/…/bin/dot’.  That way xdot
would work whether or not one has installed ‘graphviz’ independently.

Could you take a look?

Thanks,
Ludo’.




  reply	other threads:[~2024-05-13 10:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13  4:44 bug#70910: xdot has stopped working after update to 1.3 Ada Stevenson
2024-05-13 10:18 ` Ludovic Courtès [this message]
2024-05-13 19:08 ` bug#70910: [PATCH] gnu: xdot: Bugfix: Add the directory containing "dot" to the PATH Artyom V. Poptsov
2024-05-14  7:08 ` bug#70910: xdot has stopped working after update to 1.3 Ada Stevenson
2024-05-16 22:25 ` Sharlatan Hellseher

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=87cypqc8vm.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=70910@debbugs.gnu.org \
    --cc=adanskana@gmail.com \
    --cc=poptsov.artyom@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 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.