I've uploaded 2.0.6 to hopefully fix some significant problems with emacsen-common -- partially in implementation, and partially in specification.
I believe that these problems have been contributing to the recent upgrade failure reports (add-on packages not being properly installed, etc.). Though debhelper may also be contributing to the trouble. It looks like it may be creating broken "hybrid" add-on packages. Please check to see if your package is affected: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734531 There has also been one important policy change for add-on packages. They are now required to manage their "installed" state file directly. See debian-emacs-policy section 5B for further details, but here's the relevant diff: --- a/debian-emacs-policy +++ b/debian-emacs-policy @@ -176,6 +176,8 @@ First, for the purposes of this policy, some terminology: fi postinst: + mkdir -p 0755 /var/lib/emacsen-common/state/package/installed + touch /var/lib/emacsen-common/state/package/installed/<package> if test -e /var/lib/emacsen-common/state/package/installed/emacsen-common then /usr/lib/emacsen-common/emacs-package-install --postinst <package> @@ -186,6 +188,7 @@ First, for the purposes of this policy, some terminology: then /usr/lib/emacsen-common/emacs-package-remove --prerm <package> fi + rm -f /var/lib/emacsen-common/state/package/installed/<package> The postinst call must not be made until the package is completely configured and otherwise ready for use, and the prerm This should fix a problem caused when add-on packages were being installed at the same time as emacsen-common. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to debian-emacsen-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87d2jxxcew....@trouble.defaultvalue.org
