35692 2018-12-01 02:44:57 +0300 Gssproxy tests failed against libopenslp-2.0.0-alt1 2018-12-01 10:54:10 +0300 1 1 4 Development Sisyphus openslp unstable all Linux CLOSED FIXED P3 major --- 1 slev slev lvol qa-sisyphus oldest_to_newest 176249 0 slev 2018-12-01 02:44:57 +0300 Gssproxy tests failed with: ``` ./tests/runtests.py Traceback (most recent call last): File "./tests/runtests.py", line 56, in runtests_main ldapproc, ldapenv = setup_ldap(testdir, wrapenv) File "/usr/src/RPM/BUILD/gssproxy-0.8.0/tests/testlib.py", line 381, in setup_ldap raise ValueError("LDAP Setup failed") ValueError: LDAP Setup failed ``` A problem happens with "slapadd". Even a running of ```/usr/sbin/slapadd -d 1``` results in: ``` 5c017cd5 register_matching_rule: could not locate associated matching rule generalizedTimeMatch for ( 2.5.13.28 NAME 'generalizedTimeOrderingMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 ) slap_schema_init: Error registering matching rule ( 2.5.13.28 NAME 'generalizedTimeOrderingMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 ) 5c017cd5 slapadd: slap_schema_init failed slapadd: slap_init failed! ``` A similar behavior I see during openldap testing. Openldap is linked against openslp (recently updated to 2.0.0). An upstream of the latter knows about my issue and has a fix: https://sourceforge.net/p/openslp/bugs/149/ https://sourceforge.net/p/openslp/mercurial/ci/51ed69107d096c5b9886954d89e0709975d5aa15/ Let's apply this and other ones. 176250 1 slev 2018-12-01 02:48:55 +0300 I checked openslp-2.0.0-alt2, openldap and gssproxy tests passed. 176254 2 repository-robot 2018-12-01 10:54:10 +0300 openslp-2.0.0-alt2 -> sisyphus: Sat Dec 01 2018 Stanislav Levin <slev@altlinux> 2.0.0-alt2 - Fixed libslp namespace (closes: #35692). - Enabled SLPv2 Security. - Enabled testing. - Applied security fixes (fixes: CVE-2012-4428, CVE-2016-4912, CVE-2016-7567, CVE-2017-17833).