Author: jvkersch
Revision Date: 2016-02-21 11:57:39 UTC

Fix changelog

Author: Rob Browning
Revision Date: 2014-05-21 15:19:38 UTC

* 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 <tats@vega.ocn.ne.jp> for the report.
  (Closes: 736062)

* emacs-package-remove: remove unused context variable.

Author: Rob Browning
Revision Date: 2014-05-21 15:19:38 UTC

* 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 <tats@vega.ocn.ne.jp> for the report.
  (Closes: 736062)

* emacs-package-remove: remove unused context variable.

Author: Rob Browning
Revision Date: 2014-05-21 15:19:38 UTC

* 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 <tats@vega.ocn.ne.jp> for the report.
  (Closes: 736062)

* emacs-package-remove: remove unused context variable.

Author: Rob Browning
Revision Date: 2014-05-21 15:19:38 UTC

* 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 <tats@vega.ocn.ne.jp> for the report.
  (Closes: 736062)

* emacs-package-remove: remove unused context variable.

Author: Rob Browning
Revision Date: 2014-01-13 11:00:10 UTC

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)

Author: Rob Browning
Revision Date: 2014-01-13 11:00:10 UTC

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)

Author: Rob Browning
Revision Date: 2012-12-12 20:15:05 UTC

* 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)

Author: Rob Browning
Revision Date: 2012-12-12 20:15:05 UTC

* 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)

Author: Rob Browning
Revision Date: 2012-12-12 20:15:05 UTC

* 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)

Author: Rob Browning
Revision Date: 2012-05-22 22:53:55 UTC

* 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.

Author: Steve Langasek
Revision Date: 2011-11-08 06:24:41 UTC

releasing version 1.4.22ubuntu1

Author: Andrey Bondarenko
Revision Date: 2010-11-25 14:31:18 UTC

[ Andrey Bondarenko ]
* debian-startup.el: fix "Warning: 'mapcar' called for effect"
  patch by Era Eriksson (LP: #482849) taken from Debian bug #530961.

[ Alessio Treglia ]
* Set target to natty.

Author: Andrey Bondarenko
Revision Date: 2010-11-25 14:31:18 UTC

[ Andrey Bondarenko ]
* debian-startup.el: fix "Warning: 'mapcar' called for effect"
  patch by Era Eriksson (LP: #482849) taken from Debian bug #530961.

[ Alessio Treglia ]
* Set target to natty.

Author: Loïc Minier
Revision Date: 2009-10-26 11:39:15 UTC

emacs-package-install: don't throw an error when maintainer scripts call
this hook while emacsen-common isn't yet configured; LP: #456523.

Author: Loïc Minier
Revision Date: 2009-10-26 11:39:15 UTC

emacs-package-install: don't throw an error when maintainer scripts call
this hook while emacsen-common isn't yet configured; LP: #456523.

Author: Loïc Minier
Revision Date: 2009-10-26 11:39:15 UTC

emacs-package-install: don't throw an error when maintainer scripts call
this hook while emacsen-common isn't yet configured; LP: #456523.

Author: Rob Browning
Revision Date: 2006-01-05 18:10:56 UTC

* 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.

Author: Rob Browning
Revision Date: 2006-01-05 18:10:56 UTC

* 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.

Author: Rob Browning
Revision Date: 2006-01-05 18:10:56 UTC

* 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.

Author: Rob Browning
Revision Date: 2006-01-05 18:10:56 UTC

* 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.

Author: Rob Browning
Revision Date: 2006-01-05 18:10:56 UTC

* 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.

Author: Rob Browning
Revision Date: 2006-01-05 18:10:56 UTC

* 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.

Author: Rob Browning
Revision Date: 2006-01-05 18:10:56 UTC

* 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.

Author: Rob Browning
Revision Date: 2005-01-27 12:27:09 UTC

* 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)

Author: Rob Browning
Revision Date: 2002-02-18 11:42:31 UTC

* 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.

Author: Rob Browning
Revision Date: 2002-02-18 11:42:31 UTC

* 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.