Stop depending on invirt-mail-config in invirt-base

This was basically an attempt to stuff an XVM site-specific config
into the namespace of invirt packages. If we don't expect other users
of invirt to roll their own packages, we should depend on packages
they can't provide.

The dependency on xvm-mail-config will move into a set of xvm
metapackages

svn path=/trunk/packages/invirt-base/; revision=1803

diff --git a/debian/changelog b/debian/changelog
index 3223a9c..f06235f 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+invirt-base (0.0.15) unstable; urgency=low
+
+  * Stop trying to stuff the XVM site-specific packages into the invirt
+    namespace
+
+ -- Evan Broder <broder@mit.edu>  Sun, 07 Dec 2008 09:08:40 -0500
+
 invirt-base (0.0.14) unstable; urgency=low
 
   * Move the XVM production .k5login out of this package

diff --git a/debian/control b/debian/control
index 550a5ff..3c12e66 100644 (file)
--- a/debian/control
+++ b/debian/control
@@ -9,7 +9,7 @@ Package: invirt-base
 Architecture: all
 Depends: ${python:Depends}, ${misc:Depends}, molly-guard, apticron,
  python-json (>= 3.4-2), python-yaml (>= 3.05), python-mako (>=
- 0.2.2), invirt-config, invirt-mail-config
+ 0.2.2), invirt-config
 Provides: ${python:Provides}
 XB-Python-Version: ${python:Versions}
 Description: Base configuration required for all Invirt servers