Gentoo Archives: gentoo-releng-autobuilds

From: catalyst@××××××××××××××××.name
To: jmbsvicetto@×××××.com, gentoo-releng-autobuilds@l.g.o
Subject: [gentoo-releng-autobuilds] [amd64-experimental] Catalyst non-fatal build error - stage4-minimal.spec
Date: Sat, 02 Mar 2019 16:21:51
Message-Id: 20190302162147.4338361BA1@thor.jmbsvicetto.name
1 *** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f stage4-minimal.spec
2 02 Mar 2019 16:21:11 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
3 02 Mar 2019 16:21:11 UTC: NOTICE : conf_values[options] = {'preserve_libs', 'bindist', 'clear-autoresume', 'pkgcache'}
4 02 Mar 2019 16:21:11 UTC: NOTICE : Processing spec file: stage4-minimal.spec
5 02 Mar 2019 16:21:11 UTC: NOTICE : Using target: stage4
6 02 Mar 2019 16:21:11 UTC: NOTICE : Source file specification matching setting is: loose
7 02 Mar 2019 16:21:11 UTC: NOTICE : Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
8 02 Mar 2019 16:21:12 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-latest.tar.xz
9 02 Mar 2019 16:21:12 UTC: NOTICE : --- Running action sequence: unpack
10 02 Mar 2019 16:21:12 UTC: NOTICE : Clearing the chroot path ...
11 02 Mar 2019 16:21:12 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-20190302T162037Z
12 02 Mar 2019 16:21:12 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-latest.tar.xz
13 02 Mar 2019 16:21:12 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-20190302T162037Z (this may take some time) ..
14 02 Mar 2019 16:21:16 UTC: NOTICE : --- Running action sequence: unpack_snapshot
15 02 Mar 2019 16:21:16 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
16 02 Mar 2019 16:21:30 UTC: NOTICE : --- Running action sequence: config_profile_link
17 02 Mar 2019 16:21:30 UTC: NOTICE : --- Running action sequence: setup_confdir
18 02 Mar 2019 16:21:30 UTC: NOTICE : --- Running action sequence: portage_overlay
19 02 Mar 2019 16:21:30 UTC: NOTICE : --- Running action sequence: bind
20 02 Mar 2019 16:21:30 UTC: NOTICE : --- Running action sequence: chroot_setup
21 02 Mar 2019 16:21:30 UTC: NOTICE : Setting up chroot...
22 02 Mar 2019 16:21:30 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
23 02 Mar 2019 16:21:30 UTC: WARNING : If your build fails look here first as the possible problem.
24 02 Mar 2019 16:21:30 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
25 02 Mar 2019 16:21:30 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
26 02 Mar 2019 16:21:30 UTC: WARNING : You have been warned.
27 02 Mar 2019 16:21:30 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-20190302T162037Z/etc/portage/make.conf
28 02 Mar 2019 16:21:30 UTC: NOTICE : STICKY-CONFIG is enabled
29 02 Mar 2019 16:21:30 UTC: NOTICE : --- Running action sequence: setup_environment
30 02 Mar 2019 16:21:30 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/default/stage4-amd64-minimal-20190302T162037Z/tmp
33 copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-minimal-20190302T162037Z/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/default/stage4-amd64-minimal-20190302T162037Z /tmp/stage4-chroot.sh
37 >>> Regenerating /etc/ld.so.cache...
38 emerge --quiet --usepkg --buildpkg --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 >>> Emerging binary (1 of 1) sys-apps/portage-2.3.51-r1::gentoo
45 >>> Failed to emerge sys-apps/portage-2.3.51-r1, Log file:
46 >>> '/home/release/tmp/logs/sys-apps:portage-2.3.51-r1:20190302-162140.log'
47 >>> Extracting info
48 * Package: sys-apps/portage-2.3.51-r1
49 * Repository: gentoo
50 * USE: python_targets_python3_6 elibc_glibc userland_GNU abi_x86_64 ipc amd64 native-extensions xattr kernel_linux python_targets_python2_7
51 * FEATURES: preserve-libs sandbox userpriv usersandbox
52 * Please follow the instructions in the news item:
53 * 2017-12-26-experimental-amd64-17-1-profiles
54 * or choose the 17.0 profile.
55 * ERROR: sys-apps/portage-2.3.51-r1::gentoo failed (setup phase):
56 * ERROR: 17.1 migration has not been performed!!
57 *
58 * Call stack:
59 * ebuild.sh, line 792: Called __ebuild_main 'setup'
60 * phase-functions.sh, line 984: Called __source_all_bashrcs
61 * ebuild.sh, line 429: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
62 * ebuild.sh, line 484: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
63 * profile.bashrc, line 6: Called die
64 * The specific snippet of code:
65 * die "ERROR: 17.1 migration has not been performed!!"
66 *
67 * If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.51-r1::gentoo'`,
68 * the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.51-r1::gentoo'`.
69 * The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.51-r1:20190302-162140.log'.
70 * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.51-r1/temp/build.log'.
71 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.51-r1/temp/environment'.
72 * Working directory: '/var/tmp/portage/sys-apps/portage-2.3.51-r1/homedir'
73 * S: '/var/tmp/portage/sys-apps/portage-2.3.51-r1/work/portage-2.3.51'
74 * Messages for package sys-apps/portage-2.3.51-r1:
75 * Log file: /home/release/tmp/logs/sys-apps:portage-2.3.51-r1:20190302-162140.log
76 * Please follow the instructions in the news item:
77 * 2017-12-26-experimental-amd64-17-1-profiles
78 * or choose the 17.0 profile.
79 * ERROR: sys-apps/portage-2.3.51-r1::gentoo failed (setup phase):
80 * ERROR: 17.1 migration has not been performed!!
81 *
82 * Call stack:
83 * ebuild.sh, line 792: Called __ebuild_main 'setup'
84 * phase-functions.sh, line 984: Called __source_all_bashrcs
85 * ebuild.sh, line 429: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
86 * ebuild.sh, line 484: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
87 * profile.bashrc, line 6: Called die
88 * The specific snippet of code:
89 * die "ERROR: 17.1 migration has not been performed!!"
90 *
91 * If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.51-r1::gentoo'`,
92 * the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.51-r1::gentoo'`.
93 * The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.51-r1:20190302-162140.log'.
94 * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.51-r1/temp/build.log'.
95 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.51-r1/temp/environment'.
96 * Working directory: '/var/tmp/portage/sys-apps/portage-2.3.51-r1/homedir'
97 * S: '/var/tmp/portage/sys-apps/portage-2.3.51-r1/work/portage-2.3.51'
98
99
100 02 Mar 2019 16:21:41 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
101 02 Mar 2019 16:21:41 UTC: ERROR : CatalystError: stage4build aborting due to error.
102 02 Mar 2019 16:21:41 UTC: ERROR : Exception running action sequence build_packages
103 Traceback (most recent call last):
104 File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1551, in build_packages
105 cmd(command, env=self.env)
106 File "/usr/lib64/python3.6/site-packages/catalyst/support.py", line 54, in cmd
107 print_traceback=False)
108 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
109
110 During handling of the above exception, another exception occurred:
111
112 Traceback (most recent call last):
113 File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1455, in run
114 getattr(self, x)()
115 File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1558, in build_packages
116 "build aborting due to error.")
117 catalyst.support.CatalystError: stage4build aborting due to error.
118 02 Mar 2019 16:21:46 UTC: NOTICE : Cleaning up... Running unbind()
119 Command exited with non-zero status 2
120 35.49user 4.51system 0:35.42elapsed 112%CPU (0avgtext+0avgdata 359008maxresident)k
121 328inputs+3887912outputs (0major+326353minor)pagefaults 0swaps
122
123
124
125 Full build log at /home/release/tmp/run/catalyst-auto.20190302T162037Z.utKSjw/log/stage4-minimal.log