Your message dated Sun, 02 Dec 2012 14:56:41 -0600 with message-id <[email protected]> and subject line Re: Bug#618720: please use dpkg trigger facility instead of making packages depend on emacsen-common has caused the Debian Bug report #618720, regarding please use dpkg trigger facility instead of making packages depend on emacsen-common to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 618720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618720 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: emacsen-common Severity: important Hi! I've seen several packages stumble into the #614578 case in the last years, and then emacsen-common was added to Depends and later removed again and whatsnot. Actually, this exact case is what dpkg triggers were invented for. Pretty please, with sugar on top, finally make use of them and then please file bugreports against the reverse depends of emacsen-common to tell people to drop the handling and let the dpkg trigger do its magic. Thank you very much in advance!! Rhonda
--- End Message ---
--- Begin Message ---Rob Browning <[email protected]> writes: > Rob Browning <[email protected]> writes: > >> Actually, triggers won't work[1], but last summer, just before debconf, >> I came up with a plan that I believe will work. However, I ended up >> putting it off until after squeeze -- I plan to get back to it in a few >> weeks. > > It looks like I determined that triggers won't work because they don't > fire until the postrm, and at that point, all of the files associated > with an add-on package are already gone. Since I'd still like to allow > add-on packages to control their own removal, that's not sufficient. > > (I just wanted to provide an update. Once I finish remembering where I > left things, I'll probably start a discussion on debian-emacsen.) So I finally overhauled emacsen-common (2.*), which implements the plan I mentioned above. Among other things, it removes the requirement that add-on packages depend on emacsen in any way. Another goal of the overhaul was to eliminate the need for most, if not all, of the trivial foo-el packages. Since the dependencies are no longer required, it should be possible to handle the emacs-related bits for a larger package within the package itself (if desired). So given the overhaul, I'm tentatively closing this bug, but feel free to re-open it (or file a new one), if the new approach doesn't satisfy your concerns. (See 2.0.* /usr/share/doc/emacsen-common/debian-emacs-policy.gz for the details.) 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
--- End Message ---
