similar to: Bug#399700: xen-unstable: bugfix, patch included. now build-deps on linux-support-2.6.22-3

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

Package: xen-utils-3.2-1 Version: 3.2.0-4 Severity: important Tags: patch pygrub uses tools/libfsimage to read a guest filesystem. Unfortunately the grub derived code does not support 256 byte inodes. Grub itself has been patched (see #463236 and #463123) and this patch has now been applied to the upstream Xen tree. See <http://xenbits.xensource.com/staging/xen-unstable.hg?rev/c777e572a467>

Package: xen-unstable Version: 3.0-unstable+hg11561-1 Severity: serious Build-depends on linux-support-2.6.17-2, which is no longer available in sid. -- Stephen R. Marenka If life's not fun, you're not doing it right! <stephen@marenka.net> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size:

Package: xen-3.0 Version: 3.0.3~rc4+hg11760-1 Severity: wishlist There was an error while trying to autobuild your package: > Automatic build of xen-3.0_3.0.3~rc4+hg11760-1 on caballero by sbuild/ia64 85 > Build started at 20061021-0451 [...] > ** Using build dependencies supplied by package: > Build-Depends: debhelper (>= 5.0.37.2), python-dev (>= 2.3), libsdl1.2-dev, bcc,

Author: ultrotter Date: 2006-02-17 06:56:29 +0000 (Fri, 17 Feb 2006) New Revision: 9 Modified: trunk/debian/changelog trunk/debian/control Log: Change the version and debian revision, as agreed on the ML Start tracking the bugs that need to be closed on upload Modified: trunk/debian/changelog =================================================================== --- trunk/debian/changelog

Package: xen-3.0 Version: 3.0.2-3+hg9762-1 Severity: wishlist There was an error while trying to autobuild your package: > Automatic build of xen-3.0_3.0.2-3+hg9762-1 on caballero by sbuild/ia64 85 > Build started at 20060922-0812 [...] > ** Using build dependencies supplied by package: > Build-Depends: debhelper (>= 5.0.37.2), libcurl3-dev | libcurl-dev, python-dev, python

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-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

Package: xen-3 Version: 3.2.1-1 Severity: important Apparently upstream supports ia64 in xen 3 or 3.1 or so.... lamont There was an error while trying to autobuild your package: > Automatic build of xen-3_3.2.1-1 on mundy by sbuild/ia64 98 > Build started at 20080527-2018 [...] > ** Using build dependencies supplied by package: > Build-Depends: debhelper (>= 5.0.37.2),

# xm create -c vm01.cfg Error: Cannot open config file "vm01.cfg" www:/var/log/xen# xm create -c /etc/xen/auto/vm01.cfg Using config file "/etc/xen/auto/vm01.cfg". Error: (22, 'Invalid argument') # xm log [2006-10-24 16:16:30 xend.util.security 29229] INFO (__init__:1072) Resource label file not found. [2006-10-24 16:16:30 xend.util.security 29229] INFO

Package: xen-utils-3.0-unstable-1 Version: 3.0-unstable+hg11561-1 Severity: grave Justification: renders package unusable with the recent unstable kernel, the evtchn device should be created with major/minor 10, 63. Instead, it's being created with 10, 201. If fixed manually, xenstored will re-create it with the wrong minor number. This causes Xen to be entirely unusable, as xenstored is

Processing commands for control at bugs.debian.org: > close 396556 Bug #396556 [src:xen] Please build gdbserver-xen in the xen-utils package Marked Bug as done > forcemerge 446114 396556 Bug #446114 {Done: Ian Campbell <ijc at debian.org>} [src:xen] xen-utils-3.1-1: build gdbserver Bug #396556 {Done: Ian Campbell <ijc at debian.org>} [src:xen] Please build gdbserver-xen in the

Anyone else seeing problems with this combo? I'm running: linux-image-2.6.18-4-xen-686 2.6.18.dfsg.1-9 linux-modules-2.6.18-4-xen-686 2.6.18.dfsg.1-9 xen-hypervisor-3.0-unstable-1-i386-pae 3.0-unstable+hg11561-1 xen-utils-3.0-unstable-1 3.0-unstable+hg11561-1 xen-utils-common 3.0.3-0-2 When I try to fire up xend, it bombs.. doing some

user debian-release at lists.debian.org usertag 469013 -goal-python2.5 retitle 469013 Python API memory handling bug in unused code path found 469013 3.0-unstable+hg11561-1 thanks Hi, the code that exhibits the buggy PyObject_NEW/PyMem_DEL behaviour (in xen-unstable-3.0-unstable+hg11561/tools/pygrub/src/fsys/ext2/ext2module.c) is not actually compiled and the results shipped[1]. As such,

Hello, I''m trying to get my first HVM domU installed (another Debian domU is already working under the same dom0). I intend to install the guest OS from a bootable CD-ROM. But when I create the new HVM domU with ''xm create xp1-cd.cfg'' , I don''t get the expected installation-window and find this in /var/log/xen/qemu-dm.6575.log: domid: 6 qemu: the number

Package: xen-utils-common Version: 3.0.3-0-2 Severity: important I have installed all the packages I can think of to get Xen going and it still fails with the following : /var/log/xen/xend-debug.log: Exception starting xend: (111, 'Connection refused') er.py", line 463, in process_request_thread self.finish_request(request, client_address) File "SocketServer.py",

FYI: The status of the xen-unstable source package in Debian's testing distribution has changed. Previous version: 3.0-unstable+hg11292-2 Current version: 3.0-unstable+hg11561-1 -- This email is automatically generated; henning@makholm.net is responsible. See http://people.debian.org/~henning/trille/ for more information.

Package: xen-ioemu-3.0-unstable Version: 3.0-unstable+hg11561-1 Severity: normal When trying to create an HVM domain with vif settings enabled (as default) qemu-dm fails to start the virtual machine claiming that the tap device cannot be found. This is because qemu-dm tries to execute /etc/xen/qemu-ifup which is instead located in /etc/xen/scripts/qemu-ifup. As a side note qemu-dm seems to be

Package: xen-ioemu-3.0-unstable Version: 3.0-unstable+hg11561-1 Severity: normal Hi, in #393609 /etc/xen/scripts/qemu-ifup is wrongly placed/referred. This script is missing from the amd64 package, making network enabled HVM domain not startable. Regards, L -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture:

Package: xen-hypervisor-3.0-unstable-1-i386 Version: 3.0-unstable+hg11561-1 Severity: important I've installed xen-linux-system-2.6.17-2-xen-k7 (version 2.6.17-9) on a server, and planned to run 3 Xen domUs on it. Creating the domUs was no problem, and running two of them works well. Starting the third one however will crash the dom0 and forces it to reboot. The machine is a Athlon64 3800+