Package: bacula-director-pgsql Version: 1.38.11-2 Severity: serious Justification: Policy 7.2
Antony DeRobertis noted in http://permalink.gmane.org/gmane.linux.debian.backports.general/2913 | The postrm script. Policy says "note, however, that the |postrm| cannot | rely on any non-essential packages to be present during the purge | phase." And policy means it. Let's find out why: | | # dpkg --remove bacula-director-pgsql | dpkg: error processing bacula-director-pgsql (--remove): | Package is in a very bad inconsistent state - you should | reinstall it before attempting a removal. | Errors were encountered while processing: | bacula-director-pgsq | | | | But, alas, when we try and reinstall it, dpkg runs the old package's | prerm. Which fails. Then it runs the new one's. That fails to. Then it | runs the new one's with and abort- argument. That fails also. So, the | package is still half-installed. | | I bet this problem is in unstable, too. And indeed this the case. Verified in bacula-director-pgsql_1.38.11-2_ia64.deb. cu andreas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
