Undeclared xbindkeys dependency on Tk

  • Done
  • quality assurance status badge
Details
2 participants
  • mandraker
  • Tobias Geerinckx-Rice
Owner
unassigned
Submitted by
mandraker
Severity
normal
M
M
mandraker wrote on 2 Feb 2021 10:53
(address . bug-guix@gnu.org)
bf457c807a2ea869915ddce215a85ddf@inventati.org
Dear Guix Dev.

$ xbindkeys_show
/home/eric/.guix-profile/bin/xbindkeys_show: line 3: exec: wish: not
found

$ cat /home/eric/.guix-profile/bin/xbindkeys_show
#!/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/sh
# \
exec wish "$0" "$@"
^
| ...
|
|
xbindkeys_show use the package Tk that is not declared

SeeYAAA!
T
T
Tobias Geerinckx-Rice wrote on 2 Feb 2021 18:01
(address . mandraker@inventati.org)
87pn1iv1y4.fsf@nckx
Mandraker,

mandraker@inventati.org ???
Toggle quote (5 lines)
> $ 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.

Toggle quote (2 lines)
> 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]:
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCYBmFYw0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW15DEYA+wdHz7IRx2CHEV0jpa+QvJDzIe74Pqk14T8u7HVu
UdWxAP40QitcIEkSvhX0rkZtUsCub4JLr/peVQLVPrVOSFmGDg==
=8AWV
-----END PGP SIGNATURE-----

?
Your comment

This issue is archived.

To comment on this conversation send an email to 46255@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 46255
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch