Stabilize sys-libs/libcap-ng-0.6.4.
Arch teams, please do your thing.
fails test for me. ( bug 342301 ) It seems to be a regression on amd64, right? https://bugs.gentoo.org/show_bug.cgi?id=292133#c4 the rest seems ok.
Tests passed for me. amd64 done
arm stable
Fails test, which is a regression, no maintainer, we are out. PASS: lib_test Testing thread separation of capabilities Detected capabilities when they should not be any FAIL: thread_test =================== 1 of 2 tests failed =================== make[3]: *** [check-TESTS] Error 1 make[3]: Leaving directory `/var/tmp/portage/sys-libs/libcap-ng-0.6.4/work/libcap-ng-0.6.4/src/test' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/var/tmp/portage/sys-libs/libcap-ng-0.6.4/work/libcap-ng-0.6.4/src/test' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/sys-libs/libcap-ng-0.6.4/work/libcap-ng-0.6.4/src' make: *** [check-recursive] Error 1
(In reply to comment #5) > Fails test, which is a regression, no maintainer, we are out. Argh, wrong bug. We stay.
(In reply to comment #5) It's fixed.
x86 stable
ppc done
ppc64 stable
Fails to compile on amd64: -------------------------------------------------------- libcap-ng Version: 0.6.4 Target: x86_64-pc-linux-gnu Installation prefix: /usr Compiler: x86_64-pc-linux-gnu-gcc Compiler flags: -march=native -O2 -pipe >>> Source configured. >>> Compiling source in /var/tmp/portage/sys-libs/libcap-ng-0.6.4/work/libcap-ng-0.6.4 ... make -j1 make all-recursive make[1]: Entering directory `/var/tmp/portage/sys-libs/libcap-ng-0.6.4/work/libcap-ng-0.6.4' Making all in src make[2]: Entering directory `/var/tmp/portage/sys-libs/libcap-ng-0.6.4/work/libcap-ng-0.6.4/src' Making all in test make[3]: Entering directory `/var/tmp/portage/sys-libs/libcap-ng-0.6.4/work/libcap-ng-0.6.4/src/test' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/var/tmp/portage/sys-libs/libcap-ng-0.6.4/work/libcap-ng-0.6.4/src/test' make[3]: Entering directory `/var/tmp/portage/sys-libs/libcap-ng-0.6.4/work/libcap-ng-0.6.4/src' /bin/sh ../libtool --tag=CC --mode=compile x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I. -I.. -fPIC -DPIC -W -Wall -Wshadow -Wformat -Wundef -D_GNU_SOURCE -march=native -O2 -pipe -MT cap-ng.lo -MD -MP -MF .deps/cap-ng.Tpo -c -o cap-ng.lo cap-ng.c libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I. -I.. -fPIC -DPIC -W -Wall -Wshadow -Wformat -Wundef -D_GNU_SOURCE -march=native -O2 -pipe -MT cap-ng.lo -MD -MP -MF .deps/cap-ng.Tpo -c cap-ng.c -fPIC -DPIC -o .libs/cap-ng.o cap-ng.c: In function 'get_bounding_set': cap-ng.c:225:70: warning: signed and unsigned type in conditional expression cap-ng.c: In function 'capng_get_caps_fd': cap-ng.c:325:21: error: 'XATTR_NAME_CAPS' undeclared (first use in this function) cap-ng.c:325:21: note: each undeclared identifier is reported only once for each function it appears in cap-ng.c: In function 'capng_apply_caps_fd': cap-ng.c:539:25: error: 'XATTR_NAME_CAPS' undeclared (first use in this function) make[3]: *** [cap-ng.lo] Error 1 make[3]: Leaving directory `/var/tmp/portage/sys-libs/libcap-ng-0.6.4/work/libcap-ng-0.6.4/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/sys-libs/libcap-ng-0.6.4/work/libcap-ng-0.6.4/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/sys-libs/libcap-ng-0.6.4/work/libcap-ng-0.6.4' make: *** [all] Error 2 emake failed * ERROR: sys-libs/libcap-ng-0.6.4 failed: * emake failed * * Call stack: * ebuild.sh, line 56: Called src_compile * environment, line 5559: Called default * ebuild.sh, line 1609: Called _eapi2_src_compile * ebuild.sh, line 659: Called die * The specific snippet of code: * emake || die "emake failed" * -------------------------------------------------------- Could it be, that a dependency isn't correctly set?
new issues -> new bugs
(In reply to comment #12) > new issues -> new bugs > Sorry, I thought if it doesn't even compile, it would be an important information for the discussion whether to stabilize it or not. I'll open a new bug then.
Tested on SPARC, captest runs just fine, and both pscap and netcap showed correct information for system running w/ full caps.
sys-libs/libcap-ng-0.6.5 will be stabilized in bug #353448.