> > I checked in a fix yesterday --- if the installer sees Python <2.3 it
> > installs a private copy of the Python 2.3 tempfile module.
>
> I didn't notice this because the unstable-src tarball I download for my
> RPM packaging wasn't updated this morning - it's still dated 18-Mar-2004
> 03:57. 
I'm afraid the nightly build failed last night due to lack of
disk space. I've cranked the handle manually so it should be
there now.
BTW: Within the tar ball, I'm thinking of renaming the
'xeno-unstable.bk' directory to something based on the MD5KEY of
the repository e.g. 'xeno-unstable-d7f7a767b78c50a7d2dd.bk' and
create a soft link from xeno.bk to the new name. The idea behind
this change is that when we receive patches we'd be able to
easily tell what version of the repository the patch is against. 
Any objections?
Ian
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel