Gentoo Archives: gentoo-releng-autobuilds

From: catalyst@××××××××××××××××.name
To: jmbsvicetto@×××××.com, gentoo-releng-autobuilds@l.g.o
Subject: [gentoo-releng-autobuilds] [amd64-auto] Catalyst non-fatal build error - hardened/stage4-nomultilib-minimal.spec
Date: Tue, 16 Jul 2019 03:40:16
Message-Id: 20190716034013.5EBC7603D4@thor.jmbsvicetto.name
1 *** Running command: time catalyst -a -c /etc/catalyst/release/amd64-auto.conf -f hardened/stage4-nomultilib-minimal.spec
2 16 Jul 2019 03:39:09 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
3 16 Jul 2019 03:39:09 UTC: NOTICE : conf_values[options] = {'pkgcache', 'clear-autoresume', 'preserve_libs', 'bindist'}
4 16 Jul 2019 03:39:09 UTC: NOTICE : Processing spec file: hardened/stage4-nomultilib-minimal.spec
5 16 Jul 2019 03:39:09 UTC: NOTICE : Using target: stage4
6 16 Jul 2019 03:39:09 UTC: NOTICE : Source file specification matching setting is: loose
7 16 Jul 2019 03:39:09 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
8 16 Jul 2019 03:39:09 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.xz
9 16 Jul 2019 03:39:09 UTC: NOTICE : --- Running action sequence: unpack
10 16 Jul 2019 03:39:09 UTC: NOTICE : Clearing the chroot path ...
11 16 Jul 2019 03:39:09 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-nomultilib-20190716T030312Z
12 16 Jul 2019 03:39:09 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.xz
13 16 Jul 2019 03:39:09 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-nomultilib-20190716T030312Z (this may take some time) ..
14 16 Jul 2019 03:39:13 UTC: NOTICE : --- Running action sequence: unpack_snapshot
15 16 Jul 2019 03:39:13 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
16 16 Jul 2019 03:39:42 UTC: NOTICE : --- Running action sequence: config_profile_link
17 16 Jul 2019 03:39:42 UTC: NOTICE : --- Running action sequence: setup_confdir
18 16 Jul 2019 03:39:42 UTC: NOTICE : --- Running action sequence: portage_overlay
19 16 Jul 2019 03:39:42 UTC: NOTICE : --- Running action sequence: bind
20 16 Jul 2019 03:39:42 UTC: NOTICE : --- Running action sequence: chroot_setup
21 16 Jul 2019 03:39:42 UTC: NOTICE : Setting up chroot...
22 16 Jul 2019 03:39:42 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
23 16 Jul 2019 03:39:42 UTC: WARNING : If your build fails look here first as the possible problem.
24 16 Jul 2019 03:39:42 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
25 16 Jul 2019 03:39:42 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
26 16 Jul 2019 03:39:42 UTC: WARNING : You have been warned.
27 16 Jul 2019 03:39:42 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-nomultilib-20190716T030312Z/etc/portage/make.conf
28 16 Jul 2019 03:39:42 UTC: NOTICE : STICKY-CONFIG is enabled
29 16 Jul 2019 03:39:42 UTC: NOTICE : --- Running action sequence: setup_environment
30 16 Jul 2019 03:39:42 UTC: NOTICE : --- Running action sequence: build_packages
31 Copying stage4-chroot.sh to /tmp
32 copying stage4-chroot.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-nomultilib-20190716T030312Z/tmp
33 copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-nomultilib-20190716T030312Z/tmp
34 Ensure the file has the executable bit set
35 Running stage4-chroot.sh in chroot:
36 chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-nomultilib-20190716T030312Z /tmp/stage4-chroot.sh
37 >>> Regenerating /etc/ld.so.cache...
38 emerge --quiet --usepkg --buildpkg --binpkg-respect-use=y --newuse --oneshot --update --newuse sys-apps/portage
39
40 Performing Global Updates
41 (Could take a couple of minutes if you have a lot of binary packages.)
42
43
44 Bringing system up to date using profile specific use flags
45 emerge --quiet --usepkg --buildpkg --binpkg-respect-use=y --newuse -u @system
46 >>> Emerging binary (1 of 3) sys-apps/busybox-1.29.3::gentoo
47 >>> Failed to emerge sys-apps/busybox-1.29.3, Log file:
48 >>> '/home/release/tmp/logs/sys-apps:busybox-1.29.3:20190716-034010.log'
49 >>> Extracting info
50 * Package: sys-apps/busybox-1.29.3
51 * Repository: gentoo
52 * USE: kernel_linux userland_GNU elibc_glibc amd64 ipv6 abi_x86_64
53 * FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox
54 * Please follow the instructions in the news item:
55 * 2019-06-05-amd64-17-1-profiles-are-now-stable
56 * or choose the 17.0 profile.
57 * ERROR: sys-apps/busybox-1.29.3::gentoo failed (setup phase):
58 * ERROR: 17.1 migration has not been performed!!
59 *
60 * Call stack:
61 * ebuild.sh, line 780: Called __ebuild_main 'setup'
62 * phase-functions.sh, line 988: Called __source_all_bashrcs
63 * ebuild.sh, line 417: Called __try_source '/var/db/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
64 * ebuild.sh, line 474: Called __qa_source '/var/db/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
65 * ebuild.sh, line 111: Called source '/var/db/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
66 * profile.bashrc, line 6: Called die
67 * The specific snippet of code:
68 * die "ERROR: 17.1 migration has not been performed!!"
69 *
70 * If you need support, post the output of `emerge --info '=sys-apps/busybox-1.29.3::gentoo'`,
71 * the complete build log and the output of `emerge -pqv '=sys-apps/busybox-1.29.3::gentoo'`.
72 * The complete build log is located at '/home/release/tmp/logs/sys-apps:busybox-1.29.3:20190716-034010.log'.
73 * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/busybox-1.29.3/temp/build.log'.
74 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/busybox-1.29.3/temp/environment'.
75 * Working directory: '/var/tmp/portage/sys-apps/busybox-1.29.3/homedir'
76 * S: '/var/tmp/portage/sys-apps/busybox-1.29.3/work/busybox-1.29.3'
77 * Messages for package sys-apps/busybox-1.29.3:
78 * Log file: /home/release/tmp/logs/sys-apps:busybox-1.29.3:20190716-034010.log
79 * Please follow the instructions in the news item:
80 * 2019-06-05-amd64-17-1-profiles-are-now-stable
81 * or choose the 17.0 profile.
82 * ERROR: sys-apps/busybox-1.29.3::gentoo failed (setup phase):
83 * ERROR: 17.1 migration has not been performed!!
84 *
85 * Call stack:
86 * ebuild.sh, line 780: Called __ebuild_main 'setup'
87 * phase-functions.sh, line 988: Called __source_all_bashrcs
88 * ebuild.sh, line 417: Called __try_source '/var/db/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
89 * ebuild.sh, line 474: Called __qa_source '/var/db/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
90 * ebuild.sh, line 111: Called source '/var/db/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
91 * profile.bashrc, line 6: Called die
92 * The specific snippet of code:
93 * die "ERROR: 17.1 migration has not been performed!!"
94 *
95 * If you need support, post the output of `emerge --info '=sys-apps/busybox-1.29.3::gentoo'`,
96 * the complete build log and the output of `emerge -pqv '=sys-apps/busybox-1.29.3::gentoo'`.
97 * The complete build log is located at '/home/release/tmp/logs/sys-apps:busybox-1.29.3:20190716-034010.log'.
98 * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/busybox-1.29.3/temp/build.log'.
99 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/busybox-1.29.3/temp/environment'.
100 * Working directory: '/var/tmp/portage/sys-apps/busybox-1.29.3/homedir'
101 * S: '/var/tmp/portage/sys-apps/busybox-1.29.3/work/busybox-1.29.3'
102
103
104 16 Jul 2019 03:40:11 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'build_packages', 'net-misc/dhcp', 'net-misc/iputils', 'sys-boot/grub', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-devel/bc', 'sys-power/acpid', 'app-crypt/gentoo-keys']) exited 1
105 16 Jul 2019 03:40:11 UTC: ERROR : CatalystError: stage4build aborting due to error.
106 16 Jul 2019 03:40:11 UTC: ERROR : Exception running action sequence build_packages
107 Traceback (most recent call last):
108 File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1561, in build_packages
109 cmd(command, env=self.env)
110 File "/usr/lib64/python3.6/site-packages/catalyst/support.py", line 54, in cmd
111 print_traceback=False)
112 catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'build_packages', 'net-misc/dhcp', 'net-misc/iputils', 'sys-boot/grub', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-devel/bc', 'sys-power/acpid', 'app-crypt/gentoo-keys']) exited 1
113
114 During handling of the above exception, another exception occurred:
115
116 Traceback (most recent call last):
117 File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1465, in run
118 getattr(self, x)()
119 File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1568, in build_packages
120 "build aborting due to error.")
121 catalyst.support.CatalystError: stage4build aborting due to error.
122 16 Jul 2019 03:40:11 UTC: NOTICE : Cleaning up... Running unbind()
123 Command exited with non-zero status 2
124 32.90user 4.63system 1:02.56elapsed 59%CPU (0avgtext+0avgdata 351692maxresident)k
125 576inputs+3680840outputs (0major+363296minor)pagefaults 0swaps
126
127
128
129 Full build log at /home/release/tmp/run/catalyst-auto.20190716T030312Z.9vULzE/log/hardened_stage4-nomultilib-minimal.log