This bug only occurs in Karmic (removing the package works fine in Jaunty although the package version and contents are exactly the same). I did some debugging and think that the new version of dpkg in Karmic is stricter in some things and this causes the prerm script fail. The problem is that the prerm script is calling update-alternatives --remove twice (first in deconfigure- and then in remove-phase) and it fails the second time because the first run has removed the alternatives already. This works in Jaunty but in Karmic it fails.
I've made a simple hackish patch that removes the update-alternatives calls from remove (they still remain in upgrade/deconfigure). It's probably not the correct solution here but it works and the package can be removed successfully. Apply the patch with sudo patch /var/lib/dpkg/info/flashplugin-installer.prerm path_to_flash.patch Remember to replace path_to_flash.patch with the actual path to the downloaded flash.patch -file. ** Attachment added: "A quick hack that makes the pre-removal script work" http://launchpadlibrarian.net/29383483/flash.patch -- package flashplugin-installer 10.0.22.87ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 https://bugs.launchpad.net/bugs/398042 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
