Change log for emacsen-common package in Debian
1 → 20 of 20 results | First • Previous • Next • Last |
emacsen-common (3.0.5) unstable; urgency=medium * Update copyright information. * Avoid writes to HOME via EMACS_INHIBIT_AUTOMATIC_NATIVE_COMPILATION. Since GNU Emacs doesn't currently have any way to redirect the natively compiled eln files away from HOME, just suppress them for now. (Closes: #1021842) -- Rob Browning <email address hidden> Mon, 26 Dec 2022 12:29:39 -0600
Available diffs
- diff from 3.0.4 to 3.0.5 (1.1 KiB)
emacsen-common (3.0.4) unstable; urgency=medium * Conflict with xemacs21-support (<< 21.4.24-6~). Restore conflict with xemacs21-support, but version it to exclude everything before the emacsen-common 3.0 compatibility patches were applied. Thanks to Adrian Bunk for reporting the issue. -- Rob Browning <email address hidden> Sat, 15 Sep 2018 13:25:41 -0500
Available diffs
- diff from 3.0.3 to 3.0.4 (676 bytes)
emacsen-common (3.0.3) unstable; urgency=medium * Don't conflict with xemacs21; it's now ready for 3.0. * Rename emacsen-common.maintscripts to emacsen-common.maintscript. Update rm version to 3.0.3~. (Closes: 908099, 908126) -- Rob Browning <email address hidden> Sat, 08 Sep 2018 14:20:34 -0500
Available diffs
- diff from 3.0.2 to 3.0.3 (710 bytes)
emacsen-common (3.0.2) unstable; urgency=medium * Move from experimental to unstable. -- Rob Browning <email address hidden> Sun, 29 Jul 2018 19:25:02 -0500
Available diffs
- diff from 2.0.8 to 3.0.2 (7.9 KiB)
Deleted in experimental-release (Reason: None provided.) |
emacsen-common (3.0.1) experimental; urgency=medium * Conflict with xemacs21 entirely until it's ready for 3.0. Thanks to David Bremner for reporting the problem. (Closes: 902208) * emacsen-common.maintstripts: update rm_conffile versions. Apparently this wasn't right the first time around. Thanks to Sean Whitton for reporting the problem and providing the fix. (Closes: 901450) -- Rob Browning <email address hidden> Sat, 30 Jun 2018 13:23:49 -0500
Superseded in experimental-release |
emacsen-common (3.0.0) experimental; urgency=medium * Accommodate the unversioning of the Emacs packages, i.e. emacs25 is becoming emacs. * Improve sample packaging scripts (quoting, etc.). * Remove 00debian-vars.el. Rely on flavors to set the mail-host-address and gnus-nntpserver-file values themselves, when appropriate. * Adjust policy to reflect dissolution of shared emacs metaflavor. There will no longer be a shared emacs metaflavor -- the emacs25 package is planning to "unversion" to become the concrete emacs flavor. * Update debian/compat to 10. * Conflict with older emacsen flavors. Given the dissolution of the emacs metaflavor and the unversioning of the emacs25 package, conflict with the core package in all previous emacsen flavors so that we can manage the transition without having to carry around a lot of duplicated compatibility code here, and/or in the various flavors. * Clean up emacsen-common install and remove. * Move debian-startup.el to share/emacsen-common. * Drop /etc/emacs/site-start.el. * Remove vestigial debian-emacs-flavor handling. * Don't run emacs/site-start.d anymore. * Drop /usr/local/emacs/site-lisp. -- Rob Browning <email address hidden> Sat, 19 May 2018 14:03:17 -0500
Superseded in buster-release |
Published in stretch-release |
Published in jessie-release |
Superseded in sid-release |
emacsen-common (2.0.8) unstable; urgency=medium * Require add-on packages to depend on emacsen-common >= 2.0.8. This should be simpler and safer, and emacsen-common is only ~140k, which shouldn't be too big a burden. One specific problem this solves is the handling of /var/lib/emacsen-common when emacsen-common is purged -- in particular /var/lib/emacsen-common/state/package/installed/*. Without the dependency, emacsen-common can't remove the tree without clobbering the state for every add-on, but if emacsen-common can't remove it, who can? This release changes the following requirements for add-on packages (see debian-emacs-policy for the details): - They must now depend on emacsen-common >= 2.0.8. - They don't need to conflict with emacsen-common anymore. - They don't need to guard their calls to emacs-install-package. - They don't need to guard their calls to emacs-remove-package. - They should no longer manage their package/installed/ file directly. In addition emacsen flavor packages should now depend on emacsen-common >= 2.0.8. * emacs-package-install: don't try to validate the package during the preinst. The package files that we're looking for won't be available. Thanks to Tatsuya Kinoshita <email address hidden> for the report. (Closes: 736062) * emacs-package-remove: remove unused context variable. -- Rob Browning <email address hidden> Wed, 21 May 2014 15:19:38 -0500
Available diffs
- diff from 2.0.7 to 2.0.8 (2.2 KiB)
emacsen-common (2.0.7) unstable; urgency=medium * Fix typo; add missing "-m" to mkdir call in postinst and policy. Thanks to Stefan Lippers-Hollmann <email address hidden> for the report. (Closes: 735155) -- Rob Browning <email address hidden> Mon, 13 Jan 2014 11:00:10 -0600
Available diffs
- diff from 2.0.6 to 2.0.7 (630 bytes)
emacsen-common (2.0.6) unstable; urgency=low * 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 <email address hidden> for the report. (Closes: 723157) * sample-package-remove-foo: don't fail if elc_dir is already gone. Thanks to Kevin Ryde <email address hidden> 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 <email address hidden> Sat, 11 Jan 2014 20:22:23 -0600
Available diffs
- diff from 2.0.5 to 2.0.6 (3.7 KiB)
emacsen-common (2.0.5) unstable; urgency=low * 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 <email address hidden> 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 <email address hidden> for the report. (closes: #693472) -- Rob Browning <email address hidden> Wed, 12 Dec 2012 20:15:05 -0600
Available diffs
- diff from 2.0.3 to 2.0.5 (2.8 KiB)
emacsen-common (2.0.3) unstable; urgency=low * 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 <email address hidden> Tue, 22 May 2012 22:53:55 -0500
Available diffs
- diff from 1.4.22ubuntu1 (in Ubuntu) to 2.0.3 (31.7 KiB)
emacsen-common (2.0.2) unstable; urgency=low * Install usr/local/emacs/site-lisp in the right place so debhelper will handle it. Thanks to Vincent Lefevre <email address hidden> for the report. (Closes: #672878) -- Rob Browning <email address hidden> Mon, 14 May 2012 19:40:05 -0500
emacsen-common (2.0.0) unstable; urgency=low * 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 <email address hidden> Sun, 13 May 2012 16:38:30 -0500
emacsen-common (1.4.23) unstable; urgency=low * Remove vestigal dependency on bsdmainutils. Thanks to Sven Joachim <email address hidden> 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" <email address hidden> for the original report. (Closes: #122444) -- Rob Browning <email address hidden> Sat, 11 Feb 2012 15:55:07 -0600
emacsen-common (1.4.22) unstable; urgency=medium * Call mapc instead of mapcar in debian-startup.el since mapcar was only being called for side-effects. Thanks to "Trent W. Buck" <email address hidden> for the report. (closes: 530961) -- Rob Browning <email address hidden> Wed, 01 Dec 2010 21:46:10 -0600
emacsen-common (1.4.21) unstable; urgency=medium * Don't print a message if /etc/mailname doesn't exist. Thanks to Josh Triplett <email address hidden> for the report. (closes: 27757) -- Rob Browning <email address hidden> Tue, 30 Nov 2010 17:57:47 -0600
emacsen-common (1.4.20) unstable; urgency=medium * 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 <email address hidden> for the report. (closes: #604164) -- Rob Browning <email address hidden> Mon, 29 Nov 2010 21:26:02 -0600
emacsen-common (1.4.19) unstable; urgency=low * 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 <email address hidden>. (closes: 424940) * Update debian-file->string to use insert-file-contents-literally. Change gnus-nntpserver-file defvar to setq. Thanks to Jari Aalto <email address hidden>. (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` <email address hidden> and Andrew Kemp <email address hidden>. (closes: 222518, 136779) * Thanks to Agustin Martin Domingo <email address hidden> 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 <email address hidden> Sun, 17 May 2009 15:42:24 -0700
emacsen-common (1.4.18) unstable; urgency=low * Add --no-site-file and --no-init-file for the compilation of emacsen-common's .elc files. Those options should be fine for emacsen-common itself right now. Thanks to Peter S Galbraith <email address hidden>. (closes: 132355) * Fix minor documentation bug. Thanks to Roland Stigge <email address hidden>. (closes: 208414) * Print the error message when debian-run-directories encounters an error while loading a file. Thanks to Kevin Ryde <email address hidden>. (closes: 329030) -- Rob Browning <email address hidden> Sun, 10 May 2009 20:52:52 -0700
emacsen-common (1.4.17) unstable; urgency=low * 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 <email address hidden> Thu, 5 Jan 2006 18:10:56 -0800
1 → 20 of 20 results | First • Previous • Next • Last |