On Thu, Apr 25, 2013 at 04:08:22PM +0200, linux wrote:
On 2013-04-25 13:58, linux wrote:
>On 2013-04-25 12:10, Jakub Hrozek wrote:
>>On Thu, Apr 25, 2013 at 09:24:22AM +0200, linux wrote:
>>>I'm trying to build sssd 1.9.5 on Ubuntu 12.10 and I got the
>>>Running suite(s): sysdb
>>>99%: Checks: 800, Failures: 1, Errors: 1
>>>Tests:test_sysdb_add_user:27000: (after this point) Test timeout
>>>Tests:test_sysdb_getpwnam:27000: Invalid number of replies.
>>>1, got 0
>>Is this reproducable? We run the unit tests on each build
>>nigtlies) and it never failed for us.
>No, now I get the following error:
>Running suite(s): access_simple
>80%: Checks: 10, Failures: 1, Errors: 1
>allow/deny:test_group_both_set:0: (after this point) Test timeout
>allow/deny:test_group_case:0: Could not add private group
>maybe my desktop is too overloaded which causes the timeout. I'll
>stop the VMs running and try again.
>My goal is to build a debian package for Ubuntu and Debian
>>Can you step the test_sysdb_add_user with a gdb ?
>I'm not so familiar with C programming and debugging, but will do
>that if my workstation is not the cause for the failure.
>>sssd-devel mailing list
>sssd-devel mailing list
With a freshly rebooted system I get the following error:
dh_install: libsss-sudo1 missing files (usr/lib/*/libsss_sudo.so.*),
Sorry, I'm not familiar with Debian packaging so I don't know what the
dh_install script does.
make: *** [override_dh_install] Error 255
some lines above, I see
/bin/bash ./libtool --mode=install /usr/bin/install -c
libtool: install: /usr/bin/install -c .libs/libsss_sudo.so
libtool: install: /usr/bin/install -c .libs/libsss_sudo.lai
libtool: install: warning: remember to run `libtool --finish
so there is no libsss_sudo.so.* but a libsss_sudo.so
That's quite expected, libsss_sudo.so is not a library that is expected
to be linked with (there is no libsss_sudo.h for instance) but it's
expected that sudo would dlopen it and dlsym the interface. It shouldn't
be even installed to libdir, but unfortunately that's where sudo loads
it from :-/
I noticed that we actually call ldconfig for libsss_sudo in the upstream
sssd specfile which is a bug and I'll send a patch.