Package: google-android-m2repository-installer Version: 33 Severity: serious User: debian...@lists.debian.org Usertags: piuparts
Hi, during a test with piuparts I noticed your package failed to install, remove (but not purge), and install again. Before the second installation the package is in config-files-remaining state. The configuration is remaining from the last version that was successfully configured - which is the same version that is going to be installed again. Like a plain failure on initial install this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): [...] install -d -m0755 /usr/share/doc/google-android-m2repository gzip -9 --stdout /var/cache/google-android-m2repository-installer/m2repository/NOTICE.txt > /usr/share/doc/google-android-m2repository/copyright.gz install -m0644 /var/cache/google-android-m2repository-installer/m2repository/source.properties /usr/share/doc/google-android-m2repository/ install -d -m0755 /usr/lib/android-sdk/extras/android mv /var/cache/google-android-m2repository-installer/m2repository /usr/lib/android-sdk/extras/android/ mv: cannot move '/var/cache/google-android-m2repository-installer/m2repository' to '/usr/lib/android-sdk/extras/android/m2repository': Directory not empty Makefile:15: recipe for target 'install' failed make: *** [install] Error 1 make: Leaving directory '/var/cache/google-android-m2repository-installer' dpkg: error processing package google-android-m2repository-installer (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: google-android-m2repository-installer Probably the maintainer scripts don't clean up properly on removal but just on purge. cheers, Andreas
google-android-m2repository-installer_33.log.gz
Description: application/gzip
