~ubuntu-branches/ubuntu/trusty/emacsen-common/trusty-proposed : changes

~ubuntu-branches/ubuntu/trusty/emacsen-common/trusty-proposed » Changes from revision 14

From Revision 14

Rev	Summary	Authors	Tags	Date
14	Fix typo; add missing "-m" to mkdir call in postinst and pol... Fix typo; add missing "-m" to mkdir call in postinst and policy. Thanks to Stefan Lippers-Hollmann <s.L-H@gmx.de> for the report. (Closes: 735155)	Rob Browning	2.0.7	10 years ago
13	* Don't use given/when syntax in emacs-install and * Don't use given/when syntax in emacs-install and emacs-package-install. It's experimental and produces warnings with Perl 5.18. Thanks to Guillem Jover <guillem@debian.org> for the report. (Closes: 723157) * sample-package-remove-foo: don't fail if elc_dir is already gone. Thanks to Kevin Ryde <user42@zip.com.au> for the suggestion. (Closes: 711915) * Complain loudly if an add-on package appears to be broken. Add validate_add_on_pkg() to verify that an add-on package's invocations match its "style", and call it from emacs-package-install and emacs-package-remove. * Ensure there are no duplicates in get_installed_add_on_packages() result. * Check dpkg exit status when reading package status. * emacs-install: mark emacsen flavor available before handling all the add-ons. * Check for unlink errors when handling emacsen flavor installed state file. * emacs-install/emacs-remove: stop messing with package installed state files. That was just wrong -- the installed state file only indicates that a package is ready to go (i.e. it's safe to start calling the install/remove scripts). It has nothing to do with emacsen flavors. * emacs-install/emacs-remove: treat each add-on as old/new case-by-case. Whether or not an add-on package is old or new is a property of the package itself. The old or new status of the emacsen flavor is irrelevant. * Check for unlink errors when handling an add-on's installed state file. * Fix handling of add-on package installed state file. Mark an add-on package as ready (installed) sooner, and wait until after all of the relevant removals before marking an add-on as unavailable. Note that the state file is only intended to indicate that the package is ready for processing by emacsen-common. * debian-emacs-policy: require add-on postinst/prerm to handle state directly. Add-on packages must now maintain their installed/<package> file directly from their postinst/prerm scripts. This should fix a race whenever emacsen-common and an add-on package are being installed at the same time (i.e. perhaps via "apt-get install add-on emacs24"). If the add-on's postinst goes first, its emacsen install script won't be run. * debian-emacs-policy: change conflicts requirement from "<" to "<<".	Rob Browning	2.0.6	10 years ago
12	* Don't ignore dependency install scripts in emacs-package-i... * Don't ignore dependency install scripts in emacs-package-install. The previous code didn't actually update the script name properly in the loop where it was trying to install all of an add-on package's dependencies. As a result, none of the dependencies' install scripts were actually invoked. Thanks to Sébastien Villemot <sebastien@debian.org> for tracking down the problem, and providing the patch. (closes: #693472) * Invoke each add-on install script correctly as new-style or old-style. Previously, emacs-package-install would invoke all of the add-on install scripts in a dependency chain as either old-style or new-style, based solely on whether or not the package that triggered the install was old-style or new-style. Now it should invoke each package's install script based on whether the package itself is new-style or old-style, as determined by the presence or absence of the policy-required /usr/lib/emacsen-common/packages/compat/PACKAGE file. Thanks to Sébastien Villemot <sebastien@debian.org> for the report. (closes: #693472)	Rob Browning	2.0.5	11 years ago
11	* Move #DEBHEPLER# up in the postinst to avoid an emacs comp... * Move #DEBHEPLER# up in the postinst to avoid an emacs complaint about a missing /usr/local/emacs/site-lisp during the emacsen-common package install script. * Report something like "ERROR: install script from foo package failed" to more clearly indicate the cause of an install/remove failure.	Rob Browning	2.0.3	12 years ago
10	Install usr/local/emacs/site-lisp in the right place so debh... Install usr/local/emacs/site-lisp in the right place so debhelper will handle it. Thanks to Vincent Lefevre <vincent@vinc17.net> for the report. (Closes: #672878)	Rob Browning	2.0.2	12 years ago
9	* Remove the requirement that add-on packages depend on emac... * Remove the requirement that add-on packages depend on emacsen or emacsen-common. This should eliminate the need for many of the trivial Debian foo-el packages, but before the dependencies can be removed, an add-on package must be changed to follow the updated debian-emacs-policy. * Treat the failure of any add-on package install or remove script as a fatal error. Otherwise inter-add-on package dependencies won't be respected. * Migrate to debhelper.	Rob Browning	2.0.0	12 years ago
8	* Remove vestigal dependency on bsdmainutils. Thanks to Sve... * Remove vestigal dependency on bsdmainutils. Thanks to Sven Joachim <svenjoac@gmx.de> for the report. (Closes: #480894) * Require add-on packages to create .el symlinks alongside .elc files. Update debian-emacs-policy to require add-on packages to install a .el symlink alongside each compiled .elc file. Thanks to "Karl M. Hegbloom" <karlheg@microsharp.com> for the original report. (Closes: #122444)	Rob Browning	1.4.23	12 years ago
7	Call mapc instead of mapcar in debian-startup.el since mapca... Call mapc instead of mapcar in debian-startup.el since mapcar was only being called for side-effects. Thanks to "Trent W. Buck" <trentbuck@gmail.com> for the report. (closes: 530961)	Rob Browning	1.4.22	13 years ago
6	Don't print a message if /etc/mailname doesn't exist. Thank... Don't print a message if /etc/mailname doesn't exist. Thanks to Josh Triplett <josh@joshtriplett.org> for the report. (closes: 27757)	Rob Browning	1.4.21	13 years ago
5	* Update debian-emacs-policy to correctly reflect current us... * Update debian-emacs-policy to correctly reflect current usage. * Don't call install-info to remove old emacs entry in the postinst. It's been many years since the last package created that entry. Thanks to Marco Nenciarini <mnencia@debian.org> for the report. (closes: #604164)	Rob Browning	1.4.20	13 years ago
4	* Move the sample package install/remove scripts from * Move the sample package install/remove scripts from debian-emacs-policy to the files sample-package-install-foo and sample-package-remove-foo in /usr/share/doc/emacsen-common. * Fix some suspicious code in the sample package install/remove scripts. Thanks to Kevin Ryde <user42@zip.com.au>. (closes: 424940) * Update debian-file->string to use insert-file-contents-literally. Change gnus-nntpserver-file defvar to setq. Thanks to Jari Aalto <jari.aalto@poboxes.com>. (closes: 269155) * Always call debian-run-directories. Previously a bug would prevent it from running if debian-emacs-flavor wasn't set. Thanks to Francesco Potorti` <pot@gnu.org> and Andrew Kemp <ajwk@pell.uklinux.net>. (closes: 222518, 136779) * Thanks to Agustin Martin Domingo <agmartin@debian.org> for collecting and incorporating many of the fixes in the previous release, this release, and probably the next several releases into his git repository. That work is being used heavily as a reference during these updates.	Rob Browning	1.4.19	15 years ago
3	* Remove "Conflicts: emacs". If I recall correctly, this da... * Remove "Conflicts: emacs". If I recall correctly, this dates back to a time when the Emacs binary package was just named "emacs" (i.e. unversioned), and before the creation of emacsen-common and the Debian Emacs Policy. The Conflicts should be safe to remove now, and the removal will allow us to create a new emacs-defaults source package (a la gcc-defaults) that will produce an emacs package that always depends on the current "standard" version of Emacs (i.e. emacs21, emacs22, etc.). * Update to Standards-Version to 3.6.2.	Rob Browning	1.4.17	18 years ago
2	* Fix sarge RC bug. Alter debian-pkg-add-load-path-item to ... * Fix sarge RC bug. Alter debian-pkg-add-load-path-item to handle nil in load-path. Thanks to Manoj Srivastava. (closes: 270388) * Include section and priorty in dpkg-gencontrol generated control file. (closes: 288752) * Don't create /usr/doc/ symlinks anymore. * Remove pause in 00debian-vars.el when there is no /etc/mailname. The message will always be available in Messages. The real fix for this may involve bug 149924. (closes: 115116) * Ignore ~ when generating package list. Eventually we may do something more like run-parts, but this is at least an improvement. (ref: #29494) Make the package description a bit more elaborate. (closes: 209469) * Fix debian-emacs-policy typo. (closes: 175779)	Rob Browning	1.4.16	19 years ago
1	* make /etc/emacs/site-start.d/00debian-vars.el a conffile a... * make /etc/emacs/site-start.d/00debian-vars.el a conffile as per Debian policy. (closes: Bug#132842) * don't use dolist (not defined everywhere by default). (closes: Bug#132352) * document debian-pkg-add-load-path-item better and fix to actually modify load-path. (closes: Bug#134464) * make debian-unique-strings iterative since elisp isn't as recursion friendly as we might like. (closes: Bug#131803) * for now, issue a descriptive error message if emacsen-common is used before it's configured.	Rob Browning	1.4.15	22 years ago