Source: uwsgi
Severity: serious
Hi,
similar to #715472 reported by Julien, you should really think twice whether you
want to depend on a hardcoded API version. Unlike PHP our version is much less
often to change, but this still complicates future transitions.
That being said, the real problem is the dependency line:
676 Depends: ${shlibs:Depends}, ${misc:Depends}, apache2, apache2-api-20120211
You must NOT depend on apache2. as this pulls the entire web-server and makes it
impossible for future transitions to properly transition to a newer version
without breaking your package explicitly. From our packaging policy (found in
/usr/share/doc/apache2-dev):
72 The resulting binary package should be called libapache2-mod-<modulename> and
73 MUST NOT depend on apache2 or apache2-bin. Instead a module package must
depend
74 on our virtual package providing the module magic number which denotes the
ABI
75 compatibility version number. The virtual package is called
apache2-api-YYYYMMDD
76 and is guaranteed to be stable through all binary updates of 2.4.x. The
77 dh_apache2 helper assists in getting the dependencies right.
If you meant to depend on Apache2 to satisfy your dependency against mod_proxy,
please look at our depends line enforcing module dependencies against each
other,
documented in the same policy.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
