gpg: failed to create temporary file '/var/lib/lurker/.#lk0x57d1b100.hantslug.org.uk.2188': Permission denied
gpg: keyblock resource '/var/lib/lurker/pubring.gpg': Permission denied
gpg: Signature made Sat May 5 10:51:04 2007 BST
gpg: using RSA key ED1319F325A97448
gpg: Can't check signature: No public key
Adrian Bridgett wrote:
> On Fri, May 4, 2007 at 09:41:05 +0100 (+0100), Tony Whitmore wrote:
>> I've ended up changing /bin/sh to point to /bin/bash not /bin/dash as the
>> software, once installed, has a lot of shell scripts that assume /bin/sh
>> points to bash. Rather than editing them all, I changed the symlink. I'm not
>> sure whether this will break anything else though? Any alarm bells?
>
> Scripts that require bash-isms should either be fixed or use
> /bin/bash.
I agree. In this case there are a lot of shell scripts, not just the
installer, that seem to rely on features in bash but specify sh. I could
try and change them all but I might miss one. Changing sh to link to
bash will slow boot times - dash is primarily used because it's faster
at running scripts, especially during boot.
> If they are part of Ubuntu I'd file bugs (I'd be suprised
> if there were many, since Debian probably rooted out most of them some
> time ago).
No, sadly this is evil proprietary software. (ArcServe's Backup Agent
for Linux, if anyone's interested. And it's not very good and certainly
doesn't work properly on any Ubuntu distribution newer than 32-bit Dapper.)
> Can't see anything wrong with your command there - not sure if "echo
> -e" is allowed, but I wouldn't call it a "bad substitution".
Interestingly the init script created by the installer had some rogue
"-e"s in it (just on lines on their own) even when the installer was run
under bash.
I think I'm going to conclude that it's one of the inherent problems
with using proprietary software (especially on Linux) and work out how
to not use it any more.
Tony
