Your message dated Fri, 6 Jul 2012 16:43:19 +0100
with message-id 
<capq4b8n+5zkqc3qpkrfpwhggxuuc9a5az1kgwy54unk0jq3...@mail.gmail.com>
and subject line Closing orphan/obsolete bugs (emacs21 with tag fixed-upstream)
has caused the Debian Bug report #181532,
regarding emacs21: ldap.el parsing is broken under LDAP 2
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.)


-- 
181532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=181532
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: emacs21
Version: 21.2-6
Severity: normal
Tags: upstream



-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux bigbox 2.4.19-686 #1 Mon Nov 18 23:59:03 EST 2002 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages emacs21 depends on:
ii  emacs21-common            21.2-6         The GNU Emacs editor's common infr
ii  libc6                     2.3.1-11       GNU C Library: Shared libraries an
ii  libjpeg62                 6b-6           The Independent JPEG Group's JPEG 
ii  libncurses5               5.3.20021109-2 Shared libraries for terminal hand
ii  libpng12-0                1.2.5-10       PNG library - runtime
ii  libtiff3g                 3.5.7-2        Tag Image File Format library
ii  xaw3dg                    1.5-22         Xaw3d widget set
ii  xlibs                     4.2.1-5        X Window System client libraries
ii  zlib1g                    1:1.1.4-9      compression library - runtime

-- no debconf information

Emacs fails to parse LDAP information properly. LDAP's RFCs specify
that long lines are wrapped; this version of emacs's ldap.el does not
unwrap them. The following patch should fix it:

--- /usr/share/emacs/21.2/lisp/net/ldap.el~     2001-12-28 01:28:32.000000000 
-0500
+++ /usr/share/emacs/21.2/lisp/net/ldap.el      2003-02-18 15:59:30.000000000 
-0500
@@ -574,6 +574,10 @@
       (insert "\n")
       (goto-char (point-min))
        
+     (while (re-search-forward "[\t\n\f]+ " nil t)   ;; from lisp/replace.el
+        (replace-match "" nil nil))
+      (goto-char (point-min))
+
       (if (looking-at "usage")
          (error "Incorrect ldapsearch invocation")
        (message "Parsing results... ")

In addition, "-LLL" should be added to ldap-ldapsearch-args to suppress
some of the extraneous output. 

Incidentally, my LDAP packages are:

ii  ldap-utils     2.0.27-3       OpenLDAP utilities.
ii  ldaptor-utils  0.0.12         Command-line LDAP utilities
ii  libldap2       2.0.27-4       OpenLDAP libraries (without TLS support).
ii  libldap2-tls   2.0.27-4       OpenLDAP libraries (with TLS support).
ii  libnet-ldap-pe 0.26-2         A Client interface to LDAP servers.

This is probably an upstream bug, but I'm reporting it here to make
certain. I have talked to the ldap.el maintainer about this (months
ago), but his name is no longer in the file --- I guess someone else
has taken over

--Joe



--- End Message ---
--- Begin Message ---
Hello,

Thanks for your interest in improving Debian, and sorry that the bugs
were not fully resolved or closed in due time.

emacs21 packages have been removed from testing in 2009 [1], not
present even in the current stable.  Consequently, these bugs are now
orphan (without maintainer assigned) so they probably will not be
attended/noticed further.

[1] http://packages.qa.debian.org/e/emacs21.html

The bugs deemed valid are going to be verified and reassigned, but the
current bugs that I'm closing now are very ancient (more than 10 years
sometimes) and marked as fixed-upstream years ago, with no recent
input, and are supposed to be fixed in emacs22 at the latest.

Please comment if you want think that some of the raised questions are
still pending and need to be addressed differently (e.g., reassigned
to other packages, etc.).

Cheers.


--- End Message ---

Reply via email to