[et-mgmt-tools] ANNOUNCE: New release virtinst 0.300.3

[Tiago Cruz]

Hi,

Where can I find one package for RHEL5.1, like this build:
http://builder.virt-manager.org/logs/modules/virtinst--devel-build-output.log

I cant build my package, 'cause the python-virtinst.spec has empty...

creating dist
tar -cf dist/virtinst-0.300.3.tar virtinst-0.300.3
gzip -f9 dist/virtinst-0.300.3.tar
removing 'virtinst-0.300.3' (and everything under it)

if [ -f /usr/bin/rpmbuild ]; then
  if [ -n "$AUTOBUILD_COUNTER" ]; then
    EXTRA_RELEASE=".auto$AUTOBUILD_COUNTER"
  else
    NOW=`date +"%s"`
    EXTRA_RELEASE=".$USER$NOW"
  fi
  rpmbuild --define "extra_release $EXTRA_RELEASE" \
           --define "_sourcedir `pwd`/dist" \
           -ba --clean python-virtinst.spec
fi
date +"%s"
pwd
error: Name field must be present in package: (main package)
error: Version field must be present in package: (main package)
error: Release field must be present in package: (main package)
error: Summary field must be present in package: (main package)
error: Group field must be present in package: (main package)
error: License field must be present in package: (main package)


Thanks


On Tue, 2008-03-11 at 03:55 +0000, Daniel P. Berrange wrote:
> I'm happy to announce a new release of virtinst, release 0.300.3 is now 
> available for download at:
> 
>   http://virt-manager.org/download.html
> 
> The direct download link is:
> 
>   http://virt-manager.org/download/sources/virtinst/virtinst-0.300.3.tar.gz
> 
> This release addresses a number of major bugs, and optimizes aspects of the
> installation process. When probing for OS distro type it will test file 
> existance, rather than fetching the entire file. RFC compliant NFS uris 
> are now accepted & converted where needed. When probing for Red Hat distro
> variants, look for the .treeinfo file to determine initrd/kernel locations.
> Print user friendly error instead of stack traces, and hide bogus libvirt 
> error messages from console. Add a --noreboot flag to virt-install to 
> prevent the automatic reboot at end of installation. Use the libvirt 
> capabilities XML to determine the guest types supported by a hypervisor.
> Add --force option to prevent any interactive prompting.
> 
> Thanks to everyone who has contributed to this release whether by testing,
> bug reporting, submitting patches,  and otherwise sending feedback !
> 
> Regards,
> Daniel.
-- 
Tiago Cruz
http://everlinux.com
Linux User #282636