Package: mumble-server-web Version: 1.2.2-6+squeeze1 Severity: serious Rational:
I use nginx + php5-fpm for my webserver, others might use lighttpd or any other server. It does not make sense to rigidly associate web-management pages with a specific webserver. It is my interpretation that the severity should be serious since apache2 is not necessary to fulfill the goal of serving a mumble/murmer management page over http/https protocols: http://www.debian.org/doc/debian-policy/ch-binary.html#s-dependencies 3.5 "Every package must specify the dependency information about other packages that are required for the first to work correctly." and 3.6 "All packages should use virtual package names where appropriate, and arrange to create new ones if necessary." As I see it there are two obvious solutions, one fast, the other more correct. Short term: Please do not depend on apache2, and instead depend on phpapi-20100525 (or appropriate PHP interpreter) as provided by php5-fpm, php5-cgi, php5-cli, libapache2-mod-php5, etc. Long term: Please split package in to packages such as mumble-server-web-php and mumble-server-web-apache2-integration: The management files should be in their own library like package which I can graft in to my webserver configuration and thus automatically get security updates. The Apache specific integration details can go in another package so that Apache needn't be a dependency of the common php parts. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
