: safe-utf8 ... KNOWN FAILED (misc/mbsencode-safe-utf8) : invalid-utf8 ... KNOWN FAILED (misc/mbsencode-invalid-utf8) ... KNOWN FAILED (2 from 4 sub-tests) misc: mcookie ... SKIPPED (mcookie not found) misc: rev ... SKIPPED (rev not found) misc: setarch ... SKIPPED (setarch not found) ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-plasma_libressl-abi32+64-test_20180608-205622 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python3.6 (fallback) [3] python2.7 (fallback) emerge -qpv sys-apps/util-linux [ebuild U ] sys-apps/util-linux-2.32-r3 [2.30.2-r1] USE="cramfs ncurses nls pam readline suid {test*} udev* unicode -build -caps -fdformat -kill -python (-selinux) -slang -static-libs -systemd -tty-helpers" ABI_X86="32* (64) (-x32)" PYTHON_SINGLE_TARGET="python3_5 -python2_7 -python3_4 -python3_6" PYTHON_TARGETS="python2_7 python3_5 -python3_4 -python3_6"
Created attachment 535352 [details] emerge-info.txt
Created attachment 535354 [details] emerge-history.txt
Created attachment 535356 [details] environment
Created attachment 535358 [details] etc.portage.tbz2
Created attachment 535360 [details] logs.tbz2
Created attachment 535362 [details] sys-apps:util-linux-2.32-r3:20180609-043955.log.bz2
Created attachment 535364 [details] temp.tbz2
Created attachment 535366 [details] tests.tbz2
Failure is > uuid: oids ...uuidgen: unrecognized option '--md5' > Try 'uuidgen --help' for more information. > uuidgen: unrecognized option '--md5' > Try 'uuidgen --help' for more information. > uuidgen: unrecognized option '--sha1' > Try 'uuidgen --help' for more information. > uuidgen: unrecognized option '--sha1' > Try 'uuidgen --help' for more information. > FAILED (uuid/oids) > uuid: uuid_parser ... OK > uuid: uuidd ... SKIPPED (uuidd not found) > uuid: uuidgen ... SKIPPED (uuidgen not found) > uuid: uuidparse ... SKIPPED (uuidparse not found) >
I cannot reproduce. I first thought this could be a multilib issue and we should run test suite only for native ABI. However, it is passing for me on my test build when I try to build with ABI_X86="32 64". And from reading the code (https://github.com/karelzak/util-linux/blob/v2.32/misc-utils/uuidgen.c) I have no clue what could cause the creation of uuidgen tool without md5 or sha1 option: There's no conditional statement in the source code which could remove these options...
and it is independend from : >>> dev-libs/libressl-2.7.3 or ?
util-linux has no known dependency on dev-libs/openssl. It is shipping its own MD5/SHa1 implementation. Therefore I would be surprised if libressl would cause that. And when there would be such a problem, I wouldn't expect an "unrecognized option '--md5" error. At the moment, the error you have shown should be impossible to my understanding.
The test routine is likely using the system uuidgen binary, instead of the newly built one. uuidgen from the currently stable ebuild util-linux-2.30.2-r1 doesn't support these options.
(In reply to Carlo from comment #13) > The test routine is likely using the system uuidgen binary, instead of the > newly built one. uuidgen from the currently stable ebuild > util-linux-2.30.2-r1 doesn't support these options. Good idea but when you add > pwd 2>&1 1>/tmp/pwd.log > which uuidgen 2>&1 1>/tmp/which.log > type -P uuidgen 2>&1 1>/tmp/type.log to "tests/ts/uuid/oids" you will notice that > /var/tmp/portage/sys-apps/util-linux-2.32-r3/work/util-linux-2.32-abi_x86_32.x86/uuidgen will be used. At least for my testing on a x86 box where util-linux-2.30.2-r1 is installed. @ Toralf: Could you please run this just for native ABI so we can be sure it isn't a multilib issue?
curretly I do have only one running 32+64 bit image and that's the only one where it failed ...
(In reply to Thomas Deutschmann from comment #14) > @ Toralf: Could you please run this just for native ABI so we can be sure it > isn't a multilib issue? I tried this, and for native ABI tests pass fine: lscpu: lscpu: [10] vbox-win ... OK uuid: namespace ... OK blkid: superblocks probing: [48] small-fat32 ... OK uuid: uuid_parser ... OK blkid: superblocks probing: [49] swap0 ... OK uuid: oids ... OK uuid: uuidparse ... OK wipefs: wipefs ... SKIPPED (no root permissions) blkid: superblocks probing: [50] swap1 ... OK blkid: superblocks probing: [51] tuxonice ... OK blkid: superblocks probing: [52] ubi ... OK uuid: uuidgen ... OK blkid: superblocks probing: [53] ubifs ... OK script: replay ... OK uuid: uuidd ... OK [...SKIP...] --------------------------------------------------------------------- All 199 tests PASSED --------------------------------------------------------------------- make[3]: Leaving directory '/var/tmp/portage/sys-apps/util-linux-2.32-r4/work/util-linux-2.32-abi_x86_64.amd64' make[2]: Leaving directory '/var/tmp/portage/sys-apps/util-linux-2.32-r4/work/util-linux-2.32-abi_x86_64.amd64' make[1]: Leaving directory '/var/tmp/portage/sys-apps/util-linux-2.32-r4/work/util-linux-2.32-abi_x86_64.amd64' >>> Completed testing sys-apps/util-linux-2.32-r4
(In reply to Paolo Pedroni from comment #16) > (In reply to Thomas Deutschmann from comment #14) > > @ Toralf: Could you please run this just for native ABI so we can be sure it > > isn't a multilib issue? > > I tried this, and for native ABI tests pass fine: But did you experience the reported problem at all when building for multiple ABIs?
(In reply to Thomas Deutschmann from comment #17) > But did you experience the reported problem at all when building for > multiple ABIs? Yes.
*** Bug 662214 has been marked as a duplicate of this bug. ***
This doesn't happen when rebuilding util-linux-2.32-r3, but it happens when *upgrading* util-linux-2.30.2-r1 to util-linux-2.32-r3. $ sudo find /mnt/portagetmp/portage/sys-apps/util-linux-2.32-r4 -name uuidgen /mnt/portagetmp/portage/sys-apps/util-linux-2.32-r4/work/util-linux-2.32-abi_x86_64.amd64/uuidgen /mnt/portagetmp/portage/sys-apps/util-linux-2.32-r4/work/util-linux-2.32-abi_x86_64.amd64/.libs/uuidgen /mnt/portagetmp/portage/sys-apps/util-linux-2.32-r4/work/util-linux-2.32-abi_x86_32.x86/tests/output/uuid/uuidgen /mnt/portagetmp/portage/sys-apps/util-linux-2.32-r4/work/util-linux-2.32/bash-completion/uuidgen /mnt/portagetmp/portage/sys-apps/util-linux-2.32-r4/work/util-linux-2.32/tests/expected/uuid/uuidgen /mnt/portagetmp/portage/sys-apps/util-linux-2.32-r4/work/util-linux-2.32/tests/ts/uuid/uuidgen So, when adding the same lines to the test: $ cat /tmp/type.log /usr/bin/uuidgen $ cat /tmp/which.log /usr/bin/uuidgen $ cat /tmp/pwd.log /mnt/portagetmp/portage/sys-apps/util-linux-2.32-r4/work/util-linux-2.32-abi_x86_32.x86 uuidgen binary isn't built natively for x86_32, so it find the old version from util-linux-2.30.2-r1 at /usr/bin
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ecacc00aef905d57b8f8e6eccd21473494d53c72 commit ecacc00aef905d57b8f8e6eccd21473494d53c72 Author: Thomas Deutschmann <whissi@gentoo.org> AuthorDate: 2018-11-11 01:50:12 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2018-11-11 01:50:25 +0000 sys-apps/util-linux: fix oids test Closes: https://bugs.gentoo.org/657640 Package-Manager: Portage-2.3.51, Repoman-2.3.12 Signed-off-by: Thomas Deutschmann <whissi@gentoo.org> ...p-oids-test-when-uuidgen-is-not-available.patch | 41 ++++++++++++++++++++++ sys-apps/util-linux/util-linux-2.32.1-r1.ebuild | 1 + sys-apps/util-linux/util-linux-2.33.ebuild | 4 +++ sys-apps/util-linux/util-linux-9999.ebuild | 4 +++ 4 files changed, 50 insertions(+)
