<?xml version="1.0" encoding="utf-8"?>
<!-- name="generator" content="pyblosxom/1.4.3 01/10/2008" -->
<!DOCTYPE rss PUBLIC "-//Netscape Communications//DTD RSS 0.91//EN" "http://my.netscape.com/publish/formats/rss-0.91.dtd">

<rss version="0.91">
<channel>
<title>Gedankenblitze   </title>
<link>http://micha.lenk.info/Gedankenblitze</link>
<description>Gedankenblitze von Micha Lenk</description>
<language>de</language>
<item>
  <title>Finally transitioning to a new GnuPG key</title>
  <link>http://micha.lenk.info/Gedankenblitze/Debian/gpg-transition-signed.html</link>
  <description><![CDATA[
<p>Finally I managed to write up a <a href="/gpg-transition-2011.txt"
   target="_blank">transition statement</a> for my not so new, but
   stronger GnuPG key. See below:</p>
<pre>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1,SHA256

I am transitioning my GPG key from an old 1024-bit key to a new 4096-bit key.
The old key will continue to be valid for some time, but I prefer all new
correspondence to be encrypted for the new key, and will be making all
signatures going forward with the new key.

If you have signed my old key, I would appreciate signatures on my new key as
well, provided that your signing policy permits that without reauthenticating
me.

The old key, which I am transitioning away from, is:

pub   1024D/99E141B4 2004-02-10
      Key fingerprint = 25FE 4741 4770 0558 949D  1DB1 58DD 3FE2 99E1 41B4

The new key, to which I am transitioning, is:

pub   4096R/51B85139 2009-06-18
      Key fingerprint = A3EB B41F C5AB D675 CEE4  1C45 EA6C A6B9 51B8 5139

Thanks in advance.

Cheers,
Micha Lenk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk5aOnkACgkQWN0/4pnhQbTxPgCgzRhREZlQiKJyI9UIdJLLs3Zq
bH4AnA1myFxgDWM7aUMHXgvvsujLTjiWiQIcBAEBCAAGBQJOWjp5AAoJEOpsprlR
uFE5gCsP/0dtCUPl9aQHV1MbQl7+bMofpsC2ikkpdZmrzi68jTG16We49BuzY+PV
S8FhXqg17/YxhKYDnDNTowfztUOyjAOJxy5vrqm3X5xiLwTqN3js9mra+vb4s35k
EVbKMzLLDhj3i0FjeargWEmJmm9cVhaZWKvOvQUhDJAilqvEQ0/50P7B8I+1YvtV
UHoQKbweTljVSlK5R1YPPy9i6r2/oZBYxK4nrknWwS+qPQ5luqelJd+mZdgQ6tow
7HIvtmPgCblJ+hYZWFpoZK6vxs8RaBbuCQcKwYArNhZT/v4TeD/LAaUmIkbQMyKV
J2TKuEHya4+5GMbtg6BGKeiZpleEHPnAq1AfvGpz6opkxjxCLG3RO3X8D3EuM3RW
mkq60mWM8+Zwu1yKbb62iHplp6jpyiQgdjJlB6eHjX7SdY7CvHgYZxGDx4kclP0/
HAdig2U1T+nG6Nn5XflmmKwvNLuKlQlIwJ5NeXyCONRnYvdomQn2hgvkjwMLCdFh
ulIhxa4UvDY7/aQNPZeOrvDHb2XYpiV3TwA9hLgQXXWd0FPmUMVVPpKpRjilaWth
Mtq/QiMGP5Mq/YxgLInRZHGyajDtE67RD4+RgHYOP50cP3UGPoB4ncc2EEtM2kfe
BzJrXPHmdtyGEA6Korl0YwUTRnYsqkqkY1VqDsO0UkOLlV7RAzb9
=9vw1
-----END PGP SIGNATURE-----
</pre>

]]></description>
</item>

