----- Original Message -----
From: "BARÉ Willy SPRL" <barewillys...@scarlet.be>
To: <lilypond-user@gnu.org>
Sent: Tuesday, June 28, 2011 8:18 AM
Subject: sh install (continue Friedrich Fischer's ost by march-april 2011)
Hi,
I got the same results as Friedrich Fischer using a fresh install of Puppy
Linux
(i.e. DPup Squeezed 4.99 which is one of the last release of Puppy Linux ;
and also tried on Puppy 4.20 which has been released about 2009 - kernel
is k.2.6.25.16).
results:
--------------------------------------------------------------
# md5sum lilypond-2.14.1-1.linux-x86.sh
abc90d22222a6d8c1a7132a1b23fc0e3 lilypond-2.14.1-1.linux-x86.sh
# sh lilypond-2.14.1-1.linux-x86.sh
lilypond installer for version 2.14.1 release 1,
i686 build.
For a list of options, ...
...
Making /usr/local/lilypond
Creating script /usr/local/bin/lilypond
Creating script /usr/local/bin/lilypond-wrapper.python
Creating script /usr/local/bin/lilypond-wrapper.guile
Creating script /usr/local/bin/uninstall-lilypond
Untarring lilypond-2.14.1-1.linux-x86.sh
bzip2: (stdin) is not a bzip2 file.
tar: Child died with signal 13
tar: Error is not recoverable: exiting now
To uninstall lilypond, run ...
--------------------------------------------------------------
The used version of bunzip2 is 1.0.5
I also used its 1.0.6 version whith the same error message.
Continuing investigation doing:
--------------------------------------------------------------
# sh lilypond-2.14.1-1.linux-x86.sh --tarball
lilypond installer for version 2.14.1 release 1,
i686 build.
For a list of options, abort (^C) then do:
sh lilypond-2.14.1-1.linux-x86.sh --help
extracting lilypond-2.14.1-1.linux-x86.tar.bz2
# tar --bzip2 -xvf lilypond-2.14.1-1.linux-x86.tar.bz2
bzip2: (stdin) is not a bzip2 file.
tar: Child returned status 2
tar: Error is not recoverable: exiting now
#
--------------------------------------------------------------
Also tried opening the tar.bz2 with Xarchiver: not any file is displayed
Conclusions:
version lilypond-2.13.41.1.linux-x86.sh does install nicely !
but the next 2.13.42 do not; and the last unstable 2.15.2 neither do.
Any idea to fix that?
Thanks for any answer, Charlie
I have entered this into the tracker as
http://code.google.com/p/lilypond/issues/detail?id=1731
--
Phil Holmes
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
