File "/var/tmp/portage/net-misc/ntpsec-1.1.8/work/ntpsec-1.1.8-python3_6/wscript", line 164, in configure asciidocver_tuple = (int(lines[0]), int(lines[1]), int(lines[2])) ValueError: invalid literal for int() with base 10: '0rc1' * ERROR: net-misc/ntpsec-1.1.8::gentoo failed (configure phase): * configure failed * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_hardened-20200215-221702 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.2.0 * clang: clang version 9.0.1 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/9/bin llvm: 9.0.1 Available Python interpreters, in order of preference: [1] python3.8 [2] python3.6 [3] python3.7 (fallback) [4] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.41.0 * java-config: The following VMs are available for generation-2: ghc: The Glorious Glasgow Haskell Compilation System, version 8.0.2 repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Thu, 20 Feb 2020 23:37:37 +0000 emerge -qpvO net-misc/ntpsec [ebuild N ] net-misc/ntpsec-1.1.8 USE="seccomp smear -debug -doc -early -gdb -heat -libbsd -nist -ntpviz -rclock_arbiter -rclock_generic -rclock_gpsd -rclock_hpgps -rclock_jjy -rclock_local -rclock_modem -rclock_neoclock -rclock_nmea -rclock_oncore -rclock_pps -rclock_shm -rclock_spectracom -rclock_trimble -rclock_truetime -rclock_zyfer -samba -tests" PYTHON_TARGETS="python3_6"
Created attachment 614844 [details] emerge-info.txt
Created attachment 614846 [details] emerge-history.txt
Created attachment 614848 [details] environment
Created attachment 614850 [details] etc.portage.tbz2
Created attachment 614852 [details] logs.tbz2
Created attachment 614854 [details] net-misc:ntpsec-1.1.8:20200221-005313.log
Created attachment 614856 [details] temp.tbz2
Without looking at the includes... Mentioned upstream at [1] fixed with some dodgy policy at [2] dodgy policy revised at [3]. Should just work when the next release arrives. [1] https://gitlab.com/NTPsec/ntpsec/issues/632 [2] https://gitlab.com/NTPsec/ntpsec/-/merge_requests/1037 [3] https://gitlab.com/NTPsec/ntpsec/-/merge_requests/1095
fixed in 1.1.8 with upstream patch (next release can nuke the patch)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ff1d3efe61ef0acd2803c72d4c84722a627c0166 commit ff1d3efe61ef0acd2803c72d4c84722a627c0166 Author: Stephen Arnold <nerdboy@gentoo.org> AuthorDate: 2020-03-14 03:24:07 +0000 Commit: Stephen Arnold <nerdboy@gentoo.org> CommitDate: 2020-03-14 03:24:07 +0000 net-misc/ntpsec: add missing asciidoc patch, force docs to behave Bug: https://bugs.gentoo.org/710414 Package-Manager: Portage-2.3.67, Repoman-2.3.17 Signed-off-by: Steve Arnold <nerdboy@gentoo.org> .../ntpsec-1.1.8-fix-asciidoc-version-detect.patch | 372 +++++++++++++++++++++ net-misc/ntpsec/ntpsec-1.1.8.ebuild | 10 +- 2 files changed, 380 insertions(+), 2 deletions(-)
