+invirt-remote-server (0.0.7) unstable; urgency=low
+
+ * sipb-xen-database-common -> invirt-database
+
+ -- Evan Broder <broder@mit.edu> Sat, 25 Oct 2008 21:03:13 -0400
+
+invirt-remote-server (0.0.6) unstable; urgency=low
+
+ * Remove dependency on sipb-xen-chrony-config - we need to take care of
+ the clock, but chrony isn't the right answer
+
+ -- Evan Broder <broder@mit.edu> Sat, 25 Oct 2008 19:16:08 -0400
+
+invirt-remote-server (0.0.5) unstable; urgency=low
+
+ * Rename a remaining sipb-xen file to invirt
+
+ -- Evan Broder <broder@mit.edu> Fri, 24 Oct 2008 22:21:30 -0400
+
+invirt-remote-server (0.0.4) unstable; urgency=low
+
+ * Kill DEB_AUTO_UPDATE_DEBIAN_CONTROL
+
+ -- Evan Broder <broder@mit.edu> Fri, 24 Oct 2008 13:49:45 -0400
+
+invirt-remote-server (0.0.3) unstable; urgency=low
+
+ * Standardize on "Invirt project"
+
+ -- Evan Broder <broder@mit.edu> Fri, 24 Oct 2008 13:33:25 -0400
+
+invirt-remote-server (0.0.2) unstable; urgency=low
+
+ * oops, update control from control.in
+ * configurize web acl
+
+ -- Greg Price <price@mit.edu> Fri, 24 Oct 2008 00:28:08 -0400
+
+invirt-remote-server (0.0.1) unstable; urgency=low
+
+ * sipb-xen -> invirt
+
+ -- Greg Price <price@mit.edu> Thu, 23 Oct 2008 23:58:36 -0400
+
+sipb-xen-remote-server (0.10.2) unstable; urgency=low
+
+ * There's a race condition for if the VM gets powered off between the
+ listvms and the actual request. Solve the problem correctly by using a
+ non-conflicting error code to indicate an invalid command
+
+ -- Evan Broder <broder@mit.edu> Wed, 22 Oct 2008 00:46:38 -0400
+
+sipb-xen-remote-server (0.10.1) unstable; urgency=low
+
+ * Make both list-host and listhost valid commands, and for parity with
+ list-long, document list-host
+
+ -- Evan Broder <broder@mit.edu> Wed, 22 Oct 2008 00:36:32 -0400
+
+sipb-xen-remote-server (0.10) unstable; urgency=low
+
+ * If a command is invalid, but the machine's on, give an actually useful
+ error message
+
+ -- Evan Broder <broder@mit.edu> Wed, 22 Oct 2008 00:29:50 -0400
+