[Android-tools-devel] Bug#852139: google-android-installers: unowned directory after purge: /usr/lib/android-sdk/{build-tools/, platforms/}

[Andreas Beckmann]

Source: google-android-installers
Version: 1472023576
Severity: important
User: debian-qa at lists.debian.org
Usertags: piuparts
Control: affects -1 + google-android-build-tools-17-installer google-android-platform-2-installer

Hi,

during a test with piuparts I noticed all binary packages built
from src:google-android-installers leave 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.

The maintainer scripts create (and later remove) a file in that
directory. Manual directory removal may be not appropriate as this
directory is shared between several packages.

If the package would ship this as an empty directory, dpkg would take
care of the creation and removal (if it's empty).

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

0m58.9s ERROR: FAIL: Package purging left files on system:
  /usr/lib/android-sdk/	 not owned
  /usr/lib/android-sdk/build-tools/	 not owned

and the google-android-platform-*-installer packages have

1m9.8s ERROR: FAIL: Package purging left files on system:
  /usr/lib/android-sdk/	 not owned
  /usr/lib/android-sdk/platforms/	 not owned


cheers,

Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: google-android-build-tools-17-installer_17.0.0.log.gz
Type: application/gzip
Size: 14927 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/android-tools-devel/attachments/20170121/d493e588/attachment.bin>