Your message dated Mon, 23 Dec 2013 18:26:46 -0600 with message-id <[email protected]> and subject line Re: Bug#117564: emacs21; /usr/local/share/emacs/ is later in the load path than system dirs has caused the Debian Bug report #117564, regarding emacsen-common: load-path order vs debian-run-directories 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.) -- 117564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=117564 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: emacsen-common Version: 1.4.17 Severity: normal Tags: patch File: /usr/share/emacs/site-lisp/debian-startup.el Firing up "emacs -q" leaves a load-path with the various package additions at the start, whereas I thought the idea of debian-pkg-add-load-path-item was to have them after /usr/local. I think debian-run-directories ends up forcibly moving any additions made by the /etc/emacs/site-start.d files up to the front of the load-path. I get some joy from the change below to have debian-run-directories merely remove the things it wanted temporarily in the load-path (ie. /etc/emacs/site-start.d and /etc/flavour/site-start.d) and leave anything else done by the site-start parts alone. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.22-2-486 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages emacsen-common depends on: ii bsdmainutils 6.1.9 collection of more utilities from emacsen-common recommends no packages. -- no debconf information--- debian-startup.el.old 2007-12-07 15:34:55.000000000 +1100 +++ debian-startup.el 2007-12-07 15:37:15.000000000 +1100 @@ -107,14 +107,11 @@ files))) ;; Finally sort them, and delete duplicates - (base-names (debian-unique-strings (sort stripped-names 'string<))) - - (old-load-path load-path)) + (base-names (debian-unique-strings (sort stripped-names 'string<)))) ;; Set a new load path with the directories specified in the ;; proper order, and first. - (let ((new-path (append paths load-path))) - (setq load-path new-path) + (setq load-path (append paths load-path)) ;; Now load the files. "load" will make sure we get the byte ;; compiled one first, if any, and will respect load-path's ;; ordering. @@ -124,16 +121,10 @@ (load file nil) (error (message "Error while loading %s" file)))) base-names) - ;; restore the old load-path -- including any new paths added by - ;; files loaded in directory traversal. - (let ((add-on-package-paths - (delq nil (mapcar - (lambda (item) - (if (not (member item new-path)) - item - nil)) - load-path)))) - (setq load-path (append add-on-package-paths old-load-path)))))) + ;; remove the `paths' we added to load-path -- but leave anything the + ;; files added + (dolist (item paths) + (setq load-path (remq item load-path))))) (defun debian-startup (flavor)
--- End Message ---
--- Begin Message ---Version: 2.0.4 I believe this was finally fixed in 2.0.4: * Don't override /usr/local/* load-path entries in debian-run-directories. Previously, debian-run-directories would prepend all of the add-on package paths to load-path, which meant that (in violation of Debian policy) /usr/local wouldn't preceed the other entries. Thanks to Hendrik Tews <[email protected]> for the report and Kevin Ryde <[email protected]> for an initial suggested patch -- posted to #454778. (closes: #676424) 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 ---
