[Pkg-xen-devel] Re: [Pkg-xen-changes] r24 - trunk/debian/patches

[Guido Trotter]

On Sun, Feb 19, 2006 at 01:31:17AM +0100, Ralph Passgang wrote:

Hi,

> it's working at least as good as my version, but to check the pae-hypervisor 
> in combination with the normal user-space tools I need to wait till monday, 
> because I have some pae-compatible systems at work to really test these 
> changes.
> 

Ok, great! We'll wait for the results!

> the only difference between your version and my patch is that your version 
> will install some .h files to /usr/include/xen again that already were copied 
> with the "make dist" call before. My patch didn't do this, but because the 
> files are identical that should be no problem at all (but only compiling the 
> pae version would result in less .h files (which seems to be an upstream 
> issue)).
> 

Strange... ;)

> and another question, wouldn't it be better to also use "Debian Xen Team 
> <pkg-xen-devel at lists.alioth.debian.org>" (or something like that) in the 
> changelog? We don't need the information who changed the package for 
> ourselves, because we use svn. But for the real release using the team 
> emailadress might help to have users mail to the list instead to just one 
> person. I also saw that for other packages like kde.
> 

Well, it's in the maintainer field, which is the most important piece of
information... As for the changelog, I was actually under the impression that we
needed a DD's name there (the name of the one who actually makes the upload), so
he could sign the changes. My impresson was due to the fact that most other
cooperatively maintained packages do it like that (apache2, glibc,
debian-policy, just to name a few...). Since for example kde and gnome guys do
it like you say it's probably possible to do it that way too, and my impression
was wrong... I guess other people do it just because it's convenient for them to
have dch manage that line, so that it updates the date, dpkg-buildpackage and
debsign automatically find the developer key if it's being compiled on a host
that has them, etc... And information on who changed what is already in the
changelog (for changes that only one of us made, the others are before them), so
that line is only useful to track who uploaded the package, I think...

On the other hand I think that people will bug either the bts (which will send
to this list) or the maintainer (which is set to this list) and not the
individual uploader, so we should be fine...

Open to comments, anyway! ;)

Guido