+invirt-remote (0.4.1) unstable; urgency=low
+
+ [Paul Weaver]
+ * Give a reasonable error message on remctl 'control nonexistent-vm'.
+
+ -- Greg Price <price@mit.edu> Sun, 20 Sep 2009 16:15:25 -0400
+
+invirt-remote (0.4.0) unstable; urgency=low
+
+ * Instead of running all of the disk-wiping dds simultaneously, run them
+ sequentially using a janitor daemon (LP: #411486).
+
+ -- Evan Broder <broder@mit.edu> Tue, 11 Aug 2009 19:37:55 -0700
+
+invirt-remote (0.3.15) unstable; urgency=low
+
+ * If a particular VM is being autoinstalled, include that in the
+ invirt-listvms output.
+
+ -- Evan Broder <broder@mit.edu> Wed, 10 Jun 2009 14:46:39 -0700
+
+invirt-remote (0.3.14) unstable; urgency=low
+
+ * Maybe we won't be /quite/ so ionice to the dd over a deleted LV.
+
+ -- Evan Broder <broder@mit.edu> Sun, 03 May 2009 03:46:13 -0400
+
+invirt-remote (0.3.13) unstable; urgency=low
+
+ * I totally failed to patch the right server.
+
+ -- Evan Broder <broder@mit.edu> Fri, 03 Apr 2009 20:02:34 -0400
+
invirt-remote (0.3.12) unstable; urgency=low
* ionice the dd to wipe out deleted LVs so it doesn't hose the system.
+ * availability takes way too long to type.
- -- Evan Broder <broder@mit.edu> Thu, 02 Apr 2009 01:46:38 -0400
+ -- Evan Broder <broder@mit.edu> Thu, 02 Apr 2009 20:35:17 -0400
invirt-remote (0.3.11) unstable; urgency=low