Bug#793683: fusionforge-db-local: unowned directories after purge: /var/lib/fusionforge/*

[beuc]

Here's a root cause investigation:

The files are created by the DB upgrade process
(post-install.d/db/db.sh ->
db/20140710-forum-migrate-attachments-to-fs.php
db/20120603-docman-file-moved-in-fs.php
db/20120409-tracker-attachement-moved-in-fs.php)

They are normally created by fusionforge-web as empty dpkg
directories.

Removing /var/lib/fusionforge/* from the db-local package sounds like
a bad idea.

Creating the directories from db-local dpkg also sounds like a bad
idea since the package doesn't use them besides old data migration.

We may make the upgrade procedure skip the creation of the directories
is there's no data to migrate (during fresh installs).

-- 
Sylvain

Bug#793683: fusionforge-db-local: unowned directories after purge: /var/lib/fusionforge/*

[Andreas Beckmann]

Package: fusionforge-db-local
Version: 6.0.2+20150708-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned
directories on the system after purge, which is a violation of
policy 6.8:

https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

Manual directory removal may be not appropriate as this
directory is shared between several packages.

If the package would ship these as empty directories, dpkg would take
care of the creation and removal (if they are empty).

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

1m41.8s ERROR: FAIL: Package purging left files on system:
  /var/lib/fusionforge/docman/   not owned
  /var/lib/fusionforge/forum/not owned
  /var/lib/fusionforge/forum/pending/not owned
  /var/lib/fusionforge/tracker/  not owned


cheers,

Andreas


fusionforge-db-local_6.0.2+20150708-1.log.gz
Description: application/gzip