[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] HVM support to be removed from Debian Squeeze: call for volunteers


  • To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
  • From: Thomas Goirand <thomas@xxxxxxxxxx>
  • Date: Wed, 16 Dec 2009 01:14:34 +0800
  • Cc: Bastian Blank <waldi@xxxxxxxxxx>, Debian Xen Team <pkg-xen-devel@xxxxxxxxxxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 15 Dec 2009 09:14:57 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=goirand.fr; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=VG3 ksNBARu4bM1Jijnp0WzaS2MfDJIZNrE4dq0ImVv3hoYPe+YocQ0v9+XFDSAYg4bz GDWTgLyF6xRfVNCn7EPfOv5zj8B8yGSXa5IKe0KeDlX96NORKOfJsRsJlrd1Q1hG or/ucdP5piAyLSh6gBkp8hthlogY7hf0niKsLqzw=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Openpgp: id=98EF9A49

Ian Jackson wrote:
> Thomas Goirand writes ("[Xen-devel] HVM support to be removed from Debian 
> Squeeze: call for volunteers"):
>>  Someone that is willing to do this job of security
>> maintenance HAS to raise hand here,
> 
> Hello.  Yes, I volunteer (with my day job hat on).  I've done security
> patching before in other contexts.

Great.

>> Mainly, the work would be to have a script (or some Makefile entries
>> with DESTDIR= for example) that would install all needed files in
> 
> You mean in the upstream package ?  This isn't quite trivial but it
> should be doable.

To me, that's the most easy way, yes, because this avoids the
double-work of listing files to install (once in the "make install" and
once in the debian/install).

> There is a slight difficulty in that the filesystem layout of the
> Debian Xen packages is quite different to upstream's.

Yes, because Debian uses versionned folders for /usr/lib/xen. Maybe we
could overwrite this in the Makefile with a variable. That's what I did
for numerous projects so that "make install" could be used by a spec
file using "make install MANUAL_DIR=%{_mandir}" for example. What do you
think? Could this apply to this project?

> But partitioning the output of `make dist-tools' etc. to provide
> something that can be used for qemu-dm build should be easy enough.

What do you mean here here? What's the use of "make dist-tools"?

One of my issue is to create the .orig.tar.gz with only the relevant
code, I'm not sure where to start. Could you do that? Maybe add a target
to the "upstream" Makefile? How should we do it?

>> debian/xen-hvm-support (if we call that package xen-hvm-support). Also,
>> the source package should contain ONLY what is strictly concerning
>> Qemu-dm (not a big issue, but it would be cleaner this way and make the
>> source package smaller). As of now, I don't know who is maintaining Qemu
>> in Xen at all. Any volunteer here that would work with me does NOT need
>> to know anything about Debian or Debian packaging, but only about Qemu
>> and Xen itself.
> 
> I'm very happy to help out with this

Cool.

> [swaps hats]
> 
> Also, I am a Debian Developer although I haven't been very active in
> Debian recently.  I would be happy to sponsor uploads, provided they
> seemed sane to me.

Great.

>> I think that the best way here, is to build a (small, 3 or 4 persons)
>> team to work on this issue so it can be addressed fast.
> 
> Yes.
> 
> Regards,
> Ian.

Can you start a project on Alioth, with a git repo? Would it be useful
(I never used alioth or gforge yet)?

Thomas

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.