* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst non-fatal build error - hardened/stage4-minimal.spec
@ 2019-03-02 16:13 catalyst
0 siblings, 0 replies; 7+ messages in thread
From: catalyst @ 2019-03-02 16:13 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f hardened/stage4-minimal.spec
02 Mar 2019 16:12:55 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
02 Mar 2019 16:12:55 UTC: NOTICE : conf_values[options] = {'clear-autoresume', 'bindist', 'preserve_libs', 'pkgcache'}
02 Mar 2019 16:12:55 UTC: NOTICE : Processing spec file: hardened/stage4-minimal.spec
02 Mar 2019 16:12:55 UTC: NOTICE : Using target: stage4
02 Mar 2019 16:12:55 UTC: NOTICE : Source file specification matching setting is: loose
02 Mar 2019 16:12:55 UTC: NOTICE : Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
02 Mar 2019 16:12:55 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.xz
02 Mar 2019 16:12:55 UTC: NOTICE : --- Running action sequence: unpack
02 Mar 2019 16:12:55 UTC: NOTICE : Clearing the chroot path ...
02 Mar 2019 16:12:55 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190302T160623Z
02 Mar 2019 16:12:55 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.xz
02 Mar 2019 16:12:55 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190302T160623Z (this may take some time) ..
02 Mar 2019 16:13:03 UTC: NOTICE : --- Running action sequence: unpack_snapshot
02 Mar 2019 16:13:03 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
02 Mar 2019 16:13:27 UTC: NOTICE : --- Running action sequence: config_profile_link
02 Mar 2019 16:13:27 UTC: NOTICE : --- Running action sequence: setup_confdir
02 Mar 2019 16:13:27 UTC: NOTICE : --- Running action sequence: portage_overlay
02 Mar 2019 16:13:27 UTC: NOTICE : --- Running action sequence: bind
02 Mar 2019 16:13:27 UTC: NOTICE : --- Running action sequence: chroot_setup
02 Mar 2019 16:13:27 UTC: NOTICE : Setting up chroot...
02 Mar 2019 16:13:27 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
02 Mar 2019 16:13:27 UTC: WARNING : If your build fails look here first as the possible problem.
02 Mar 2019 16:13:27 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
02 Mar 2019 16:13:27 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
02 Mar 2019 16:13:27 UTC: WARNING : You have been warned.
02 Mar 2019 16:13:27 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190302T160623Z/etc/portage/make.conf
02 Mar 2019 16:13:27 UTC: NOTICE : STICKY-CONFIG is enabled
02 Mar 2019 16:13:27 UTC: NOTICE : --- Running action sequence: setup_environment
02 Mar 2019 16:13:27 UTC: NOTICE : --- Running action sequence: build_packages
Copying stage4-chroot.sh to /tmp
copying stage4-chroot.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190302T160623Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190302T160623Z/tmp
Ensure the file has the executable bit set
Running stage4-chroot.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190302T160623Z /tmp/stage4-chroot.sh
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot --update --newuse sys-apps/portage
Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)
* Last emerge --sync was 210d 3h 8m 30s ago.
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-apps/portage-2.3.40-r1::gentoo
>>> Failed to emerge sys-apps/portage-2.3.40-r1, Log file:
>>> '/home/release/tmp/logs/sys-apps:portage-2.3.40-r1:20190302-161332.log'
* Package: sys-apps/portage-2.3.40-r1
* Repository: gentoo
* Maintainer: dev-portage@gentoo.org
* Upstream: dev-portage@gentoo.org
* USE: abi_x86_64 amd64 elibc_glibc ipc kernel_linux native-extensions python_targets_python2_7 python_targets_python3_6 userland_GNU xattr
* FEATURES: preserve-libs sandbox userpriv usersandbox
* Please follow the instructions in the news item:
* 2017-12-26-experimental-amd64-17-1-profiles
* or choose the 17.0 profile.
* ERROR: sys-apps/portage-2.3.40-r1::gentoo failed (setup phase):
* ERROR: 17.1 migration has not been performed!!
*
* Call stack:
* ebuild.sh, line 610: Called __source_all_bashrcs
* ebuild.sh, line 429: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 484: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* profile.bashrc, line 6: Called die
* The specific snippet of code:
* die "ERROR: 17.1 migration has not been performed!!"
*
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.40-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.40-r1::gentoo'`.
* The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.40-r1:20190302-161332.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.40-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.40-r1/temp/die.env'.
* Working directory: '/var/tmp/portage/sys-apps/portage-2.3.40-r1/homedir'
* S: '/var/tmp/portage/sys-apps/portage-2.3.40-r1/work/portage-2.3.40'
* Messages for package sys-apps/portage-2.3.40-r1:
* Log file: /home/release/tmp/logs/sys-apps:portage-2.3.40-r1:20190302-161332.log
* Please follow the instructions in the news item:
* 2017-12-26-experimental-amd64-17-1-profiles
* or choose the 17.0 profile.
* ERROR: sys-apps/portage-2.3.40-r1::gentoo failed (setup phase):
* ERROR: 17.1 migration has not been performed!!
*
* Call stack:
* ebuild.sh, line 610: Called __source_all_bashrcs
* ebuild.sh, line 429: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 484: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* profile.bashrc, line 6: Called die
* The specific snippet of code:
* die "ERROR: 17.1 migration has not been performed!!"
*
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.40-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.40-r1::gentoo'`.
* The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.40-r1:20190302-161332.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.40-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.40-r1/temp/die.env'.
* Working directory: '/var/tmp/portage/sys-apps/portage-2.3.40-r1/homedir'
* S: '/var/tmp/portage/sys-apps/portage-2.3.40-r1/work/portage-2.3.40'
02 Mar 2019 16:13:33 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'build_packages', 'net-misc/dhcp', 'sys-boot/grub', 'sys-apps/dmidecode', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-devel/bc', 'sys-power/acpid', 'app-crypt/gentoo-keys']) exited 1
02 Mar 2019 16:13:34 UTC: ERROR : CatalystError: stage4build aborting due to error.
02 Mar 2019 16:13:34 UTC: ERROR : Exception running action sequence build_packages
Traceback (most recent call last):
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1551, in build_packages
cmd(command, env=self.env)
File "/usr/lib64/python3.6/site-packages/catalyst/support.py", line 54, in cmd
print_traceback=False)
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'build_packages', 'net-misc/dhcp', 'sys-boot/grub', 'sys-apps/dmidecode', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-devel/bc', 'sys-power/acpid', 'app-crypt/gentoo-keys']) exited 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1455, in run
getattr(self, x)()
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1558, in build_packages
"build aborting due to error.")
catalyst.support.CatalystError: stage4build aborting due to error.
02 Mar 2019 16:13:35 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
30.11user 4.12system 0:40.26elapsed 85%CPU (0avgtext+0avgdata 351032maxresident)k
472inputs+3450360outputs (0major+502478minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20190302T160623Z.XUSM3x/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst non-fatal build error - hardened/stage4-minimal.spec
@ 2019-03-02 17:18 catalyst
0 siblings, 0 replies; 7+ messages in thread
From: catalyst @ 2019-03-02 17:18 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f hardened/stage4-minimal.spec
02 Mar 2019 17:17:57 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
02 Mar 2019 17:17:57 UTC: NOTICE : conf_values[options] = {'bindist', 'preserve_libs', 'clear-autoresume', 'pkgcache'}
02 Mar 2019 17:17:57 UTC: NOTICE : Processing spec file: hardened/stage4-minimal.spec
02 Mar 2019 17:17:57 UTC: NOTICE : Using target: stage4
02 Mar 2019 17:17:57 UTC: NOTICE : Source file specification matching setting is: loose
02 Mar 2019 17:17:57 UTC: NOTICE : Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
02 Mar 2019 17:17:57 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.xz
02 Mar 2019 17:17:57 UTC: NOTICE : --- Running action sequence: unpack
02 Mar 2019 17:17:57 UTC: NOTICE : Clearing the chroot path ...
02 Mar 2019 17:17:57 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190302T162037Z
02 Mar 2019 17:17:57 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.xz
02 Mar 2019 17:17:57 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190302T162037Z (this may take some time) ..
02 Mar 2019 17:18:03 UTC: NOTICE : --- Running action sequence: unpack_snapshot
02 Mar 2019 17:18:03 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
02 Mar 2019 17:18:50 UTC: NOTICE : --- Running action sequence: config_profile_link
02 Mar 2019 17:18:50 UTC: NOTICE : --- Running action sequence: setup_confdir
02 Mar 2019 17:18:50 UTC: NOTICE : --- Running action sequence: portage_overlay
02 Mar 2019 17:18:50 UTC: NOTICE : --- Running action sequence: bind
02 Mar 2019 17:18:50 UTC: NOTICE : --- Running action sequence: chroot_setup
02 Mar 2019 17:18:50 UTC: NOTICE : Setting up chroot...
02 Mar 2019 17:18:50 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
02 Mar 2019 17:18:50 UTC: WARNING : If your build fails look here first as the possible problem.
02 Mar 2019 17:18:50 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
02 Mar 2019 17:18:50 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
02 Mar 2019 17:18:50 UTC: WARNING : You have been warned.
02 Mar 2019 17:18:50 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190302T162037Z/etc/portage/make.conf
02 Mar 2019 17:18:50 UTC: NOTICE : STICKY-CONFIG is enabled
02 Mar 2019 17:18:50 UTC: NOTICE : --- Running action sequence: setup_environment
02 Mar 2019 17:18:50 UTC: NOTICE : --- Running action sequence: build_packages
Copying stage4-chroot.sh to /tmp
copying stage4-chroot.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190302T162037Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190302T162037Z/tmp
Ensure the file has the executable bit set
Running stage4-chroot.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190302T162037Z /tmp/stage4-chroot.sh
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot --update --newuse sys-apps/portage
Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)
>>> Emerging binary (1 of 1) sys-apps/portage-2.3.51-r1::gentoo
>>> Failed to emerge sys-apps/portage-2.3.51-r1, Log file:
>>> '/home/release/tmp/logs/sys-apps:portage-2.3.51-r1:20190302-171852.log'
>>> Extracting info
* Package: sys-apps/portage-2.3.51-r1
* Repository: gentoo
* USE: native-extensions ipc abi_x86_64 amd64 userland_GNU python_targets_python2_7 kernel_linux xattr elibc_glibc python_targets_python3_6
* FEATURES: preserve-libs sandbox userpriv usersandbox
* Please follow the instructions in the news item:
* 2017-12-26-experimental-amd64-17-1-profiles
* or choose the 17.0 profile.
* ERROR: sys-apps/portage-2.3.51-r1::gentoo failed (setup phase):
* ERROR: 17.1 migration has not been performed!!
*
* Call stack:
* ebuild.sh, line 792: Called __ebuild_main 'setup'
* phase-functions.sh, line 984: Called __source_all_bashrcs
* ebuild.sh, line 429: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 484: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* profile.bashrc, line 6: Called die
* The specific snippet of code:
* die "ERROR: 17.1 migration has not been performed!!"
*
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.51-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.51-r1::gentoo'`.
* The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.51-r1:20190302-171852.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.51-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.51-r1/temp/environment'.
* Working directory: '/var/tmp/portage/sys-apps/portage-2.3.51-r1/homedir'
* S: '/var/tmp/portage/sys-apps/portage-2.3.51-r1/work/portage-2.3.51'
* Messages for package sys-apps/portage-2.3.51-r1:
* Log file: /home/release/tmp/logs/sys-apps:portage-2.3.51-r1:20190302-171852.log
* Please follow the instructions in the news item:
* 2017-12-26-experimental-amd64-17-1-profiles
* or choose the 17.0 profile.
* ERROR: sys-apps/portage-2.3.51-r1::gentoo failed (setup phase):
* ERROR: 17.1 migration has not been performed!!
*
* Call stack:
* ebuild.sh, line 792: Called __ebuild_main 'setup'
* phase-functions.sh, line 984: Called __source_all_bashrcs
* ebuild.sh, line 429: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 484: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* profile.bashrc, line 6: Called die
* The specific snippet of code:
* die "ERROR: 17.1 migration has not been performed!!"
*
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.51-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.51-r1::gentoo'`.
* The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.51-r1:20190302-171852.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.51-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.51-r1/temp/environment'.
* Working directory: '/var/tmp/portage/sys-apps/portage-2.3.51-r1/homedir'
* S: '/var/tmp/portage/sys-apps/portage-2.3.51-r1/work/portage-2.3.51'
02 Mar 2019 17:18:53 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'build_packages', 'net-misc/dhcp', 'sys-boot/grub', 'sys-apps/dmidecode', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-devel/bc', 'sys-power/acpid', 'app-crypt/gentoo-keys']) exited 1
02 Mar 2019 17:18:53 UTC: ERROR : CatalystError: stage4build aborting due to error.
02 Mar 2019 17:18:53 UTC: ERROR : Exception running action sequence build_packages
Traceback (most recent call last):
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1551, in build_packages
cmd(command, env=self.env)
File "/usr/lib64/python3.6/site-packages/catalyst/support.py", line 54, in cmd
print_traceback=False)
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'build_packages', 'net-misc/dhcp', 'sys-boot/grub', 'sys-apps/dmidecode', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-devel/bc', 'sys-power/acpid', 'app-crypt/gentoo-keys']) exited 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1455, in run
getattr(self, x)()
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1558, in build_packages
"build aborting due to error.")
catalyst.support.CatalystError: stage4build aborting due to error.
02 Mar 2019 17:18:53 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
29.03user 3.96system 0:56.78elapsed 58%CPU (0avgtext+0avgdata 351016maxresident)k
440inputs+3477888outputs (0major+324347minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20190302T162037Z.utKSjw/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst non-fatal build error - hardened/stage4-minimal.spec
@ 2019-06-11 1:33 catalyst
0 siblings, 0 replies; 7+ messages in thread
From: catalyst @ 2019-06-11 1:33 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f hardened/stage4-minimal.spec
11 Jun 2019 01:32:55 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
11 Jun 2019 01:32:55 UTC: NOTICE : conf_values[options] = {'pkgcache', 'clear-autoresume', 'bindist', 'preserve_libs'}
11 Jun 2019 01:32:55 UTC: NOTICE : Processing spec file: hardened/stage4-minimal.spec
11 Jun 2019 01:32:55 UTC: NOTICE : Using target: stage4
11 Jun 2019 01:32:55 UTC: NOTICE : Source file specification matching setting is: loose
11 Jun 2019 01:32:55 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
11 Jun 2019 01:32:55 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.xz
11 Jun 2019 01:32:55 UTC: NOTICE : --- Running action sequence: unpack
11 Jun 2019 01:32:55 UTC: NOTICE : Clearing the chroot path ...
11 Jun 2019 01:32:55 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190611T012607Z
11 Jun 2019 01:32:55 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.xz
11 Jun 2019 01:32:55 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190611T012607Z (this may take some time) ..
11 Jun 2019 01:32:59 UTC: NOTICE : --- Running action sequence: unpack_snapshot
11 Jun 2019 01:32:59 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
11 Jun 2019 01:33:27 UTC: NOTICE : --- Running action sequence: config_profile_link
11 Jun 2019 01:33:27 UTC: NOTICE : --- Running action sequence: setup_confdir
11 Jun 2019 01:33:27 UTC: NOTICE : --- Running action sequence: portage_overlay
11 Jun 2019 01:33:27 UTC: NOTICE : --- Running action sequence: bind
11 Jun 2019 01:33:27 UTC: NOTICE : --- Running action sequence: chroot_setup
11 Jun 2019 01:33:27 UTC: NOTICE : Setting up chroot...
11 Jun 2019 01:33:27 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
11 Jun 2019 01:33:27 UTC: WARNING : If your build fails look here first as the possible problem.
11 Jun 2019 01:33:27 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
11 Jun 2019 01:33:27 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
11 Jun 2019 01:33:27 UTC: WARNING : You have been warned.
11 Jun 2019 01:33:27 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190611T012607Z/etc/portage/make.conf
11 Jun 2019 01:33:27 UTC: NOTICE : STICKY-CONFIG is enabled
11 Jun 2019 01:33:27 UTC: NOTICE : --- Running action sequence: setup_environment
11 Jun 2019 01:33:27 UTC: NOTICE : --- Running action sequence: build_packages
Copying stage4-chroot.sh to /tmp
copying stage4-chroot.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190611T012607Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190611T012607Z/tmp
Ensure the file has the executable bit set
Running stage4-chroot.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190611T012607Z /tmp/stage4-chroot.sh
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --binpkg-respect-use=y --newuse --oneshot --update --newuse sys-apps/portage
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-apps/portage-2.3.62-r2
* Determining the location of the kernel source code
* Unable to find kernel sources at /usr/src/linux
* Please make sure that /usr/src/linux points at your running kernel,
* (or the kernel you wish to build against).
* Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Checking for suitable kernel configuration options...
[ ok ]
>>> Emerging (1 of 1) sys-apps/portage-2.3.62-r2::gentoo
>>> Failed to emerge sys-apps/portage-2.3.62-r2, Log file:
>>> '/home/release/tmp/logs/sys-apps:portage-2.3.62-r2:20190611-013332.log'
* Package: sys-apps/portage-2.3.62-r2
* Repository: gentoo
* Maintainer: dev-portage@gentoo.org
* Upstream: dev-portage@gentoo.org
* USE: abi_x86_64 amd64 elibc_glibc ipc kernel_linux native-extensions python_targets_python2_7 python_targets_python3_6 rsync-verify userland_GNU xattr
* FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox
* Please follow the instructions in the news item:
* 2017-12-26-experimental-amd64-17-1-profiles
* or choose the 17.0 profile.
* ERROR: sys-apps/portage-2.3.62-r2::gentoo failed (setup phase):
* ERROR: 17.1 migration has not been performed!!
*
* Call stack:
* ebuild.sh, line 598: Called __source_all_bashrcs
* ebuild.sh, line 417: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 474: Called __qa_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 111: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* profile.bashrc, line 6: Called die
* The specific snippet of code:
* die "ERROR: 17.1 migration has not been performed!!"
*
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.62-r2::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.62-r2::gentoo'`.
* The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.62-r2:20190611-013332.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.62-r2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.62-r2/temp/die.env'.
* Working directory: '/var/tmp/portage/sys-apps/portage-2.3.62-r2/homedir'
* S: '/var/tmp/portage/sys-apps/portage-2.3.62-r2/work/portage-2.3.62'
* Messages for package sys-apps/portage-2.3.62-r2:
* Log file: /home/release/tmp/logs/sys-apps:portage-2.3.62-r2:20190611-013331.log
* Unable to find kernel sources at /usr/src/linux
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Messages for package sys-apps/portage-2.3.62-r2:
* Log file: /home/release/tmp/logs/sys-apps:portage-2.3.62-r2:20190611-013332.log
* Please follow the instructions in the news item:
* 2017-12-26-experimental-amd64-17-1-profiles
* or choose the 17.0 profile.
* ERROR: sys-apps/portage-2.3.62-r2::gentoo failed (setup phase):
* ERROR: 17.1 migration has not been performed!!
*
* Call stack:
* ebuild.sh, line 598: Called __source_all_bashrcs
* ebuild.sh, line 417: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 474: Called __qa_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 111: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* profile.bashrc, line 6: Called die
* The specific snippet of code:
* die "ERROR: 17.1 migration has not been performed!!"
*
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.62-r2::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.62-r2::gentoo'`.
* The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.62-r2:20190611-013332.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.62-r2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.62-r2/temp/die.env'.
* Working directory: '/var/tmp/portage/sys-apps/portage-2.3.62-r2/homedir'
* S: '/var/tmp/portage/sys-apps/portage-2.3.62-r2/work/portage-2.3.62'
11 Jun 2019 01:33:33 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'build_packages', 'net-misc/dhcp', 'sys-boot/grub', 'sys-apps/dmidecode', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-devel/bc', 'sys-power/acpid', 'app-crypt/gentoo-keys']) exited 1
11 Jun 2019 01:33:33 UTC: ERROR : CatalystError: stage4build aborting due to error.
11 Jun 2019 01:33:33 UTC: ERROR : Exception running action sequence build_packages
Traceback (most recent call last):
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1561, in build_packages
cmd(command, env=self.env)
File "/usr/lib64/python3.6/site-packages/catalyst/support.py", line 54, in cmd
print_traceback=False)
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'build_packages', 'net-misc/dhcp', 'sys-boot/grub', 'sys-apps/dmidecode', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-devel/bc', 'sys-power/acpid', 'app-crypt/gentoo-keys']) exited 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1465, in run
getattr(self, x)()
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1568, in build_packages
"build aborting due to error.")
catalyst.support.CatalystError: stage4build aborting due to error.
11 Jun 2019 01:33:33 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
33.94user 4.45system 0:38.93elapsed 98%CPU (0avgtext+0avgdata 362904maxresident)k
312inputs+3908264outputs (0major+614952minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20190611T012607Z.4ssuYw/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst non-fatal build error - hardened/stage4-minimal.spec
@ 2019-06-11 9:26 catalyst
0 siblings, 0 replies; 7+ messages in thread
From: catalyst @ 2019-06-11 9:26 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f hardened/stage4-minimal.spec
11 Jun 2019 09:26:48 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
11 Jun 2019 09:26:48 UTC: NOTICE : conf_values[options] = {'preserve_libs', 'pkgcache', 'bindist', 'clear-autoresume'}
11 Jun 2019 09:26:48 UTC: NOTICE : Processing spec file: hardened/stage4-minimal.spec
11 Jun 2019 09:26:48 UTC: NOTICE : Using target: stage4
11 Jun 2019 09:26:48 UTC: NOTICE : Source file specification matching setting is: loose
11 Jun 2019 09:26:48 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
11 Jun 2019 09:26:48 UTC: ERROR : CatalystError: File Not Found: /home/release/buildroot/amd64-exp/builds/hardened/stage3-amd64-hardened-latest
Command exited with non-zero status 2
0.20user 0.02system 0:00.29elapsed 79%CPU (0avgtext+0avgdata 18212maxresident)k
0inputs+0outputs (0major+9474minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20190611T092541Z.nNqC3R/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst non-fatal build error - hardened/stage4-minimal.spec
@ 2019-06-14 18:35 catalyst
0 siblings, 0 replies; 7+ messages in thread
From: catalyst @ 2019-06-14 18:35 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f hardened/stage4-minimal.spec
14 Jun 2019 18:35:34 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
14 Jun 2019 18:35:34 UTC: NOTICE : conf_values[options] = {'bindist', 'clear-autoresume', 'preserve_libs', 'pkgcache'}
14 Jun 2019 18:35:34 UTC: NOTICE : Processing spec file: hardened/stage4-minimal.spec
14 Jun 2019 18:35:34 UTC: NOTICE : Using target: stage4
14 Jun 2019 18:35:34 UTC: NOTICE : Source file specification matching setting is: loose
14 Jun 2019 18:35:34 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
14 Jun 2019 18:35:35 UTC: ERROR : CatalystError: File Not Found: /home/release/buildroot/amd64-exp/builds/hardened/stage3-amd64-hardened-latest
Command exited with non-zero status 2
0.22user 0.00system 0:00.32elapsed 72%CPU (0avgtext+0avgdata 18080maxresident)k
0inputs+0outputs (0major+9482minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20190614T183511Z.BWvov2/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst non-fatal build error - hardened/stage4-minimal.spec
@ 2019-06-15 6:32 catalyst
0 siblings, 0 replies; 7+ messages in thread
From: catalyst @ 2019-06-15 6:32 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
Full build log at /home/release/tmp/run/catalyst-auto.20190614T184237Z.7Vt1sS/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst non-fatal build error - hardened/stage4-minimal.spec
@ 2019-06-15 6:32 catalyst
0 siblings, 0 replies; 7+ messages in thread
From: catalyst @ 2019-06-15 6:32 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
Full build log at /home/release/tmp/run/catalyst-auto.20190614T185156Z.VHU94x/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2019-06-15 6:32 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-06-14 18:35 [gentoo-releng-autobuilds] [amd64-experimental] Catalyst non-fatal build error - hardened/stage4-minimal.spec catalyst
-- strict thread matches above, loose matches on Subject: below --
2019-06-15 6:32 catalyst
2019-06-15 6:32 catalyst
2019-06-11 9:26 catalyst
2019-06-11 1:33 catalyst
2019-03-02 17:18 catalyst
2019-03-02 16:13 catalyst
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox