* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst fatal build error - stage1-nomultilib.spec
@ 2019-03-02 16:09 catalyst
0 siblings, 0 replies; 5+ messages in thread
From: catalyst @ 2019-03-02 16:09 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f stage1-nomultilib.spec
02 Mar 2019 16:09:14 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
02 Mar 2019 16:09:14 UTC: NOTICE : conf_values[options] = {'clear-autoresume', 'bindist', 'preserve_libs', 'pkgcache'}
02 Mar 2019 16:09:14 UTC: NOTICE : Processing spec file: stage1-nomultilib.spec
02 Mar 2019 16:09:14 UTC: NOTICE : Using target: stage1
02 Mar 2019 16:09:14 UTC: NOTICE : Source file specification matching setting is: loose
02 Mar 2019 16:09:14 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
02 Mar 2019 16:09:15 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-nomultilib-latest.tar.xz
02 Mar 2019 16:09:15 UTC: NOTICE : stage1 stage path is /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190302T160623Z/tmp/stage1root
02 Mar 2019 16:09:15 UTC: NOTICE : --- Running action sequence: unpack
02 Mar 2019 16:09:15 UTC: NOTICE : Clearing the chroot path ...
02 Mar 2019 16:09:15 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190302T160623Z
02 Mar 2019 16:09:15 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-nomultilib-latest.tar.xz
02 Mar 2019 16:09:15 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190302T160623Z (this may take some time) ..
02 Mar 2019 16:09:19 UTC: NOTICE : --- Running action sequence: unpack_snapshot
02 Mar 2019 16:09:19 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
02 Mar 2019 16:09:34 UTC: NOTICE : --- Running action sequence: setup_confdir
02 Mar 2019 16:09:34 UTC: NOTICE : --- Running action sequence: portage_overlay
02 Mar 2019 16:09:34 UTC: NOTICE : --- Running action sequence: base_dirs
02 Mar 2019 16:09:34 UTC: NOTICE : --- Running action sequence: bind
02 Mar 2019 16:09:34 UTC: NOTICE : --- Running action sequence: chroot_setup
02 Mar 2019 16:09:34 UTC: NOTICE : Setting up chroot...
02 Mar 2019 16:09:34 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
02 Mar 2019 16:09:34 UTC: WARNING : If your build fails look here first as the possible problem.
02 Mar 2019 16:09:34 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
02 Mar 2019 16:09:34 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
02 Mar 2019 16:09:34 UTC: WARNING : You have been warned.
02 Mar 2019 16:09:34 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190302T160623Z/etc/portage/make.conf
02 Mar 2019 16:09:34 UTC: NOTICE : STICKY-CONFIG is enabled
02 Mar 2019 16:09:34 UTC: NOTICE : --- Running action sequence: setup_environment
02 Mar 2019 16:09:34 UTC: NOTICE : --- Running action sequence: run_local
copying make.conf to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190302T160623Z/tmp/stage1root/etc/portage
Copying stage1-chroot.sh to /tmp
copying stage1-chroot.sh to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190302T160623Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190302T160623Z/tmp
Ensure the file has the executable bit set
Running stage1-chroot.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190302T160623Z /tmp/stage1-chroot.sh
>>> Regenerating /etc/ld.so.cache...
Adding USE="${USE} build" to make.conf for portage build
emerge --quiet --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 4m 36s 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-160938.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 build elibc_glibc ipc kernel_linux native-extensions python_targets_python2_7 python_targets_python3_6 rsync-verify 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-160938.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-160938.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-160938.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:09:39 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1
02 Mar 2019 16:09:39 UTC: ERROR : CatalystError: Stage build aborting due to error.
02 Mar 2019 16:09:39 UTC: ERROR : Exception running action sequence run_local
Traceback (most recent call last):
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1355, in run_local
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/stage1/stage1-controller.sh', 'run']) 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 1364, in run_local
print_traceback=False)
catalyst.support.CatalystError: Stage build aborting due to error.
02 Mar 2019 16:09:39 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
32.10user 3.90system 0:25.38elapsed 141%CPU (0avgtext+0avgdata 357976maxresident)k
0inputs+3626840outputs (0major+498387minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20190302T160623Z.XUSM3x/log/stage1-nomultilib.log
^ permalink raw reply [flat|nested] 5+ messages in thread
* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst fatal build error - stage1-nomultilib.spec
@ 2019-03-02 16:22 catalyst
0 siblings, 0 replies; 5+ messages in thread
From: catalyst @ 2019-03-02 16:22 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f stage1-nomultilib.spec
02 Mar 2019 16:22:13 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
02 Mar 2019 16:22:13 UTC: NOTICE : conf_values[options] = {'clear-autoresume', 'pkgcache', 'bindist', 'preserve_libs'}
02 Mar 2019 16:22:13 UTC: NOTICE : Processing spec file: stage1-nomultilib.spec
02 Mar 2019 16:22:13 UTC: NOTICE : Using target: stage1
02 Mar 2019 16:22:13 UTC: NOTICE : Source file specification matching setting is: loose
02 Mar 2019 16:22:13 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
02 Mar 2019 16:22:14 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-nomultilib-latest.tar.xz
02 Mar 2019 16:22:14 UTC: NOTICE : stage1 stage path is /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190302T162037Z/tmp/stage1root
02 Mar 2019 16:22:14 UTC: NOTICE : --- Running action sequence: unpack
02 Mar 2019 16:22:14 UTC: NOTICE : Clearing the chroot path ...
02 Mar 2019 16:22:14 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190302T162037Z
02 Mar 2019 16:22:14 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-nomultilib-latest.tar.xz
02 Mar 2019 16:22:14 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190302T162037Z (this may take some time) ..
02 Mar 2019 16:22:18 UTC: NOTICE : --- Running action sequence: unpack_snapshot
02 Mar 2019 16:22:18 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
02 Mar 2019 16:22:28 UTC: NOTICE : --- Running action sequence: setup_confdir
02 Mar 2019 16:22:28 UTC: NOTICE : --- Running action sequence: portage_overlay
02 Mar 2019 16:22:28 UTC: NOTICE : --- Running action sequence: base_dirs
02 Mar 2019 16:22:28 UTC: NOTICE : --- Running action sequence: bind
02 Mar 2019 16:22:28 UTC: NOTICE : --- Running action sequence: chroot_setup
02 Mar 2019 16:22:28 UTC: NOTICE : Setting up chroot...
02 Mar 2019 16:22:28 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
02 Mar 2019 16:22:28 UTC: WARNING : If your build fails look here first as the possible problem.
02 Mar 2019 16:22:28 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
02 Mar 2019 16:22:28 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
02 Mar 2019 16:22:28 UTC: WARNING : You have been warned.
02 Mar 2019 16:22:28 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190302T162037Z/etc/portage/make.conf
02 Mar 2019 16:22:28 UTC: NOTICE : STICKY-CONFIG is enabled
02 Mar 2019 16:22:28 UTC: NOTICE : --- Running action sequence: setup_environment
02 Mar 2019 16:22:28 UTC: NOTICE : --- Running action sequence: run_local
copying make.conf to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190302T162037Z/tmp/stage1root/etc/portage
Copying stage1-chroot.sh to /tmp
copying stage1-chroot.sh to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190302T162037Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190302T162037Z/tmp
Ensure the file has the executable bit set
Running stage1-chroot.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190302T162037Z /tmp/stage1-chroot.sh
>>> Regenerating /etc/ld.so.cache...
Adding USE="${USE} build" to make.conf for portage build
emerge --quiet --oneshot --update --newuse sys-apps/portage
Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)
>>> Verifying ebuild manifests
>>> Emerging (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-162231.log'
* Package: sys-apps/portage-2.3.51-r1
* Repository: gentoo
* Maintainer: dev-portage@gentoo.org
* Upstream: dev-portage@gentoo.org
* USE: abi_x86_64 amd64 build elibc_glibc ipc kernel_linux native-extensions python_targets_python2_7 python_targets_python3_6 rsync-verify 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.51-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.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-162231.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/die.env'.
* 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-162231.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 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.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-162231.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/die.env'.
* 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 16:22:32 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1
02 Mar 2019 16:22:32 UTC: ERROR : CatalystError: Stage build aborting due to error.
02 Mar 2019 16:22:32 UTC: ERROR : Exception running action sequence run_local
Traceback (most recent call last):
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1355, in run_local
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/stage1/stage1-controller.sh', 'run']) 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 1364, in run_local
print_traceback=False)
catalyst.support.CatalystError: Stage build aborting due to error.
02 Mar 2019 16:22:32 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
31.79user 3.95system 0:19.44elapsed 183%CPU (0avgtext+0avgdata 357952maxresident)k
0inputs+3653048outputs (0major+486616minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20190302T162037Z.utKSjw/log/stage1-nomultilib.log
^ permalink raw reply [flat|nested] 5+ messages in thread
* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst fatal build error - stage1-nomultilib.spec
@ 2019-06-11 1:29 catalyst
0 siblings, 0 replies; 5+ messages in thread
From: catalyst @ 2019-06-11 1:29 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f stage1-nomultilib.spec
11 Jun 2019 01:29:25 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
11 Jun 2019 01:29:25 UTC: NOTICE : conf_values[options] = {'preserve_libs', 'pkgcache', 'clear-autoresume', 'bindist'}
11 Jun 2019 01:29:25 UTC: NOTICE : Processing spec file: stage1-nomultilib.spec
11 Jun 2019 01:29:25 UTC: NOTICE : Using target: stage1
11 Jun 2019 01:29:25 UTC: NOTICE : Source file specification matching setting is: loose
11 Jun 2019 01:29:25 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
11 Jun 2019 01:29:25 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-nomultilib-latest.tar.xz
11 Jun 2019 01:29:25 UTC: NOTICE : stage1 stage path is /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190611T012607Z/tmp/stage1root
11 Jun 2019 01:29:25 UTC: NOTICE : --- Running action sequence: unpack
11 Jun 2019 01:29:25 UTC: NOTICE : Clearing the chroot path ...
11 Jun 2019 01:29:25 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190611T012607Z
11 Jun 2019 01:29:25 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/default/stage3-amd64-nomultilib-latest.tar.xz
11 Jun 2019 01:29:25 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190611T012607Z (this may take some time) ..
11 Jun 2019 01:29:29 UTC: NOTICE : --- Running action sequence: unpack_snapshot
11 Jun 2019 01:29:29 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
11 Jun 2019 01:29:45 UTC: NOTICE : --- Running action sequence: setup_confdir
11 Jun 2019 01:29:45 UTC: NOTICE : --- Running action sequence: portage_overlay
11 Jun 2019 01:29:45 UTC: NOTICE : --- Running action sequence: base_dirs
11 Jun 2019 01:29:45 UTC: NOTICE : --- Running action sequence: bind
11 Jun 2019 01:29:45 UTC: NOTICE : --- Running action sequence: chroot_setup
11 Jun 2019 01:29:45 UTC: NOTICE : Setting up chroot...
11 Jun 2019 01:29:45 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
11 Jun 2019 01:29:45 UTC: WARNING : If your build fails look here first as the possible problem.
11 Jun 2019 01:29:45 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
11 Jun 2019 01:29:45 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
11 Jun 2019 01:29:45 UTC: WARNING : You have been warned.
11 Jun 2019 01:29:45 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190611T012607Z/etc/portage/make.conf
11 Jun 2019 01:29:45 UTC: NOTICE : STICKY-CONFIG is enabled
11 Jun 2019 01:29:45 UTC: NOTICE : --- Running action sequence: setup_environment
11 Jun 2019 01:29:45 UTC: NOTICE : --- Running action sequence: run_local
copying make.conf to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190611T012607Z/tmp/stage1root/etc/portage
Copying stage1-chroot.sh to /tmp
copying stage1-chroot.sh to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190611T012607Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190611T012607Z/tmp
Ensure the file has the executable bit set
Running stage1-chroot.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/default/stage1-amd64-nomultilib-20190611T012607Z /tmp/stage1-chroot.sh
>>> Regenerating /etc/ld.so.cache...
Adding USE="${USE} build" to make.conf for portage build
emerge --quiet --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-012949.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 build 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-012949.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-012948.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-012949.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-012949.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:29:50 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1
11 Jun 2019 01:29:50 UTC: ERROR : CatalystError: Stage build aborting due to error.
11 Jun 2019 01:29:50 UTC: ERROR : Exception running action sequence run_local
Traceback (most recent call last):
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1360, in run_local
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/stage1/stage1-controller.sh', 'run']) 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 1369, in run_local
print_traceback=False)
catalyst.support.CatalystError: Stage build aborting due to error.
11 Jun 2019 01:29:50 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
33.62user 4.67system 0:25.90elapsed 147%CPU (0avgtext+0avgdata 356540maxresident)k
16inputs+3873872outputs (0major+624263minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20190611T012607Z.4ssuYw/log/stage1-nomultilib.log
^ permalink raw reply [flat|nested] 5+ messages in thread
* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst fatal build error - stage1-nomultilib.spec
@ 2019-06-11 9:26 catalyst
0 siblings, 0 replies; 5+ 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 stage1-nomultilib.spec
11 Jun 2019 09:26:46 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
11 Jun 2019 09:26:46 UTC: NOTICE : conf_values[options] = {'clear-autoresume', 'preserve_libs', 'pkgcache', 'bindist'}
11 Jun 2019 09:26:46 UTC: NOTICE : Processing spec file: stage1-nomultilib.spec
11 Jun 2019 09:26:46 UTC: NOTICE : Using target: stage1
11 Jun 2019 09:26:46 UTC: NOTICE : Source file specification matching setting is: loose
11 Jun 2019 09:26:46 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:46 UTC: ERROR : CatalystError: File Not Found: /home/release/buildroot/amd64-exp/builds/default/stage3-amd64-nomultilib-latest
Command exited with non-zero status 2
0.21user 0.01system 0:00.29elapsed 77%CPU (0avgtext+0avgdata 18324maxresident)k
0inputs+0outputs (0major+9487minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20190611T092541Z.nNqC3R/log/stage1-nomultilib.log
^ permalink raw reply [flat|nested] 5+ messages in thread
* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst fatal build error - stage1-nomultilib.spec
@ 2019-06-14 18:35 catalyst
0 siblings, 0 replies; 5+ 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 stage1-nomultilib.spec
14 Jun 2019 18:35:33 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
14 Jun 2019 18:35:33 UTC: NOTICE : conf_values[options] = {'preserve_libs', 'clear-autoresume', 'pkgcache', 'bindist'}
14 Jun 2019 18:35:33 UTC: NOTICE : Processing spec file: stage1-nomultilib.spec
14 Jun 2019 18:35:33 UTC: NOTICE : Using target: stage1
14 Jun 2019 18:35:33 UTC: NOTICE : Source file specification matching setting is: loose
14 Jun 2019 18:35:33 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:33 UTC: ERROR : CatalystError: File Not Found: /home/release/buildroot/amd64-exp/builds/default/stage3-amd64-nomultilib-latest
Command exited with non-zero status 2
0.21user 0.01system 0:00.27elapsed 83%CPU (0avgtext+0avgdata 18288maxresident)k
0inputs+0outputs (0major+9449minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20190614T183511Z.BWvov2/log/stage1-nomultilib.log
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2019-06-14 18:35 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-06-11 1:29 [gentoo-releng-autobuilds] [amd64-experimental] Catalyst fatal build error - stage1-nomultilib.spec catalyst
-- strict thread matches above, loose matches on Subject: below --
2019-06-14 18:35 catalyst
2019-06-11 9:26 catalyst
2019-03-02 16:22 catalyst
2019-03-02 16:09 catalyst
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox