Le mercredi 03 janvier 2007 14:41, Vincent Panel a écrit : > On 1/3/07, Guillaume Rousse <[EMAIL PROTECTED]> wrote: > > Since I started testing xen on mandriva one month ago, I keep > > discovering various issues, such as: > > - documentation not build (#27620) > > - lack of libvnc support, preventing HVM usage (#27652) > > - wrong default network configuration [#27674) > > - kernel package not creating correct initrd or source symlinks (#27617) > > - outdated package (not even final 3.0.3) > > - etc... > > > > Whereas making errors happens to everyone, I'm quite concerned that > > despite reporting every issue with bugzilla, I had absolutly no response > > sofar from maintainer, Arnaud... And as the package is protected by SVN > > ACLs, I can't even fix those issues by myself. Once again, kernel team > > preference for private developement method hampers overall quality, > > rather than improving it. I'm curious about CS4, which is supposed to be > > 'virtualisation-ready'... > > > > Now, what can we do for improving the situation ? I'd like Arnaud to > > manifest himself once for a while. Otherwise, maybe we could start a > > parallel xen packaging, with another xen package in contrib, and the xen > > patch integrated into some non-official kernel ? I hate duplicating > > work, but I don't really see any other situation. > > I vote for a fixed forked contrib package if you don't have an answer > within one month.
Given the fact xen package is not the only package suffering from this kind of problem ( ie locked by someone with a limited time to devote to the packaging ), maybe a more direct approach with a dedicated repository hosted somewhere else would yield more visible results. From a technical point of view, since we now use svn for whole packages, we have much more technical possiblity for forking and merging changes, even if, in the case of some packages, there is no merging to be done. And we also have mature tools to handle repository, like youri ( http://youri.zarb.org ), the only thing that lack is someone to handle it. -- Michael Scherer
