[Debian-med-packaging] Bug#682490: biomaj-watcher: modifies ownership/permissions of files from the biomaj package

[Andreas Beckmann]

Package: biomaj-watcher
Version: 1.2.0-8
Severity: serious
User: debian-qa at lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package modifies files from
another package.

>From the attached log (scroll to the bottom...):

2m3.0s ERROR: FAIL: After purging files have been modified:
  /etc/biomaj/db_properties/	 owned by: biomaj
  /etc/biomaj/db_properties/admin/	 owned by: biomaj
  /etc/biomaj/db_properties/admin/alu.properties	 owned by: biomaj
  /etc/biomaj/db_properties/admin/sts.properties	 owned by: biomaj
  /etc/biomaj/db_properties/global.properties	 owned by: biomaj
  /var/lib/biomaj/	 owned by: biomaj
  /var/lib/biomaj/migration/	 owned by: biomaj
  /var/lib/biomaj/migration/update.pl	 owned by: biomaj
  /var/log/biomaj/	 owned by: biomaj


The modifications done here are (in the postinst):

      chown -R tomcat6 /etc/biomaj/db_properties
      chown -R tomcat6 /usr/share/java/webapps/biomaj-watcher
      chmod -R 775 /etc/biomaj/db_properties
      chown -R tomcat6 /var/log/biomaj
      chmod -R 775 /var/log/biomaj
      chown -R tomcat6 /var/lib/biomaj
      chmod -R 775 /var/lib/biomaj
      chown -R tomcat6 /etc/biomaj-watcher
      chown -R tomcat6 /etc/biomaj-watcher

The permission changes (at least on the files) will be reverted whenever
the biomaj package is reinstalled or upgraded - if you really need
tomcat ownership and write permissions: use dpkg-statoverride.
If you don't need them, don't set them.

Setting the severity to serious because this has the potential to break
biomaj-watcher after an biomaj upgrade.


cheers,

Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: biomaj-watcher_1.2.0-8.log.gz
Type: application/x-gzip
Size: 20605 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/debian-med-packaging/attachments/20120723/9a021790/attachment-0001.bin>