<?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: Testing the Current Upstream Linux Kernel</title>
	<atom:link href="http://news.opensuse.org/2007/08/15/testing-the-current-upstream-linux-kernel/feed/" rel="self" type="application/rss+xml" />
	<link>http://news.opensuse.org/2007/08/15/testing-the-current-upstream-linux-kernel/</link>
	<description>The latest stuff happening in the openSUSE universe</description>
	<pubDate>Thu, 16 Oct 2008 07:11:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: jengelh</title>
		<link>http://news.opensuse.org/2007/08/15/testing-the-current-upstream-linux-kernel/#comment-344</link>
		<dc:creator>jengelh</dc:creator>
		<pubDate>Fri, 24 Aug 2007 11:01:48 +0000</pubDate>
		<guid isPermaLink="false">http://news.opensuse.org/?p=137#comment-344</guid>
		<description>So install apparmor from factory.</description>
		<content:encoded><![CDATA[<p>So install apparmor from factory.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://news.opensuse.org/2007/08/15/testing-the-current-upstream-linux-kernel/#comment-294</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 17 Aug 2007 16:20:37 +0000</pubDate>
		<guid isPermaLink="false">http://news.opensuse.org/?p=137#comment-294</guid>
		<description>I am using the repo for 10.2. As of 2.6.23_rc3_g28e8351a-32.1 apparmor-parser and apparmor-profiles conflicts with kernel-default. Also, perl-Bootloader from http://download.opensuse.org/repositories/home:/dirkmueller/openSUSE_10.2/i586/ is a required dependency. 

Sure, kernel bugs should be reported upstream, but what about packaging ones? I'd like to see seamless integration with the current version of openSUSE and the upstream development kernel.</description>
		<content:encoded><![CDATA[<p>I am using the repo for 10.2. As of 2.6.23_rc3_g28e8351a-32.1 apparmor-parser and apparmor-profiles conflicts with kernel-default. Also, perl-Bootloader from <a href="http://download.opensuse.org/repositories/home:/dirkmueller/openSUSE_10.2/i586/" rel="nofollow">http://download.opensuse.org/repositories/home:/dirkmueller/openSUSE_10.2/i586/</a> is a required dependency. </p>
<p>Sure, kernel bugs should be reported upstream, but what about packaging ones? I&#8217;d like to see seamless integration with the current version of openSUSE and the upstream development kernel.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nikolay Derkach</title>
		<link>http://news.opensuse.org/2007/08/15/testing-the-current-upstream-linux-kernel/#comment-286</link>
		<dc:creator>Nikolay Derkach</dc:creator>
		<pubDate>Thu, 16 Aug 2007 11:06:31 +0000</pubDate>
		<guid isPermaLink="false">http://news.opensuse.org/?p=137#comment-286</guid>
		<description>This is likely because you are using openSUSE 10.2.
Try this repo: http://download.opensuse.org/repositories/Kernel:/Vanilla/openSUSE_10.2/</description>
		<content:encoded><![CDATA[<p>This is likely because you are using openSUSE 10.2.<br />
Try this repo: <a href="http://download.opensuse.org/repositories/Kernel:/Vanilla/openSUSE_10.2/" rel="nofollow">http://download.opensuse.org/repositories/Kernel:/Vanilla/openSUSE_10.2/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://news.opensuse.org/2007/08/15/testing-the-current-upstream-linux-kernel/#comment-278</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 15 Aug 2007 17:35:30 +0000</pubDate>
		<guid isPermaLink="false">http://news.opensuse.org/?p=137#comment-278</guid>
		<description>Unfortunately, apparmor-parser and apparmor-profiles conflict with the upstream development kernel. How difficult would it be to have these working as well?</description>
		<content:encoded><![CDATA[<p>Unfortunately, apparmor-parser and apparmor-profiles conflict with the upstream development kernel. How difficult would it be to have these working as well?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
