diff --git a/debian/control b/debian/control
index 7ef4922..d422d11 100644
--- a/debian/control
+++ b/debian/control
@@ -1,19 +1,28 @@
 Source: openxcap
 Section: net
 Priority: optional
 Maintainer: Dan Pascu <dan@ag-projects.com>
 Uploaders: Adrian Georgescu <ag@ag-projects.com>
 Build-Depends: debhelper (>= 9), python(>= 2.7)
 Standards-Version: 3.9.8
 
 Package: openxcap
 Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}, lsb-base, python-lxml (>= 2.0.7-1), python-zope.interface, python-twisted-core (>= 8.1.0), python-application (>= 2.8.0), python-gnutls (>= 3.1.0), python-sqlobject, python-mysqldb, python-sipsimple
+Depends: ${python:Depends}, ${misc:Depends},
+         lsb-base,
+         python-application (>= 2.8.0),
+         python-gnutls (>= 3.1.0),
+         python-lxml,
+         python-mysqldb,
+         python-sipsimple,
+         python-sqlobject,
+         python-twisted-core,
+         python-zope.interface
 Description: XCAP server implementation
  XCAP protocol allows a client to read, write and modify application
  configuration data stored in XML format on a server. XCAP maps XML document
  sub-trees and element attributes to HTTP URIs, so that these components can
  be directly accessed by HTTP. An XCAP server is used by the XCAP clients to
  store data like Presence policy in combination with a SIP Presence server
  that supports PUBLISH/SUBSCRIBE/NOTIFY methods to provide a complete SIP
  SIMPLE server solution.