Your message dated Tue, 23 Feb 2010 11:23:48 +0100
with message-id <[email protected]>
and subject line update
has caused the Debian Bug report #564661,
regarding mpop: Does not work with gsasl 1.4
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.)
--
564661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564661
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mpop
Version: 1.0.19-1
Severity: grave
Since libgsasl has been upgraded from 1.1-1 to 1.4-1 mpop does not work
and returns this message:
mpop: GNU SASL: Low-level crypto error in SASL library
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32.3-grsec (PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages mpop depends on:
ii dpkg 1.15.5.5 Debian package management system
ii install-info 4.13a.dfsg.1-5 Manage installed documentation in
ii libc6 2.10.2-2 GNU C Library: Shared libraries
ii libcomerr2 1.41.9-1 common error description library
ii libgnutls26 2.8.5-2 the GNU TLS library - runtime libr
ii libgsasl7 1.4.0-1 GNU SASL library
ii libgssapi-krb5-2 1.7+dfsg-4 MIT Kerberos runtime libraries - k
ii libidn11 1.15-2 GNU Libidn library, implementation
ii libk5crypto3 1.7+dfsg-4 MIT Kerberos runtime libraries - C
ii libkrb5-3 1.7+dfsg-4 MIT Kerberos runtime libraries
ii libntlm0 1.1-1 NTLM authentication library
mpop recommends no packages.
mpop suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
fixed 564661 1.4.0-2
thanks
Version 1.4.0-2 depends on libgcrypt 1.4.5, which is now in debian
testing, which should prevent this problem from occuring. I forgot to
add the appropriate closes tag in the changelog, so I'm closing the
report this way. Thanks for debug help!
/Simon
--- End Message ---
