<?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 for Wolfgang's blog</title>
	<atom:link href="http://www.rosenauer.org/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rosenauer.org/blog</link>
	<description>Just another weblog</description>
	<pubDate>Wed, 20 Aug 2008 07:20:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>Comment on Firefox 3.0 and openSUSE 11.0 by cjk</title>
		<link>http://www.rosenauer.org/blog/2008/05/24/firefox-30-and-opensuse-110/#comment-7771</link>
		<dc:creator>cjk</dc:creator>
		<pubDate>Fri, 30 May 2008 15:21:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.rosenauer.org/blog/?p=29#comment-7771</guid>
		<description>Speaking of numbers moving faster than others: for years now, release numbers in the normal tree (e.g. /10.2/suse/i586) have sometimes been higher than those in the update tree (update/10.2/rpm/i586) creating a lot of confusion which of the ones the real update actually is.</description>
		<content:encoded><![CDATA[<p>Speaking of numbers moving faster than others: for years now, release numbers in the normal tree (e.g. /10.2/suse/i586) have sometimes been higher than those in the update tree (update/10.2/rpm/i586) creating a lot of confusion which of the ones the real update actually is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Firefox 3.0 and openSUSE 11.0 by Administrator</title>
		<link>http://www.rosenauer.org/blog/2008/05/24/firefox-30-and-opensuse-110/#comment-7752</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Thu, 29 May 2008 16:53:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.rosenauer.org/blog/?p=29#comment-7752</guid>
		<description>That's bad but just means that release numbers in Factory are counting faster than in the OBS repository :-( The mozilla-nss package in OBS is indeed quite newer than the one in Factory (it has been updated yesterday to the latest NSS tag to feature FF3.0rc2).
Anyway in the meantime I figured that having the crypto source code in a package is enough for the limitations to be applied :-(</description>
		<content:encoded><![CDATA[<p>That&#8217;s bad but just means that release numbers in Factory are counting faster than in the OBS repository <img src='http://www.rosenauer.org/blog/wp-includes/images/smilies/icon_sad.gif' alt=':-(' class='wp-smiley' /> The mozilla-nss package in OBS is indeed quite newer than the one in Factory (it has been updated yesterday to the latest NSS tag to feature FF3.0rc2).<br />
Anyway in the meantime I figured that having the crypto source code in a package is enough for the limitations to be applied <img src='http://www.rosenauer.org/blog/wp-includes/images/smilies/icon_sad.gif' alt=':-(' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Firefox 3.0 and openSUSE 11.0 by cjk</title>
		<link>http://www.rosenauer.org/blog/2008/05/24/firefox-30-and-opensuse-110/#comment-7751</link>
		<dc:creator>cjk</dc:creator>
		<pubDate>Thu, 29 May 2008 16:46:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.rosenauer.org/blog/?p=29#comment-7751</guid>
		<description>There were no dependencies except xulrunner190 that had to be updated as part of moving from 3.0b5 -&#62; 3.0rc1, so the crypto argument sounds moot to me—unless the crypto is in xul, which I do not think, it's in mozilla-nss.</description>
		<content:encoded><![CDATA[<p>There were no dependencies except xulrunner190 that had to be updated as part of moving from 3.0b5 -&gt; 3.0rc1, so the crypto argument sounds moot to me—unless the crypto is in xul, which I do not think, it&#8217;s in mozilla-nss.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Firefox 3.0 and openSUSE 11.0 by Sandy</title>
		<link>http://www.rosenauer.org/blog/2008/05/24/firefox-30-and-opensuse-110/#comment-7682</link>
		<dc:creator>Sandy</dc:creator>
		<pubDate>Sun, 25 May 2008 14:40:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.rosenauer.org/blog/?p=29#comment-7682</guid>
		<description>Firefox is probably the most used and most tested application in openSUSE 11.  This seems worth making an exception (should be really easy to catch regressions).  RC1 fixes many Beta5 bugs that make popular web apps like GMail *very* slow.  Believe it or not, many users are going to judge openSUSE 11 based on their browsing experience.

Please keep this in mind!</description>
		<content:encoded><![CDATA[<p>Firefox is probably the most used and most tested application in openSUSE 11.  This seems worth making an exception (should be really easy to catch regressions).  RC1 fixes many Beta5 bugs that make popular web apps like GMail *very* slow.  Believe it or not, many users are going to judge openSUSE 11 based on their browsing experience.</p>
<p>Please keep this in mind!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Firefox 3.0 and openSUSE 11.0 by Me</title>
		<link>http://www.rosenauer.org/blog/2008/05/24/firefox-30-and-opensuse-110/#comment-7668</link>
		<dc:creator>Me</dc:creator>
		<pubDate>Sat, 24 May 2008 12:07:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.rosenauer.org/blog/?p=29#comment-7668</guid>
		<description>&#62; And about your second statement: Yes, the crypto stuff gets updated
&#62; then but you also can see how to test the latest stuff and it’s not like it
&#62; was a major update or so. So far there are not a lot of changes in NSS
&#62; between current and beta version.
Ok. I have no problems with NSS being updated, I use the packages from the OBS and still I'm confident they are safe enough. I was just confused for not being updated before release and being updated after release... US export regulations explain it.

I thought these export regulations were from the PGP/Zimmermann times. I don't think today makes any sense... I'm sure North Korea already has any information they could obtain from consumer software.</description>
		<content:encoded><![CDATA[<p>&gt; And about your second statement: Yes, the crypto stuff gets updated<br />
&gt; then but you also can see how to test the latest stuff and it’s not like it<br />
&gt; was a major update or so. So far there are not a lot of changes in NSS<br />
&gt; between current and beta version.<br />
Ok. I have no problems with NSS being updated, I use the packages from the OBS and still I&#8217;m confident they are safe enough. I was just confused for not being updated before release and being updated after release&#8230; US export regulations explain it.</p>
<p>I thought these export regulations were from the PGP/Zimmermann times. I don&#8217;t think today makes any sense&#8230; I&#8217;m sure North Korea already has any information they could obtain from consumer software.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Firefox 3.0 and openSUSE 11.0 by Administrator</title>
		<link>http://www.rosenauer.org/blog/2008/05/24/firefox-30-and-opensuse-110/#comment-7666</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Sat, 24 May 2008 11:42:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.rosenauer.org/blog/?p=29#comment-7666</guid>
		<description>There were several reasons for that decision:
1. Firefox' roadmap wasn't fixed and FF3 was expected much earlier
2. The last stable version is 2.0.0.x and most people would complain having that version instead of a new major version which was released even before the upcoming openSUSE version will be released.
3. Once openSUSE 11.0 is released people want to run an update anyway and will get the latest greated (final) Firefox version</description>
		<content:encoded><![CDATA[<p>There were several reasons for that decision:<br />
1. Firefox&#8217; roadmap wasn&#8217;t fixed and FF3 was expected much earlier<br />
2. The last stable version is 2.0.0.x and most people would complain having that version instead of a new major version which was released even before the upcoming openSUSE version will be released.<br />
3. Once openSUSE 11.0 is released people want to run an update anyway and will get the latest greated (final) Firefox version</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Firefox 3.0 and openSUSE 11.0 by enrico</title>
		<link>http://www.rosenauer.org/blog/2008/05/24/firefox-30-and-opensuse-110/#comment-7665</link>
		<dc:creator>enrico</dc:creator>
		<pubDate>Sat, 24 May 2008 11:15:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.rosenauer.org/blog/?p=29#comment-7665</guid>
		<description>Why realise openSUSE 11.0 with a beta version of Firefox? I think it should be better to stay with teh last stable version...
The browser is an important part for the secutity of a OS. I'll never feel secure to committ a bank transition with a browser in its beta or RC version...</description>
		<content:encoded><![CDATA[<p>Why realise openSUSE 11.0 with a beta version of Firefox? I think it should be better to stay with teh last stable version&#8230;<br />
The browser is an important part for the secutity of a OS. I&#8217;ll never feel secure to committ a bank transition with a browser in its beta or RC version&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Firefox 3.0 and openSUSE 11.0 by Administrator</title>
		<link>http://www.rosenauer.org/blog/2008/05/24/firefox-30-and-opensuse-110/#comment-7663</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Sat, 24 May 2008 09:06:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.rosenauer.org/blog/?p=29#comment-7663</guid>
		<description>crypto freeze is needed because of US export regulations. Don't ask me for details but I understand that every export of cryptographic software has to be approved from US authorities (you know Novell is a US company).
And about your second statement: Yes, the crypto stuff gets updated then but you also can see how to test the latest stuff and it's not like it was a major update or so. So far there are not a lot of changes in NSS between current and beta version.</description>
		<content:encoded><![CDATA[<p>crypto freeze is needed because of US export regulations. Don&#8217;t ask me for details but I understand that every export of cryptographic software has to be approved from US authorities (you know Novell is a US company).<br />
And about your second statement: Yes, the crypto stuff gets updated then but you also can see how to test the latest stuff and it&#8217;s not like it was a major update or so. So far there are not a lot of changes in NSS between current and beta version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Firefox 3.0 and openSUSE 11.0 by Me</title>
		<link>http://www.rosenauer.org/blog/2008/05/24/firefox-30-and-opensuse-110/#comment-7662</link>
		<dc:creator>Me</dc:creator>
		<pubDate>Sat, 24 May 2008 08:46:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.rosenauer.org/blog/?p=29#comment-7662</guid>
		<description>I must admit I don't really understand the situation.
Why there is a "crypto freeze"? I suppose it's to have time to test (the important) cryptographic algorithms. But then are you saying that these cryptographic algorithms that have been so tested in betas... are going to be updated the first day openSUSE is released???</description>
		<content:encoded><![CDATA[<p>I must admit I don&#8217;t really understand the situation.<br />
Why there is a &#8220;crypto freeze&#8221;? I suppose it&#8217;s to have time to test (the important) cryptographic algorithms. But then are you saying that these cryptographic algorithms that have been so tested in betas&#8230; are going to be updated the first day openSUSE is released???</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on XULRunner 1.9 / Firefox 3.0b3 by Administrator</title>
		<link>http://www.rosenauer.org/blog/2008/02/29/xulrunner-19-firefox-30b3/#comment-6156</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Thu, 13 Mar 2008 18:08:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.rosenauer.org/blog/2008/02/29/xulrunner-19-firefox-30b3/#comment-6156</guid>
		<description>Ahh, that was an issue in one of the earlier builds. Please get the latest one. It has libjemalloc.so built in.</description>
		<content:encoded><![CDATA[<p>Ahh, that was an issue in one of the earlier builds. Please get the latest one. It has libjemalloc.so built in.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
