<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Bad idea of the day: upgrading to Lenny with aptitude</title>
	<atom:link href="http://blog.workaround.org/2008/08/23/bad-idea-of-the-day-upgrading-to-lenny-with-aptitude/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.workaround.org/2008/08/23/bad-idea-of-the-day-upgrading-to-lenny-with-aptitude/</link>
	<description>Rants, discoveries and my tireless search for perfect Linux tools</description>
	<pubDate>Wed, 07 Jan 2009 04:29:53 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Daniel Burrows</title>
		<link>http://blog.workaround.org/2008/08/23/bad-idea-of-the-day-upgrading-to-lenny-with-aptitude/#comment-712</link>
		<dc:creator>Daniel Burrows</dc:creator>
		<pubDate>Sat, 23 Aug 2008 18:25:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.workaround.org/?p=28#comment-712</guid>
		<description>My suspicion (I don't have enough information yet to know what's happening) is that this is caused by code that's shared between all apt frontends.  If aptitude is going wrong and apt-get isn't, it might be because aptitude is more aggressive about removing unused packages.  That is, apt-get *would* do this if it tried to upgrade slapd at the same time that it removed libldap-2.3-0, but it doesn't remove unused stuff by default, so it doesn't hit this case.  If that turns out to be what's happening, you might be able to avoid this particular case by passing "-o Aptitude::Delete-Unused=true" on the command-line, but you could still be bitten in a different upgrade that happens to create the same situation.

But as I said, I don't really know what's happening here, so all I'm doing is guessing.</description>
		<content:encoded><![CDATA[<p>My suspicion (I don&#8217;t have enough information yet to know what&#8217;s happening) is that this is caused by code that&#8217;s shared between all apt frontends.  If aptitude is going wrong and apt-get isn&#8217;t, it might be because aptitude is more aggressive about removing unused packages.  That is, apt-get *would* do this if it tried to upgrade slapd at the same time that it removed libldap-2.3-0, but it doesn&#8217;t remove unused stuff by default, so it doesn&#8217;t hit this case.  If that turns out to be what&#8217;s happening, you might be able to avoid this particular case by passing &#8220;-o Aptitude::Delete-Unused=true&#8221; on the command-line, but you could still be bitten in a different upgrade that happens to create the same situation.</p>
<p>But as I said, I don&#8217;t really know what&#8217;s happening here, so all I&#8217;m doing is guessing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelly Clowers</title>
		<link>http://blog.workaround.org/2008/08/23/bad-idea-of-the-day-upgrading-to-lenny-with-aptitude/#comment-709</link>
		<dc:creator>Kelly Clowers</dc:creator>
		<pubDate>Sat, 23 Aug 2008 15:43:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.workaround.org/?p=28#comment-709</guid>
		<description>If you like "apt-cache search", try "aptitude search". I don't think it has a source command, though.</description>
		<content:encoded><![CDATA[<p>If you like &#8220;apt-cache search&#8221;, try &#8220;aptitude search&#8221;. I don&#8217;t think it has a source command, though.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
