[Pkg-xen-devel] Re: [Pkg-xen-changes] r70 - trunk/xen-3.0/debian

[Ralph Passgang]

Am Samstag, 4. März 2006 13:45 schrieb Julien Danjou:
> On Fri, Mar 03, 2006 at 06:08:49PM +0000, Ralph Passgang wrote:
> > - Added the xen package again, because we believe there is a valid
> >   upgrade procedure. This helps the user to easily upgrade a xen2 system
> >   and to install a complete xen system (consisting of hypervisor & tools)
> >   by installing the xen "meta-package".
>
> Bastian, why did you remove this package in your last commit?

I would like to have an explanation for that too. We believe we don't need to 
remove this package (at least now where all problems with upgrading from 
older versions have been fixed) and it helps to have a setup that is easy to 
setup for new users (because they only need to run: "apt-get install xen") 
and even it helps for upgrading a xen2 setup to xen3.

Maybe there also other solutions, what about renaming the "xen" package to 
"xen-3.0" and providing "xen" within "xen-3.0"?

Please explain at least why you think this is wrong. We are a team, so we 
should discuss such stuff. I also tried to explain why I added the xen 
package again in my svn comment, please also use this svn log more. just 
"updated control" is a absolout useless comment, because the information 
which files you updated is obvious.
 
And your changes in the last svn commits were quite massive! I haven't looked 
at each change for now, but my first impression is, that some of these 
changes are really good, but some others I don't understand really (but I may 
just need some time to understand it better), some others may cause trouble.

for example there are two entries for "xen-utils-3.0" in debian/control now. 
Or why do you cross-compile hypervisors? I always had problems with this, even 
if you found a working solution to compile 64bit hypervisors on i386 and the 
other way round, there is a problem with that:
If you use a 64bit hypervisor you have to use a 64bit dom0 kernel and you have 
to use 64bit version of xen userspace tools. So just compiling 64bit 
hypervisor on i386 doesn't help as long as you don't provide also 64bit 
userspace tools. Same the other way around, image someone compiles the 
package on a amd64 host and installs the 32bit hypervisor and a 32bit dom0 
kernel then. He will not be able to use the userspace tools, because he 
compiled the 64bit version.

And the rules files seems to be broken in some places, because when I try to 
compile xen with the debian dir with all svn commits from you, I have this 
error at the end:

cp: cannot stat `debian/tmp//usr/share/doc/xen/examples': No such file or 
directory
dh_install: command returned error code 256
make: *** [install-tools] Error 1

I think there are some more svn commits needed to fix these new problems.

-- Ralph