<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Tumbleweed Rants</title>
  <subtitle>Stefano's World</subtitle>
  <link rel="alternate" type="text/html" href="http://tumbleweed.org.za/2007/04/10/etch-upgrades"/>
  <link rel="self" type="application/atom+xml" href="http://tumbleweed.org.za/node/67/atom/feed"/>
  <id>http://tumbleweed.org.za/node/67/atom/feed</id>
  <updated>2008-09-19T09:17:57+00:00</updated>
  <entry>
    <title>etch upgrades</title>
    <link rel="alternate" type="text/html" href="http://tumbleweed.org.za/2007/04/10/etch-upgrades" />
    <id>http://tumbleweed.org.za/2007/04/10/etch-upgrades</id>
    <published>2007-04-10T12:37:56+00:00</published>
    <updated>2008-09-19T09:17:57+00:00</updated>
    <author>
      <name>tumbleweed</name>
    </author>
    <category term="clug" />
    <category term="debian" />
    <category term="software" />
    <summary type="html"><![CDATA[<p>I&#8217;ve done etch upgrades in the past (i.e. before etch came out), and they were sometimes quite hairy. Especially the transition from <span class="geshifilter"><code class="geshifilter-text">ssh</code></span> to <span class="geshifilter"><code class="geshifilter-text">openssh-server</code></span> and <span class="geshifilter"><code class="geshifilter-text">openssh-client</code></span>. I had a few&nbsp;broken&nbsp;upgrades&#8230;</p>

<p>Since etch has come out, I&#8217;ve been upgraded a few machines, and it&#8217;s a piece of cake. In fact the <span class="caps"><span class="caps">CLUG</span></span> webserver and backup-server have&nbsp;been&nbsp;upgraded.</p>

<p>My servers tend to use custom kernels without initrds, so upgrading is quite simple. The <a href="http://www.za.debian.org/releases/etch/i386/release-notes/ch-upgrading.en.html" title="i386 release notes">release notes</a> seem to cover it pretty well. There are only a couple of gotchas&nbsp;I&#8217;ve&nbsp;had:</p>

<p>Upgrade <span class="geshifilter"><code class="geshifilter-text">vim</code></span> with an <span class="geshifilter"><code class="geshifilter-text">aptitude install vim</code></span> before you do any dist-upgrading. Personally, I like to use <span class="geshifilter"><code class="geshifilter-text">vimdiff</code></span> for configuration file changes. This means I can keep the configuration file format and comments of the latest package, <em>and</em> my configuration changes from when the machine was originally set up. If vim is half installed, you can&#8217;t run <span class="geshifilter"><code class="geshifilter-text">vimdiff</code></span>&#8230;</p>

<p>When you are done, you might need to&nbsp;purge&nbsp;hotplug:</p>

<div class="geshifilter"><div class="text geshifilter-text" style="font-family:monospace;"># aptitude purge hotplug</div></div>

<p>You can also remove non-<span class="caps"><span class="caps">US</span></span> from your <span class="geshifilter"><code class="geshifilter-text">sources.list</code></span>.</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>I&#8217;ve done etch upgrades in the past (i.e. before etch came out), and they were sometimes quite hairy. Especially the transition from <code>ssh</code> to <code>openssh-server</code> and <code>openssh-client</code>. I had a few broken&nbsp;upgrades&#8230;</p>

<p>Since etch has come out, I&#8217;ve been upgraded a few machines, and it&#8217;s a piece of cake. In fact the <span class="caps">CLUG</span> webserver and backup-server have been&nbsp;upgraded.</p>

<p>My servers tend to use custom kernels without initrds, so upgrading is quite simple. The <a href="http://www.za.debian.org/releases/etch/i386/release-notes/ch-upgrading.en.html" title="i386 release notes">release notes</a> seem to cover it pretty well. There are only a couple of gotchas I&#8217;ve&nbsp;had:</p>

<p>Upgrade <code>vim</code> with an <code>aptitude install vim</code> before you do any dist-upgrading. Personally, I like to use <code>vimdiff</code> for configuration file changes. This means I can keep the configuration file format and comments of the latest package, <em>and</em> my configuration changes from when the machine was originally set up. If vim is half installed, you can&#8217;t run <code>vimdiff</code>&#8230;</p>

<p>When you are done, you might need to purge&nbsp;hotplug:</p>

<div class="geshifilter"><div class="text geshifilter-text" style="font-family:monospace;"># aptitude purge hotplug</div></div>

<p>You can also remove non-<span class="caps">US</span> from your <code>sources.list</code>.</p>
    ]]></content>
  </entry>
</feed>
