Package: browser-plugin-freshplayer-pepperflash Version: 0.3.4-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts
Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package browser-plugin-freshplayer-pepperflash. (Reading database ... (Reading database ... 9551 files and directories currently installed.) Preparing to unpack .../browser-plugin-freshplayer-pepperflash_0.3.4-1_amd64.deb ... Unpacking browser-plugin-freshplayer-pepperflash (0.3.4-1) ... Setting up browser-plugin-freshplayer-pepperflash (0.3.4-1) ... update-alternatives: using /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so to provide /usr/lib/mozilla/plugins/flash-mozilla.so (flash-mozilla.so) in auto mode update-alternatives: error: error creating symbolic link '/usr/lib/mozilla/plugins/flash-mozilla.so.dpkg-tmp': No such file or directory dpkg: error processing package browser-plugin-freshplayer-pepperflash (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: browser-plugin-freshplayer-pepperflash The package must ship all directories where (slave) alternatives will be placed. Ship them as empty directories, don't create them manually in the maintainer scripts. cheers, Andreas
browser-plugin-freshplayer-pepperflash_0.3.4-1.log.gz
Description: application/gzip
