Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#17774 - [vim-limp] 0.3.4-4 fails to start
Attached to Project:
Community Packages
Opened by Christian Walther (cptsalek) - Saturday, 09 January 2010, 21:07 GMT
Last edited by Andrea Scarpino (BaSh) - Sunday, 10 January 2010, 02:58 GMT
Opened by Christian Walther (cptsalek) - Saturday, 09 January 2010, 21:07 GMT
Last edited by Andrea Scarpino (BaSh) - Sunday, 10 January 2010, 02:58 GMT
|
DetailsDescription:
Using vimp-limp 0.3.4-4 fails to startup properly. It seems to hang indefinetely. Adding set -x to /usr/bin/lisp.sh reveals, that it's waiting for a temporary file to be filled with additional information: + echo 'screen -t Lisp 0 /usr/local/limp/0.3.4/bin/lisp.sh -c /usr/lib/sbcl/sbcl.core -P /tmp/limp_bridge-screenrc.sNZvK4 -p /tmp/limp_sty_YknrB2' + screen -c /tmp/limp_bridge-screenrc.sNZvK4 -dmS limp_listener-mylisp + '[' '!' -s /tmp/limp_sty_YknrB2 ']' + sleep 1s + '[' '!' -s /tmp/limp_sty_YknrB2 ']' + sleep 1s + '[' '!' -s /tmp/limp_sty_YknrB2 ']' + sleep 1s + '[' '!' -s /tmp/limp_sty_YknrB2 ']' + sleep 1s + '[' '!' -s /tmp/limp_sty_YknrB2 ']' + sleep 1s The problem is in the first line of the output: /usr/bin/lisp.sh starts itself inside a screen session, but uses the wrong path /usr/local/limp/0.3.4. This is defined in line 20 of /usr/bin/lisp.sh: LIMPDIR=${LIMPRUNTIME:-/usr/local/limp/$VERSION} The easiest solution would be to change the line to: LIMPDIR=${LIMPRUNTIME:-/usr} /usr/local/limp doesn't make any sense in ArchLinux anyway, since /usr/local isn't used. IMO it would be easier to use $0 in the script anyway, because it would just use the script in the location that was used to launch it in the first place (/usr/bin that is). I guess this would be something to discuss upstream, though. Steps to reproduce: Install vim-limp, run it... |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Sunday, 10 January 2010, 02:58 GMT
Reason for closing: Not a bug
Additional comments about closing: we do not support AUR package
Sunday, 10 January 2010, 02:58 GMT
Reason for closing: Not a bug
Additional comments about closing: we do not support AUR package