diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-November/009524.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-November/009524.html | 216 |
1 files changed, 216 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-November/009524.html b/zarb-ml/mageia-dev/2011-November/009524.html new file mode 100644 index 000000000..ea6ad0e87 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-November/009524.html @@ -0,0 +1,216 @@ +<!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%09move%20from%20qemu-kvm%20to%20qemu%3F&In-Reply-To=%3C201111141553.43885.bgmilne%40staff.telkomsa.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="009511.html"> + <LINK REL="Next" HREF="009574.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>Buchan Milne</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%09move%20from%20qemu-kvm%20to%20qemu%3F&In-Reply-To=%3C201111141553.43885.bgmilne%40staff.telkomsa.net%3E" + TITLE="[Mageia-dev] qemu new upstream release (1.0-rc1) and should we move from qemu-kvm to qemu?">bgmilne at staff.telkomsa.net + </A><BR> + <I>Mon Nov 14 14:53:43 CET 2011</I> + <P><UL> + <LI>Previous 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>Next message: <A HREF="009574.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#9524">[ date ]</a> + <a href="thread.html#9524">[ thread ]</a> + <a href="subject.html#9524">[ subject ]</a> + <a href="author.html#9524">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Sunday, 13 November 2011 23:32:45 Kamil Rytarowski wrote: +><i> On 13.11.2011 10:58, Michael Scherer wrote: +</I>><i> > Le samedi 12 novembre 2011 à 21:11 +0100, Kamil Rytarowski a écrit : +</I>><i> >> On 12.11.2011 20:20, Michael Scherer wrote: +</I>><i> >>> Le samedi 12 novembre 2011 à 16:44 +0100, Kamil Rytarowski a écrit : +</I>><i> >>>> There is also one important patch missed in Mageia - +</I>><i> >>>> <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> +</I>><i> >>>> it's dependency for the GNS3 simulator. OpenSUSE already includes it +</I>><i> >>>> <A HREF="https://build.opensuse.org/package/files?package=qemu&project=openSUS">https://build.opensuse.org/package/files?package=qemu&project=openSUS</A> +</I>><i> >>>> E%3ATools +</I>><i> >>>> +</I>><i> >>>> If nobody is against I will do it and contact the maintainer (misc). +</I>><i> >>> +</I>><i> >>> I prefer to wait on the stable release ( ie, no rc1 ). +</I>><i> >>> We will wait on stable version of qemu. +</I>><i> >> +</I>><i> >> OK +</I>><i> >> +</I>><i> >>> And no patch unless it comes from upstream ( and even, I am not keen on +</I>><i> >>> backporting feature, better wait for stable release ). +</I>><i> >> +</I>><i> >> GNS3 is already in stable! This package is broken - no dynamips (=no +</I>><i> >> router emulation at all...), no patched qemu (no virtualization support +</I>><i> >> at all...) According to the developers and their online documentation +</I>><i> >> for package maintainers <A HREF="http://forum.gns3.net/post11571.html">http://forum.gns3.net/post11571.html</A> UDP patched +</I>><i> >> Qemu is dependency/very important. +</I>><i> > +</I>><i> > The fact that someone pushed a broken package is not a good reason to +</I>><i> > add patches to qemu. +</I>><i> +</I>><i> OK, but I don't understand this. +</I>><i> +</I>><i> Why to keep defunct packages (this could be at least "major+ issue" on +</I>><i> our bugzilla) in stable and don't even want to fix, ignore this academic +</I>><i> software (with maybe overall 1 000 000* downloads and 100 000 regular +</I>><i> users), and to support... the inadvisable opinion of Mageia around.. at +</I>><i> least the GNS3 users. +</I>><i> +</I>><i> * 799 968 Windows Downloads (just from the sourceforge mirrors) of the +</I>><i> latest Windows binary of GNS3 (source +</I>><i> <A HREF="http://sourceforge.net/projects/gns-3/files/GNS3/0.7.4/">http://sourceforge.net/projects/gns-3/files/GNS3/0.7.4/</A>) +</I>><i> +</I>><i> > We have too many patches on a general scale, and I +</I>><i> > do not want to end with a 2nd package like gdb. +</I>><i> > +</I>><i> > Patches make harder to upgrade, harder to make sure security is done +</I>><i> > correctly, and harder to ensure stuff are working ( since we are on our +</I>><i> > own when we patch something ). +</I>><i> > So for the patches, make sure it is upstream +</I>><i> +</I>><i> It's not qemu upstream, it's GNS3 and its community upstream. +</I>><i> +</I>><i> > ( and given the discussion +</I>><i> > +</I>><i> > on ml, it should be soon ) +</I>><i> +</I>><i> When I ask the developers, they don't know if qemu will include the +</I>><i> patch at all and when (now or after one year) and they suggested to do +</I>><i> the openSUSE way (today the most recommended and full featured Linux +</I>><i> distro for GNS3). +</I> +[...] + +><i> +</I>><i> OK. So if gns3 can't be fixed for the stable - than should be removed +</I>><i> from the repos (for ISOs is to late). +</I>><i> +</I>><i> If we don't provide qemu patch, then gns3 should be removed from +</I>><i> Cauldron as well. +</I>><i> +</I>><i> I believe removing GNS3 is better than keeping it broken and.. irritate +</I>><i> people (I don't count the opinion of our quality). Later some 3rd party +</I>><i> repos can provide GNS3 and its dependencies. +</I> +You seem to imply that the only use of GNS3 is with this qemu patch. + +But I used GNS3 with just dynamips, and this issue of GNS3 not being usable at +all due to missing dynamips can really be solved quite quickly just by +shipping dynamips to updates. + +But, it looks like someone blindly imported gns3 and dynagen from Mandriva +without even understanding the use of these tools: + +$ rpm -q --suggests dynagen +dynamips >= 0.2.8 +xterm + +(dynamips isn't explicitly required to be installed on the host with gns3 or +dynagen, as the hypervisor can be run on a different host than dynagen/GNS3). + +Regards, +Buchan +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous 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>Next message: <A HREF="009574.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#9524">[ date ]</a> + <a href="thread.html#9524">[ thread ]</a> + <a href="subject.html#9524">[ subject ]</a> + <a href="author.html#9524">[ 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> |