[Pkg-xen-devel] Bug#655301: Bug#655301: Status check for Wheezy

[Thomas Goirand]

On 02/29/2012 06:53 PM, Ritesh Raj Sarraf wrote:
> I did
> notice that I do not have anything in /etc/default/xen.
> 
> lnx200-39:/etc/init.d# cat /etc/default/xen
> # Configuration for Xen system
> # ----------------------------
> 
> # There exists several tool stacks to configure a Xen system.
> # …
> # Attention: You need to reboot after changing this!
> TOOLSTACK=

My understanding is that this should be treated as if you had "xm". I
already proposed a patch for this almost a month ago, as well as a
debconf solution for it, but it's still sitting in the Xen devel list,
with apparently no action from Waldi.

If others agree, I can upload a new version of Xen with the fix though,
at least for fixing the init.d script (which is the most urgent fix).

Here's the list of things that needs to be addressed though:
1- /etc/init.d/xendomains needs to be fixed to understand xl and xe.
2- We need a debconf thing for setting the correct value in
/etc/default/xen, with xm, xl or xe as valid values (please, nothing
else!!!)
3- /etc/init.d/xend needs to be fixed to start xend only if xm (or an
empty value) is set in /etc/default/xen
4- We need xe to check the value of the TOOLSTACK variable (xm and xl
are doing that already)
5- We need a wrapper around xm, so that we keep compatibility with older
software (IMHO).

I've already sent patches for 2- and 3-, which haven't received any
critics so far (they did in the past, but it was fixed). It's been a
loooong time these are ready.

The thing is, I'd like to do more, but I don't want to step on Waldi's
feet, and upload without his approval.

Using SVN for the packaging of Xen is also a blocker for me (I never
really learned it), and I'd like to move Xen packaging to Git, but I
never received a green light to start that work (neither a refusal
either by the way).

What do you think? Should I upload a fix? Should I switch Xen packaging
to Git?

Thomas