<item>
  <title>Debian Developer</title>
  <link>http://micha.lenk.info/Gedankenblitze/Debian/DebianDeveloper.html</link>
  <description><![CDATA[
<p>Once upon a time I prepared a Debian package for a runtime library
   I'm using frequently on my computer. I thought that other users should
   benefit from what I've done for my own purposes. I thought it wouldn't
   cost me a penny to share it with others, so I uploaded it to
   a public accessible place and announced it to the public.</p>
<p>All of a sudden a Debian Developer came and uploaded my Debian
   package to the official Debian archive, where it became official
   part of the Debian distribution. Henceforth the Debian Developer
   guided me on how to properly package Debian packages and on
   improving my packages. I learned a lot and became more and more
   familiar with Debian's procedures and tools.</p>
<p>As the time passed by, he encouraged me to apply as a Debian Developer.
   So I did. It was again a time of challenging tasks to be done, but as the
   other Debian Developer managing my application was very short in time, I
   also had to be very patient for a long time again and again. To cut a
   long story short: After more than three years of mostly waiting and
   contributing to Debian as good as I could, I finally have become
   official <b>Debian Developer</b> on September, the 13<sup>st</sup> 2009.</p>
<p>I'm happy that I eventually made it. And, at this stage it is
   time to say thank you to all of the fellow Debian Developers who
   kindly sponsored my uploads or encouraged me to keep on going.
   You've all done a wonderful job and were of great help to me.</p>

]]></description>
</item>

<item>
  <title>I&apos;m going to DebConf9</title>
  <link>http://micha.lenk.info/Gedankenblitze/Debian/dc9-imgoingto.html</link>
  <description><![CDATA[
<a href="http://debconf8.debconf.org">
<img src="http://media.debconf.org/dc8/images/debconf8-going-to.png"
     alt="I'm going to DebConf8, edition 2008 of the annual Debian developers meeting"
     align="right" vspace="10" hspace="20" />
</a>
<p>I'm going to this year's Debian developers meeting, the DebConf9.</p>
<p>Unfortunately the conference overlaps with even more important events,
   so I will only be there half the time from 27<sup>th</sup> of July, but I
   will stay to the end. Being a first time visitor of DebConf I'm curious
   about what's going to happen there and about getting in touch with all the
   other geeks... *grin* &mdash; See you there!</p>

]]></description>
</item>

<item>
  <title>Icedove 2.0 backport for Debian Etch available</title>
  <link>http://micha.lenk.info/Gedankenblitze/Debian/icedove.html</link>
  <description><![CDATA[
<p>Someone told be about the cool features of the <a target="_blank" href="https://addons.mozilla.org/de/thunderbird/addon/2313">Thunderbird
Lightning extension</a>, an extension managing your calendar and tasks within Thunderbird.
As this extension is only available for Thunderbird 2.0 and as Icedove is only available in
version 1.5 in Debian Etch, I backported Icedove 2.0.0.16-1 from Lenny.</p>
<p>If you're a Debian Etch user you can add the following line to your <tt>/etc/apt/sources.list</tt>,
run <tt>apt-get update</tt> and install it with <tt>aptitude install icedove</tt>.
<pre>

  deb <a href="http://micha.lenk.info/debian/etch/">http://micha.lenk.info/debian etch/</a>

</pre>
Have fun!
</p>

]]></description>
</item>

<item>
  <title>checkinstall for Debian Etch</title>
  <link>http://micha.lenk.info/Gedankenblitze/Debian/checkinstall.html</link>
  <description><![CDATA[
<p>Unfortunately checkinstall didn't made it into Debian Etch, hence I needed to backport it from Lenny.
I tried to follow the instructions given on www.backports.org, but unfortunately the package FTBFS
on 64 bit architectures with the libc6-dev provided with Etch. I dropped the versioned build-dependency
on libc6-dev and restricted its build to Architecture: i386, but probably this renders the package
inacceptable for www.backports.org...</p>

<p>You can find the backport <a href="http://micha.lenk.info/debian/etch-backports/" target="_blank">here</a>.</p>

]]></description>
</item>

<item>
  <title>pdfedit for Debian Etch</title>
  <link>http://micha.lenk.info/Gedankenblitze/Debian/pdfedit.html</link>
  <description><![CDATA[
<p>Just in case anybody is interested: I just built a backport of <a
href="http://packages.debian.org/sid/pdfedit">pdfedit</a> for Debian Etch.  The
package is available from my personal package repository, which you can include
in your <tt>/etc/apt/sources.list</tt> using following line:</p>
<pre>

  deb <a href="http://micha.lenk.info/debian/etch/">http://micha.lenk.info/debian etch/</a>

</pre>
<p>Unfortunately it seems to be quite instabile, so <em>be warned...</em></p>

]]></description>
</item>

</channel>
</rss>

