From: catalyst@nightheron.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [x86-auto] Catalyst fatal build error - i686/stage1.spec
Date: Fri, 13 Apr 2018 21:57:00 +0000 (UTC) [thread overview]
Message-ID: <20180413215700.6E00D2024B@nightheron.gentoo.org> (raw)
*** Running command: time catalyst -a -c /etc/catalyst/release/x86-auto.conf -f i686/stage1.spec
13 Apr 2018 21:53:18 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/x86-auto.conf
13 Apr 2018 21:53:18 UTC: NOTICE : conf_values[options] = {'snapcache', 'autoresume', 'preserve_libs', 'bindist', 'pkgcache', 'seedcache', 'clear-autoresume'}
13 Apr 2018 21:53:18 UTC: NOTICE : Processing spec file: i686/stage1.spec
13 Apr 2018 21:53:18 UTC: NOTICE : Using target: stage1
13 Apr 2018 21:53:18 UTC: NOTICE : Source file specification matching setting is: loose
13 Apr 2018 21:53:18 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
13 Apr 2018 21:53:20 UTC: NOTICE : Source path set to /release/buildroot/x86-dev/builds/default/stage3-i686-latest.tar.bz2
13 Apr 2018 21:53:20 UTC: NOTICE : stage1 stage path is /release/buildroot/x86-dev/tmp/default/stage1-i686-20180413T214503Z/tmp/stage1root
13 Apr 2018 21:53:20 UTC: NOTICE : Removing AutoResume Points ...
13 Apr 2018 21:53:20 UTC: NOTICE : Emptying directory: /release/buildroot/x86-dev/tmp/default/.autoresume-stage1-i686-20180413T214503Z
13 Apr 2018 21:53:20 UTC: NOTICE : --- Running action sequence: unpack
13 Apr 2018 21:53:20 UTC: NOTICE : Referenced SEEDCACHE does not appear to be a directory, trying to untar...
13 Apr 2018 21:53:20 UTC: NOTICE : Resume: "seed source" unpack resume point is disabled
13 Apr 2018 21:53:20 UTC: NOTICE : Resume: Target chroot is invalid, cleaning up...
13 Apr 2018 21:53:20 UTC: NOTICE : Removing AutoResume Points ...
13 Apr 2018 21:53:20 UTC: NOTICE : Emptying directory: /release/buildroot/x86-dev/tmp/default/.autoresume-stage1-i686-20180413T214503Z
13 Apr 2018 21:53:20 UTC: NOTICE : Clearing the chroot path ...
13 Apr 2018 21:53:20 UTC: NOTICE : Emptying directory: /release/buildroot/x86-dev/tmp/default/stage1-i686-20180413T214503Z
13 Apr 2018 21:53:20 UTC: NOTICE : Starting auto from /release/buildroot/x86-dev/builds/default/stage3-i686-latest.tar.bz2
13 Apr 2018 21:53:20 UTC: NOTICE : to /release/buildroot/x86-dev/tmp/default/stage1-i686-20180413T214503Z (this may take some time) ..
13 Apr 2018 21:53:24 UTC: NOTICE : --- Running action sequence: unpack_snapshot
13 Apr 2018 21:53:24 UTC: NOTICE : --- Running action sequence: setup_confdir
13 Apr 2018 21:53:24 UTC: NOTICE : --- Running action sequence: portage_overlay
13 Apr 2018 21:53:24 UTC: NOTICE : --- Running action sequence: base_dirs
13 Apr 2018 21:53:24 UTC: NOTICE : --- Running action sequence: bind
13 Apr 2018 21:53:24 UTC: NOTICE : --- Running action sequence: chroot_setup
13 Apr 2018 21:53:24 UTC: NOTICE : Setting up chroot...
13 Apr 2018 21:53:24 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
13 Apr 2018 21:53:24 UTC: WARNING : If your build fails look here first as the possible problem.
13 Apr 2018 21:53:24 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
13 Apr 2018 21:53:24 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
13 Apr 2018 21:53:24 UTC: WARNING : You have been warned.
13 Apr 2018 21:53:24 UTC: NOTICE : Writing the stage make.conf to: /release/buildroot/x86-dev/tmp/default/stage1-i686-20180413T214503Z/etc/portage/make.conf
13 Apr 2018 21:53:24 UTC: NOTICE : STICKY-CONFIG is enabled
13 Apr 2018 21:53:24 UTC: NOTICE : --- Running action sequence: setup_environment
13 Apr 2018 21:53:24 UTC: NOTICE : --- Running action sequence: run_local
copying make.conf to /release/buildroot/x86-dev/tmp/default/stage1-i686-20180413T214503Z/tmp/stage1root/etc/portage
Copying stage1-chroot.sh to /tmp
copying stage1-chroot.sh to /release/buildroot/x86-dev/tmp/default/stage1-i686-20180413T214503Z/tmp
copying chroot-functions.sh to /release/buildroot/x86-dev/tmp/default/stage1-i686-20180413T214503Z/tmp
Ensure the file has the executable bit set
Running stage1-chroot.sh in chroot:
setarch linux32 chroot /release/buildroot/x86-dev/tmp/default/stage1-i686-20180413T214503Z /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 2) dev-lang/python-3.5.4-r1::gentoo
>>> Installing (1 of 2) dev-lang/python-3.5.4-r1::gentoo
>>> Emerging (2 of 2) sys-apps/portage-2.3.24-r1::gentoo
>>> Installing (2 of 2) sys-apps/portage-2.3.24-r1::gentoo
* Messages for package dev-lang/python-3.5.4-r1:
* You have just upgraded from an older version of Python.
*
* Please adjust PYTHON_TARGETS (if so desired), and run emerge with the --newuse or --changed-use option to rebuild packages installing python modules.
Updating seed stage...
emerge --quiet --buildpkg=n --update --deep @world
[nomerge ] virtual/package-manager-1::gentoo [0::gentoo]
[nomerge ] sys-apps/portage-2.3.24-r1::gentoo USE="build (ipc) native-extensions xattr -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_4 (-pypy) -python3_5"
[nomerge ] dev-python/setuptools-34.0.2-r1::gentoo USE="{-test}" PYTHON_TARGETS="python2_7 python3_4 (-pypy) (-pypy3) -python3_5 -python3_6"
[nomerge ] dev-python/six-1.11.0::gentoo [1.10.0::gentoo] USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_4 python3_5* (-pypy) (-pypy3) -python3_6"
[nomerge ] dev-python/setuptools-34.0.2-r1::gentoo USE="{-test}" PYTHON_TARGETS="python2_7 python3_4 python3_5* (-pypy) (-pypy3) -python3_6"
[ebuild R ] dev-python/certifi-2017.4.17::gentoo PYTHON_TARGETS="python2_7 python3_4 python3_5* (-pypy) (-pypy3) -python3_6" 0 KiB
[ebuild R ] dev-python/setuptools-34.0.2-r1::gentoo USE="{-test}" PYTHON_TARGETS="python2_7 python3_4 python3_5* (-pypy) (-pypy3) -python3_6" 0 KiB
[ebuild R ] dev-python/packaging-16.8::gentoo USE="{-test}" PYTHON_TARGETS="python2_7 python3_4 python3_5* (-pypy) (-pypy3) -python3_6" 0 KiB
[ebuild U ] dev-python/six-1.11.0::gentoo [1.10.0::gentoo] USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_4 python3_5* (-pypy) (-pypy3) -python3_6" 0 KiB
Total: 4 packages (1 upgrade, 3 reinstalls), 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, ebuild scheduled for merge) (buildtime)
(dev-python/six-1.11.0:0/0::gentoo, ebuild scheduled for merge) (buildtime)
* Note that circular dependencies can often be avoided by temporarily
* disabling USE flags that trigger optional dependencies.
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
sys-libs/readline:0
(sys-libs/readline-7.0_p3:0/7::gentoo, ebuild scheduled for merge) pulled in by
>=sys-libs/readline-7.0:0= required by (app-shells/bash-4.4_p12:0/0::gentoo, ebuild scheduled for merge)
^^ ^^^^^^
(sys-libs/readline-6.3_p8-r3:0/0::gentoo, installed) pulled in by
>=sys-libs/readline-4.1:0/0= required by (dev-lang/python-3.5.4-r1:3.5/3.5m::gentoo, installed)
^^^^^
(and 2 more with the same problem)
dev-python/setuptools:0
(dev-python/setuptools-34.0.2-r1:0/0::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)
(dev-python/setuptools-34.0.2-r1:0/0::gentoo, ebuild scheduled for merge) pulled in by
dev-python/setuptools[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (dev-python/six-1.11.0:0/0::gentoo, ebuild scheduled for merge)
dev-python/setuptools[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (dev-python/certifi-2017.4.17:0/0::gentoo, ebuild scheduled for merge)
sys-libs/gdbm:0
(sys-libs/gdbm-1.13-r2:0/1.13::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)
(sys-libs/gdbm-1.11:0/0::gentoo, installed) pulled in by
sys-libs/gdbm:0/0=[berkdb] required by (dev-lang/python-3.5.4-r1:3.5/3.5m::gentoo, installed)
^^^^^
NOTE: Use the '--verbose-conflicts' option to display parents omitted above
It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously. If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously.
For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.
The following USE changes are necessary to proceed:
(see "package.use" in the portage(5) man page for more details)
# required by dev-python/setuptools-34.0.2-r1::gentoo
# required by dev-python/certifi-2017.4.17::gentoo
>=dev-python/six-1.11.0 python_targets_python3_4
# required by dev-python/setuptools-34.0.2-r1::gentoo
# required by dev-python/certifi-2017.4.17::gentoo
>=dev-python/packaging-16.8 python_targets_python3_4
# required by dev-python/setuptools-34.0.2-r1::gentoo
# required by dev-python/certifi-2017.4.17::gentoo
>=dev-python/appdirs-1.4.3 python_targets_python3_4
# required by dev-python/setuptools-34.0.2-r1::gentoo
# required by dev-python/six-1.11.0::gentoo
# required by dev-python/packaging-16.8::gentoo
>=dev-python/certifi-2017.4.17 python_targets_python3_4
# required by dev-python/packaging-16.8::gentoo
# required by dev-python/setuptools-34.0.2-r1::gentoo
# required by dev-python/certifi-2017.4.17::gentoo
>=dev-python/pyparsing-2.2.0 python_targets_python3_4
# required by dev-python/certifi-2017.4.17::gentoo
>=dev-python/setuptools-34.0.2-r1 python_targets_python3_4
Use --autounmask-write to write changes to config files (honoring
CONFIG_PROTECT). Carefully examine the list of proposed changes,
paying special attention to mask or keyword changes that may expose
experimental or unstable packages.
* In order to avoid wasting time, backtracking has terminated early
* due to the above autounmask change(s). The --autounmask-backtrack=y
* option can be used to force further backtracking, but there is no
* guarantee that it will produce a solution.
emerge: there are no ebuilds built with USE flags to satisfy ">=dev-python/six-1.10.0[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)]".
!!! One of the following packages is required to complete your request:
- dev-python/six-1.10.0::gentoo (Change USE: +python_targets_python3_4)
- dev-python/setuptools-34.0.2-r1::gentoo (Change USE: -python_targets_python3_4)
(dependency required by "dev-python/setuptools-34.0.2-r1::gentoo" [installed])
(dependency required by "dev-python/pyxattr-0.5.5::gentoo" [installed])
(dependency required by "sys-apps/portage-2.3.24-r1::gentoo[python_targets_python2_7,-python_targets_pypy,xattr]" [installed])
(dependency required by "virtual/package-manager-1::gentoo" [ebuild])
(dependency required by "@system" [set])
(dependency required by "@world" [argument])
13 Apr 2018 21:57:00 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1
13 Apr 2018 21:57:00 UTC: ERROR : CatalystError: Stage build aborting due to error.
13 Apr 2018 21:57:00 UTC: ERROR : Exception running action sequence run_local
Traceback (most recent call last):
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1354, in run_local
env=self.env)
File "/usr/lib64/python3.4/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.4/site-packages/catalyst/base/stagebase.py", line 1454, in run
getattr(self, x)()
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1363, in run_local
print_traceback=False)
catalyst.support.CatalystError: Stage build aborting due to error.
13 Apr 2018 21:57:00 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
288.66user 82.84system 3:42.04elapsed 167%CPU (0avgtext+0avgdata 848640maxresident)k
469224inputs+2630872outputs (0major+11304048minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20180413T214503Z.KNZPLk/log/i686_stage1.log
next reply other threads:[~2018-04-13 21:57 UTC|newest]
Thread overview: 151+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 21:57 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-15 2:57 [gentoo-releng-autobuilds] [x86-auto] Catalyst fatal build error - i686/stage1.spec catalyst
2020-11-30 23:49 catalyst
2020-11-23 23:44 catalyst
2020-09-30 3:00 catalyst
2020-09-23 3:00 catalyst
2020-09-16 3:00 catalyst
2020-09-09 3:00 catalyst
2020-09-02 3:00 catalyst
2020-08-26 3:00 catalyst
2020-08-19 3:00 catalyst
2020-08-12 3:00 catalyst
2020-08-05 3:00 catalyst
2020-07-29 3:00 catalyst
2020-07-22 3:00 catalyst
2020-07-15 3:00 catalyst
2020-07-08 3:00 catalyst
2020-07-01 3:00 catalyst
2020-06-24 3:00 catalyst
2020-06-17 3:00 catalyst
2020-06-10 3:00 catalyst
2020-06-03 3:00 catalyst
2020-05-27 3:00 catalyst
2020-05-20 3:00 catalyst
2020-05-16 11:18 catalyst
2020-05-13 3:00 catalyst
2020-05-06 3:00 catalyst
2020-04-29 3:00 catalyst
2020-01-08 4:04 catalyst
2019-12-10 21:48 catalyst
2019-09-04 3:00 catalyst
2019-02-14 16:06 catalyst
2019-01-09 6:43 catalyst
2019-01-03 13:28 catalyst
2019-01-03 13:17 catalyst
2019-01-02 21:48 catalyst
2019-01-02 18:44 catalyst
2019-01-01 3:54 catalyst
2018-09-07 12:37 catalyst
2018-09-07 12:36 catalyst
2018-07-08 1:38 catalyst
2018-07-08 9:15 ` M. J. Everitt
2018-04-11 21:57 catalyst
2018-04-09 21:57 catalyst
2018-04-06 21:57 catalyst
2018-04-02 21:55 catalyst
2018-02-17 0:55 catalyst
2018-02-15 0:55 catalyst
2018-02-13 0:55 catalyst
2018-02-10 0:34 catalyst
2018-02-03 0:32 catalyst
2018-02-01 1:52 catalyst
2018-01-31 6:44 catalyst
2018-01-31 3:01 catalyst
2018-01-30 0:28 catalyst
2018-01-27 0:23 catalyst
2018-01-25 0:21 catalyst
2018-01-24 5:03 catalyst
2018-01-23 0:19 catalyst
2018-01-20 0:22 catalyst
2017-12-25 22:12 catalyst
2017-12-22 22:11 catalyst
2017-12-20 22:11 catalyst
2017-12-18 23:07 catalyst
2017-10-26 3:26 catalyst
2017-10-26 3:25 catalyst
2017-10-26 3:25 catalyst
2017-10-26 3:25 catalyst
2017-10-26 3:25 catalyst
2017-09-27 3:11 catalyst
2017-09-20 3:09 catalyst
2017-09-13 3:09 catalyst
2017-09-05 1:19 catalyst
2017-03-22 8:04 catalyst
2017-03-15 9:24 catalyst
2017-03-08 3:01 catalyst
2017-03-01 3:00 catalyst
2017-02-22 3:10 catalyst
2017-02-15 3:11 catalyst
2017-02-08 3:11 catalyst
2017-02-01 3:10 catalyst
2017-01-25 3:11 catalyst
2017-01-18 3:11 catalyst
2017-01-11 3:08 catalyst
2017-01-04 3:09 catalyst
2016-12-28 3:09 catalyst
2016-12-21 3:09 catalyst
2016-12-14 3:08 catalyst
2016-12-07 3:08 catalyst
2016-11-30 3:01 catalyst
2016-11-23 3:01 catalyst
2016-11-16 3:01 catalyst
2016-11-09 3:01 catalyst
2016-11-02 3:01 catalyst
2016-10-26 3:02 catalyst
2016-10-19 3:01 catalyst
2016-10-12 3:01 catalyst
2016-10-05 3:02 catalyst
2016-09-28 7:44 catalyst
2016-09-21 7:29 catalyst
2016-09-14 3:00 catalyst
2016-09-07 3:00 catalyst
2016-08-31 3:00 catalyst
2016-08-24 3:00 catalyst
2016-08-17 3:00 catalyst
2016-08-10 3:01 catalyst
2016-08-03 3:01 catalyst
2016-07-27 3:03 catalyst
2016-07-20 3:01 catalyst
2016-05-18 3:02 catalyst
2016-05-11 3:02 catalyst
2015-12-23 3:05 catalyst
2015-12-01 2:29 catalyst
2015-08-19 5:20 catalyst
2015-08-05 5:02 catalyst
2015-08-04 6:45 catalyst
2015-07-22 5:21 catalyst
2015-07-08 4:29 catalyst
2015-06-24 8:12 catalyst
2015-06-17 3:08 catalyst
2015-06-03 3:06 catalyst
2015-06-01 1:25 catalyst
2015-05-20 3:07 catalyst
2015-05-13 3:06 catalyst
2015-05-06 3:06 catalyst
2015-04-29 3:06 catalyst
2015-04-22 3:47 catalyst
2015-03-10 6:21 catalyst
2015-02-22 2:38 catalyst
2015-02-17 1:18 catalyst
2015-02-11 3:07 catalyst
2015-02-10 1:19 catalyst
2015-02-04 3:07 catalyst
2015-02-03 1:19 catalyst
2015-01-28 3:08 catalyst
2015-01-27 1:16 catalyst
2015-01-20 1:18 catalyst
2015-01-13 1:19 catalyst
2015-01-06 1:19 catalyst
2014-12-30 1:19 catalyst
2014-12-23 1:20 catalyst
2014-12-16 1:20 catalyst
2014-11-19 3:43 catalyst
2012-09-11 1:38 catalyst
2012-09-04 1:38 catalyst
2012-01-17 11:49 catalyst
2011-11-22 5:06 catalyst
2011-11-15 4:52 catalyst
2011-08-23 1:33 catalyst
2011-08-16 3:31 catalyst
2011-05-17 3:07 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=20180413215700.6E00D2024B@nightheron.gentoo.org \
--to=catalyst@nightheron.gentoo.org \
--cc=gentoo-releng-autobuilds@lists.gentoo.org \
--cc=releng@gentoo.org \
/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