[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Accepted emacsen-common 2.0.6 (source all)



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 11 Jan 2014 20:22:23 -0600
Source: emacsen-common
Binary: emacsen-common
Architecture: source all
Version: 2.0.6
Distribution: unstable
Urgency: low
Maintainer: Rob Browning <rlb@defaultvalue.org>
Changed-By: Rob Browning <rlb@defaultvalue.org>
Description: 
 emacsen-common - Common facilities for all emacsen
Closes: 711915 723157
Changes: 
 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 <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 "<<".
Checksums-Sha1: 
 961a8deeb3dd482237bdec63ad3be75720c629ea 1431 emacsen-common_2.0.6.dsc
 feb379c0465e1c382a21dfb067a25b94336ee5fd 18989 emacsen-common_2.0.6.tar.gz
 87ea0724589ca1c7ef39b362763084b6325674f1 20624 emacsen-common_2.0.6_all.deb
Checksums-Sha256: 
 70d9d61403d20ba7b5d303a2784fa27f748a1badf817aabac6455d7f9b4e19a5 1431 emacsen-common_2.0.6.dsc
 0e2dc896bf47ce8d1e29e622cd97f1b851292a3f8b58105a296e29089265acdf 18989 emacsen-common_2.0.6.tar.gz
 c3b6412f198a44ae6864080391ffa55cfe7a39a9d2f2e0424316cd8f7592dd87 20624 emacsen-common_2.0.6_all.deb
Files: 
 cd017dc08279a4790e4c8aae2da63806 1431 editors optional emacsen-common_2.0.6.dsc
 991bb8751955834de99c1fd834cf5830 18989 editors optional emacsen-common_2.0.6.tar.gz
 591fb5a540b7095232431f7f12feb54f 20624 editors optional emacsen-common_2.0.6_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)

iQIcBAEBCAAGBQJS0t/iAAoJEO7xFsVaWkLxe3oP/jjkqdwbTp7Xr1lSFUiFBfUr
XO7qIiow469liaCWp+oWUsXzJlPb8y6OGfkD1FDjy60Kgt1yohD/ewog7vgoBWTv
pBDZA0CB+6gxP0AYdqUTXJjM8l04LNwEYpsd5Y0UXXFkDADHNrBCdK4zwX/BIIla
pKMqe3mTv8W5j+1qiQ0MlEOMkphoO2bqcNPyDBQmREec5ZtSYWWlKR7pz1fL2Vs/
kBxYGkP2b6Xg9PDTtgvBaGoaFNQMgPgLaniWxZxhFfRyMubVxWI78OGqarN85K6W
vP6XNswaK50ClyiFK8Hxpv+lRdhq1n23HJNR7j9QI7joJFODZ6fEI29FHVgMQ4MU
yKEvbd/di2+/s6NzP6E4dHqMxQSPgaSc98HpxtVYnghyhEyACsowwm7fNGSFBC0H
8ozFTCYyvVKW1TQ+4T8403wzNZSo3ETuiQjEUqRD5tk/yUhdAIoq7UpSPhc5Lv/g
6hxgVk8n04OtFPoZ77bOz2lGc+FyJJrsCFJLrryMb3LrG2xYq8R+5wt/1+7LPDe/
UkUgfZF2e0NhcGMh9xZiXMXd7sikHcwjHwCrmzqT26gyhuIXHy+HltGY1W8UEeuH
3L112NPQA+3kpLd4ywvvFBomq+7qdXj/QP3PQjMcRiXSDTsRUUbG6HSJwT/vmZnf
9RrWbG/lUbMTWg2ofdiR
=1RUR
-----END PGP SIGNATURE-----


Reply to: