From: catalyst@nightheron.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-cloud.spec
Date: Thu, 26 Oct 2017 22:59:23 +0000 (UTC) [thread overview]
Message-ID: <20171026225923.6D23A34119@nightheron.gentoo.org> (raw)
Copyright 2003-2008 Gentoo Foundation
Copyright 2008-2012 various authors
Distributed under the GNU General Public License version 2.1
Using command line specified Catalyst configuration file, /etc/catalyst/release/amd64-auto.conf
Setting sharedir to config file value "/usr/lib64/catalyst/"
Setting snapshot_cache to config file value "/release/tmp/snapshots"
Setting hash_function to config file value "crc32"
Setting storedir to config file value "/release/buildroot/amd64-dev"
Setting portdir to config file value "/release/trees/portage-auto"
Setting distdir to config file value "/release/tmp/distfiles/"
Setting options to config file value "autoresume bindist pkgcache preserve_libs seedcache snapcache"
Autoresuming support enabled.
Binary redistribution enabled
Package cache support enabled.
Preserving libs during unmerge.
Seed cache support enabled.
Snapshot cache support enabled.
Envscript support enabled.
Using target: stage4
Building natively for amd64
Source path set to /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.bz2
Caching snapshot to /release/tmp/snapshots/20171026/
The autoresume path is /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-20171026/
Location of the package cache is /release/buildroot/amd64-dev/packages/hardened/stage4-amd64-hardened+cloud-20171026/
Checking for processes running in chroot and killing them.
Removing AutoResume Points: ...
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-20171026/
>>> Waiting 10 seconds before starting...
>>> (Control-C to abort)...
Purging Caches ... in: 10 9 8 7 6 5 4 3 2 1
clearing autoresume ...
Removing AutoResume Points: ...
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-20171026/
clearing chroot ...
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-20171026/
clearing package cache ...
purging the pkgcache ...
clearing kerncache ...
--- Running action sequence: unpack
Referenced SEEDCACHE does not appear to be a directory, trying to untar...
No Valid Resume point detected, cleaning up...
Removing AutoResume Points: ...
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-20171026/
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-20171026/
Starting tar extract from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.bz2
to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-20171026/ (This may take some time) ...
tar: SELinux support is not available
--- Running action sequence: unpack_snapshot
Valid snapshot cache, skipping unpack of portage tree...
--- Running action sequence: config_profile_link
Configuring profile link...
--- Running action sequence: setup_confdir
Configuring /etc/portage...
--- Running action sequence: portage_overlay
--- Running action sequence: bind
--- Running action sequence: chroot_setup
Setting up chroot...
Warning!!!!
Overriding certain env variables may cause catastrophic failure.
If your build fails look here first as the possible problem.
Catalyst assumes you know what you are doing when setting
these variables.
Catalyst Maintainers use VERY minimal envscripts if used at all
You have been warned
--- Running action sequence: setup_environment
--- Running action sequence: build_packages
Copying stage4-chroot.sh to /tmp
copying stage4-chroot.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-20171026//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-20171026//tmp
Ensure the file has the executable bit set
Running stage4-chroot.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-20171026/
>>> Regenerating /etc/ld.so.cache...
Updating portage with USE=""
emerge --quiet --usepkg --buildpkg --newuse --oneshot --update --newuse sys-apps/portage
Bringing system up to date using profile specific use flags
emerge --quiet --usepkg --buildpkg --newuse -u @system
Emerging packages using stage4 use flags
emerge --quiet --usepkg --buildpkg --newuse app-admin/logrotate app-admin/sudo app-admin/syslog-ng app-editors/vim app-emulation/cloud-init app-portage/eix app-portage/gentoolkit net-misc/dhcpcd sys-boot/grub sys-apps/dmidecode sys-apps/gptfdisk sys-apps/iproute2 sys-apps/lsb-release sys-apps/pciutils sys-block/parted sys-devel/bc sys-power/acpid sys-process/cronie
[ebuild N ] sys-process/cronbase-0.3.7-r6
[ebuild N ] app-shells/quoter-3.0_p2-r1
[ebuild N ] app-shells/push-2.0-r1
[ebuild N ] net-analyzer/macchanger-1.7.0
[ebuild N ] sys-apps/tcp-wrappers-7.6.22-r1
[ebuild N ] sys-apps/dmidecode-3.0
[ebuild N ] dev-libs/libunistring-0.9.7
[ebuild N ] dev-libs/eventlog-0.2.12
[ebuild N ] sys-devel/bc-1.06.95-r1
[ebuild N ] app-eselect/eselect-vi-1.1.9
[ebuild N ] app-eselect/eselect-ctags-1.18
[ebuild R ] dev-libs/openssl-1.0.2l
[ebuild N ] sys-apps/lsb-release-1.4
[ebuild N ] dev-python/pyyaml-3.12
[ebuild N ] dev-python/webcolors-1.5
[ebuild N ] dev-python/functools32-3.2.3
[ebuild N ] dev-python/strict-rfc3339-0.6
[ebuild N ] dev-python/regex-2016.01.10
[ebuild N ] dev-python/blinker-1.4
[ebuild N ] net-dns/libidn2-2.0.4
[ebuild N ] dev-libs/libtasn1-4.12-r1
[ebuild N ] dev-python/configobj-5.0.6
[ebuild N ] dev-libs/nettle-3.3-r2
[ebuild N ] app-portage/gentoolkit-0.4.0
[ebuild N ] dev-python/idna-2.5
[ebuild N ] dev-python/pyserial-3.2.1
[ebuild N ] dev-python/vcversioner-2.16.0.0
[ebuild N ] dev-python/rfc3987-1.3.7
[ebuild N ] dev-python/chardet-3.0.4
[ebuild N ] dev-python/enum34-1.1.6
[ebuild N ] dev-python/asn1crypto-0.22.0
[ebuild N ] dev-python/ply-3.9
[ebuild N ] dev-python/PySocks-1.6.7
[ebuild N ] dev-python/jsonpointer-1.10
[ebuild N ] dev-python/pyjwt-1.5.3
[ebuild N ] dev-python/markupsafe-0.23
[ebuild N ] dev-python/pygments-2.1.1
[ebuild N ] dev-python/ipaddress-1.0.18
[ebuild N ] virtual/python-ipaddress-1.0-r1
[ebuild N ] dev-python/jinja-2.9.5
[ebuild N ] dev-python/jsonpatch-1.13
[ebuild N ] dev-python/jsonschema-2.6.0
[ebuild N ] dev-python/pycparser-2.14
[ebuild N ] dev-python/docutils-0.13.1
[ebuild N ] app-editors/vim-core-8.0.0386
[ebuild N ] dev-util/ctags-20161028
[ebuild N ] app-editors/vim-8.0.0386
[ebuild N ] app-vim/gentoo-syntax-20170225
[ebuild N ] app-admin/syslog-ng-3.7.3
[ebuild N ] sys-apps/gptfdisk-1.0.1
[ebuild N ] sys-process/cronie-1.5.0-r1
[ebuild N ] media-libs/freetype-2.8
[ebuild N ] sys-libs/efivar-30
[ebuild N ] dev-python/cffi-1.9.1
[ebuild N ] net-libs/gnutls-3.5.15
[ebuild N ] app-portage/eix-0.32.9
[ebuild N ] sys-block/parted-3.2-r1
[ebuild N ] sys-power/acpid-2.0.28
[ebuild N ] dev-python/cryptography-2.0.2-r1
[ebuild N ] virtual/logger-0
[ebuild N ] sys-fs/growpart-0.0.30
[ebuild N ] virtual/cron-0-r1
[ebuild N ] dev-python/pyopenssl-17.2.0
[ebuild N ] dev-python/oauthlib-2.0.2
[ebuild N ] mail-mta/nullmailer-2.0-r1
[ebuild N ] app-admin/logrotate-3.12.3-r1
[ebuild N ] dev-python/urllib3-1.22
[ebuild N ] virtual/mta-1
[ebuild N ] dev-python/requests-2.18.2-r1
[ebuild N ] app-admin/sudo-1.8.20_p2
[ebuild N ] app-emulation/cloud-init-17.1
[ebuild N ] virtual/libudev-232
[ebuild N ] sys-apps/pciutils-3.4.1
[ebuild N ] net-misc/dhcpcd-6.11.3
[ebuild N ] sys-boot/efibootmgr-14
[ebuild N ] sys-boot/grub-2.02
The following USE changes are necessary to proceed:
(see "package.use" in the portage(5) man page for more details)
# required by dev-python/cryptography-2.0.2-r1::gentoo
# required by dev-python/oauthlib-2.0.2::gentoo
# required by app-emulation/cloud-init-17.1::gentoo
# required by app-emulation/cloud-init (argument)
>=dev-libs/openssl-1.0.2l -bindist
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.
!!! catalyst: Error in attempt to build packages
Traceback (most recent call last):
File "modules/generic_stage_target.py", line 1432, in build_packages
"Error in attempt to build packages",env=self.env)
File "/usr/lib64/catalyst//modules/catalyst_support.py", line 541, in cmd
raise CatalystError,myexc
CatalystError
None
!!! catalyst: stage4build aborting due to error.
Traceback (most recent call last):
File "/usr/lib64/catalyst/catalyst", line 218, in build_target
mytarget.run()
File "modules/generic_stage_target.py", line 1333, in run
apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1437, in build_packages
"build aborting due to error."
CatalystError
!!! catalyst: Error encountered during run of target stage4
Catalyst aborting....
lockfile does not exist '/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-20171026/.catalyst_lock'
Command exited with non-zero status 1
39.66user 5.39system 0:28.18elapsed 159%CPU (0avgtext+0avgdata 807520maxresident)k
112inputs+1877608outputs (0major+209379minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171026.LrbDkj/log/hardened_stage4-cloud.log
next reply other threads:[~2017-10-26 22:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 22:59 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-03 21:11 [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-cloud.spec catalyst
2017-12-03 20:47 catalyst
2017-12-03 20:41 catalyst
2017-12-01 0:31 catalyst
2017-11-24 3:47 catalyst
2017-11-16 23:59 catalyst
2017-11-09 23:14 catalyst
2017-11-02 23:42 catalyst
2017-10-19 22:53 catalyst
2017-10-12 22:41 catalyst
2017-10-05 23:18 catalyst
2017-09-28 20:07 catalyst
2017-09-21 10:44 catalyst
2017-09-14 10:41 catalyst
2017-09-08 5:27 catalyst
2017-09-01 5:39 catalyst
2017-03-01 3:47 catalyst
2017-03-01 3:47 catalyst
2017-03-01 3:47 catalyst
2016-08-18 17:06 catalyst
2016-07-30 13:06 catalyst
2016-07-25 3:10 catalyst
2016-05-30 3:00 catalyst
2016-04-30 13:17 catalyst
2016-01-25 23:07 catalyst
2016-01-18 6:02 catalyst
2016-01-14 19:51 catalyst
2015-12-28 4:19 catalyst
2015-12-28 3:00 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=20171026225923.6D23A34119@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