Hi Steffen! Please do not top post: http://en.wikipedia.org/wiki/Top_posting (yes, I know I am a maniac).
On Thu, 19 Mar 2009 19:57:01 +0100, Steffen Moeller wrote:
> attached the two patches that I consider to address the issues - the
> push of mine before pushed the wrong bits ... one should not Push when
> what one should do is Rush.
Do not worry, since this is something you understand only after you make
the first error, welcome on board :-D
> Luca? The data.tar.gz must be some remnant of an earlier aborted
> installation of some sort.
Exactly: in my case the first installation gave the tar error, then I
removed /usr/local/bin/tar and restarted the installation, which gave
the ar error.
However, since GNU ar by default overwrite existing FILES, I would like
to understand if busybox is at fault here (IIRC busybox behavior should
be the same as non-stripped versions). In such a case, we should be
aware that any workaround must be *temporary*.
> If you don't have other ideas, e.g. an exit 1 added to the ( )s upon
> failure, then I would perform analogously for the other invocations of
> (cd /tmp ; ar) .
[...]
> * already existing / left over data.tar.gz file is removed
I agree on this (temporary) solution: however, I will not care about
advising the user of that, since we are working with our proper files
and more precisely stored in /tmp, which is there for such a use.
> * ( )s removed so an error will not remain unnoticed
`man bash`:
Compound Commands
A compound command is one of the following:
(list)
list is executed in a subshell environment (see COMMAND
EXECUTION ENVIRONMENT below). Variable assignments and
builtin commands that affect the shell's environment do
not remain in effect after the command completes. The
return status is the exit status of list.
If I read it correctly, the exit status should be an error, since the
second part of the list gives an error, and thus the script should exits
with the same error ans the list one. However, this is not the case,
thus my understanding of the above is wrong.
Here is an example that explains the above words:
=====
l...@gismo:~$ cat test-parenthesis.sh
#!/bin/sh
set -e
( cd /tmp && $USER )
echo "exit status after the parenthesis: $?"
cd /tmp && $USER
echo "exit status without the parenthesis: $?"
l...@gismo:~$ ./test-parenthesis.sh
./test-parenthesis.sh: line 5: luca: command not found
exit status after the parenthesis: 127
./test-parenthesis.sh: line 8: luca: command not found
l...@gismo:~$ echo $?
127
l...@gismo:~$
=====
Since we get the expected bevahior without the parenthesis, I would
suggest to simply remove them ;-)
Thx, bye,
Gismo / Luca
pgpGFtP81MFTl.pgp
Description: PGP signature
_______________________________________________ pkg-fso-maint mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-fso-maint
