<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Straight Ornamental: Category Debian</title>
    <link>http://grahamstratton.org/blog/public/articles/category/debian</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Ramblings from a rambler</description>
    <item>
      <title>More fcgi</title>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <pubDate>Tue, 08 Aug 2006 00:33:23 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:3634a4ea-080e-46c0-8def-6514173249e9</guid>
      <author>Graham Stratton</author>
      <link>http://grahamstratton.org/blog/public/articles/2006/08/08/more-fcgi</link>
      <category>Rails</category>
      <category>Debian</category>
    </item>
    <item>
      <title>No more fcgi</title>
      <description>&lt;p&gt;After the complexity of trying to get mod_fcgid to install last time, I&amp;#8217;m giving up and just using cgi this time.&lt;/p&gt;


	&lt;p&gt;I tried what I did last time, but&lt;/p&gt;


	&lt;p&gt;gem install fcgi&lt;/p&gt;


	&lt;p&gt;failed with&lt;/p&gt;


	&lt;p&gt;checking for &lt;span class="caps"&gt;FCGX&lt;/span&gt;_Accept() in -lfcgi&amp;#8230; no&lt;/p&gt;


	&lt;p&gt;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:&lt;/p&gt;


	&lt;p&gt;multiple definition of `__i686.get_pc_thunk.bx&amp;#8217;&lt;/p&gt;


	&lt;p&gt;I really don&amp;#8217;t know why it&amp;#8217;s so hard.  Surely apache2 on debian must be one of the more common deployment platforms?&lt;/p&gt;</description>
      <pubDate>Wed, 02 Aug 2006 20:02:17 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:7076f94b-82f3-49fa-804a-2046fd1d0de4</guid>
      <author>Graham Stratton</author>
      <link>http://grahamstratton.org/blog/public/articles/2006/08/02/no-more-fcgi</link>
      <category>Rails</category>
      <category>Debian</category>
    </item>
    <item>
      <title>Fixing fonts</title>
      <description>&lt;p&gt;After upgrading X to x.org 7.0, I found that some fonts which had previously been anti-aliased were no longer.&lt;/p&gt;


	&lt;p&gt;By running &amp;#8216;dpkg-reconfigure fontconfig-config&amp;#8217; I restored my display to its former glory.  Now all I need to do is to get suspend to work, and I won&amp;#8217;t need a Mac.&lt;/p&gt;</description>
      <pubDate>Wed, 03 May 2006 14:07:00 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:c37e4c9430d717b76ca7cd87638c6052</guid>
      <author>Graham Stratton</author>
      <link>http://grahamstratton.org/blog/public/articles/2006/05/03/fising-fonts</link>
      <category>Debian</category>
      <category>Linux</category>
    </item>
    <item>
      <title>debian keys</title>
      <description>&lt;p&gt;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.&lt;/p&gt;


	&lt;p&gt;A bit of googling suggested that I needed to update the debian keys.  This should easily be done with &amp;#8216;apt-key update&amp;#8217;, but that returned an error saying:&lt;/p&gt;


	&lt;p&gt;&lt;span class="caps"&gt;ERROR&lt;/span&gt;: Can&amp;#8217;t find the archive-keyring
Is the debian-keyring package installed?&lt;/p&gt;


	&lt;p&gt;I installed the package, but the error remained.  It seems this is a bug in debian.  Changing&lt;/p&gt;


	&lt;p&gt;&lt;span class="caps"&gt;ARCHIVE&lt;/span&gt;_KEYRING=/usr/share/keyrings/debian-keyring.gpg&lt;/p&gt;


	&lt;p&gt;to&lt;/p&gt;


	&lt;p&gt;&lt;span class="caps"&gt;ARCHIVE&lt;/span&gt;_KEYRING=/usr/share/keyrings/debian-archive-keyring.gpg&lt;/p&gt;


	&lt;p&gt;in /usr/bin/apt-key line 12&lt;/p&gt;


	&lt;p&gt;allowed me to run &amp;#8216;apt-key update&amp;#8217;, which downloaded 903 keys but then hung.  But apt-get update still reported&lt;/p&gt;


	&lt;p&gt;E: Some packages could not be authenticated&lt;/p&gt;


	&lt;p&gt;and apt-get install still gave the error&lt;/p&gt;


	&lt;p&gt;The following signatures couldn&amp;#8217;t be verified because the public key is not available: NO_PUBKEY 010908312D230C5F&lt;/p&gt;


	&lt;p&gt;gpg&amp;#8212;keyserver wwwkeys.eu.pgp.net&amp;#8212;recv-keys 2D230C5F&lt;/p&gt;


	&lt;p&gt;fetches the relevant key successfully.&lt;/p&gt;


	&lt;p&gt;It should then be possible to it them to the keychain with&lt;/p&gt;


	&lt;p&gt;gpg&amp;#8212;armor&amp;#8212;export 2D230C5F | apt-key add -&lt;/p&gt;


	&lt;p&gt;but that command returns&lt;/p&gt;


	&lt;p&gt;gpg: no writable keyring found: eof
gpg: error reading `-&amp;#8217;: general error
gpg: import from `-&amp;#8217; failed: general error&lt;/p&gt;


	&lt;p&gt;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.&lt;/p&gt;</description>
      <pubDate>Fri, 10 Feb 2006 14:53:00 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:e720f648058127487c728ab06ab9ebb5</guid>
      <author>Graham Stratton</author>
      <link>http://grahamstratton.org/blog/public/articles/2006/02/10/debian-keys</link>
      <category>Debian</category>
      <category>Linux</category>
    </item>
  </channel>
</rss>
