Bug#668258: lintian: warn when php5enmod/php5dismod is not being used
Package: lintian
Version: 2.5.6
Severity: wishlist
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
PHP (with 5.4) has changed way how modules should be installed. It used
to be that config files are installed directly in /etc/php5/conf.d, and
now they should be installed as /etc/php5/mods-available/<name>.ini
calling php5enmod/php5dismod in postinst/postrm to activate these
configs. It would be great if lintian could detect this.
Bug reports for this (not all as this usertag covers more issues):
http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=php54;users=pkg-php-maint@lists.alioth.debian.org
- --
Michal Čihař | http://cihar.com | http://blog.cihar.com
- -- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.9-1.4-desktop (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages lintian depends on:
ii binutils 2.22-6
ii bzip2 1.0.6-1
ii diffstat 1.55-2
ii file 5.11-1
ii gettext 0.18.1.1-5
ii intltool-debian 0.35.0+20060710.1
ii libapt-pkg-perl 0.1.26
ii libc-bin 2.13-27
ii libclass-accessor-perl 0.34-1
ii libclone-perl 0.31-1+b2
ii libdpkg-perl 1.16.2
ii libemail-valid-perl 0.190-1
ii libipc-run-perl 0.91-1
ii libparse-debianchangelog-perl 1.2.0-1
ii libtimedate-perl 1.2000-1
ii liburi-perl 1.60-1
ii locales 2.13-27
ii man-db 2.6.1-2
ii patchutils 0.3.2-1.1
ii perl [libdigest-sha-perl] 5.14.2-9
ii unzip 6.0-5
lintian recommends no packages.
Versions of packages lintian suggests:
ii binutils-multiarch 2.22-6
ii dpkg-dev 1.16.2
ii libhtml-parser-perl 3.69-1+b1
ii libtext-template-perl 1.45-2
ii man-db 2.6.1-2
ii xz-utils 5.1.1alpha+20110809-3
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJPg/l1AAoJEGo39bHX+xdNjEgP/i86VqsSA2PVJz+uHvYYCN4t
NxVwPJY0JiRymsx470S6ZNL3wDgZQ3ynDEd/4UO8QU17sa3CCYXQnrelz3p9MYVh
I/h2ncBDJvclN7SBrmraoZqJTB5SQeQt0dEbb0wwlq5vtxIRuQnLHbJHOX3Xui66
xcMu3ddmd55kdEq+93BUYvscvfflejtowtJTU+p2cNnnk7Z6o3XvAek136AaKSdU
9EDNEBf3aweGCSFjY/FF8yAVJmYFdfFyX4b8xNiMHP8movT8i2DMzC9PSObVwEIX
1rYmHHoybhu7aY9zrd4HkqQk0DiV7fQxux6ob/jCs6mI8OGL4tuc8WnSEoo8ygdw
LvoR1vLHazdvrKYcBix9QenJDDis9OnNndbTxUrvQZyRh4ZptqIIt1PQPLZoNKSy
liqNAH/9BPultqHrm5nnwgFku2nvbUaZQCaYDBbxRk73D289I2PbiEr4bWuzUogv
Muq0/kyJ7CnRM+i+hN3LrRh8ZNfPN6uiPibHl8OkYNvfaOTfmNJ9uGhBr4TQCIjy
wJ1LjLx/TANs86oN+K4g8MRJz+TnKi8+mKs9TOmdk2X3tGJ/o8vpw8VyKj3oRi1O
kSOcf/eBjoN2mLVhS7+KIclAM7SOC7LTENYzdbRoBGzWT8ttwB7B3gQE6I6ILsDL
IuHYKqoJsNCCtqtV8HHn
=/tpQ
-----END PGP SIGNATURE-----
Reply to: