Pkg xen devel - Dec 2008 - Bug#502123: [PATCH] Re: xen-hypervisor-unstable-amd64: Post update from 3.2 -> 3.3, initrd which previously worled fails

retitle 502123 xen-utils-unstable: Debian patch breaks paravirtualized guest
initrd
thanks

I see that this bug is still present in pkg-xen svn:
http://svn.debian.org/wsvn/pkg-xen/trunk/xen-unstable/debian/patches/tools-python-xen-xm-relative-path.diff?op=file

Perhaps I wasn?t clear how severe this problem is.  Using the current 
Debianized xen-utils-unstable, it is impossible to boot any 
paravirtualized guest that has an initrd (which is basically all 
paravirtualized guests), because the erroneous 
debian/patches/tools-python-xen-xm-relative-path.diff causes the path to 
the ramdisk to be replaced with the path to the kernel:
-        config_image.append([ 'ramdisk', os.path.abspath(vals.ramdisk)
])
+        config_image.append([ 'ramdisk', abspath(vals.kernel,
'boot') ])
This is a very bad regression over xen-utils-3.2, and an obvious typo with 
an easy and well-tested fix.

Processing commands for control at bugs.debian.org:
> retitle 502123 xen-utils-unstable: Debian patch breaks paravirtualized
guest initrd
Bug#502123: xen-hypervisor-unstable-amd64: Post update from 3.2 -> 3.3,
initrd which previously worked fails
Changed Bug title to `xen-utils-unstable: Debian patch breaks paravirtualized
guest initrd' from `xen-hypervisor-unstable-amd64: Post update from 3.2
-> 3.3, initrd which previously worked fails'.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)