similar to: r14 - trunk/debian

I just also wanted to mention that I have the current released source tarballs downloaded and placed at http://people.debian.org/~jbouse/xen/ at this time. As the only way to get the source tarballs I've found is via bittorrent unless you want to give your email address I'll continue to keep the the current tarball located there. That is one thing that I noticed about Ralph's

Author: acid Date: 2006-02-16 10:45:13 +0000 (Thu, 16 Feb 2006) New Revision: 3 Modified: trunk/changelog trunk/control Log: - Change maintainer and add uploaders field - Prepare changelog for new upload Modified: trunk/changelog =================================================================== --- trunk/changelog 2006-02-15 23:05:09 UTC (rev 2) +++ trunk/changelog 2006-02-16 10:45:13

Author: tha-guest Date: 2006-03-03 18:08:48 +0000 (Fri, 03 Mar 2006) New Revision: 70 Modified: trunk/xen-3.0/debian/changelog trunk/xen-3.0/debian/control trunk/xen-3.0/debian/xen-utils-3.0.postinst Log: The "Sorry for the step back, but I guess it''s more a 2 steps forwards" commit - Added the xen package again, because we believe there is a valid upgrade

Am Freitag, 24. Februar 2006 11:02 schrieb Matthew Grant: > Ralph, Hi Matthew, > I am a Debian Maintainer who is seriously considering getting Xen into > Debian and Ubuntu. > > I have been installing xen-unstable.hg from source on my AMD 64 and have > been impressed with its relative stability. > > I am prepared to sponsor your packages into Debian if we can get them >

Looking through the build files I'm wondering if we can't do some clean-up and remove extraneous kruft before we release. Like the config.dbs and the README.build that talks about the config.dbs. From looking through the build setup I don't see either file actually critically needed and looks like Ralph may have come to a similar conclusion by the comments added to the README.build

I've been working on a buildrelease.sh script to call hg2dist.sh, export debian/ from svn and run dpkg-source for me. When I ran dpkg-source I noticed that it gave warnings regarding the *.dpatch files being chmod 0755 is there any reason to maintain this within the repository or would 0644 suffice and remove these warnings from dpkg-source? Regards, Jeremy --

Author: tha-guest Date: 2006-02-18 16:38:52 +0000 (Sat, 18 Feb 2006) New Revision: 19 Modified: trunk/debian/control trunk/debian/patches/00list trunk/debian/rules trunk/debian/xen-hypervisor-pae.install trunk/debian/xen-hypervisor.install Log: - changed debian/rules to build a pae hypervisor on i386 (has to be done after the "make dist" for the non-pae stuff) - changed

I've just been trying to catch up with the posts already so figured I'd just start another thread as it seemed I would address things from multiple emails. I really need to get my sieve filter script updated to move the list emails into the proper folder now I guess :) We can play with the revision of the packaging during testing. One idea would be to use 3.0.1-0.YYYYMMDD for

Author: tha-guest Date: 2006-02-17 16:52:19 +0000 (Fri, 17 Feb 2006) New Revision: 13 Modified: trunk/debian/control Log: We don''t want to suggest linux-xen0-2.6, because that was just my xen0 kernel package. Modified: trunk/debian/control =================================================================== --- trunk/debian/control 2006-02-17 14:31:17 UTC (rev 12) +++

Author: tha-guest Date: 2006-02-20 18:22:11 +0000 (Mon, 20 Feb 2006) New Revision: 40 Modified: trunk/debian/control trunk/debian/rules Log: - changed "hotplug | udev (>=0.059)" dependency to "hotplug | udev" - removed "hotplug" as build-dependency - updated rules file to have hotplug & udev etc files installed Modified: trunk/debian/control

Author: tha-guest Date: 2006-02-18 22:55:21 +0000 (Sat, 18 Feb 2006) New Revision: 24 Removed: trunk/debian/patches/30rename-pae-hypervisor.dpatch Log: Guido found a better way to have the pae hypervisor installed with another name without patching upstream and it seems to work as good as the patched upstream version, so I removed my patch from svn again. There seems to be no need to just

libxen-dev_3.0.1-2_i386.deb to pool/main/x/xen/libxen-dev_3.0.1-2_i386.deb libxen-python_3.0.1-2_i386.deb to pool/main/x/xen/libxen-python_3.0.1-2_i386.deb (new) libxen3.0_3.0.1-2_i386.deb extra libs control library for XEN, a Virtual Machine Monitor Library to control the XEN microkernel. Contains functions for creating, starting, stopping, saving, virtual instances.

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-1 Severity: normal Tags: patch Manpages that are provided with the source are not included with the utilities. Use perl-doc package at build-time to generate appropriate manpages and dh_manpages to install them in the appropriate locations. diff -urN xen-3.0-3.0.3-0/debian/control xen-3.0-3.0.3-0.new/debian/control --- xen-3.0-3.0.3-0/debian/control

Hello people. I'm going to maintain a setup of several "big-resource" machines (>= 4 CPUs, >=8 Gb of ram), which should host large number of "small" systems in xen domains. As far as I understand, using "big machines" is not currently possible within debian xen packages, because there is no kernel with pae support to use in domain 0, which in turn

Hi! I was running lintian on our package... Among the copious errors and warnings there are: W: xen-utils: manpage-has-errors-from-man usr/share/man/man1/xm.1.gz 668: warning: can't find numbered character 160 Should we try to fix this, perhaps? E: xen-hypervisor-pae: unstripped-binary-or-object ./boot/xen_pae-syms-3.0.1 E: xen-hypervisor: unstripped-binary-or-object ./boot/xen-syms-3.0.1

Package: xen-unstable Version: 3.0-unstable+hg11561-1 Followup-For: Bug #399700 The included patch overcomes the old build dependency on linux-support-2.6.17-2, and replaces it with linux-support-2.6.22-3. I filed a previous bug #453912 - but I guess it doesn't apply? -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable')

Hi, since the repo is up and the debian files from "xen3.0.1-0tha2" are uploaded I want to say some words about my work. This could help to understand what I have done and makes it easier to understand what needs to be done to have it in a good shape for debian. - I have written down (more or less all) changes to debian/changelog, so reading it might help understanding what is

Now that we've got the script to generate the patch file prior to building the source DEB, do we really need to maintain having wget in the build-depends? With the script we should be the ones generating the patch file and then building the kernel-patch package doesn't need to download the kernel to build. I just noticed this while examining the rules and control files.

Author: ultrotter Date: 2006-02-24 19:29:40 +0000 (Fri, 24 Feb 2006) New Revision: 55 Modified: trunk/debian/copyright Log: Update FSF address Modified: trunk/debian/copyright =================================================================== --- trunk/debian/copyright 2006-02-24 19:14:50 UTC (rev 54) +++ trunk/debian/copyright 2006-02-24 19:29:40 UTC (rev 55) @@ -18,8 +18,7 @@ You

Author: ultrotter Date: 2006-03-21 16:54:07 +0000 (Tue, 21 Mar 2006) New Revision: 127 Modified: trunk/xen-3.0/debian/xen-utils-3.0.postrm Log: Stop xend & xendomains on remove, and call update-rc.d on purge... Modified: trunk/xen-3.0/debian/xen-utils-3.0.postrm =================================================================== --- trunk/xen-3.0/debian/xen-utils-3.0.postrm 2006-03-21