Package: shaarli Version: 0.0.42~beta~dfsg1-1 Severity: serious Justification: Policy 10.7.3
After installing shaarli from Testing on a new machine, a 500 Internal Server Error is logged when accessing the page for the first time. >From /var/log/nginx/error.log: 2014/12/13 14:39:27 [error] 10171#0: *29 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught exception 'RainTpl_Exception' with message 'Cache directory /var/cache/shaarli/tmp/doesn't have write permission. Set write permission or set RAINTPL_CHECK_TEMPLATE_UPDATE to false. More details on http://www.raintpl.com/Documentation/Documentation-for-PHP-developers/Configuration/' in /usr/share/raintpl/inc/rain.tpl.class.php:321 Stack trace: #0 /usr/share/raintpl/inc/rain.tpl.class.php(274): RainTPL->compileFile('install', NULL, 'tpl/install.htm...', '/var/cache/shaa...', '/var/cache/shaa...') #1 /usr/share/raintpl/inc/rain.tpl.class.php(164): RainTPL->check_template('install') #2 /usr/share/shaarli/index.php(674): RainTPL->draw('install') #3 /usr/share/shaarli/index.php(2107): pageBuilder->renderPage('install') #4 /usr/share/shaarli/index.php(108): install() #5 {main} thrown in /usr/share/raintpl/inc/rain.tpl.class.php on line 321" while reading response header from upstream, client: 127.0.0.1, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "127.0.0.1" The permission on the /var/cache/shaarli/tmp folder is incorrectly set (root instead of www-data, which is the user under which the Apache and nginx web servers run by default). In fact, the following folders should also be writable by www-data: /var/lib/shaarli/data /var/cache/shaarli/cache /var/cache/shaarli/pagecache The following fixes this issue: sudo chown www-data:www-data /var/lib/shaarli/data /var/cache/shaarli/cache /var/cache/shaarli/pagecache /var/cache/shaarli/tmp Justification for severity "serious": >From the bug severity description [0]: serious is a severe violation of Debian policy (roughly, it violates a must or required directive), or, in the package maintainer's or release manager's opinion, makes the package unsuitable for release. In my opinion, a package should (as much as possible, i.e. not "must") work out of the box. This is somewhat mentioned in section 10.7.3 of the Debian Policy Manual [1]: "Ideally the sysadmin should not have to do any configuration other than that done (semi-)automatically by the postinst script." +Emilien [0] https://www.debian.org/Bugs/Developer#severities [1] https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3 -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages shaarli depends on: ii javascript-common 11 ii libjs-jquery 1.7.2+dfsg-3.2 ii libjs-jquery-lazyload 1.7.2-1 ii libjs-jquery-ui 1.10.1+dfsg-1 ii php5 5.6.3+dfsg-1 ii php5-fpm 5.6.3+dfsg-1 ii php5-gd 5.6.3+dfsg-1 ii raintpl 2.7.2-1 Versions of packages shaarli recommends: ii nginx-full [httpd] 1.6.2-5 shaarli suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
