all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: me--- via Bug reports for GNU Guix <bug-guix@gnu.org>
To: mandraker@inventati.org
Cc: 46255-done@debbugs.gnu.org, bug-guix@gnu.org
Subject: bug#46255: Undeclared xbindkeys dependency on Tk
Date: Tue, 02 Feb 2021 18:01:23 +0100	[thread overview]
Message-ID: <87pn1iv1y4.fsf@nckx> (raw)
In-Reply-To: <bf457c807a2ea869915ddce215a85ddf@inventati.org>

[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]

Mandraker,

mandraker@inventati.org 写道：
> $ xbindkeys_show
> /home/eric/.guix-profile/bin/xbindkeys_show: line 3: exec: wish: 
> not
> found

Thanks.

This was due to ...unconventional shebang usage upstream:

  #!/bin/sh 
  # \
  exec wish "$0" "$@"

I don't pretend to comprehend why.  I don't see any polyglottal 
cleverness going on below it.

Our built-in ‘patch-shebang’ has no problem patching first one 
(creating a bogus dependency on bash, now gone) but can't see the 
obfuscated wish one.

Fixed[0] by turning it into a proper shebang first.

Please test and report your results; it complains about a missing 
configuration file here.

> xbindkeys_show use the package Tk that is not declared

They do declare it, kind of, in xbindkeys.spec and ./configure 
etc.  And (incidentally) halfway down the ChangeLog file.  Hardly 
obvious, indeed.

Kind regards,

T G-R

[0]: 
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=72fabd8d6ef7fbfd19c1f1ef294b26e3c5a16bbf

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

      reply	other threads:[~2021-02-02 17:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02  9:53 bug#46255: Undeclared xbindkeys dependency on Tk mandraker
2021-02-02 17:01 ` me--- via Bug reports for GNU Guix [this message]

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=87pn1iv1y4.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=46255-done@debbugs.gnu.org \
    --cc=mandraker@inventati.org \
    --cc=me@tobias.gr \
    /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.