>
> SaVi 1.4.5-2
>
> I can confirm that the problem related to oogl files IS fixed, but
> still depends on the existence of /vmlinuz or /boot/vmlinuz file to
> start up. If that file MUST exist in a standard Debian installation
> (I'm not sure, think of the multi-kernel systems) I sh
package
severity 633533 important
thanks
On Tue, 12 Jul 2011 08:53:50 +0800
YunQiang Su wrote:
> here, on Debian, the $ARCH is "ubuntu", not "unknown", so it
> *redefine* SAVIBIN.
> > the working directory is /usr/lib/savi. Changing this line to
> > SAVIBIN=${SAVI}/bin/SaVi fix things for me.
>
> Well, I think the bug is in the file /usr/lib/savi/savi, line 71.
> The variable SAVIBIN is set to bin/SaVi which is only correct when
yes, it did, but please note Line 180-181
if [ ! ${ARCH} = "unknown" ]; then
SAVIBIN="${SAVI}/${SAVIBIN}"
here, on Debian, the $ARCH is "ubuntu", not "unknown
On Tue, 12 Jul 2011 03:30:25 +0800
YunQiang Su wrote:
> Could you give me more details about how you start it?
>
> I cannot reproduce it.
>
Two ways:
Alone from the command line:
$~ savi
SaVi: did not attempt to launch a missing binary executable.
please note the home direct
Could you give me more details about how you start it?
I cannot reproduce it.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: savi
Version: 1.4.5-1
Severity: grave
Hi,
When I try to start savi this is what you read:
SaVi: did not attempt to launch a missing binary executable.
After editing /usr/bin/savi and replacing
sh /usr/lib/savi/savi $*
with
cd /usr/lib/savi
sh ./savi $*
6 matches
Mail list logo