From: catalyst@thor.jmbsvicetto.name
To: jmbsvicetto@gmail.com,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - stage2.spec
Date: Tue, 16 Jul 2019 11:16:20 +0000 (UTC) [thread overview]
Message-ID: <20190716111620.AAD6E60EAE@thor.jmbsvicetto.name> (raw)
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-auto.conf -f stage2.spec
16 Jul 2019 11:15:21 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
16 Jul 2019 11:15:21 UTC: NOTICE : conf_values[options] = {'bindist', 'preserve_libs', 'clear-autoresume', 'pkgcache'}
16 Jul 2019 11:15:21 UTC: NOTICE : Processing spec file: stage2.spec
16 Jul 2019 11:15:21 UTC: NOTICE : Using target: stage2
16 Jul 2019 11:15:21 UTC: NOTICE : Source file specification matching setting is: loose
16 Jul 2019 11:15:21 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
16 Jul 2019 11:15:22 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/default/stage1-amd64-20190716T102132Z.tar.xz
16 Jul 2019 11:15:22 UTC: NOTICE : --- Running action sequence: unpack
16 Jul 2019 11:15:22 UTC: NOTICE : Clearing the chroot path ...
16 Jul 2019 11:15:22 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/default/stage2-amd64-20190716T102132Z
16 Jul 2019 11:15:22 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/default/stage1-amd64-20190716T102132Z.tar.xz
16 Jul 2019 11:15:22 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/default/stage2-amd64-20190716T102132Z (this may take some time) ..
16 Jul 2019 11:15:23 UTC: NOTICE : --- Running action sequence: unpack_snapshot
16 Jul 2019 11:15:23 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
16 Jul 2019 11:15:43 UTC: NOTICE : --- Running action sequence: setup_confdir
16 Jul 2019 11:15:43 UTC: NOTICE : --- Running action sequence: portage_overlay
16 Jul 2019 11:15:43 UTC: NOTICE : --- Running action sequence: base_dirs
16 Jul 2019 11:15:43 UTC: NOTICE : --- Running action sequence: bind
16 Jul 2019 11:15:43 UTC: NOTICE : --- Running action sequence: chroot_setup
16 Jul 2019 11:15:43 UTC: NOTICE : Setting up chroot...
16 Jul 2019 11:15:43 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
16 Jul 2019 11:15:43 UTC: WARNING : If your build fails look here first as the possible problem.
16 Jul 2019 11:15:43 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
16 Jul 2019 11:15:43 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
16 Jul 2019 11:15:43 UTC: WARNING : You have been warned.
16 Jul 2019 11:15:43 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/default/stage2-amd64-20190716T102132Z/etc/portage/make.conf
16 Jul 2019 11:15:43 UTC: NOTICE : STICKY-CONFIG is enabled
16 Jul 2019 11:15:43 UTC: NOTICE : --- Running action sequence: setup_environment
16 Jul 2019 11:15:43 UTC: NOTICE : --- Running action sequence: run_local
Copying stage2-chroot.sh to /tmp
copying stage2-chroot.sh to /home/release/buildroot/amd64-dev/tmp/default/stage2-amd64-20190716T102132Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/default/stage2-amd64-20190716T102132Z/tmp
Ensure the file has the executable bit set
Running stage2-chroot.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/default/stage2-amd64-20190716T102132Z /tmp/stage2-chroot.sh
>>> Regenerating /etc/ld.so.cache...
^[(B^[[m^[[1m^[[32mGentoo Linux; ^[(B^[[m^[[1m^[[34mhttp://www.gentoo.org/^[(B^[[m
Copyright 1999-$ Gentoo Foundation; Distributed under the GPLv2
-------------------------------------------------------------------------------
[[ (0/3) Locating packages ]]
^[(B^[[m^[[1m^[[32m*^[(B^[[m Using baselayout : >=sys-apps/baselayout-2
^[(B^[[m^[[1m^[[32m*^[(B^[[m Using portage : portage
^[(B^[[m^[[1m^[[32m*^[(B^[[m Using os-headers : >=sys-kernel/linux-headers-4.14-r1
^[(B^[[m^[[1m^[[32m*^[(B^[[m Using binutils : sys-devel/binutils
^[(B^[[m^[[1m^[[32m*^[(B^[[m Using gcc : sys-devel/gcc
^[(B^[[m^[[1m^[[32m*^[(B^[[m Using gettext : gettext
^[(B^[[m^[[1m^[[32m*^[(B^[[m Using libc : virtual/libc
^[(B^[[m^[[1m^[[32m*^[(B^[[m Using texinfo : sys-apps/texinfo
^[(B^[[m^[[1m^[[32m*^[(B^[[m Using zlib : zlib
^[(B^[[m^[[1m^[[32m*^[(B^[[m Using ncurses : ncurses
-------------------------------------------------------------------------------
[[ (1/3) Configuring environment ]]
-------------------------------------------------------------------------------
[[ (2/3) Updating portage ]]
Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)
>>> Running pre-merge checks for sys-apps/portage-2.3.66-r1
* 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 binary (1 of 1) sys-apps/portage-2.3.66-r1::gentoo
>>> Installing (1 of 1) sys-apps/portage-2.3.66-r1::gentoo
* Messages for package sys-apps/portage-2.3.66-r1:
* Log file: /home/release/tmp/logs/sys-apps:portage-2.3.66-r1:20190716-111557.log
* Unable to find kernel sources at /usr/src/linux
* Unable to calculate Linux Kernel version for build, attempting to use running version
-------------------------------------------------------------------------------
[[ (3/3) Emerging packages ]]
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-devel/gcc-8.3.0-r1
>>> Emerging binary (1 of 13) sys-libs/zlib-1.2.11-r2::gentoo
>>> Installing (1 of 13) sys-libs/zlib-1.2.11-r2::gentoo
>>> Emerging binary (2 of 13) sys-apps/baselayout-2.6-r1::gentoo
>>> Failed to emerge sys-apps/baselayout-2.6-r1, Log file:
>>> '/home/release/tmp/logs/sys-apps:baselayout-2.6-r1:20190716-111619.log'
>>> Extracting info
* Package: sys-apps/baselayout-2.6-r1
* Repository: gentoo
* USE: abi_x86_64 kernel_linux userland_GNU split-usr amd64 elibc_glibc
* FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox
* Converting /lib from a dir to a symlink
* ERROR: sys-apps/baselayout-2.6-r1::gentoo failed (setup phase):
* non-empty dir found where we needed a symlink: /lib
*
* Call stack:
* ebuild.sh, line 124: Called pkg_setup
* environment, line 1453: Called multilib_layout
* environment, line 1284: Called die
* The specific snippet of code:
* die "non-empty dir found where we needed a symlink: ${prefix}lib";
*
* If you need support, post the output of `emerge --info '=sys-apps/baselayout-2.6-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/baselayout-2.6-r1::gentoo'`.
* The complete build log is located at '/home/release/tmp/logs/sys-apps:baselayout-2.6-r1:20190716-111619.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/baselayout-2.6-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/baselayout-2.6-r1/temp/environment'.
* Working directory: '/var/tmp/portage/sys-apps/baselayout-2.6-r1/homedir'
* S: '/var/tmp/portage/sys-apps/baselayout-2.6-r1/work/baselayout-2.6'
* Messages for package sys-apps/baselayout-2.6-r1:
* Log file: /home/release/tmp/logs/sys-apps:baselayout-2.6-r1:20190716-111619.log
* Converting /lib from a dir to a symlink
* ERROR: sys-apps/baselayout-2.6-r1::gentoo failed (setup phase):
* non-empty dir found where we needed a symlink: /lib
*
* Call stack:
* ebuild.sh, line 124: Called pkg_setup
* environment, line 1453: Called multilib_layout
* environment, line 1284: Called die
* The specific snippet of code:
* die "non-empty dir found where we needed a symlink: ${prefix}lib";
*
* If you need support, post the output of `emerge --info '=sys-apps/baselayout-2.6-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/baselayout-2.6-r1::gentoo'`.
* The complete build log is located at '/home/release/tmp/logs/sys-apps:baselayout-2.6-r1:20190716-111619.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/baselayout-2.6-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/baselayout-2.6-r1/temp/environment'.
* Working directory: '/var/tmp/portage/sys-apps/baselayout-2.6-r1/homedir'
* S: '/var/tmp/portage/sys-apps/baselayout-2.6-r1/work/baselayout-2.6'
16 Jul 2019 11:16:20 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage2/stage2-controller.sh', 'run']) exited 1
16 Jul 2019 11:16:20 UTC: ERROR : CatalystError: Stage build aborting due to error.
16 Jul 2019 11:16:20 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/stage2/stage2-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.
16 Jul 2019 11:16:20 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
31.18user 4.80system 0:59.22elapsed 60%CPU (0avgtext+0avgdata 332280maxresident)k
32inputs+2448544outputs (0major+1038010minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20190716T102132Z.ae9vp0/log/stage2.log
next reply other threads:[~2019-07-16 11:16 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 11:16 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-17 22:11 [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - stage2.spec catalyst
2020-06-14 22:13 catalyst
2020-05-11 16:26 catalyst
2020-02-03 1:07 catalyst
2019-07-22 3:59 catalyst
2019-07-16 0:53 catalyst
2018-08-14 16:27 catalyst
2017-12-26 21:58 catalyst
2017-12-24 21:59 catalyst
2017-12-23 3:45 catalyst
2017-12-21 21:58 catalyst
2017-12-19 21:54 catalyst
2017-12-17 22:45 catalyst
2017-12-15 7:26 catalyst
2017-12-03 21:10 catalyst
2017-12-03 20:46 catalyst
2017-12-03 20:40 catalyst
2017-10-26 3:25 catalyst
2015-11-21 19:17 catalyst
2015-11-16 5:10 catalyst
2015-11-09 5:04 catalyst
2015-11-02 5:07 catalyst
2015-11-01 5:30 catalyst
2015-10-30 2:31 catalyst
2015-10-29 22:43 catalyst
2015-10-29 4:15 catalyst
2015-10-26 4:28 catalyst
2015-10-24 2:11 catalyst
2015-10-23 5:26 catalyst
2015-08-29 17:43 catalyst
2015-08-29 17:29 catalyst
2015-08-29 17:17 catalyst
2015-08-29 11:23 catalyst
2015-08-29 2:55 catalyst
2015-08-29 2:52 catalyst
2015-08-29 2:45 catalyst
2015-08-13 12:20 catalyst
2015-06-16 2:35 catalyst
2015-06-08 5:05 catalyst
2015-05-11 4:58 catalyst
2015-02-23 4:24 catalyst
2014-11-24 4:35 catalyst
2014-11-17 4:45 catalyst
2011-03-31 4:35 catalyst
2011-03-24 5:19 catalyst
2011-03-10 5:40 catalyst
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190716111620.AAD6E60EAE@thor.jmbsvicetto.name \
--to=catalyst@thor.jmbsvicetto.name \
--cc=gentoo-releng-autobuilds@lists.gentoo.org \
--cc=jmbsvicetto@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox