From: catalyst@thor.jmbsvicetto.name
To: jmbsvicetto@gmail.com,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [x86-auto] Catalyst fatal build error - hardened/stage3.spec
Date: Wed, 4 Apr 2018 06:33:32 +0000 (UTC) [thread overview]
Message-ID: <20180404063332.579EB66827@thor.jmbsvicetto.name> (raw)
*** Running command: time catalyst -a -c /etc/catalyst/release/x86-auto.conf -f hardened/stage3.spec
04 Apr 2018 06:32:41 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/x86-auto.conf
04 Apr 2018 06:32:41 UTC: NOTICE : conf_values[options] = {'bindist', 'pkgcache', 'preserve_libs', 'clear-autoresume'}
04 Apr 2018 06:32:41 UTC: NOTICE : Processing spec file: hardened/stage3.spec
04 Apr 2018 06:32:41 UTC: NOTICE : Using target: stage3
04 Apr 2018 06:32:41 UTC: NOTICE : Source file specification matching setting is: loose
04 Apr 2018 06:32:41 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
04 Apr 2018 06:32:42 UTC: NOTICE : Source path set to /home/release/buildroot/x86-dev/builds/hardened/stage2-i686-hardened-20180404T030003Z.tar.xz
04 Apr 2018 06:32:42 UTC: NOTICE : --- Running action sequence: unpack
04 Apr 2018 06:32:42 UTC: NOTICE : Clearing the chroot path ...
04 Apr 2018 06:32:42 UTC: NOTICE : Emptying directory: /home/release/buildroot/x86-dev/tmp/hardened/stage3-i686-hardened-20180404T030003Z
04 Apr 2018 06:32:42 UTC: NOTICE : Starting auto from /home/release/buildroot/x86-dev/builds/hardened/stage2-i686-hardened-20180404T030003Z.tar.xz
04 Apr 2018 06:32:42 UTC: NOTICE : to /home/release/buildroot/x86-dev/tmp/hardened/stage3-i686-hardened-20180404T030003Z (this may take some time) ..
04 Apr 2018 06:32:43 UTC: NOTICE : --- Running action sequence: unpack_snapshot
04 Apr 2018 06:32:43 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
04 Apr 2018 06:32:59 UTC: NOTICE : --- Running action sequence: setup_confdir
04 Apr 2018 06:32:59 UTC: NOTICE : --- Running action sequence: portage_overlay
04 Apr 2018 06:32:59 UTC: NOTICE : --- Running action sequence: base_dirs
04 Apr 2018 06:32:59 UTC: NOTICE : --- Running action sequence: bind
04 Apr 2018 06:32:59 UTC: NOTICE : --- Running action sequence: chroot_setup
04 Apr 2018 06:32:59 UTC: NOTICE : Setting up chroot...
04 Apr 2018 06:32:59 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
04 Apr 2018 06:32:59 UTC: WARNING : If your build fails look here first as the possible problem.
04 Apr 2018 06:32:59 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
04 Apr 2018 06:32:59 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
04 Apr 2018 06:32:59 UTC: WARNING : You have been warned.
04 Apr 2018 06:32:59 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/x86-dev/tmp/hardened/stage3-i686-hardened-20180404T030003Z/etc/portage/make.conf
04 Apr 2018 06:32:59 UTC: NOTICE : STICKY-CONFIG is enabled
04 Apr 2018 06:32:59 UTC: NOTICE : --- Running action sequence: setup_environment
04 Apr 2018 06:32:59 UTC: NOTICE : --- Running action sequence: run_local
Copying stage3-chroot.sh to /tmp
copying stage3-chroot.sh to /home/release/buildroot/x86-dev/tmp/hardened/stage3-i686-hardened-20180404T030003Z/tmp
copying chroot-functions.sh to /home/release/buildroot/x86-dev/tmp/hardened/stage3-i686-hardened-20180404T030003Z/tmp
Ensure the file has the executable bit set
Running stage3-chroot.sh in chroot:
setarch linux32 chroot /home/release/buildroot/x86-dev/tmp/hardened/stage3-i686-hardened-20180404T030003Z /tmp/stage3-chroot.sh
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot --update --newuse sys-apps/portage
>>> Emerging binary (1 of 2) dev-python/pyblake2-1.1.0::gentoo
>>> Installing (1 of 2) dev-python/pyblake2-1.1.0::gentoo
>>> Emerging binary (2 of 2) sys-apps/portage-2.3.24-r1::gentoo
>>> Installing (2 of 2) sys-apps/portage-2.3.24-r1::gentoo
emerge --quiet --usepkg --buildpkg --newuse -e --update --deep --with-bdeps=y @system
[nomerge ] virtual/package-manager-1::gentoo
[nomerge ] sys-apps/portage-2.3.24-r1::gentoo USE="(ipc) native-extensions (xattr) -build -doc -epydoc -gentoo-dev -rsync-verify (-selinux)" PYTHON_TARGETS="python2_7 python3_5 -pypy -python3_4 -python3_6"
[nomerge ] dev-python/pyxattr-0.5.5::gentoo USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_5 (-pypy) -python3_4"
[nomerge ] dev-python/setuptools-34.0.2-r1::gentoo USE="{-test}" PYTHON_TARGETS="python2_7 python3_5 (-pypy) (-pypy3) -python3_4 -python3_6"
[binary N ] dev-python/packaging-16.8::gentoo USE="{-test}" PYTHON_TARGETS="python2_7 python3_5 (-pypy) (-pypy3) -python3_4 -python3_6" 0 KiB
[ebuild N ] dev-python/six-1.11.0::gentoo USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_5 (-pypy) (-pypy3) -python3_4 -python3_6" 0 KiB
[binary N ] dev-python/setuptools-34.0.2-r1::gentoo USE="{-test}" PYTHON_TARGETS="python2_7 python3_5 (-pypy) (-pypy3) -python3_4 -python3_6" 0 KiB
Total: 3 packages (3 new, 2 binaries), Size of downloads: 0 KiB
* Error: circular dependencies:
(dev-python/six-1.11.0:0/0::gentoo, ebuild scheduled for merge) depends on
(dev-python/setuptools-34.0.2-r1:0/0::gentoo, binary scheduled for merge) (buildtime)
(dev-python/six-1.11.0:0/0::gentoo, ebuild scheduled for merge) (runtime)
* Note that circular dependencies can often be avoided by temporarily
* disabling USE flags that trigger optional dependencies.
04 Apr 2018 06:33:31 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage3/stage3-controller.sh', 'run']) exited 1
04 Apr 2018 06:33:32 UTC: ERROR : CatalystError: Stage build aborting due to error.
04 Apr 2018 06:33:32 UTC: ERROR : Exception running action sequence run_local
Traceback (most recent call last):
File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1354, in run_local
env=self.env)
File "/usr/lib64/python3.5/site-packages/catalyst/support.py", line 54, in cmd
print_traceback=False)
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage3/stage3-controller.sh', 'run']) exited 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1454, in run
getattr(self, x)()
File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1363, in run_local
print_traceback=False)
catalyst.support.CatalystError: Stage build aborting due to error.
04 Apr 2018 06:33:32 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
30.62user 3.90system 0:50.42elapsed 68%CPU (0avgtext+0avgdata 322228maxresident)k
0inputs+2184760outputs (0major+487977minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20180404T030003Z.ufjahC/log/hardened_stage3.log
next reply other threads:[~2018-04-04 6:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 6:33 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-15 13:05 [gentoo-releng-autobuilds] [x86-auto] Catalyst fatal build error - hardened/stage3.spec catalyst
2020-05-13 16:30 catalyst
2020-03-17 17:04 catalyst
2018-04-18 6:32 catalyst
2018-04-11 6:33 catalyst
2017-12-28 4:11 catalyst
2017-12-27 11:15 catalyst
2017-12-20 11:09 catalyst
2015-11-25 11:11 catalyst
2015-06-24 10:51 catalyst
2015-03-18 11:03 catalyst
2015-01-07 9:30 catalyst
2014-12-24 8:34 catalyst
2014-06-08 12:22 catalyst
2012-04-18 12:53 catalyst
2012-04-11 12:59 catalyst
2012-04-04 12:53 catalyst
2012-03-28 12:48 catalyst
2012-03-21 12:09 catalyst
2012-03-14 11:55 catalyst
2012-03-07 14:50 catalyst
2012-02-29 14:29 catalyst
2011-05-11 0:32 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=20180404063332.579EB66827@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