summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-November/009506.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-November/009506.html')
-rw-r--r--zarb-ml/mageia-dev/2011-November/009506.html173
1 files changed, 173 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-November/009506.html b/zarb-ml/mageia-dev/2011-November/009506.html
new file mode 100644
index 000000000..aee04c286
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-November/009506.html
@@ -0,0 +1,173 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] qemu new upstream release (1.0-rc1) and should we move from qemu-kvm to qemu?
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20qemu%20new%20upstream%20release%20%281.0-rc1%29%20and%20should%20we%0A%20move%20from%20qemu-kvm%20to%20qemu%3F&In-Reply-To=%3C1321178295.14147.10.camel%40localhost%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="009503.html">
+ <LINK REL="Next" HREF="009511.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] qemu new upstream release (1.0-rc1) and should we move from qemu-kvm to qemu?</H1>
+ <B>Michael Scherer</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20qemu%20new%20upstream%20release%20%281.0-rc1%29%20and%20should%20we%0A%20move%20from%20qemu-kvm%20to%20qemu%3F&In-Reply-To=%3C1321178295.14147.10.camel%40localhost%3E"
+ TITLE="[Mageia-dev] qemu new upstream release (1.0-rc1) and should we move from qemu-kvm to qemu?">misc at zarb.org
+ </A><BR>
+ <I>Sun Nov 13 10:58:15 CET 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="009503.html">[Mageia-dev] qemu new upstream release (1.0-rc1) and should we move from qemu-kvm to qemu?
+</A></li>
+ <LI>Next message: <A HREF="009511.html">[Mageia-dev] qemu new upstream release (1.0-rc1) and should we move from qemu-kvm to qemu?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#9506">[ date ]</a>
+ <a href="thread.html#9506">[ thread ]</a>
+ <a href="subject.html#9506">[ subject ]</a>
+ <a href="author.html#9506">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le samedi 12 novembre 2011 &#224; 21:11 +0100, Kamil Rytarowski a &#233;crit :
+&gt;<i> On 12.11.2011 20:20, Michael Scherer wrote:
+</I>&gt;<i> &gt; Le samedi 12 novembre 2011 &#224; 16:44 +0100, Kamil Rytarowski a &#233;crit :
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt;&gt; There is also one important patch missed in Mageia -
+</I>&gt;<i> &gt;&gt; <A HREF="http://lists.gnu.org/archive/html/qemu-devel/2011-11/msg00787.html">http://lists.gnu.org/archive/html/qemu-devel/2011-11/msg00787.html</A> it's
+</I>&gt;<i> &gt;&gt; dependency for the GNS3 simulator. OpenSUSE already includes it
+</I>&gt;<i> &gt;&gt; <A HREF="https://build.opensuse.org/package/files?package=qemu&amp;project=openSUSE%3ATools">https://build.opensuse.org/package/files?package=qemu&amp;project=openSUSE%3ATools</A>
+</I>&gt;<i> &gt;&gt;
+</I>&gt;<i> &gt;&gt; If nobody is against I will do it and contact the maintainer (misc).
+</I>&gt;<i> &gt; I prefer to wait on the stable release ( ie, no rc1 ).
+</I>&gt;<i> &gt; We will wait on stable version of qemu.
+</I>&gt;<i> OK
+</I>&gt;<i> &gt; And no patch unless it comes from upstream ( and even, I am not keen on
+</I>&gt;<i> &gt; backporting feature, better wait for stable release ).
+</I>&gt;<i> &gt;
+</I>&gt;<i> GNS3 is already in stable! This package is broken - no dynamips (=no
+</I>&gt;<i> router emulation at all...), no patched qemu (no virtualization support
+</I>&gt;<i> at all...) According to the developers and their online documentation
+</I>&gt;<i> for package maintainers <A HREF="http://forum.gns3.net/post11571.html">http://forum.gns3.net/post11571.html</A> UDP patched
+</I>&gt;<i> Qemu is dependency/very important.
+</I>
+The fact that someone pushed a broken package is not a good reason to
+add patches to qemu. We have too many patches on a general scale, and I
+do not want to end with a 2nd package like gdb.
+
+Patches make harder to upgrade, harder to make sure security is done
+correctly, and harder to ensure stuff are working ( since we are on our
+own when we patch something ).
+
+So for the patches, make sure it is upstream ( and given the discussion
+on ml, it should be soon ) and then in a tarball ( again, given that's a
+rc 1, that should be ok soon ).
+
+&gt;<i> We must fix the package and provide at least not so heavy broken ones...
+</I>&gt;<i>
+</I>&gt;<i> I've prepared new version of GNS3, included into svn dynamips and
+</I>&gt;<i> xdotool (this one suggested) - these I can maintain with my mentor, so I
+</I>&gt;<i> ask for patch qemu in stable versus UDP support.
+</I>
+Updates are not supposed to get new features, so that's no. And again,
+maybe people could do more tests before pushing broken rpm to stable
+( like gsn3 ).
+--
+Michael Scherer
+
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="009503.html">[Mageia-dev] qemu new upstream release (1.0-rc1) and should we move from qemu-kvm to qemu?
+</A></li>
+ <LI>Next message: <A HREF="009511.html">[Mageia-dev] qemu new upstream release (1.0-rc1) and should we move from qemu-kvm to qemu?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#9506">[ date ]</a>
+ <a href="thread.html#9506">[ thread ]</a>
+ <a href="subject.html#9506">[ subject ]</a>
+ <a href="author.html#9506">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
+mailing list</a><br>
+</body></html>