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