Yeah, when I originally created the patch it was for Xen 3.3, and I forgot to change it for the Xen 3.2 version of the patch. It's a typo, but the package is actually for Xen 3.2
Are you sure you don't have hardy-backports turned on? If you let apt install the libxen3 from hardy-backports, that will have the behavior you describe, because libxen3 in -backports is Xen 3.3, and isn't interoperable with Xen 3.2.
Yeah, when I originally created the patch it was for Xen 3.3, and I forgot to change it for the Xen 3.2 version of the patch. It's a typo, but the package is actually for Xen 3.2
Are you sure you don't have hardy-backports turned on? If you let apt install the libxen3 from hardy-backports, that will have the behavior you describe, because libxen3 in -backports is Xen 3.3, and isn't interoperable with Xen 3.2.
If that's what happened, you should download and install <http:// mirrors. kernel. org/ubuntu/ pool/main/ x/xen-3. 2/libxen3_ 3.2.0-0ubuntu10 .1_amd64. deb>, and then add this to /etc/apt/ preferences:
Package: libxen3
Pin: release a=hardy-updates
Pin-Priority: 700