Pkg xen devel - Sep 2006 - xen-3.0_3.0.2-3+hg9762-1_multi.changes is NEW

xen-3.0_3.0.2-3+hg9762-1.diff.gz
  to pool/main/x/xen-3.0/xen-3.0_3.0.2-3+hg9762-1.diff.gz
xen-3.0_3.0.2-3+hg9762-1.dsc
  to pool/main/x/xen-3.0/xen-3.0_3.0.2-3+hg9762-1.dsc
xen-3.0_3.0.2-3+hg9762.orig.tar.gz
  to pool/main/x/xen-3.0/xen-3.0_3.0.2-3+hg9762.orig.tar.gz
xen-docs-3.0_3.0.2-3+hg9762-1_all.deb
  to pool/main/x/xen-3.0/xen-docs-3.0_3.0.2-3+hg9762-1_all.deb
(new) xen-hypervisor-3.0.2-1-amd64_3.0.2-3+hg9762-1_amd64.deb extra misc
The Xen Hypervisor on AMD64
 The hypervisor is the "core" for XEN itself.  It gets booted by the
boot
 loader and controls cpu and memory, sharing them between your
 administrative domain (Domain 0) and the virtual guest systems.
 .
 In order to boot a XEN system along with this package you also need a
 kernel specifically crafted to work as the Domain 0, mediating hardware
 access for XEN itself.  An example config file for this kernel and
 documentation on how to build it can be found in the xen-docs package.
(new) xen-hypervisor-3.0.2-1-i386-pae_3.0.2-3+hg9762-1_i386.deb extra misc
The Xen Hypervisor on i386-pae-class
 The hypervisor is the "core" for XEN itself.  It gets booted by the
boot
 loader and controls cpu and memory, sharing them between your
 administrative domain (Domain 0) and the virtual guest systems.
 .
 In order to boot a XEN system along with this package you also need a
 kernel specifically crafted to work as the Domain 0, mediating hardware
 access for XEN itself.  An example config file for this kernel and
 documentation on how to build it can be found in the xen-docs package.
 .
 This version of the hypervisor is built with PAE enabled, in order to
 support systems with more than 4GB of memory.  If you have less than that
 you should probably choose the non -pae version.
(new) xen-hypervisor-3.0.2-1-i386_3.0.2-3+hg9762-1_i386.deb extra misc
The Xen Hypervisor on i386-class
 The hypervisor is the "core" for XEN itself.  It gets booted by the
boot
 loader and controls cpu and memory, sharing them between your
 administrative domain (Domain 0) and the virtual guest systems.
 .
 In order to boot a XEN system along with this package you also need a
 kernel specifically crafted to work as the Domain 0, mediating hardware
 access for XEN itself.  An example config file for this kernel and
 documentation on how to build it can be found in the xen-docs package.
 .
 This version of the hypervisor is built with support for systems with up
 to 4GB of memory.  If you have more please install the -pae version
 instead.
xen-ioemu-3.0_3.0.2-3+hg9762-1_amd64.deb
  to pool/main/x/xen-3.0/xen-ioemu-3.0_3.0.2-3+hg9762-1_amd64.deb
xen-ioemu-3.0_3.0.2-3+hg9762-1_i386.deb
  to pool/main/x/xen-3.0/xen-ioemu-3.0_3.0.2-3+hg9762-1_i386.deb
(new) xen-utils-3.0.2-1_3.0.2-3+hg9762-1_amd64.deb extra misc
XEN administrative tools
 The userspace tools to manage a system virtualized through the XEN virtual
 machine monitor.
(new) xen-utils-3.0.2-1_3.0.2-3+hg9762-1_i386.deb extra misc
XEN administrative tools
 The userspace tools to manage a system virtualized through the XEN virtual
 machine monitor.
Changes: xen-3.0 (3.0.2-3+hg9762-1) unstable; urgency=low
 .
  * New upstream snapshot.
  * Rename hypervisor and utils packages to include the complete version.
  * Redo build environment.


Override entries for your package:
xen-3.0_3.0.2-3+hg9762-1.dsc - source misc
xen-docs-3.0_3.0.2-3+hg9762-1_all.deb - extra misc
xen-ioemu-3.0_3.0.2-3+hg9762-1_amd64.deb - extra misc
xen-ioemu-3.0_3.0.2-3+hg9762-1_i386.deb - extra misc

Announcing to debian-devel-changes@lists.debian.org


Your package contains new components which requires manual editing of
the override file.  It is ok otherwise, so please be patient.  New
packages are usually added to the override file about once a week.

You may have gotten the distribution wrong.  You'll get warnings above
if files already exist in other distributions.