<?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: Ubuntu Dapper is NOT debian-unstable</title>
	<atom:link href="http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/feed/" rel="self" type="application/rss+xml" />
	<link>http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/</link>
	<description>Adventures in Computer Programming</description>
	<pubDate>Fri, 21 Nov 2008 20:06:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Raoul</title>
		<link>http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/#comment-7282</link>
		<dc:creator>Raoul</dc:creator>
		<pubDate>Sun, 13 May 2007 15:05:38 +0000</pubDate>
		<guid isPermaLink="false">http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/#comment-7282</guid>
		<description>Maybe a better (or simply different) way to overcome the problem : 

sudo aptitude keep libc6 libc6-dev

Cheers !</description>
		<content:encoded><![CDATA[<p>Maybe a better (or simply different) way to overcome the problem : </p>
<p>sudo aptitude keep libc6 libc6-dev</p>
<p>Cheers !</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Samir Patil</title>
		<link>http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/#comment-6943</link>
		<dc:creator>Samir Patil</dc:creator>
		<pubDate>Fri, 20 Apr 2007 17:42:08 +0000</pubDate>
		<guid isPermaLink="false">http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/#comment-6943</guid>
		<description>I had a similar problem trying to install latest version of QPxTool from Debian unstable. It had dependencies on libqt3-mt then libfontconfig1 then fontconfig-config
It got stuck when installing fontconfig-config.  This blog helped me. 
sudo apt-get install -f fontconfig-config/edgy</description>
		<content:encoded><![CDATA[<p>I had a similar problem trying to install latest version of QPxTool from Debian unstable. It had dependencies on libqt3-mt then libfontconfig1 then fontconfig-config<br />
It got stuck when installing fontconfig-config.  This blog helped me.<br />
sudo apt-get install -f fontconfig-config/edgy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stg</title>
		<link>http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/#comment-6259</link>
		<dc:creator>Stg</dc:creator>
		<pubDate>Thu, 08 Mar 2007 19:39:40 +0000</pubDate>
		<guid isPermaLink="false">http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/#comment-6259</guid>
		<description>Thank's for this post!! It was very very helpfull!!</description>
		<content:encoded><![CDATA[<p>Thank&#8217;s for this post!! It was very very helpfull!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas David Baker</title>
		<link>http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/#comment-6032</link>
		<dc:creator>Thomas David Baker</dc:creator>
		<pubDate>Wed, 21 Feb 2007 18:43:46 +0000</pubDate>
		<guid isPermaLink="false">http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/#comment-6032</guid>
		<description>It's not a bad philosophy, but GHC6.6 takes about 8 hours to compile on my machine IF I have GHC6.4 installed already.  God knows how long it takes when it has to bootstrap with a C compiler only.  A long time!</description>
		<content:encoded><![CDATA[<p>It&#8217;s not a bad philosophy, but GHC6.6 takes about 8 hours to compile on my machine IF I have GHC6.4 installed already.  God knows how long it takes when it has to bootstrap with a C compiler only.  A long time!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: viza</title>
		<link>http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/#comment-6031</link>
		<dc:creator>viza</dc:creator>
		<pubDate>Wed, 21 Feb 2007 18:38:48 +0000</pubDate>
		<guid isPermaLink="false">http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/#comment-6031</guid>
		<description>I generally just install from source if package dependancies aren't being met, and the software is bleeding edge. It's almost always easier that way. Of course if the system isn't  yours you may not have access to the compiler.

You can control where it's installed and simply remove it and install the package when the packagers catch up. With a well written configure script (or reasonably easy to understand make file), the source and your compiler can be more flexible with dealing with your installed libc stuff, unless there are dependancies on functions within libc with a signature which is different from the installed version and the one the code was written against. If there are, you can often fix the issue in the source code and not need to upgrade glibc (or whatever).

I sort of got into this when OpenSSL had a serious vulnerability and it took forever for the new package to be built by the distro maintainers. I had a mandate to get it patched in 48 hours or the servers get the plug pulled. I got it done and ever since, I compile all web server and related software from source. (php, openssl, apache, and many other packages).

If there is a serious vulnerability I can patch it the moment the developers release the patch. I don't need to wait weeks (or even months) for the packagers to get to it while exposed systems are vulnerable. After scripting the build process, it's a snap to deal with when you need to recompile something.

I follow this philosophy for any service which is exposed to that combat zone we call the internet.</description>
		<content:encoded><![CDATA[<p>I generally just install from source if package dependancies aren&#8217;t being met, and the software is bleeding edge. It&#8217;s almost always easier that way. Of course if the system isn&#8217;t  yours you may not have access to the compiler.</p>
<p>You can control where it&#8217;s installed and simply remove it and install the package when the packagers catch up. With a well written configure script (or reasonably easy to understand make file), the source and your compiler can be more flexible with dealing with your installed libc stuff, unless there are dependancies on functions within libc with a signature which is different from the installed version and the one the code was written against. If there are, you can often fix the issue in the source code and not need to upgrade glibc (or whatever).</p>
<p>I sort of got into this when OpenSSL had a serious vulnerability and it took forever for the new package to be built by the distro maintainers. I had a mandate to get it patched in 48 hours or the servers get the plug pulled. I got it done and ever since, I compile all web server and related software from source. (php, openssl, apache, and many other packages).</p>
<p>If there is a serious vulnerability I can patch it the moment the developers release the patch. I don&#8217;t need to wait weeks (or even months) for the packagers to get to it while exposed systems are vulnerable. After scripting the build process, it&#8217;s a snap to deal with when you need to recompile something.</p>
<p>I follow this philosophy for any service which is exposed to that combat zone we call the internet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gesteur</title>
		<link>http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/#comment-5894</link>
		<dc:creator>gesteur</dc:creator>
		<pubDate>Sun, 11 Feb 2007 12:11:09 +0000</pubDate>
		<guid isPermaLink="false">http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/#comment-5894</guid>
		<description>Hi thank you very much, i also got stuck into this problem, got madwifi package under debian-unstable.
However the apt-get did not work, i had to do, aptitude install libc6/dapper, this solved my problem.

thanks again</description>
		<content:encoded><![CDATA[<p>Hi thank you very much, i also got stuck into this problem, got madwifi package under debian-unstable.<br />
However the apt-get did not work, i had to do, aptitude install libc6/dapper, this solved my problem.</p>
<p>thanks again</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas David Baker</title>
		<link>http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/#comment-5823</link>
		<dc:creator>Thomas David Baker</dc:creator>
		<pubDate>Thu, 08 Feb 2007 15:08:33 +0000</pubDate>
		<guid isPermaLink="false">http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/#comment-5823</guid>
		<description>Hi Brian, I have ghc6.6 working on Dapper just fine.  I just installed the "generic linux" download from the ghc site instead of the debian stuff.</description>
		<content:encoded><![CDATA[<p>Hi Brian, I have ghc6.6 working on Dapper just fine.  I just installed the &#8220;generic linux&#8221; download from the ghc site instead of the debian stuff.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brian</title>
		<link>http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/#comment-5822</link>
		<dc:creator>brian</dc:creator>
		<pubDate>Thu, 08 Feb 2007 15:01:13 +0000</pubDate>
		<guid isPermaLink="false">http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/#comment-5822</guid>
		<description>has anyone been able to install ghc 6.6 on edgy?  I guess wait for next ubuntu release in a couple of months?</description>
		<content:encoded><![CDATA[<p>has anyone been able to install ghc 6.6 on edgy?  I guess wait for next ubuntu release in a couple of months?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: will</title>
		<link>http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/#comment-5293</link>
		<dc:creator>will</dc:creator>
		<pubDate>Tue, 23 Jan 2007 04:46:41 +0000</pubDate>
		<guid isPermaLink="false">http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/#comment-5293</guid>
		<description>Thank you for this post.  That'll show me for blindly adding depositories and expecting everything to work like magic....</description>
		<content:encoded><![CDATA[<p>Thank you for this post.  That&#8217;ll show me for blindly adding depositories and expecting everything to work like magic&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: javierguillot</title>
		<link>http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/#comment-5211</link>
		<dc:creator>javierguillot</dc:creator>
		<pubDate>Sat, 20 Jan 2007 02:13:57 +0000</pubDate>
		<guid isPermaLink="false">http://bluebones.net/2007/01/ubuntu-dapper-is-not-debian-unstable/#comment-5211</guid>
		<description>Thank you very much for this post!!! I was fighting with a very similar problem with libc6 since about 3 days, and had gotten no help from the ubuntu forums. I had  committed the mistake of installing a libc6 package from the debian page (packages.debian.org), which was not within the ubuntu repositories. But I did this AFTER installing a libgpod package from the same place, so I had to run

sudo apt-get install -f libc6/dapper libgpod0/dapper

to get the problem fixed.

Once again thank you.</description>
		<content:encoded><![CDATA[<p>Thank you very much for this post!!! I was fighting with a very similar problem with libc6 since about 3 days, and had gotten no help from the ubuntu forums. I had  committed the mistake of installing a libc6 package from the debian page (packages.debian.org), which was not within the ubuntu repositories. But I did this AFTER installing a libgpod package from the same place, so I had to run</p>
<p>sudo apt-get install -f libc6/dapper libgpod0/dapper</p>
<p>to get the problem fixed.</p>
<p>Once again thank you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
