From: Thomas Goirand <thomas@goirand.fr>
To: Xen-devel <xen-devel@lists.xensource.com>
Subject: Is Xen support in Debian going to nowhere?
Date: Wed, 31 Mar 2010 01:51:25 +0800 [thread overview]
Message-ID: <4BB23A1D.2000406@goirand.fr> (raw)
Hi there,
If you didn't see it, you should read the thread "Xen, Squeeze, and
Beyond" on the debian-devel list that you may have missed:
http://lists.debian.org/debian-devel/2010/02/thrd2.html#00653
http://lists.debian.org/debian-devel/2010/03/threads.html#00005
This clearly shows you what I told you about the lack of support for Xen
in Debian. What I see is that there's more a lack of communication than
anything else.
Debian is like no others distribution, if nobody cares doing the dirty
work of packaging, some software can go away from the archive, simply
because of the lack of task force. The disaster of the Lenny dom0 with
no upstream support should be avoided at all costs, and the only way to
do so is by having people working on Xen involved in Debian. Otherwise,
the Debian kernel team will simply hate working on maintaining a Xen
dom0 (which is already the case, I believe).
Any lack of responsiveness of everyone can lead to nowhere. I feel it's
a shame that nobody from this list stood in this thread to say that he
will help the kernel team this time, so that the Debian kernel team can
feel there's a real support from "upstream".
Thomas
P.S: Of course, everyone knows that if the patches from J. are finally
accepted, all issues are over, but betting that this will happen before
Squeeze is released is a very dangerous bet.
next reply other threads:[~2010-03-30 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 17:51 Thomas Goirand [this message]
2010-03-30 18:08 ` Is Xen support in Debian going to nowhere? Konrad Rzeszutek Wilk
2010-03-30 18:11 ` Ian Campbell
2010-03-30 18:19 ` Thomas Goirand
2010-03-30 19:14 ` Martinx - ジェームズ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BB23A1D.2000406@goirand.fr \
--to=thomas@goirand.fr \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).