On 04/29/2011 01:02 AM, Niccolò Belli wrote:
> Il 28/04/2011 16:55, Thomas Goirand ha scritto:
>> Bastian, I just saw you did an upload, does this include the above fix
>> (eg, inclusion of xentoollog.h)? Should I write a bug report?
> I fear you wasted your time trying to fix qemu-dm :|
Not *trying*, it's done, and I was setting-up a test environment...
> xen (4.1.0-3) unstable; urgency=low
> * Add ghostscript to build-deps.
> * Enable qemu-dm build.
> - Add qemu as another orig tar.
> - Remove blktap1, bluetooth and sdl support from qemu.
> - Recommend qemu-keymaps and qemu-utils.
> -- Bastian Blank <email@example.com> Thu, 28 Apr 2011 15:20:45 +0200
That's totally unbelievable... No communication. Just an upload, and I
discover what happens, after I'm done with my work. What changed in
Bastian mind so that what he wrote in July 2009:
"I refuse to maintain the security-hog called qemu for the next stable
release, so it can only come from a different source package."
isn't valid anymore? Nobody will ever know, as there's no communication
on Bastian side.
Also, there are issues on the package:
- Why is sdl support removed?
- The ROM bios of the tool directory aren't built, aren't shipped, and
they ARE different from the normal qemu.
- no dependencies on PXE ROMs and others, so I am guessing it wont ever
work or start with network support. Of course, no symlink to the
- The debian/copyright of Xen mention the authors of Qemu, but not the
licenses (multiple types, very complicated mix).
- no support for sound backends (pulse, esd, alsa...), which can be
considered a regression.
- debian/xen-utils.NEWS still mentions that qemu isn't supported.
Words are missing to express the feeling I have with this...
Bastian, why are you refusing team work and communication? Why isn't
your packaging work shared in a VCS? I really don't get it...
Thomas Goirand (zigo)
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org