Bug#1065633: openldap: FTBFS on hppa - implicit declaration of function 'kadm5_s_init_with_password_ctx'

[Ryan Tandy]

On Fri, Mar 08, 2024 at 07:33:59PM -0800, Steve Langasek wrote:
>This bug is also reproducible on the armel and armhf release archs as a
>result of the time_t transition, so bumping this to serious.

ACK.

>This does fix the build failure.  I was about to push such a change to the
>repo and do a maintainer upload, since I've never been removed from the
>uploaders field after all these years ;)  Do you want me to do this, or
>would you be able to do it tonight?  Getting openldap to build is a priority
>wrt rebootstrapping 32-bit archs for time_t.

I wasn't sure where openldap was on the priority list for arm* since 
it's still BD-Uninstallable on the buildds.

Yes, I can upload it tonight, in a couple of hours from now. Is that OK?

>BTW there's also a reproducible test failure that I'm seeing on armhf in
>both Debian and Ubuntu which is new; I'm not sure if it's related to time_t,
>or if it affects other archs?
>
>>>>>> Starting test046-dds for mdb...
>running defines.sh
>Running slapadd to build slapd database...
>Running slapindex to index slapd database...
>
>WARNING!
>Running as root!
>There's a fair chance slapd will fail to start.
>Check file permissions!
>
>Starting slapd on TCP/IP port 9011...
>Testing slapd searching...
>Creating a dynamic entry...
>ldapadd failed (255)!
>../../../tests/scripts/test046-dds: 93: kill: No such process
>
>>>>>> test046-dds failed for mdb after 2 seconds
>(exit 255)
>make[4]: *** [Makefile:303: mdb-mod] Error 255

I have not seen this failure. Ran it again just now and it passed. But I 
only run amd64... I wouldn't be able to dig into that tonight, even if I 
could reproduce it. Do you think I should disable the test proactively?

thanks,
Ryan