all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "bdju" via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "bdju" <bdju@tilde.team>, <57762@debbugs.gnu.org>
Subject: bug#57762: dragon-drop package's binary is missing
Date: Wed, 14 Sep 2022 05:05:47 -0500	[thread overview]
Message-ID: <CMW1GA5DE7VN.3HHZL8NIEHO19@masaki> (raw)
In-Reply-To: <CMV95SZMUSHO.12XH2B5FIWBOD@masaki>

On Tue Sep 13, 2022 at 6:55 AM CDT, bdju wrote:
> On Mon Sep 12, 2022 at 10:32 PM CDT, bdju via Bug reports for GNU Guix wrote:
> > After upgrades I no longer have the `dragon` command that is used by the
> > dragon-drop package, making the program unusable. The package is still
> > in my manifest file that I applied, still shows up in a search, and I
> > also tried to manually `guix install` it again. No luck.
> >
> > I use this in a lot of scripts due to gtk file pickers crashing software
> > for me a lot and trying to avoid them. A fix would be very much
> > appreciated.
>
> I found that doing the following:
> find $(guix build dragon-drop)
>
> revealed that `dragon` is inside .../bin/bin instead of just /bin.
> Perhaps this could cause issues with setting the PATH properly.

I did a rollback until dragon worked again, then did a whereis on it
output shows just one bin dir and not two
/gnu/store/njlv1a4b1pvcs42dy0wwgcxr6cx2wf55-profile/bin/dragon


Hopefully this info helps someone figure out the problem.




  reply	other threads:[~2022-09-14 10:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13  3:32 bug#57762: dragon-drop package's binary is missing bdju via Bug reports for GNU Guix
2022-09-13 11:55 ` bdju via Bug reports for GNU Guix
2022-09-14 10:05   ` bdju via Bug reports for GNU Guix [this message]
2022-09-14 14:27   ` arkhan--- via Bug reports for GNU Guix

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=CMW1GA5DE7VN.3HHZL8NIEHO19@masaki \
    --to=bug-guix@gnu.org \
    --cc=57762@debbugs.gnu.org \
    --cc=bdju@tilde.team \
    /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.