------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1-test-20200215-161616 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.2.0 * Available Python interpreters, in order of preference: [1] python3.7 [2] python3.6 [3] python2.7 (fallback) repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Sat, 15 Feb 2020 20:37:20 +0000 emerge -qpvO sys-devel/autoconf [ebuild U ] sys-devel/autoconf-2.69-r5 [2.69-r4] USE="-emacs"
Created attachment 614004 [details] emerge-info.txt
Created attachment 614006 [details] emerge-history.txt
Created attachment 614008 [details] etc.portage.tbz2
Created attachment 614010 [details] net-nds:openldap-2.4.49-r1:20200215-224245.log.bz2
Created attachment 614012 [details] _emerge-20200216-013220.log emerge output lacks postinst error
Portage is somehow misbehaving here, the package log file contains this section: chown: cannot access '/var/run/openldap': No such file or directory chmod: cannot access '/var/run/openldap': No such file or directory * ERROR: net-nds/openldap-2.4.49-r1::gentoo failed (postinst phase): * (no error message) * which I do miss in the atatched emerge output file (usually that contains the "* ERROR: ... (xxx phase)" line too
and FWIW: mr-fox ~ # emerge -qpvO net-nds/openldap [ebuild R ] net-nds/openldap-2.4.49-r1 USE="berkdb crypt ipv6 ssl syslog tcpd test -cxx -debug -experimental -gnutls -iodbc -kerberos -kinit -libressl -minimal -odbc -overlays -pbkdf2 -perl -samba -sasl (-selinux) -sha2 -smbkrb5passwd -static-libs" ABI_X86="(64) -32 (-x32)"
Created attachment 614018 [details] sys-devel:autoconf-2.69-r5:20200216-001218.log and for completeness here the other failed postinst log file (which is rather a test phase issue, or?
*** Bug 709806 has been marked as a duplicate of this bug. ***
This is fixed in net-nds/openldap-2.4.29-r2
