[ubuntu/lucid] convirt2 2.0.1-0lucid1 (Accepted)

[Brian Thomason]

convirt2 (2.0.1-0lucid1) lucid; urgency=low

  * Initial release
  * Prompting user as to whether or not DB should be created automatically.
    If the user chooses no, or the configuration fails, user will be presented
    with instructions to remedy the issue. This approach has the unfortunate
    side effect of always displaying this message on upgrades as the DB already
    exists and therefore throws an error. However, vendor would rather the user
    see this message as in some cases it may be necessary for the user to
    manually drop the DB before proceeding with an upgrade anyway.
  * Cleaning up files manually on purge as pyc files are created in /opt and
    therefore not handled automatically.
  * Removed usage of python virtualenv and instead use system python libs.
  * Added check for root privs in convirt-ctl script
  * Removed --daemon arg for paster as upstart wasn't handling the fork
    properly, and pid file <file> functionality does not yet appear to work in
    upstart either.

Date: Thu, 03 Feb 2011 17:53:28 -0500
Changed-By: Brian Thomason <brian.thomason at canonical.com>
https://launchpad.net/ubuntu/lucid/+source/convirt2/2.0.1-0lucid1
-------------- next part --------------
Format: 1.8
Date: Thu, 03 Feb 2011 17:53:28 -0500
Source: convirt2
Binary: convirt2
Architecture: source
Version: 2.0.1-0lucid1
Distribution: lucid
Urgency: low
Maintainer: Brian Thomason <brian.thomason at canonical.com>
Changed-By: Brian Thomason <brian.thomason at canonical.com>
Description: 
 convirt2   - management system for open source hypervisors and cloud platforms
Changes: 
 convirt2 (2.0.1-0lucid1) lucid; urgency=low
 .
   * Initial release
   * Prompting user as to whether or not DB should be created automatically.
     If the user chooses no, or the configuration fails, user will be presented
     with instructions to remedy the issue. This approach has the unfortunate
     side effect of always displaying this message on upgrades as the DB already
     exists and therefore throws an error. However, vendor would rather the user
     see this message as in some cases it may be necessary for the user to
     manually drop the DB before proceeding with an upgrade anyway.
   * Cleaning up files manually on purge as pyc files are created in /opt and
     therefore not handled automatically.
   * Removed usage of python virtualenv and instead use system python libs.
   * Added check for root privs in convirt-ctl script
   * Removed --daemon arg for paster as upstart wasn't handling the fork
     properly, and pid file <file> functionality does not yet appear to work in
     upstart either.
Checksums-Sha1: 
 36c7fc92dfe3cd6108cf266c32ccc9525e32c77b 1059 convirt2_2.0.1-0lucid1.dsc
 bfe2f9bc29813a52444770dacb17107262a97235 2208112 convirt2_2.0.1.orig.tar.gz
 f90963e086a3c12703d876bb10e48769831cad71 6440 convirt2_2.0.1-0lucid1.diff.gz
Checksums-Sha256: 
 95b5dcfe02d9a7c217b223635b326bce0da356858c8a8161f4dc4d598202927c 1059 convirt2_2.0.1-0lucid1.dsc
 4c01e359c9eb4209aacf1a25f874499d38e534901ee3f67e8c531e336ce514ae 2208112 convirt2_2.0.1.orig.tar.gz
 e6ce72812acd25fba568d665cab543cbd373d3fa062cc7e6744ab85ce63399db 6440 convirt2_2.0.1-0lucid1.diff.gz
Files: 
 b77aa0ec2cad5de8391afdf4159d8bcf 1059 partner/utils extra convirt2_2.0.1-0lucid1.dsc
 1a847d0f750a95aab84ce9c78bbb54e2 2208112 partner/utils extra convirt2_2.0.1.orig.tar.gz
 82bbd86791e2b4624d087eb6ad04889f 6440 partner/utils extra convirt2_2.0.1-0lucid1.diff.gz