Posted by Graham Stratton Tue, 08 Aug 2006 00:33:23 GMT
After discovering that the error message in my last post was apparently due to a gcc bug (in debian stable?!?), I decided to have another go. For some reason gem install fcgi worked without installing anything else new. Then I just had to change the apache config file slightly and fiddle with permissions of lots of log files, and fix a bug in typo, and now I have fcgi working again.
Posted by Graham Stratton Wed, 02 Aug 2006 20:02:17 GMT
After the complexity of trying to get mod_fcgid to install last time, I’m giving up and just using cgi this time.
I tried what I did last time, but
gem install fcgi
failed with
checking for FCGX_Accept() in -lfcgi… no
I found someone who claimed to have a setup working, by compiling fcgi from fastcgi.com for themselves, but when I tried the compiler spewed this one:
multiple definition of `__i686.get_pc_thunk.bx’
I really don’t know why it’s so hard. Surely apache2 on debian must be one of the more common deployment platforms?
Posted by Graham Stratton Wed, 03 May 2006 14:07:00 GMT
After upgrading X to x.org 7.0, I found that some fonts which had previously been anti-aliased were no longer.
By running ‘dpkg-reconfigure fontconfig-config’ I restored my display to its former glory. Now all I need to do is to get suspend to work, and I won’t need a Mac.
Posted by Graham Stratton Fri, 10 Feb 2006 14:53:00 GMT
I just installed kanotix 2005-4, but when I came to install some new packages, I got a warning saying that the packages cannot be authenticated.
A bit of googling suggested that I needed to update the debian keys. This should easily be done with ‘apt-key update’, but that returned an error saying:
ERROR: Can’t find the archive-keyring Is the debian-keyring package installed?
I installed the package, but the error remained. It seems this is a bug in debian. Changing
ARCHIVE_KEYRING=/usr/share/keyrings/debian-keyring.gpg
to
ARCHIVE_KEYRING=/usr/share/keyrings/debian-archive-keyring.gpg
in /usr/bin/apt-key line 12
allowed me to run ‘apt-key update’, which downloaded 903 keys but then hung. But apt-get update still reported
E: Some packages could not be authenticated
and apt-get install still gave the error
The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 010908312D230C5F
gpg—keyserver wwwkeys.eu.pgp.net—recv-keys 2D230C5F
fetches the relevant key successfully.
It should then be possible to it them to the keychain with
gpg—armor—export 2D230C5F | apt-key add -
but that command returns
gpg: no writable keyring found: eof gpg: error reading `-’: general error gpg: import from `-’ failed: general error
Eventually I realised that this is an environment issue. If I ran these commands as root instead of using sudo, the keys can be added.
