<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="http://feeds.liveforge.org/~d/styles/rss2full.xsl" type="text/xsl" media="screen"?><?xml-stylesheet href="http://feeds.liveforge.org/~d/styles/itemcontent.css" type="text/css" media="screen"?><rss 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" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
<channel>
	<title>Comments for Bits by Ben</title>
	
	<link>http://ben.liveforge.org</link>
	<description>a Gentoo Linux geek blogging about free software and technology</description>
	<pubDate>Tue, 15 Jul 2008 14:55:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.liveforge.org/BitsByBen/comments/rss2" type="application/rss+xml" /><item>
		<title>Comment on Arora and other additions to portage by Ben</title>
		<link>http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~3/329997034/arora-and-other-additions-to-portage</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Tue, 08 Jul 2008 10:07:23 +0000</pubDate>
		<guid isPermaLink="false">http://ben.liveforge.org/?p=22#comment-158</guid>
		<description>Thanks! I'll correct it.</description>
		<content:encoded><![CDATA[<p>Thanks! I&#8217;ll correct it.</p>
<img src="http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~4/329997034" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://ben.liveforge.org/2008/07/08/arora-and-other-additions-to-portage#comment-158</feedburner:origLink></item>
	<item>
		<title>Comment on Arora and other additions to portage by Jason</title>
		<link>http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~3/329997035/arora-and-other-additions-to-portage</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Tue, 08 Jul 2008 06:30:04 +0000</pubDate>
		<guid isPermaLink="false">http://ben.liveforge.org/?p=22#comment-157</guid>
		<description>Hey I'm an arora dev. Thought I should point out that

EGIT_REPO_URI="git://github.com/icefox/arora.git"

is incorrect. Icefox's repository is no longer the main one. The line should instead read:

EGIT_REPO_URI="git://github.com/Arora/arora.git"</description>
		<content:encoded><![CDATA[<p>Hey I&#8217;m an arora dev. Thought I should point out that</p>
<p>EGIT_REPO_URI=&#8221;git://github.com/icefox/arora.git&#8221;</p>
<p>is incorrect. Icefox&#8217;s repository is no longer the main one. The line should instead read:</p>
<p>EGIT_REPO_URI=&#8221;git://github.com/Arora/arora.git&#8221;</p>
<img src="http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~4/329997035" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://ben.liveforge.org/2008/07/08/arora-and-other-additions-to-portage#comment-157</feedburner:origLink></item>
	<item>
		<title>Comment on The joy of updates by kernelOfTruth</title>
		<link>http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~3/312802523/the-joy-of-updates</link>
		<dc:creator>kernelOfTruth</dc:creator>
		<pubDate>Sun, 15 Jun 2008 10:14:08 +0000</pubDate>
		<guid isPermaLink="false">http://ben.liveforge.org/?p=21#comment-154</guid>
		<description>update:

nope, it was kind of an regression with gcc-4.3.1 + hardened toolchain:
-march=core2 causes all this weird crashing, -march=nocona and/or -mtune=nocona -msse3 -mssse3 fixes it (already reported on the toolchain thread) 

I'm glad however that the memory hunger of X has been fixed ;)</description>
		<content:encoded><![CDATA[<p>update:</p>
<p>nope, it was kind of an regression with gcc-4.3.1 + hardened toolchain:<br />
-march=core2 causes all this weird crashing, -march=nocona and/or -mtune=nocona -msse3 -mssse3 fixes it (already reported on the toolchain thread) </p>
<p>I&#8217;m glad however that the memory hunger of X has been fixed ;)</p>
<img src="http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~4/312802523" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://ben.liveforge.org/2008/06/13/the-joy-of-updates#comment-154</feedburner:origLink></item>
	<item>
		<title>Comment on The joy of updates by kernelOfTruth</title>
		<link>http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~3/311824912/the-joy-of-updates</link>
		<dc:creator>kernelOfTruth</dc:creator>
		<pubDate>Sat, 14 Jun 2008 13:08:38 +0000</pubDate>
		<guid isPermaLink="false">http://ben.liveforge.org/?p=21#comment-153</guid>
		<description>thanks for this information:

xorg had kept on crashing for me for the last 2 or 3 days, now I know it's due to pixman - not gcc-4.3.1 or glibc-2.8</description>
		<content:encoded><![CDATA[<p>thanks for this information:</p>
<p>xorg had kept on crashing for me for the last 2 or 3 days, now I know it&#8217;s due to pixman - not gcc-4.3.1 or glibc-2.8</p>
<img src="http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~4/311824912" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://ben.liveforge.org/2008/06/13/the-joy-of-updates#comment-153</feedburner:origLink></item>
	<item>
		<title>Comment on The joy of updates by energyman</title>
		<link>http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~3/311518020/the-joy-of-updates</link>
		<dc:creator>energyman</dc:creator>
		<pubDate>Fri, 13 Jun 2008 23:24:08 +0000</pubDate>
		<guid isPermaLink="false">http://ben.liveforge.org/?p=21#comment-148</guid>
		<description>emerge -e system broke pretty hard for me.
 Now I get this:
checking for C compiler default output file name... configure: error: C compiler cannot create executables

and this:
ls /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.1/
ls: cannot access /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.1/: No such file or directory

equery says there should be something but there isn't.

tcpwrappers fails with tons of  include errors - all related to glibc - and even man doesn't even work anymore.

I am not impressed.</description>
		<content:encoded><![CDATA[<p>emerge -e system broke pretty hard for me.<br />
 Now I get this:<br />
checking for C compiler default output file name&#8230; configure: error: C compiler cannot create executables</p>
<p>and this:<br />
ls /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.1/<br />
ls: cannot access /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.1/: No such file or directory</p>
<p>equery says there should be something but there isn&#8217;t.</p>
<p>tcpwrappers fails with tons of  include errors - all related to glibc - and even man doesn&#8217;t even work anymore.</p>
<p>I am not impressed.</p>
<img src="http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~4/311518020" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://ben.liveforge.org/2008/06/13/the-joy-of-updates#comment-148</feedburner:origLink></item>
	<item>
		<title>Comment on The joy of updates by David Philippi</title>
		<link>http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~3/311307796/the-joy-of-updates</link>
		<dc:creator>David Philippi</dc:creator>
		<pubDate>Fri, 13 Jun 2008 17:43:02 +0000</pubDate>
		<guid isPermaLink="false">http://ben.liveforge.org/?p=21#comment-147</guid>
		<description>I think for glibc some time in package.mask might have been a good idea and for GCC waiting on 4.3.1 propably fixed quite a few really bad problems. The most strange guy is libtool-2.2 for me. It's speeding up compilation and in the few packages where I had problems with it I found a fix already in bugzilla which was far from invasive...</description>
		<content:encoded><![CDATA[<p>I think for glibc some time in package.mask might have been a good idea and for GCC waiting on 4.3.1 propably fixed quite a few really bad problems. The most strange guy is libtool-2.2 for me. It&#8217;s speeding up compilation and in the few packages where I had problems with it I found a fix already in bugzilla which was far from invasive&#8230;</p>
<img src="http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~4/311307796" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://ben.liveforge.org/2008/06/13/the-joy-of-updates#comment-147</feedburner:origLink></item>
	<item>
		<title>Comment on The joy of updates by Ben</title>
		<link>http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~3/311247162/the-joy-of-updates</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Fri, 13 Jun 2008 15:54:06 +0000</pubDate>
		<guid isPermaLink="false">http://ben.liveforge.org/?p=21#comment-146</guid>
		<description>Cardoe, I understand things will break from time to time in ~arch. That is to be expected, and I don't have a problem with that. But I hold it to be proper procedure to put an update which will very likely lead to breakage in various parts in the tree in p.mask first, and give maintainers some time (even if just one week) to test their packages and come up with fixes. Just like what has been done for gcc-4.3, and what we in video herd are doing with ffmpeg. Of course that won't catch all issues, but it will catch the most serious ones.

Personally, I can handle such occasional breakage, it's what you get for living on the (bleeding) edge. But I do care about other ~arch users, and I know there are many, especially because often packages just take ages to become stable in Gentoo.</description>
		<content:encoded><![CDATA[<p>Cardoe, I understand things will break from time to time in ~arch. That is to be expected, and I don&#8217;t have a problem with that. But I hold it to be proper procedure to put an update which will very likely lead to breakage in various parts in the tree in p.mask first, and give maintainers some time (even if just one week) to test their packages and come up with fixes. Just like what has been done for gcc-4.3, and what we in video herd are doing with ffmpeg. Of course that won&#8217;t catch all issues, but it will catch the most serious ones.</p>
<p>Personally, I can handle such occasional breakage, it&#8217;s what you get for living on the (bleeding) edge. But I do care about other ~arch users, and I know there are many, especially because often packages just take ages to become stable in Gentoo.</p>
<img src="http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~4/311247162" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://ben.liveforge.org/2008/06/13/the-joy-of-updates#comment-146</feedburner:origLink></item>
	<item>
		<title>Comment on The joy of updates by Cardoe</title>
		<link>http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~3/311174365/the-joy-of-updates</link>
		<dc:creator>Cardoe</dc:creator>
		<pubDate>Fri, 13 Jun 2008 14:05:39 +0000</pubDate>
		<guid isPermaLink="false">http://ben.liveforge.org/?p=21#comment-145</guid>
		<description>You sound like the exact user that should not be using ~arch. But should stay on a stable system. A lot of the issues you are complaining about are the same issues that anyone using an unstable or testing Debian system would have. Stuff needs some place for users to test it and for it to cook. If it works reasonably well for a developer, we need to push it to a larger audience. Sometimes things break when the larger group gets it.</description>
		<content:encoded><![CDATA[<p>You sound like the exact user that should not be using ~arch. But should stay on a stable system. A lot of the issues you are complaining about are the same issues that anyone using an unstable or testing Debian system would have. Stuff needs some place for users to test it and for it to cook. If it works reasonably well for a developer, we need to push it to a larger audience. Sometimes things break when the larger group gets it.</p>
<img src="http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~4/311174365" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://ben.liveforge.org/2008/06/13/the-joy-of-updates#comment-145</feedburner:origLink></item>
	<item>
		<title>Comment on The joy of updates by transacid</title>
		<link>http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~3/311123827/the-joy-of-updates</link>
		<dc:creator>transacid</dc:creator>
		<pubDate>Fri, 13 Jun 2008 12:23:01 +0000</pubDate>
		<guid isPermaLink="false">http://ben.liveforge.org/?p=21#comment-144</guid>
		<description>Wed Jun 11 19:31:56 2008 &gt;&gt;&gt; sys-libs/glibc-2.8_p20080602
     Wed Jun 11 19:32:40 2008 &gt;&gt;&gt; app-office/openoffice-bin-2.4.1
     Wed Jun 11 19:32:45 2008 &gt;&gt;&gt; net-misc/iputils-20071127-r2
     Wed Jun 11 19:35:15 2008 &gt;&gt;&gt; media-libs/xine-lib-1.1.12-r1
     Wed Jun 11 19:36:25 2008 &gt;&gt;&gt; app-cdr/cdrdao-1.2.2-r2
     Wed Jun 11 19:37:39 2008 &gt;&gt;&gt; net-analyzer/nmap-4.65
     Wed Jun 11 19:38:09 2008 &gt;&gt;&gt; dev-util/git-1.5.5.4
     Thu Jun 12 21:50:47 2008 &gt;&gt;&gt; games-board/pokerth-0.6.2
     Fri Jun 13 12:15:35 2008 &gt;&gt;&gt; x11-libs/pixman-0.10.0</description>
		<content:encoded><![CDATA[<p>Wed Jun 11 19:31:56 2008 &gt;&gt;&gt; sys-libs/glibc-2.8_p20080602<br />
     Wed Jun 11 19:32:40 2008 &gt;&gt;&gt; app-office/openoffice-bin-2.4.1<br />
     Wed Jun 11 19:32:45 2008 &gt;&gt;&gt; net-misc/iputils-20071127-r2<br />
     Wed Jun 11 19:35:15 2008 &gt;&gt;&gt; media-libs/xine-lib-1.1.12-r1<br />
     Wed Jun 11 19:36:25 2008 &gt;&gt;&gt; app-cdr/cdrdao-1.2.2-r2<br />
     Wed Jun 11 19:37:39 2008 &gt;&gt;&gt; net-analyzer/nmap-4.65<br />
     Wed Jun 11 19:38:09 2008 &gt;&gt;&gt; dev-util/git-1.5.5.4<br />
     Thu Jun 12 21:50:47 2008 &gt;&gt;&gt; games-board/pokerth-0.6.2<br />
     Fri Jun 13 12:15:35 2008 &gt;&gt;&gt; x11-libs/pixman-0.10.0</p>
<img src="http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~4/311123827" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://ben.liveforge.org/2008/06/13/the-joy-of-updates#comment-144</feedburner:origLink></item>
	<item>
		<title>Comment on The joy of updates by Ben</title>
		<link>http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~3/311123829/the-joy-of-updates</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Fri, 13 Jun 2008 12:17:15 +0000</pubDate>
		<guid isPermaLink="false">http://ben.liveforge.org/?p=21#comment-143</guid>
		<description>Only if they are non-essential packages.</description>
		<content:encoded><![CDATA[<p>Only if they are non-essential packages.</p>
<img src="http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~4/311123829" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://ben.liveforge.org/2008/06/13/the-joy-of-updates#comment-143</feedburner:origLink></item>
	<item>
		<title>Comment on The joy of updates by transacid</title>
		<link>http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~3/311108453/the-joy-of-updates</link>
		<dc:creator>transacid</dc:creator>
		<pubDate>Fri, 13 Jun 2008 11:59:51 +0000</pubDate>
		<guid isPermaLink="false">http://ben.liveforge.org/?p=21#comment-142</guid>
		<description>Wouldn't it be also possible to just downgrade the glibc and remerge all package build after the glibc update (only 4 here)</description>
		<content:encoded><![CDATA[<p>Wouldn&#8217;t it be also possible to just downgrade the glibc and remerge all package build after the glibc update (only 4 here)</p>
<img src="http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~4/311108453" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://ben.liveforge.org/2008/06/13/the-joy-of-updates#comment-142</feedburner:origLink></item>
	<item>
		<title>Comment on The joy of updates by Ben</title>
		<link>http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~3/311092057/the-joy-of-updates</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Fri, 13 Jun 2008 11:26:45 +0000</pubDate>
		<guid isPermaLink="false">http://ben.liveforge.org/?p=21#comment-141</guid>
		<description>Roguelazer: yeah, that was fun indeed. With htop or conky with mem-usage running, you could &lt;strong&gt;see&lt;/strong&gt; the memory being swallowed. Here it was ~40MB every 30 seconds. That was a real WTF? moment.

juantxorena: python-2.5 has been in ~arch for ages, so that's not really the issue. Of course it would be nice if it got stabilized before the python3k release. ;-)

David: I agree these packages should be unmasked and belong in ~arch. But especially in the case of core packages like glibc, I would think it would be a smoother transition if the devs had been given advance warning to test their packages against this new version of glibc, before making all ~arch users into testers.

transacid: anything that has been compiled against the new glibc, will most likely refuse to work after a downgrade. While &lt;a href="http://gentoo-wiki.com/HOWTO_downgrade_glibc" rel="nofollow"&gt;technically it is possible&lt;/a&gt;, a glibc downgrade is a &lt;strong&gt;lot&lt;/strong&gt; of hassle.</description>
		<content:encoded><![CDATA[<p>Roguelazer: yeah, that was fun indeed. With htop or conky with mem-usage running, you could <strong>see</strong> the memory being swallowed. Here it was ~40MB every 30 seconds. That was a real WTF? moment.</p>
<p>juantxorena: python-2.5 has been in ~arch for ages, so that&#8217;s not really the issue. Of course it would be nice if it got stabilized before the python3k release. ;-)</p>
<p>David: I agree these packages should be unmasked and belong in ~arch. But especially in the case of core packages like glibc, I would think it would be a smoother transition if the devs had been given advance warning to test their packages against this new version of glibc, before making all ~arch users into testers.</p>
<p>transacid: anything that has been compiled against the new glibc, will most likely refuse to work after a downgrade. While <a href="http://gentoo-wiki.com/HOWTO_downgrade_glibc">technically it is possible</a>, a glibc downgrade is a <strong>lot</strong> of hassle.</p>
<img src="http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~4/311092057" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://ben.liveforge.org/2008/06/13/the-joy-of-updates#comment-141</feedburner:origLink></item>
	<item>
		<title>Comment on The joy of updates by transacid</title>
		<link>http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~3/311060089/the-joy-of-updates</link>
		<dc:creator>transacid</dc:creator>
		<pubDate>Fri, 13 Jun 2008 10:17:30 +0000</pubDate>
		<guid isPermaLink="false">http://ben.liveforge.org/?p=21#comment-140</guid>
		<description>"We had no such advance warning for glibc-2.8 though, and this is more troubling because there is no going back after upgrading glibc."
Really? Why isn't it possible to downgrade glibc? wouldn't an -e system &amp;&amp; -e world help?</description>
		<content:encoded><![CDATA[<p>&#8220;We had no such advance warning for glibc-2.8 though, and this is more troubling because there is no going back after upgrading glibc.&#8221;<br />
Really? Why isn&#8217;t it possible to downgrade glibc? wouldn&#8217;t an -e system &amp;&amp; -e world help?</p>
<img src="http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~4/311060089" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://ben.liveforge.org/2008/06/13/the-joy-of-updates#comment-140</feedburner:origLink></item>
	<item>
		<title>Comment on The joy of updates by David Philippi</title>
		<link>http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~3/311047136/the-joy-of-updates</link>
		<dc:creator>David Philippi</dc:creator>
		<pubDate>Fri, 13 Jun 2008 09:59:05 +0000</pubDate>
		<guid isPermaLink="false">http://ben.liveforge.org/?p=21#comment-139</guid>
		<description>Nice to know that pixman was what nearly killed my system. Got to a very slow crawling due to swap but I killed X fast enough.
For GCC, libtool and glibc - I'm happy about those getting unmasked. Did libtool quite some time ago as it's faster. They don't cause hard bugs, just a few header includes or a correct call to autotools but have real gains. Having those unmasked creates the required pressure to get things actually fixed, which may take a long time otherwise IMHO.</description>
		<content:encoded><![CDATA[<p>Nice to know that pixman was what nearly killed my system. Got to a very slow crawling due to swap but I killed X fast enough.<br />
For GCC, libtool and glibc - I&#8217;m happy about those getting unmasked. Did libtool quite some time ago as it&#8217;s faster. They don&#8217;t cause hard bugs, just a few header includes or a correct call to autotools but have real gains. Having those unmasked creates the required pressure to get things actually fixed, which may take a long time otherwise IMHO.</p>
<img src="http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~4/311047136" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://ben.liveforge.org/2008/06/13/the-joy-of-updates#comment-139</feedburner:origLink></item>
	<item>
		<title>Comment on The joy of updates by juantxorena</title>
		<link>http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~3/310990548/the-joy-of-updates</link>
		<dc:creator>juantxorena</dc:creator>
		<pubDate>Fri, 13 Jun 2008 06:04:26 +0000</pubDate>
		<guid isPermaLink="false">http://ben.liveforge.org/?p=21#comment-134</guid>
		<description>What about python-2.5? Another core package, rotting in bugzilla since 2006 because of lack of mantainers of some packages (2 or 3) and because being ignored by some arches (s390, sh and the rest) and by everybody else, who doesn't seem to care/know about that issue.</description>
		<content:encoded><![CDATA[<p>What about python-2.5? Another core package, rotting in bugzilla since 2006 because of lack of mantainers of some packages (2 or 3) and because being ignored by some arches (s390, sh and the rest) and by everybody else, who doesn&#8217;t seem to care/know about that issue.</p>
<img src="http://feeds.liveforge.org/~r/BitsByBen/comments/rss2/~4/310990548" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://ben.liveforge.org/2008/06/13/the-joy-of-updates#comment-134</feedburner:origLink></item>
</channel>
</rss>
