I think that we need 3.2 RPMâs for Centos 5.1 or RHEL 5.1 64
Bits that work, tested. I am just not smart enough to install the 3.2 version
myself.
From:
xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx]
On Behalf Of Ross S. W. Walker
Sent: Monday, May 05, 2008 9:38 AM
To: jcasale@xxxxxxxxxxxxxxxxx; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: CentOS 5.1 Xen 3.2 patches
Yes, just put the patches in the SOURCE
directory and spec file in the
SPEC directory and do an rpmbuild, with or without mock, and it should
work.
You won't need these though if you build 3.2.1 as they are included. Just
download the tarball into SOURCE and change the name of the tarball in the
spec file to match (removing any patches that no longer apply of
course).
-Ross
----- Original Message -----
From: Joseph L. Casale <jcasale@xxxxxxxxxxxxxxxxx>
To: Ross S. W. Walker; xen-users@xxxxxxxxxxxxxxxxxxx
<xen-users@xxxxxxxxxxxxxxxxxxx>
Sent: Sat May 03 19:44:22 2008
Subject: RE: CentOS 5.1 Xen 3.2 patches
>Here are a couple of Xen 3.2 patches for CentOS 5.1.
>
>Just download and install the Xen 3.2 source tarball from xen.org,
>copy the xen.spec into SPECS and the patches into SOURCE and
>rebuild.
>
>These will 1) allow libvirt to work with 3.2, 2) fix the handling
>of localtime in 3.2 HVMs.
>
>-Ross
Hey Ross,
I am trying to help another guy out building some rpm's, would the addition
of these files in the respective directories under a mock build environment
allow
rpm's to be made from the srpm patched with your changes?
Thanks!
jlc
This e-mail, and any attachments thereto, is intended only
for use by the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient of this
e-mail, you are hereby notified that any dissemination, distribution or copying
of this e-mail, and any attachments thereto, is strictly prohibited. If you
have received this e-mail in error, please immediately notify the sender and
permanently delete the original and any copy or printout thereof.