Comment 17 for bug 327053

I was successful now by deactivating the old (intrepid) /var/lib/dpkg/info/hal.postinst when the upgrade starts. This ensures that the hal trigger is not run (the postinst contains the trigger code) when no new hal is installed. After the new hal is installed restarting hal works fine in my tests so we should be ok. This is a one line change in update-manager. It should be ok to do this, if hal is installed it will be upgraded and a new postinst generated, if its not installed, then the code will do nothing.