Your message dated Wed, 7 May 2008 17:20:20 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Re: ldap-haskell - FTBFS: error: 'LDAP_PROXY_AUTHZ_FAILURE'
undeclared (first use in this function)
has caused the Debian Bug report #462852,
regarding ldap-haskell_0.6.3.0: FTBFS: 'LDAP_PROXY_AUTHZ_FAILURE' undeclared
(first use in this function)
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.)
--
462852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462852
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: ldap-haskell
Version: 0.6.3.0
Severity: serious
Hi John,
ldap-haskell now fails to build in unstable and testing, because
libldap2-dev has been updated to the openldap 2.4 version and
LDAP_PROXY_AUTHZ_FAILURE has been renamed to LDAP_X_PROXY_AUTHZ_FAILURE:
[...]
Data.hsc: In function 'main':
Data.hsc:116:0:
error: 'LDAP_PROXY_AUTHZ_FAILURE' undeclared (first use in this function)
Data.hsc:116:0:
error: (Each undeclared identifier is reported only once
Data.hsc:116:0: error: for each function it appears in.)
compiling dist/build/LDAP/Data_hsc_make.c failed
command was: /usr/bin/ghc6 -c -package base-3.0.1.0
dist/build/LDAP/Data_hsc_make.c -o dist/build/LDAP/Data_hsc_make.o
Preprocessing library LDAP-0.6.3...
dh_haskell_build: command returned error code 256
[...]
A full build log is available at
<http://buildd.debian.org/fetch.cgi?pkg=ldap-haskell&arch=alpha&ver=0.6.3.0%2Bb1&stamp=1201272091&file=log&as=raw>.
The trivial find-and-replace solves this issue, but then the build fails
because several functions are now considered deprecated upstream and only
available if building with -DLDAP_DEPRECATED. Since these are language
bindings, I think it's probably appropriate to enable this flag at build
time to continue to provide the same API in Haskell.
Unrelated to this, there seem to be a pair of bugs in the LDAP/Data.hsc
enums:
LDAP/Data.hsc:89:1:
Warning: Pattern match(es) are overlapped
In the definition of `toEnum': toEnum (7) = ...
LDAP/Data.hsc:245:1:
Warning: Pattern match(es) are overlapped
In the definition of `toEnum': toEnum (0) = ...
The second is because LDAP_OPT_SUCCESS and LDAP_OPT_ERROR are included as
"LDAPOptionCode"s when they're actually return values from
ldap_get/set_option(), and the first seems to be because
LDAP_AUTH_METHOD_NOT_SUPPORTED and LDAP_STRONG_AUTH_NOT_SUPPORTED are
aliases for one another.
Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED]
--- End Message ---
--- Begin Message ---
Version: 0.6.4.0
Evidently this bug is fixed, since ldap-haskell has successfully built on
all archs since it was filed; closing the bug, so ldap-haskell will be
allowed to migrate to testing.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED]
--- End Message ---
