* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-11-03 4:44 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-11-03 4:44 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
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+nomultilib-latest.tar.bz2
Caching snapshot to /release/tmp/snapshots/20171102/
The autoresume path is /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-nomultilib-20171102/
Location of the package cache is /release/buildroot/amd64-dev/packages/hardened/stage4-amd64-hardened+cloud-nomultilib-20171102/
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-nomultilib-20171102/
>>> 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-nomultilib-20171102/
clearing chroot ...
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171102/
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-nomultilib-20171102/
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171102/
Starting tar extract from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.bz2
to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171102/ (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-nomultilib-20171102//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171102//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-nomultilib-20171102/
>>> 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/push-2.0-r1
[ebuild N ] app-shells/quoter-3.0_p2-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/strict-rfc3339-0.6
[ebuild N ] dev-python/webcolors-1.5
[ebuild N ] dev-python/functools32-3.2.3
[ebuild N ] dev-python/regex-2016.01.10
[ebuild N ] dev-python/blinker-1.4
[ebuild N ] dev-libs/libtasn1-4.12-r1
[ebuild N ] net-dns/libidn2-2.0.4
[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/markupsafe-0.23
[ebuild N ] dev-python/pyjwt-1.5.3
[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/requests-2.18.2-r1::gentoo[ssl]
# 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-nomultilib-20171102/.catalyst_lock'
Command exited with non-zero status 1
39.09user 5.53system 0:28.17elapsed 158%CPU (0avgtext+0avgdata 811296maxresident)k
16inputs+1825736outputs (0major+216178minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171102.I7IfWF/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-12-03 21:11 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-12-03 21:11 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
usage: catalyst [-h] [-V] [-d] [-v]
[--log-level {critical,error,warning,notice,info,debug}]
[--log-file LOG_FILE] [--color] [--nocolor] [--trace]
[--profile] [-a] [-p] [-P] [-T] [-F] [-c CONFIGS] [-f FILE]
[-s SNAPSHOT] [-C ...]
catalyst: error: argument -f/--file: file does not exist: hardened/stage4-nomultilib-cloud.spec
Command exited with non-zero status 2
0.13user 0.00system 0:00.14elapsed 98%CPU (0avgtext+0avgdata 63376maxresident)k
0inputs+8outputs (0major+3812minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171203.3rjEdu/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-12-03 20:48 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-12-03 20:48 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
usage: catalyst [-h] [-V] [-d] [-v]
[--log-level {critical,error,warning,notice,info,debug}]
[--log-file LOG_FILE] [--color] [--nocolor] [--trace]
[--profile] [-a] [-p] [-P] [-T] [-F] [-c CONFIGS] [-f FILE]
[-s SNAPSHOT] [-C ...]
catalyst: error: argument -f/--file: file does not exist: hardened/stage4-nomultilib-cloud.spec
Command exited with non-zero status 2
0.12user 0.02system 0:00.14elapsed 99%CPU (0avgtext+0avgdata 63392maxresident)k
0inputs+8outputs (0major+3818minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171203.SmV1sP/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-12-03 20:41 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-12-03 20:41 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
usage: catalyst [-h] [-V] [-d] [-v]
[--log-level {critical,error,warning,notice,info,debug}]
[--log-file LOG_FILE] [--color] [--nocolor] [--trace]
[--profile] [-a] [-p] [-P] [-T] [-F] [-c CONFIGS] [-f FILE]
[-s SNAPSHOT] [-C ...]
catalyst: error: argument -f/--file: file does not exist: hardened/stage4-nomultilib-cloud.spec
Command exited with non-zero status 2
0.12user 0.01system 0:00.14elapsed 98%CPU (0avgtext+0avgdata 62800maxresident)k
0inputs+8outputs (0major+3823minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171203.PJy7an/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-12-01 6:18 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-12-01 6:18 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
Catalyst, version 2.0.19
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.
Traceback (most recent call last):
File "/usr/lib64/catalyst/modules/catalyst/config.py", line 27, in parse_file
myf = open(filename, "r")
IOError: [Errno 2] No such file or directory: 'hardened/stage4-nomultilib-cloud.spec'
None
!!! catalyst: Could not open file hardened/stage4-nomultilib-cloud.spec
Traceback (most recent call last):
File "/usr/lib64/catalyst/catalyst", line 374, in <module>
spec = modules.catalyst.config.SpecParser(myspecfile)
File "/usr/lib64/catalyst/modules/catalyst/config.py", line 112, in __init__
self.parse_file(filename)
File "/usr/lib64/catalyst/modules/catalyst/config.py", line 29, in parse_file
raise CatalystError, "Could not open file " + filename
modules.catalyst_support.CatalystError
Command exited with non-zero status 1
0.05user 0.02system 0:00.07elapsed 97%CPU (0avgtext+0avgdata 60800maxresident)k
0inputs+8outputs (0major+3107minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171130.pmIvcr/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-11-24 10:07 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-11-24 10:07 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
Catalyst, version 2.0.19
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.
Traceback (most recent call last):
File "/usr/lib64/catalyst/modules/catalyst/config.py", line 27, in parse_file
myf = open(filename, "r")
IOError: [Errno 2] No such file or directory: 'hardened/stage4-nomultilib-cloud.spec'
None
!!! catalyst: Could not open file hardened/stage4-nomultilib-cloud.spec
Traceback (most recent call last):
File "/usr/lib64/catalyst/catalyst", line 374, in <module>
spec = modules.catalyst.config.SpecParser(myspecfile)
File "/usr/lib64/catalyst/modules/catalyst/config.py", line 112, in __init__
self.parse_file(filename)
File "/usr/lib64/catalyst/modules/catalyst/config.py", line 29, in parse_file
raise CatalystError, "Could not open file " + filename
modules.catalyst_support.CatalystError
Command exited with non-zero status 1
0.05user 0.01system 0:00.07elapsed 98%CPU (0avgtext+0avgdata 60592maxresident)k
0inputs+8outputs (0major+3110minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171123.muQaFS/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-11-17 5:08 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-11-17 5:08 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
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+nomultilib-latest.tar.bz2
Caching snapshot to /release/tmp/snapshots/20171116/
The autoresume path is /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-nomultilib-20171116/
Location of the package cache is /release/buildroot/amd64-dev/packages/hardened/stage4-amd64-hardened+cloud-nomultilib-20171116/
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-nomultilib-20171116/
>>> 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-nomultilib-20171116/
clearing chroot ...
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171116/
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-nomultilib-20171116/
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171116/
Starting tar extract from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.bz2
to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171116/ (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-nomultilib-20171116//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171116//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-nomultilib-20171116/
>>> 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/push-2.0-r1
[ebuild N ] app-shells/quoter-3.0_p2-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.2m
[ebuild N ] sys-apps/lsb-release-1.4
[ebuild N ] dev-python/pyyaml-3.12
[ebuild N ] dev-python/functools32-3.2.3
[ebuild N ] dev-python/webcolors-1.5
[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/rfc3987-1.3.7
[ebuild N ] dev-python/vcversioner-2.16.0.0
[ebuild N ] dev-python/chardet-3.0.4
[ebuild N ] dev-python/PySocks-1.6.7
[ebuild N ] dev-python/asn1crypto-0.22.0
[ebuild N ] dev-python/enum34-1.1.6
[ebuild N ] dev-python/ply-3.9
[ebuild N ] dev-python/markupsafe-0.23
[ebuild N ] dev-python/pyjwt-1.5.3
[ebuild N ] dev-python/jsonpointer-1.10
[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/jsonpatch-1.13
[ebuild N ] dev-python/jinja-2.9.5
[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.13.0
[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[-libressl]
# 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.2m -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-nomultilib-20171116/.catalyst_lock'
Command exited with non-zero status 1
39.82user 5.81system 0:28.86elapsed 158%CPU (0avgtext+0avgdata 828016maxresident)k
48inputs+1830784outputs (1major+231081minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171116.lVaiZi/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-11-10 4:15 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-11-10 4:15 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
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+nomultilib-latest.tar.bz2
Caching snapshot to /release/tmp/snapshots/20171109/
The autoresume path is /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-nomultilib-20171109/
Location of the package cache is /release/buildroot/amd64-dev/packages/hardened/stage4-amd64-hardened+cloud-nomultilib-20171109/
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-nomultilib-20171109/
>>> 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-nomultilib-20171109/
clearing chroot ...
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171109/
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-nomultilib-20171109/
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171109/
Starting tar extract from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.bz2
to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171109/ (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-nomultilib-20171109//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171109//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-nomultilib-20171109/
>>> 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.2m
[ebuild N ] sys-apps/lsb-release-1.4
[ebuild N ] dev-python/pyyaml-3.12
[ebuild N ] dev-python/blinker-1.4
[ebuild N ] dev-python/functools32-3.2.3
[ebuild N ] dev-python/webcolors-1.5
[ebuild N ] dev-python/strict-rfc3339-0.6
[ebuild N ] dev-python/regex-2016.01.10
[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/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/pyjwt-1.5.3
[ebuild N ] dev-python/jsonpointer-1.10
[ebuild N ] dev-python/rfc3987-1.3.7
[ebuild N ] dev-python/vcversioner-2.16.0.0
[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/jsonschema-2.6.0
[ebuild N ] dev-python/jsonpatch-1.13
[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/requests-2.18.2-r1::gentoo[ssl]
# required by app-emulation/cloud-init-17.1::gentoo
# required by app-emulation/cloud-init (argument)
>=dev-libs/openssl-1.0.2m -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-nomultilib-20171109/.catalyst_lock'
Command exited with non-zero status 1
38.64user 5.36system 0:28.00elapsed 157%CPU (0avgtext+0avgdata 838576maxresident)k
32inputs+1829816outputs (0major+213373minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171109.gB4av2/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-10-27 4:00 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-10-27 4:00 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
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+nomultilib-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-nomultilib-20171026/
Location of the package cache is /release/buildroot/amd64-dev/packages/hardened/stage4-amd64-hardened+cloud-nomultilib-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-nomultilib-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-nomultilib-20171026/
clearing chroot ...
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-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-nomultilib-20171026/
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171026/
Starting tar extract from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.bz2
to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-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-nomultilib-20171026//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-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-nomultilib-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/functools32-3.2.3
[ebuild N ] dev-python/strict-rfc3339-0.6
[ebuild N ] dev-python/webcolors-1.5
[ebuild N ] dev-python/regex-2016.01.10
[ebuild N ] dev-python/blinker-1.4
[ebuild N ] dev-libs/libtasn1-4.12-r1
[ebuild N ] net-dns/libidn2-2.0.4
[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/rfc3987-1.3.7
[ebuild N ] dev-python/vcversioner-2.16.0.0
[ebuild N ] dev-python/markupsafe-0.23
[ebuild N ] dev-python/jsonpointer-1.10
[ebuild N ] dev-python/chardet-3.0.4
[ebuild N ] dev-python/PySocks-1.6.7
[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/pyjwt-1.5.3
[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/jsonpatch-1.13
[ebuild N ] dev-python/jinja-2.9.5
[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-nomultilib-20171026/.catalyst_lock'
Command exited with non-zero status 1
38.79user 5.61system 0:27.93elapsed 158%CPU (0avgtext+0avgdata 813520maxresident)k
72inputs+1817624outputs (2major+219434minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171026.LrbDkj/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-10-20 3:55 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-10-20 3:55 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
Catalyst, version 2.0.19
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+nomultilib-latest.tar.bz2
Caching snapshot to /release/tmp/snapshots/20171019/
The autoresume path is /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-nomultilib-20171019/
Location of the package cache is /release/buildroot/amd64-dev/packages/hardened/stage4-amd64-hardened+cloud-nomultilib-20171019/
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-nomultilib-20171019/
>>> 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-nomultilib-20171019/
clearing chroot ...
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171019/
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-nomultilib-20171019/
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171019/
Starting tar extract from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.bz2
to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171019/ (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-nomultilib-20171019//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171019//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-nomultilib-20171019/
>>> 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
[ebuild N ] app-shells/push-2.0
[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/blinker-1.4
[ebuild N ] dev-python/markdown-2.6.5
[ebuild N ] dev-libs/libtasn1-4.12-r1
[ebuild N ] net-dns/libidn2-2.0.4
[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/cheetah-2.4.4-r1
[ebuild N ] dev-python/pyserial-3.2.1
[ebuild N ] dev-python/prettytable-0.7.2
[ebuild N ] dev-python/chardet-3.0.4
[ebuild N ] dev-python/PySocks-1.6.7
[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/pyjwt-1.5.3
[ebuild N ] dev-python/jsonpointer-1.10
[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/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.4
[ebuild N ] sys-block/parted-3.2-r1
[ebuild N ] sys-power/acpid-2.0.28
[ebuild N ] dev-python/cryptography-2.0.2
[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-0.7.9
[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::gentoo
# required by dev-python/requests-2.18.2-r1::gentoo[ssl]
# required by app-emulation/cloud-init-0.7.9::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-nomultilib-20171019/.catalyst_lock'
Command exited with non-zero status 1
38.74user 5.56system 0:28.02elapsed 158%CPU (0avgtext+0avgdata 797280maxresident)k
64inputs+1816792outputs (0major+217814minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171019.XFbnjd/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-10-13 3:37 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-10-13 3:37 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
Catalyst, version 2.0.19
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+nomultilib-latest.tar.bz2
Caching snapshot to /release/tmp/snapshots/20171012/
The autoresume path is /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-nomultilib-20171012/
Location of the package cache is /release/buildroot/amd64-dev/packages/hardened/stage4-amd64-hardened+cloud-nomultilib-20171012/
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-nomultilib-20171012/
>>> 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-nomultilib-20171012/
clearing chroot ...
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171012/
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-nomultilib-20171012/
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171012/
Starting tar extract from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.bz2
to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171012/ (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-nomultilib-20171012//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171012//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-nomultilib-20171012/
>>> 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
[ebuild N ] app-shells/push-2.0
[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/blinker-1.4
[ebuild N ] dev-python/markdown-2.6.5
[ebuild N ] dev-libs/libtasn1-4.12-r1
[ebuild N ] net-dns/libidn2-2.0.4
[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/cheetah-2.4.4-r1
[ebuild N ] dev-python/prettytable-0.7.2
[ebuild N ] dev-python/pyserial-3.2.1
[ebuild N ] dev-python/markupsafe-0.23
[ebuild N ] dev-python/jsonpointer-1.10
[ebuild N ] dev-python/chardet-3.0.4
[ebuild N ] dev-python/PySocks-1.6.7
[ebuild N ] dev-python/asn1crypto-0.22.0
[ebuild N ] dev-python/enum34-1.1.6
[ebuild N ] dev-python/ply-3.9
[ebuild N ] dev-python/pyjwt-1.5.3
[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/jsonpatch-1.13
[ebuild N ] dev-python/jinja-2.9.5
[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.13
[ebuild N ] app-portage/eix-0.32.4
[ebuild N ] sys-block/parted-3.2-r1
[ebuild N ] sys-power/acpid-2.0.28
[ebuild N ] dev-python/cryptography-2.0.2
[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-0.7.9
[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::gentoo
# required by dev-python/oauthlib-2.0.2::gentoo
# required by app-emulation/cloud-init-0.7.9::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-nomultilib-20171012/.catalyst_lock'
Command exited with non-zero status 1
38.95user 5.85system 0:28.06elapsed 159%CPU (0avgtext+0avgdata 815872maxresident)k
16inputs+1816456outputs (0major+215126minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171012.TzNcCv/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-10-06 4:26 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-10-06 4:26 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
Catalyst, version 2.0.19
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+nomultilib-latest.tar.bz2
Caching snapshot to /release/tmp/snapshots/20171005/
The autoresume path is /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-nomultilib-20171005/
Location of the package cache is /release/buildroot/amd64-dev/packages/hardened/stage4-amd64-hardened+cloud-nomultilib-20171005/
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-nomultilib-20171005/
>>> 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-nomultilib-20171005/
clearing chroot ...
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171005/
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-nomultilib-20171005/
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171005/
Starting tar extract from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.bz2
to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171005/ (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-nomultilib-20171005//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20171005//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-nomultilib-20171005/
>>> 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
[ebuild N ] app-shells/push-2.0
[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/blinker-1.4
[ebuild N ] dev-python/markdown-2.6.5
[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.3.3
[ebuild N ] dev-python/idna-2.5
[ebuild N ] dev-python/cheetah-2.4.4-r1
[ebuild N ] dev-python/pyserial-3.2.1
[ebuild N ] dev-python/prettytable-0.7.2
[ebuild N ] dev-python/jsonpointer-1.10
[ebuild N ] dev-python/markupsafe-0.23
[ebuild N ] dev-python/pyjwt-1.5.3
[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/chardet-3.0.4
[ebuild N ] dev-python/PySocks-1.6.7
[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/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.13
[ebuild N ] app-portage/eix-0.32.4
[ebuild N ] sys-block/parted-3.2-r1
[ebuild N ] sys-power/acpid-2.0.28
[ebuild N ] dev-python/cryptography-2.0.2
[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-0.7.9
[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::gentoo
# required by dev-python/pyopenssl-17.2.0::gentoo
# required by dev-python/requests-2.18.2-r1::gentoo[ssl]
# required by app-emulation/cloud-init-0.7.9::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-nomultilib-20171005/.catalyst_lock'
Command exited with non-zero status 1
38.77user 5.59system 0:28.13elapsed 157%CPU (0avgtext+0avgdata 805040maxresident)k
720inputs+1816464outputs (0major+212870minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171005.CXcBxW/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-09-28 23:16 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-09-28 23:16 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
* for logrotate to use.
* Messages for package dev-python/jinja-2.9.5:
* For i18n support, please emerge dev-python/Babel.
* Messages for package net-misc/dhcpcd-6.11.3:
*
* dhcpcd has zeroconf support active by default.
* This means it will always obtain an IP address even if no
* DHCP server can be contacted, which will break any existing
* failover support you may have configured in your net configuration.
* This behaviour can be controlled with the noipv4ll configuration
* file option or the -L command line switch.
* See the dhcpcd and dhcpcd.conf man pages for more details.
*
* Dhcpcd has duid enabled by default, and this may cause issues
* with some dhcp servers. For more information, see
* https://bugs.gentoo.org/show_bug.cgi?id=477356
*
* If you activate the lookup-hostname hook to look up your hostname
* using the dns, you need to install net-dns/bind-tools.
* Messages for package sys-power/acpid-2.0.28:
*
* You may wish to read the Gentoo Linux Power Management Guide,
* which can be found online at:
* https://wiki.gentoo.org/wiki/Power_management/Guide
*
* You should reboot the system now to get /run mounted with tmpfs!
* Messages for package dev-util/ctags-20161028:
* You can set the version to be started by /usr/bin/ctags through
* the ctags eselect module. "man ctags.eselect" for details.
* Messages for package mail-mta/nullmailer-2.0-r1:
* To create an initial setup, please do:
* emerge --config =mail-mta/nullmailer-2.0-r1
* Messages for package app-admin/logrotate-3.12.2:
* The logrotate binary is now installed under /usr/bin. Please
* update your links
*
* If you wish to have logrotate e-mail you updates, please
* emerge virtual/mailx and configure logrotate in
* /etc/logrotate.conf appropriately
*
* Additionally, /etc/logrotate.conf may need to be modified
* for your particular needs. See man logrotate for details.
* Messages for package sys-boot/grub-2.02:
* For information on how to configure GRUB2 please refer to the guide:
* https://wiki.gentoo.org/wiki/GRUB2_Quick_Start
*
* You may consider installing the following optional packages:
* sys-boot/os-prober for Detect other operating systems (grub-mkconfig)
* dev-libs/libisoburn for Create rescue media (grub-mkrescue)
* sys-fs/mdadm for Enable RAID device detection
* Messages for package dev-python/ndg-httpsclient-0.4.0:
* The following *-nspkg.pth files were found installed:
*
* /usr/lib64/python3.4/site-packages/ndg_httpsclient-0.4.0-py3.4-nspkg.pth
* /usr/lib64/python2.7/site-packages/ndg_httpsclient-0.4.0-py2.7-nspkg.pth
*
* The presence of those files may break namespaces in Python 3.5+. Please
* read our documentation on reliable handling of namespaces and update
* the ebuild accordingly:
*
* https://wiki.gentoo.org/wiki/Project:Python/Namespace_packages
* Messages for package app-emulation/cloud-init-0.7.9:
* cloud-init-local needs to be run in the boot runlevel because it
* modifies services in the default runlevel. When a runlevel is started
* it is cached, so modifications that happen to the current runlevel
* while you are in it are not acted upon.
* Messages for package app-vim/gentoo-syntax-20170225:
* Note for developers and anyone else who edits ebuilds:
* This release of gentoo-syntax now contains filetype rules to set
* fileencoding for ebuilds and ChangeLogs to utf-8 as per GLEP 31.
* If you find this feature breaks things, please submit a bug and
* assign it to vim@gentoo.org. You can use the 'ignore-glep31' USE
* flag to remove these rules.
* Messages for package app-admin/sudo-1.8.20_p2:
* To use the -A (askpass) option, you need to install a compatible
* password program from the following list. Starred packages will
* automatically register for the use with sudo (but will not force
* the -A option):
*
* [*] net-misc/ssh-askpass-fullscreen
* net-misc/x11-ssh-askpass
*
* You can override the choice by setting the SUDO_ASKPASS environmnent
* variable to the program you want to use.
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928//tmp/stage4-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928//tmp/chroot-functions.sh from the chroot
--- Running action sequence: build_kernel
Copying pre-kmerge.sh to /tmp
copying pre-kmerge.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928//tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928/
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot genkernel
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-kernel/genkernel-3.4.52.4-r2
>>> Emerging (1 of 2) app-arch/cpio-2.12-r1::gentoo
>>> Installing (1 of 2) app-arch/cpio-2.12-r1::gentoo
>>> Emerging (2 of 2) sys-kernel/genkernel-3.4.52.4-r2::gentoo
>>> Installing (2 of 2) sys-kernel/genkernel-3.4.52.4-r2::gentoo
* Messages for package sys-kernel/genkernel-3.4.52.4-r2:
* Documentation is available in the genkernel manual page
* as well as the following URL:
* https://wiki.gentoo.org/wiki/Genkernel
* This package is known to not work with reiser4. If you are running
* reiser4 and have a problem, do not file a bug. We know it does not
* work and we don't plan on fixing it since reiser4 is the one that is
* broken in this regard. Try using a sane filesystem like ext4.
* The LUKS support has changed from versions prior to 3.4.4. Now,
* you use crypt_root=/dev/blah instead of real_root=luks:/dev/blah.
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928//tmp/pre-kmerge.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928//tmp/chroot-functions.sh from the chroot
Copying kmerge.sh to /tmp
copying kmerge.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928//tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928/
>>> Regenerating /etc/ld.so.cache...
Genkernel version 3.4.52.4 found ... continuing
emerge --quiet --usepkg --buildpkg --newuse hardened-sources
[ebuild N ] sys-kernel/hardened-sources-4.8.17-r2
The following mask changes are necessary to proceed:
(see "package.unmask" in the portage(5) man page for more details)
# required by hardened-sources (argument)
# /usr/portage/profiles/package.mask:
# Anthony G. Basile <blueness@gentoo.org> (27 Aug 2017)
# Upstream is no longer providing public patches
=sys-kernel/hardened-sources-4.8.17-r2
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.
* IMPORTANT: 10 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
!!! catalyst: Runscript kernel build failed
Traceback (most recent call last):
File "modules/generic_stage_target.py", line 1457, in build_kernel
self._build_kernel(kname=kname)
File "modules/generic_stage_target.py", line 1501, in _build_kernel
"Runscript kernel build failed",env=self.env)
File "/usr/lib64/catalyst//modules/catalyst_support.py", line 541, in cmd
raise CatalystError,myexc
CatalystError
None
!!! catalyst: build aborting due to kernel build 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 1462, in build_kernel
"build aborting due to kernel build 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-nomultilib-20170928/.catalyst_lock'
Command exited with non-zero status 1
8584.46user 1345.54system 1:13:07elapsed 226%CPU (0avgtext+0avgdata 3222944maxresident)k
7073inputs+15677921outputs (0major+341421025minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20170928.r9Ro52/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-09-21 11:41 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-09-21 11:41 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
* for logrotate to use.
* Messages for package dev-python/jinja-2.9.5:
* For i18n support, please emerge dev-python/Babel.
* Messages for package net-misc/dhcpcd-6.11.3:
*
* dhcpcd has zeroconf support active by default.
* This means it will always obtain an IP address even if no
* DHCP server can be contacted, which will break any existing
* failover support you may have configured in your net configuration.
* This behaviour can be controlled with the noipv4ll configuration
* file option or the -L command line switch.
* See the dhcpcd and dhcpcd.conf man pages for more details.
*
* Dhcpcd has duid enabled by default, and this may cause issues
* with some dhcp servers. For more information, see
* https://bugs.gentoo.org/show_bug.cgi?id=477356
*
* If you activate the lookup-hostname hook to look up your hostname
* using the dns, you need to install net-dns/bind-tools.
* Messages for package sys-power/acpid-2.0.28:
*
* You may wish to read the Gentoo Linux Power Management Guide,
* which can be found online at:
* https://wiki.gentoo.org/wiki/Power_management/Guide
*
* You should reboot the system now to get /run mounted with tmpfs!
* Messages for package dev-util/ctags-20161028:
* You can set the version to be started by /usr/bin/ctags through
* the ctags eselect module. "man ctags.eselect" for details.
* Messages for package mail-mta/nullmailer-2.0-r1:
* To create an initial setup, please do:
* emerge --config =mail-mta/nullmailer-2.0-r1
* Messages for package app-admin/logrotate-3.12.2:
* The logrotate binary is now installed under /usr/bin. Please
* update your links
*
* If you wish to have logrotate e-mail you updates, please
* emerge virtual/mailx and configure logrotate in
* /etc/logrotate.conf appropriately
*
* Additionally, /etc/logrotate.conf may need to be modified
* for your particular needs. See man logrotate for details.
* Messages for package sys-boot/grub-2.02:
* For information on how to configure GRUB2 please refer to the guide:
* https://wiki.gentoo.org/wiki/GRUB2_Quick_Start
*
* You may consider installing the following optional packages:
* sys-boot/os-prober for Detect other operating systems (grub-mkconfig)
* dev-libs/libisoburn for Create rescue media (grub-mkrescue)
* sys-fs/mdadm for Enable RAID device detection
* Messages for package dev-python/ndg-httpsclient-0.4.0:
* The following *-nspkg.pth files were found installed:
*
* /usr/lib64/python3.4/site-packages/ndg_httpsclient-0.4.0-py3.4-nspkg.pth
* /usr/lib64/python2.7/site-packages/ndg_httpsclient-0.4.0-py2.7-nspkg.pth
*
* The presence of those files may break namespaces in Python 3.5+. Please
* read our documentation on reliable handling of namespaces and update
* the ebuild accordingly:
*
* https://wiki.gentoo.org/wiki/Project:Python/Namespace_packages
* Messages for package app-emulation/cloud-init-0.7.9:
* cloud-init-local needs to be run in the boot runlevel because it
* modifies services in the default runlevel. When a runlevel is started
* it is cached, so modifications that happen to the current runlevel
* while you are in it are not acted upon.
* Messages for package app-vim/gentoo-syntax-20170225:
* Note for developers and anyone else who edits ebuilds:
* This release of gentoo-syntax now contains filetype rules to set
* fileencoding for ebuilds and ChangeLogs to utf-8 as per GLEP 31.
* If you find this feature breaks things, please submit a bug and
* assign it to vim@gentoo.org. You can use the 'ignore-glep31' USE
* flag to remove these rules.
* Messages for package app-admin/sudo-1.8.20_p2:
* To use the -A (askpass) option, you need to install a compatible
* password program from the following list. Starred packages will
* automatically register for the use with sudo (but will not force
* the -A option):
*
* [*] net-misc/ssh-askpass-fullscreen
* net-misc/x11-ssh-askpass
*
* You can override the choice by setting the SUDO_ASKPASS environmnent
* variable to the program you want to use.
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170921//tmp/stage4-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170921//tmp/chroot-functions.sh from the chroot
--- Running action sequence: build_kernel
Copying pre-kmerge.sh to /tmp
copying pre-kmerge.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170921//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170921//tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170921/
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot genkernel
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-kernel/genkernel-3.4.52.4-r2
>>> Emerging (1 of 2) app-arch/cpio-2.12-r1::gentoo
>>> Installing (1 of 2) app-arch/cpio-2.12-r1::gentoo
>>> Emerging (2 of 2) sys-kernel/genkernel-3.4.52.4-r2::gentoo
>>> Installing (2 of 2) sys-kernel/genkernel-3.4.52.4-r2::gentoo
* Messages for package sys-kernel/genkernel-3.4.52.4-r2:
* Documentation is available in the genkernel manual page
* as well as the following URL:
* https://wiki.gentoo.org/wiki/Genkernel
* This package is known to not work with reiser4. If you are running
* reiser4 and have a problem, do not file a bug. We know it does not
* work and we don't plan on fixing it since reiser4 is the one that is
* broken in this regard. Try using a sane filesystem like ext4.
* The LUKS support has changed from versions prior to 3.4.4. Now,
* you use crypt_root=/dev/blah instead of real_root=luks:/dev/blah.
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170921//tmp/pre-kmerge.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170921//tmp/chroot-functions.sh from the chroot
Copying kmerge.sh to /tmp
copying kmerge.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170921//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170921//tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170921/
>>> Regenerating /etc/ld.so.cache...
Genkernel version 3.4.52.4 found ... continuing
emerge --quiet --usepkg --buildpkg --newuse hardened-sources
[ebuild N ] sys-kernel/hardened-sources-4.8.17-r2
The following mask changes are necessary to proceed:
(see "package.unmask" in the portage(5) man page for more details)
# required by hardened-sources (argument)
# /usr/portage/profiles/package.mask:
# Anthony G. Basile <blueness@gentoo.org> (27 Aug 2017)
# Upstream is no longer providing public patches
=sys-kernel/hardened-sources-4.8.17-r2
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.
* IMPORTANT: 10 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
!!! catalyst: Runscript kernel build failed
Traceback (most recent call last):
File "modules/generic_stage_target.py", line 1457, in build_kernel
self._build_kernel(kname=kname)
File "modules/generic_stage_target.py", line 1501, in _build_kernel
"Runscript kernel build failed",env=self.env)
File "/usr/lib64/catalyst//modules/catalyst_support.py", line 541, in cmd
raise CatalystError,myexc
CatalystError
None
!!! catalyst: build aborting due to kernel build 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 1462, in build_kernel
"build aborting due to kernel build 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-nomultilib-20170921/.catalyst_lock'
Command exited with non-zero status 1
2058.85user 652.09system 35:29.91elapsed 127%CPU (0avgtext+0avgdata 1239536maxresident)k
1865inputs+6040049outputs (1major+175486803minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20170921.JtAixy/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-09-14 11:37 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-09-14 11:37 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
* for logrotate to use.
* Messages for package dev-python/jinja-2.9.5:
* For i18n support, please emerge dev-python/Babel.
* Messages for package net-misc/dhcpcd-6.11.3:
*
* dhcpcd has zeroconf support active by default.
* This means it will always obtain an IP address even if no
* DHCP server can be contacted, which will break any existing
* failover support you may have configured in your net configuration.
* This behaviour can be controlled with the noipv4ll configuration
* file option or the -L command line switch.
* See the dhcpcd and dhcpcd.conf man pages for more details.
*
* Dhcpcd has duid enabled by default, and this may cause issues
* with some dhcp servers. For more information, see
* https://bugs.gentoo.org/show_bug.cgi?id=477356
*
* If you activate the lookup-hostname hook to look up your hostname
* using the dns, you need to install net-dns/bind-tools.
* Messages for package sys-power/acpid-2.0.28:
*
* You may wish to read the Gentoo Linux Power Management Guide,
* which can be found online at:
* https://wiki.gentoo.org/wiki/Power_management/Guide
*
* You should reboot the system now to get /run mounted with tmpfs!
* Messages for package dev-util/ctags-20161028:
* You can set the version to be started by /usr/bin/ctags through
* the ctags eselect module. "man ctags.eselect" for details.
* Messages for package mail-mta/nullmailer-2.0-r1:
* To create an initial setup, please do:
* emerge --config =mail-mta/nullmailer-2.0-r1
* Messages for package app-admin/logrotate-3.12.2:
* The logrotate binary is now installed under /usr/bin. Please
* update your links
*
* If you wish to have logrotate e-mail you updates, please
* emerge virtual/mailx and configure logrotate in
* /etc/logrotate.conf appropriately
*
* Additionally, /etc/logrotate.conf may need to be modified
* for your particular needs. See man logrotate for details.
* Messages for package sys-boot/grub-2.02:
* For information on how to configure GRUB2 please refer to the guide:
* https://wiki.gentoo.org/wiki/GRUB2_Quick_Start
*
* You may consider installing the following optional packages:
* sys-boot/os-prober for Detect other operating systems (grub-mkconfig)
* dev-libs/libisoburn for Create rescue media (grub-mkrescue)
* sys-fs/mdadm for Enable RAID device detection
* Messages for package dev-python/ndg-httpsclient-0.4.0:
* The following *-nspkg.pth files were found installed:
*
* /usr/lib64/python3.4/site-packages/ndg_httpsclient-0.4.0-py3.4-nspkg.pth
* /usr/lib64/python2.7/site-packages/ndg_httpsclient-0.4.0-py2.7-nspkg.pth
*
* The presence of those files may break namespaces in Python 3.5+. Please
* read our documentation on reliable handling of namespaces and update
* the ebuild accordingly:
*
* https://wiki.gentoo.org/wiki/Project:Python/Namespace_packages
* Messages for package app-emulation/cloud-init-0.7.9:
* cloud-init-local needs to be run in the boot runlevel because it
* modifies services in the default runlevel. When a runlevel is started
* it is cached, so modifications that happen to the current runlevel
* while you are in it are not acted upon.
* Messages for package app-vim/gentoo-syntax-20170225:
* Note for developers and anyone else who edits ebuilds:
* This release of gentoo-syntax now contains filetype rules to set
* fileencoding for ebuilds and ChangeLogs to utf-8 as per GLEP 31.
* If you find this feature breaks things, please submit a bug and
* assign it to vim@gentoo.org. You can use the 'ignore-glep31' USE
* flag to remove these rules.
* Messages for package app-admin/sudo-1.8.20_p2:
* To use the -A (askpass) option, you need to install a compatible
* password program from the following list. Starred packages will
* automatically register for the use with sudo (but will not force
* the -A option):
*
* [*] net-misc/ssh-askpass-fullscreen
* net-misc/x11-ssh-askpass
*
* You can override the choice by setting the SUDO_ASKPASS environmnent
* variable to the program you want to use.
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170914//tmp/stage4-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170914//tmp/chroot-functions.sh from the chroot
--- Running action sequence: build_kernel
Copying pre-kmerge.sh to /tmp
copying pre-kmerge.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170914//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170914//tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170914/
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot genkernel
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-kernel/genkernel-3.4.52.4-r2
>>> Emerging (1 of 2) app-arch/cpio-2.12-r1::gentoo
>>> Installing (1 of 2) app-arch/cpio-2.12-r1::gentoo
>>> Emerging (2 of 2) sys-kernel/genkernel-3.4.52.4-r2::gentoo
>>> Installing (2 of 2) sys-kernel/genkernel-3.4.52.4-r2::gentoo
* Messages for package sys-kernel/genkernel-3.4.52.4-r2:
* Documentation is available in the genkernel manual page
* as well as the following URL:
* https://wiki.gentoo.org/wiki/Genkernel
* This package is known to not work with reiser4. If you are running
* reiser4 and have a problem, do not file a bug. We know it does not
* work and we don't plan on fixing it since reiser4 is the one that is
* broken in this regard. Try using a sane filesystem like ext4.
* The LUKS support has changed from versions prior to 3.4.4. Now,
* you use crypt_root=/dev/blah instead of real_root=luks:/dev/blah.
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170914//tmp/pre-kmerge.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170914//tmp/chroot-functions.sh from the chroot
Copying kmerge.sh to /tmp
copying kmerge.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170914//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170914//tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170914/
>>> Regenerating /etc/ld.so.cache...
Genkernel version 3.4.52.4 found ... continuing
emerge --quiet --usepkg --buildpkg --newuse hardened-sources
[ebuild N ] sys-kernel/hardened-sources-4.8.17-r2
The following mask changes are necessary to proceed:
(see "package.unmask" in the portage(5) man page for more details)
# required by hardened-sources (argument)
# /usr/portage/profiles/package.mask:
# Anthony G. Basile <blueness@gentoo.org> (27 Aug 2017)
# Upstream is no longer providing public patches
=sys-kernel/hardened-sources-4.8.17-r2
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.
* IMPORTANT: 10 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
!!! catalyst: Runscript kernel build failed
Traceback (most recent call last):
File "modules/generic_stage_target.py", line 1457, in build_kernel
self._build_kernel(kname=kname)
File "modules/generic_stage_target.py", line 1501, in _build_kernel
"Runscript kernel build failed",env=self.env)
File "/usr/lib64/catalyst//modules/catalyst_support.py", line 541, in cmd
raise CatalystError,myexc
CatalystError
None
!!! catalyst: build aborting due to kernel build 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 1462, in build_kernel
"build aborting due to kernel build 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-nomultilib-20170914/.catalyst_lock'
Command exited with non-zero status 1
2032.31user 621.33system 34:56.42elapsed 126%CPU (0avgtext+0avgdata 1239632maxresident)k
833inputs+5842217outputs (0major+174197071minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20170914.TzyYrd/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-09-08 11:08 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-09-08 11:08 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
* for logrotate to use.
* Messages for package dev-python/jinja-2.9.5:
* For i18n support, please emerge dev-python/Babel.
* Messages for package net-misc/dhcpcd-6.11.3:
*
* dhcpcd has zeroconf support active by default.
* This means it will always obtain an IP address even if no
* DHCP server can be contacted, which will break any existing
* failover support you may have configured in your net configuration.
* This behaviour can be controlled with the noipv4ll configuration
* file option or the -L command line switch.
* See the dhcpcd and dhcpcd.conf man pages for more details.
*
* Dhcpcd has duid enabled by default, and this may cause issues
* with some dhcp servers. For more information, see
* https://bugs.gentoo.org/show_bug.cgi?id=477356
*
* If you activate the lookup-hostname hook to look up your hostname
* using the dns, you need to install net-dns/bind-tools.
* Messages for package sys-power/acpid-2.0.28:
*
* You may wish to read the Gentoo Linux Power Management Guide,
* which can be found online at:
* https://wiki.gentoo.org/wiki/Power_management/Guide
*
* You should reboot the system now to get /run mounted with tmpfs!
* Messages for package dev-util/ctags-20161028:
* You can set the version to be started by /usr/bin/ctags through
* the ctags eselect module. "man ctags.eselect" for details.
* Messages for package mail-mta/nullmailer-2.0-r1:
* To create an initial setup, please do:
* emerge --config =mail-mta/nullmailer-2.0-r1
* Messages for package app-admin/logrotate-3.12.2:
* The logrotate binary is now installed under /usr/bin. Please
* update your links
*
* If you wish to have logrotate e-mail you updates, please
* emerge virtual/mailx and configure logrotate in
* /etc/logrotate.conf appropriately
*
* Additionally, /etc/logrotate.conf may need to be modified
* for your particular needs. See man logrotate for details.
* Messages for package sys-boot/grub-2.02:
* For information on how to configure GRUB2 please refer to the guide:
* https://wiki.gentoo.org/wiki/GRUB2_Quick_Start
*
* You may consider installing the following optional packages:
* sys-boot/os-prober for Detect other operating systems (grub-mkconfig)
* dev-libs/libisoburn for Create rescue media (grub-mkrescue)
* sys-fs/mdadm for Enable RAID device detection
* Messages for package dev-python/ndg-httpsclient-0.4.0:
* The following *-nspkg.pth files were found installed:
*
* /usr/lib64/python3.4/site-packages/ndg_httpsclient-0.4.0-py3.4-nspkg.pth
* /usr/lib64/python2.7/site-packages/ndg_httpsclient-0.4.0-py2.7-nspkg.pth
*
* The presence of those files may break namespaces in Python 3.5+. Please
* read our documentation on reliable handling of namespaces and update
* the ebuild accordingly:
*
* https://wiki.gentoo.org/wiki/Project:Python/Namespace_packages
* Messages for package app-emulation/cloud-init-0.7.9:
* cloud-init-local needs to be run in the boot runlevel because it
* modifies services in the default runlevel. When a runlevel is started
* it is cached, so modifications that happen to the current runlevel
* while you are in it are not acted upon.
* Messages for package app-vim/gentoo-syntax-20170225:
* Note for developers and anyone else who edits ebuilds:
* This release of gentoo-syntax now contains filetype rules to set
* fileencoding for ebuilds and ChangeLogs to utf-8 as per GLEP 31.
* If you find this feature breaks things, please submit a bug and
* assign it to vim@gentoo.org. You can use the 'ignore-glep31' USE
* flag to remove these rules.
* Messages for package app-admin/sudo-1.8.20_p2:
* To use the -A (askpass) option, you need to install a compatible
* password program from the following list. Starred packages will
* automatically register for the use with sudo (but will not force
* the -A option):
*
* [*] net-misc/ssh-askpass-fullscreen
* net-misc/x11-ssh-askpass
*
* You can override the choice by setting the SUDO_ASKPASS environmnent
* variable to the program you want to use.
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170907//tmp/stage4-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170907//tmp/chroot-functions.sh from the chroot
--- Running action sequence: build_kernel
Copying pre-kmerge.sh to /tmp
copying pre-kmerge.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170907//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170907//tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170907/
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot genkernel
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-kernel/genkernel-3.4.52.4-r2
>>> Emerging (1 of 2) app-arch/cpio-2.12-r1::gentoo
>>> Installing (1 of 2) app-arch/cpio-2.12-r1::gentoo
>>> Emerging (2 of 2) sys-kernel/genkernel-3.4.52.4-r2::gentoo
>>> Installing (2 of 2) sys-kernel/genkernel-3.4.52.4-r2::gentoo
* Messages for package sys-kernel/genkernel-3.4.52.4-r2:
* Documentation is available in the genkernel manual page
* as well as the following URL:
* https://wiki.gentoo.org/wiki/Genkernel
* This package is known to not work with reiser4. If you are running
* reiser4 and have a problem, do not file a bug. We know it does not
* work and we don't plan on fixing it since reiser4 is the one that is
* broken in this regard. Try using a sane filesystem like ext4.
* The LUKS support has changed from versions prior to 3.4.4. Now,
* you use crypt_root=/dev/blah instead of real_root=luks:/dev/blah.
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170907//tmp/pre-kmerge.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170907//tmp/chroot-functions.sh from the chroot
Copying kmerge.sh to /tmp
copying kmerge.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170907//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170907//tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170907/
>>> Regenerating /etc/ld.so.cache...
Genkernel version 3.4.52.4 found ... continuing
emerge --quiet --usepkg --buildpkg --newuse hardened-sources
[ebuild N ] sys-kernel/hardened-sources-4.8.17-r2
The following mask changes are necessary to proceed:
(see "package.unmask" in the portage(5) man page for more details)
# required by hardened-sources (argument)
# /usr/portage/profiles/package.mask:
# Anthony G. Basile <blueness@gentoo.org> (27 Aug 2017)
# Upstream is no longer providing public patches
=sys-kernel/hardened-sources-4.8.17-r2
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.
* IMPORTANT: 10 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
!!! catalyst: Runscript kernel build failed
Traceback (most recent call last):
File "modules/generic_stage_target.py", line 1457, in build_kernel
self._build_kernel(kname=kname)
File "modules/generic_stage_target.py", line 1501, in _build_kernel
"Runscript kernel build failed",env=self.env)
File "/usr/lib64/catalyst//modules/catalyst_support.py", line 541, in cmd
raise CatalystError,myexc
CatalystError
None
!!! catalyst: build aborting due to kernel build 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 1462, in build_kernel
"build aborting due to kernel build 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-nomultilib-20170907/.catalyst_lock'
Command exited with non-zero status 1
2015.34user 639.37system 34:19.92elapsed 128%CPU (0avgtext+0avgdata 1239440maxresident)k
4505inputs+5764761outputs (0major+170765780minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20170907.0gPRKO/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-09-01 8:06 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-09-01 8:06 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
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+nomultilib-latest.tar.bz2
Caching snapshot to /release/tmp/snapshots/20170831/
The autoresume path is /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-nomultilib-20170831/
Location of the package cache is /release/buildroot/amd64-dev/packages/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831/
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-nomultilib-20170831/
>>> 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-nomultilib-20170831/
clearing chroot ...
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831/
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-nomultilib-20170831/
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831/
Starting tar extract from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.bz2
to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831/ (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-nomultilib-20170831//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170831//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-nomultilib-20170831/
>>> Regenerating /etc/ld.so.cache...
Updating portage with USE=""
emerge --quiet --usepkg --buildpkg --newuse --oneshot --update --newuse sys-apps/portage
Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)
Bringing system up to date using profile specific use flags
emerge --quiet --usepkg --buildpkg --newuse -u @system
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-devel/binutils-2.28.1::gentoo
>>> Failed to emerge sys-devel/binutils-2.28.1, Log file:
>>> '/var/tmp/portage/sys-devel/binutils-2.28.1/temp/build.log'
* Package: sys-devel/binutils-2.28.1
* Repository: gentoo
* Maintainer: toolchain@gentoo.org
* USE: abi_x86_64 amd64 cxx elibc_glibc kernel_linux nls userland_GNU
* FEATURES: preserve-libs sandbox userpriv usersandbox
/usr/bin/install: cannot change permissions of '/var/tmp/portage/sys-devel/binutils-2.28.1/work': No such file or directory
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* ERROR: sys-devel/binutils-2.28.1::gentoo failed (unpack phase):
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* Failed to create dir '/var/tmp/portage/sys-devel/binutils-2.28.1/work'
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
*
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* Call stack:
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* ebuild.sh, line 767: Called __ebuild_main 'unpack'
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* phase-functions.sh, line 1008: Called __dyn_unpack
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* phase-functions.sh, line 240: Called die
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* The specific snippet of code:
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* install -m${PORTAGE_WORKDIR_MODE:-0700} -d "${WORKDIR}" || die "Failed to create dir '${WORKDIR}'"
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
*
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* If you need support, post the output of `emerge --info '=sys-devel/binutils-2.28.1::gentoo'`,
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* the complete build log and the output of `emerge -pqv '=sys-devel/binutils-2.28.1::gentoo'`.
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* The complete build log is located at '/var/tmp/portage/sys-devel/binutils-2.28.1/temp/build.log'.
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/binutils-2.28.1/temp/environment'.
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* Working directory: '/var/tmp/portage/sys-devel/binutils-2.28.1/homedir'
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* S: '/var/tmp/portage/sys-devel/binutils-2.28.1/work/binutils-2.28.1'
* ACCESS DENIED: open_wr: /usr/lib64/python3.4/site-packages/aayc8gmb
Traceback (most recent call last):
File "/usr/lib/portage/python3.4/ebuild-ipc.py", line 282, in <module>
sys.exit(ebuild_ipc_main(sys.argv[1:]))
File "/usr/lib/portage/python3.4/ebuild-ipc.py", line 279, in ebuild_ipc_main
return ebuild_ipc.communicate(args)
File "/usr/lib/portage/python3.4/ebuild-ipc.py", line 136, in communicate
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True)
File "/usr/lib64/python3.4/site-packages/portage/locks.py", line 194, in lockfile
locking_method = portage._eintr_func_wrapper(_get_lock_fn())
File "/usr/lib64/python3.4/site-packages/portage/locks.py", line 62, in _get_lock_fn
fd, lock_path = tempfile.mkstemp()
File "/usr/lib64/python3.4/tempfile.py", line 271, in mkstemp
dir = gettempdir()
File "/usr/lib64/python3.4/tempfile.py", line 239, in gettempdir
tempdir = _get_default_tempdir()
File "/usr/lib64/python3.4/tempfile.py", line 180, in _get_default_tempdir
dirlist)
FileNotFoundError: [Errno 2] No usable temporary directory found in ['/var/tmp/portage/sys-devel/binutils-2.28.1/temp', '/var/tmp/portage/sys-devel/binutils-2.28.1/temp', '/var/tmp/portage/sys-devel/binutils-2.28.1/temp', '/tmp', '/var/tmp', '/usr/tmp', '/usr/lib64/python3.4/site-packages']
* --------------------------- ACCESS VIOLATION SUMMARY ---------------------------
* LOG FILE: "/var/log/sandbox/sandbox-18323.log"
* --------------------------------------------------------------------------------
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
* Messages for package sys-devel/binutils-2.28.1:
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
!!! 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-nomultilib-20170831/.catalyst_lock'
Command exited with non-zero status 1
34.53user 6.04system 0:24.61elapsed 164%CPU (0avgtext+0avgdata 844784maxresident)k
3984inputs+1815176outputs (0major+292809minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20170831.IkLA0t/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-03-31 8:21 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-03-31 8:21 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
*
* Additional tools that may be of interest:
*
* app-admin/eclean-kernel
* app-portage/diffmask
* app-portage/flaggie
* app-portage/install-mask
* app-portage/portpeek
* app-portage/smart-live-rebuild
* Messages for package app-admin/syslog-ng-3.7.3:
* For detailed documentation please see the upstream website:
* http://www.balabit.com/sites/default/files/documents/syslog-ng-ose-3.7-guides/en/syslog-ng-ose-v3.7-guide-admin/html/index.html
* It is highly recommended that app-admin/logrotate be emerged to
* manage the log files. syslog-ng installs a file in /etc/logrotate.d
* for logrotate to use.
* Messages for package dev-python/jinja-2.8:
* For i18n support, please emerge dev-python/Babel.
* Messages for package net-misc/dhcpcd-6.11.3:
*
* dhcpcd has zeroconf support active by default.
* This means it will always obtain an IP address even if no
* DHCP server can be contacted, which will break any existing
* failover support you may have configured in your net configuration.
* This behaviour can be controlled with the noipv4ll configuration
* file option or the -L command line switch.
* See the dhcpcd and dhcpcd.conf man pages for more details.
*
* Dhcpcd has duid enabled by default, and this may cause issues
* with some dhcp servers. For more information, see
* https://bugs.gentoo.org/show_bug.cgi?id=477356
*
* If you activate the lookup-hostname hook to look up your hostname
* using the dns, you need to install net-dns/bind-tools.
* Messages for package sys-power/acpid-2.0.28:
*
* You may wish to read the Gentoo Linux Power Management Guide,
* which can be found online at:
* https://wiki.gentoo.org/wiki/Power_management/Guide
*
* You should reboot the system now to get /run mounted with tmpfs!
* Messages for package dev-util/ctags-20161028:
* You can set the version to be started by /usr/bin/ctags through
* the ctags eselect module. "man ctags.eselect" for details.
* Messages for package dev-python/pyjwt-1.4.0:
* Available optional features:
* dev-python/flake8 for flake8
* flake8 feature requires 'flake8-import-order' and 'pep8-naming', which are not in portage yet
* Messages for package mail-mta/nullmailer-1.13-r5:
* To create an initial setup, please do:
* emerge --config =mail-mta/nullmailer-1.13-r5
* Messages for package app-admin/logrotate-3.11.0:
* The logrotate binary is now installed under /usr/bin. Please
* update your links
*
* If you wish to have logrotate e-mail you updates, please
* emerge virtual/mailx and configure logrotate in
* /etc/logrotate.conf appropriately
*
* Additionally, /etc/logrotate.conf may need to be modified
* for your particular needs. See man logrotate for details.
* Messages for package sys-boot/grub-2.02_beta3-r1:
* For information on how to configure GRUB2 please refer to the guide:
* https://wiki.gentoo.org/wiki/GRUB2_Quick_Start
*
* For manual configuration, see /usr/share/doc/grub-2.02_beta3-r1/grub.cfg.example
*
* You may consider installing the following optional packages:
* sys-boot/os-prober for Detect other operating systems (grub-mkconfig)
* dev-libs/libisoburn for Create rescue media (grub-mkrescue)
* sys-fs/mdadm for Enable RAID device detection
* Messages for package app-emulation/cloud-init-0.7.9:
* cloud-init-local needs to be run in the boot runlevel because it
* modifies services in the default runlevel. When a runlevel is started
* it is cached, so modifications that happen to the current runlevel
* while you are in it are not acted upon.
* Messages for package app-vim/gentoo-syntax-20170225:
* Note for developers and anyone else who edits ebuilds:
* This release of gentoo-syntax now contains filetype rules to set
* fileencoding for ebuilds and ChangeLogs to utf-8 as per GLEP 31.
* If you find this feature breaks things, please submit a bug and
* assign it to vim@gentoo.org. You can use the 'ignore-glep31' USE
* flag to remove these rules.
* Messages for package app-admin/sudo-1.8.18_p1:
* To use the -A (askpass) option, you need to install a compatible
* password program from the following list. Starred packages will
* automatically register for the use with sudo (but will not force
* the -A option):
*
* [*] net-misc/ssh-askpass-fullscreen
* net-misc/x11-ssh-askpass
*
* You can override the choice by setting the SUDO_ASKPASS environmnent
* variable to the program you want to use.
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170323//tmp/stage4-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170323//tmp/chroot-functions.sh from the chroot
--- Running action sequence: build_kernel
Copying pre-kmerge.sh to /tmp
copying pre-kmerge.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170323//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170323//tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170323/
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot genkernel
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-kernel/genkernel-3.4.52.4-r2
>>> Emerging (1 of 2) app-arch/cpio-2.12-r1::gentoo
>>> Installing (1 of 2) app-arch/cpio-2.12-r1::gentoo
>>> Emerging (2 of 2) sys-kernel/genkernel-3.4.52.4-r2::gentoo
>>> Installing (2 of 2) sys-kernel/genkernel-3.4.52.4-r2::gentoo
* Messages for package sys-kernel/genkernel-3.4.52.4-r2:
* Documentation is available in the genkernel manual page
* as well as the following URL:
* https://www.gentoo.org/doc/en/genkernel.xml
* This package is known to not work with reiser4. If you are running
* reiser4 and have a problem, do not file a bug. We know it does not
* work and we don't plan on fixing it since reiser4 is the one that is
* broken in this regard. Try using a sane filesystem like ext4.
* The LUKS support has changed from versions prior to 3.4.4. Now,
* you use crypt_root=/dev/blah instead of real_root=luks:/dev/blah.
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170323//tmp/pre-kmerge.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170323//tmp/chroot-functions.sh from the chroot
Copying kmerge.sh to /tmp
copying kmerge.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170323//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170323//tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170323/
>>> Regenerating /etc/ld.so.cache...
Genkernel version 3.4.52.4 found ... continuing
emerge --quiet --usepkg --buildpkg --newuse hardened-sources
>>> Verifying ebuild manifests
* IMPORTANT: 11 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
>>> Emerging (1 of 1) sys-kernel/hardened-sources-4.8.17-r2::gentoo
>>> Installing (1 of 1) sys-kernel/hardened-sources-4.8.17-r2::gentoo
>>> Recording sys-kernel/hardened-sources in "world" favorites file...
* Messages for package sys-kernel/hardened-sources-4.8.17-r2:
* If you are upgrading from a previous kernel, you may be interested
* in the following document:
* - General upgrade guide: https://wiki.gentoo.org/wiki/Kernel/Upgrade
*
* Users of grsecurity's RBAC system must ensure they are using
* sys-apps/gradm-3.1*, which is compatible with hardened-sources-4.8.17-r2.
* It is strongly recommended that the following command is issued
* prior to booting a hardened-sources-4.8.17-r2 kernel for the first time:
*
* emerge -na =sys-apps/gradm-3.1*
*
* IMPORTANT: 12 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
Setting extraversion to openstack
^[[32;01m*^[[32;01m Gentoo Linux Genkernel; Version 3.4.52.4^[[0m
^[[32;01m*^[[0m Running with options: --all-ramdisk-modules --cachedir=/tmp/kerncache/gentoo-genkernel_cache-hardened+cloud-nomultilib-20170323 --no-mountboot --kerneldir=/usr/src/linux --modulespackage=/tmp/kerncache/gentoo-modules-hardened+cloud-nomultilib-20170323.tar.bz2 --minkernpackage=/tmp/kerncache/gentoo-kernel-initrd-hardened+cloud-nomultilib-20170323.tar.bz2 all --kernel-config=/var/tmp/gentoo.config
^[[32;01m*^[[0m Using genkernel.conf from /etc/genkernel.conf
^[[32;01m*^[[0m Sourcing arch-specific config.sh from /usr/share/genkernel/arch/x86_64/config.sh ..
^[[32;01m*^[[0m Sourcing arch-specific modules_load from /usr/share/genkernel/arch/x86_64/modules_load ..
^[[32;01m*^[[0;01m Linux Kernel ^[[0;01m4.8.17-hardened-r2-openstack^[[0m for ^[[0;01mx86_64^[[0m...
^[[32;01m*^[[0m .. with config file /var/tmp/gentoo.config
^[[32;01m*^[[0m kernel: Using config from /var/tmp/gentoo.config
^[[32;01m*^[[0m kernel: >> Running mrproper...
^[[32;01m*^[[0m >> Running oldconfig...
^[[32;01m*^[[0m kernel: >> Cleaning...
^[[32;01m*^[[0m >> Compiling 4.8.17-hardened-r2-openstack bzImage...
Full build log at /release/tmp/run/catalyst-auto.20170323.1vpenk/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-03-01 3:47 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-03-01 3:47 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
01 Mar 2017 03:47:26 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
01 Mar 2017 03:47:26 UTC: NOTICE : Processing spec file: hardened/stage4-nomultilib-cloud.spec
01 Mar 2017 03:47:26 UTC: NOTICE : Using target: stage4
01 Mar 2017 03:47:26 UTC: NOTICE : Source file specification matching setting is: loose
01 Mar 2017 03:47:26 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
01 Mar 2017 03:47:26 UTC: ERROR : CatalystError: File Not Found: /home/release/buildroot/amd64-dev/snapshots/portage-20170206
Command exited with non-zero status 2
0.15user 0.01system 0:00.28elapsed 56%CPU (0avgtext+0avgdata 14872maxresident)k
8inputs+8outputs (0major+7220minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20170206.RiXK15/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-03-01 3:47 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-03-01 3:47 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
01 Mar 2017 03:47:27 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
01 Mar 2017 03:47:27 UTC: NOTICE : Processing spec file: hardened/stage4-nomultilib-cloud.spec
01 Mar 2017 03:47:27 UTC: NOTICE : Using target: stage4
01 Mar 2017 03:47:27 UTC: NOTICE : Source file specification matching setting is: loose
01 Mar 2017 03:47:27 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
01 Mar 2017 03:47:27 UTC: ERROR : CatalystError: File Not Found: /home/release/buildroot/amd64-dev/snapshots/portage-20170130
Command exited with non-zero status 2
0.13user 0.02system 0:00.19elapsed 78%CPU (0avgtext+0avgdata 14864maxresident)k
8inputs+8outputs (0major+7152minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20170130.GAEpMk/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-03-01 3:47 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-03-01 3:47 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
01 Mar 2017 03:47:24 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
01 Mar 2017 03:47:24 UTC: NOTICE : Processing spec file: hardened/stage4-nomultilib-cloud.spec
01 Mar 2017 03:47:24 UTC: NOTICE : Using target: stage4
01 Mar 2017 03:47:24 UTC: NOTICE : Source file specification matching setting is: loose
01 Mar 2017 03:47:24 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
01 Mar 2017 03:47:24 UTC: ERROR : CatalystError: File Not Found: /home/release/buildroot/amd64-dev/snapshots/portage-20170220
Command exited with non-zero status 2
0.17user 0.00system 0:00.31elapsed 54%CPU (0avgtext+0avgdata 14844maxresident)k
8inputs+8outputs (0major+7216minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20170220.EFjx1c/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2017-03-01 3:47 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2017-03-01 3:47 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
01 Mar 2017 03:47:24 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
01 Mar 2017 03:47:24 UTC: NOTICE : Processing spec file: hardened/stage4-nomultilib-cloud.spec
01 Mar 2017 03:47:24 UTC: NOTICE : Using target: stage4
01 Mar 2017 03:47:24 UTC: NOTICE : Source file specification matching setting is: loose
01 Mar 2017 03:47:24 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
01 Mar 2017 03:47:24 UTC: ERROR : CatalystError: File Not Found: /home/release/buildroot/amd64-dev/snapshots/portage-20170213
Command exited with non-zero status 2
0.14user 0.02system 0:00.18elapsed 86%CPU (0avgtext+0avgdata 14980maxresident)k
8inputs+8outputs (0major+7289minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20170213.X83Cxb/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2016-08-18 17:07 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2016-08-18 17:07 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
Catalyst, version 2.0.19
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+nomultilib-latest.tar.bz2
Caching snapshot to /release/tmp/snapshots/20160818/
The autoresume path is /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-nomultilib-20160818/
Location of the package cache is /release/buildroot/amd64-dev/packages/hardened/stage4-amd64-hardened+cloud-nomultilib-20160818/
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-nomultilib-20160818/
>>> 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-nomultilib-20160818/
clearing chroot ...
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160818/
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-nomultilib-20160818/
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160818/
Starting tar extract from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.bz2
to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160818/ (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-nomultilib-20160818//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160818//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-nomultilib-20160818/
>>> Regenerating /etc/ld.so.cache...
Updating portage with USE=""
emerge --quiet --usepkg --buildpkg --newuse --oneshot --update --newuse sys-apps/portage
Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)
Bringing system up to date using profile specific use flags
emerge --quiet --usepkg --buildpkg --newuse -u @system
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-apps/openrc-0.21.3::gentoo
>>> Failed to emerge sys-apps/openrc-0.21.3, Log file:
>>> '/var/tmp/portage/sys-apps/openrc-0.21.3/temp/build.log'
* Package: sys-apps/openrc-0.21.3
* Repository: gentoo
* Maintainer: openrc@gentoo.org
* USE: abi_x86_64 amd64 elibc_glibc kernel_linux ncurses netifrc pam unicode userland_GNU
* FEATURES: preserve-libs sandbox userpriv usersandbox
/usr/bin/install: cannot change permissions of '/var/tmp/portage/sys-apps/openrc-0.21.3/work': No such file or directory
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* ERROR: sys-apps/openrc-0.21.3::gentoo failed (unpack phase):
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* Failed to create dir '/var/tmp/portage/sys-apps/openrc-0.21.3/work'
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
*
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* Call stack:
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* ebuild.sh, line 780: Called __ebuild_main 'unpack'
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* phase-functions.sh, line 1005: Called __dyn_unpack
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* phase-functions.sh, line 240: Called die
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* The specific snippet of code:
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* install -m${PORTAGE_WORKDIR_MODE:-0700} -d "${WORKDIR}" || die "Failed to create dir '${WORKDIR}'"
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
*
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* If you need support, post the output of `emerge --info '=sys-apps/openrc-0.21.3::gentoo'`,
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* the complete build log and the output of `emerge -pqv '=sys-apps/openrc-0.21.3::gentoo'`.
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* The complete build log is located at '/var/tmp/portage/sys-apps/openrc-0.21.3/temp/build.log'.
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/openrc-0.21.3/temp/environment'.
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* Working directory: '/usr/lib64/python3.4/site-packages'
/usr/lib/portage/python3.4/isolated-functions.sh: line 264: echo: write error: No space left on device
* S: '/var/tmp/portage/sys-apps/openrc-0.21.3/work/openrc-0.21.3'
!!! 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-nomultilib-20160818/.catalyst_lock'
Command exited with non-zero status 1
35.53user 6.51system 0:25.15elapsed 167%CPU (0avgtext+0avgdata 735456maxresident)k
1800inputs+1752312outputs (1major+453538minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20160818.Cog4eh/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2016-07-30 13:09 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2016-07-30 13:09 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
30 Jul 2016 13:08:45 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
30 Jul 2016 13:08:45 UTC: NOTICE : Processing spec file: hardened/stage4-nomultilib-cloud.spec
30 Jul 2016 13:08:45 UTC: NOTICE : Using target: stage4
30 Jul 2016 13:08:45 UTC: NOTICE : Source file specification matching setting is: loose
30 Jul 2016 13:08:45 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
30 Jul 2016 13:08:46 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.xz
>>> Waiting 10 seconds before starting...
>>> (Control-C to abort)...
Purging Caches ... in: 10 9 8 7 6 5 4 3 2 1
30 Jul 2016 13:08:56 UTC: NOTICE : purge(); clearing autoresume ...
30 Jul 2016 13:08:58 UTC: NOTICE : purge(); clearing chroot ...
30 Jul 2016 13:08:58 UTC: NOTICE : Clearing the chroot path ...
30 Jul 2016 13:08:58 UTC: NOTICE : purge(); clearing package cache ...
30 Jul 2016 13:08:58 UTC: NOTICE : purging the pkgcache ...
30 Jul 2016 13:08:58 UTC: NOTICE : purge(); clearing kerncache ...
30 Jul 2016 13:08:58 UTC: NOTICE : --- Running action sequence: unpack
30 Jul 2016 13:08:58 UTC: NOTICE : Clearing the chroot path ...
30 Jul 2016 13:08:58 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.xz
30 Jul 2016 13:08:58 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160730 (this may take some time) ..
Index and archive differ as to next file: ./var/tmp/.keep vs ./var/tmp/portage/._unmerge_/
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
30 Jul 2016 13:08:59 UTC: ERROR : 'pixz' extraction of /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.xz to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160730 failed.
30 Jul 2016 13:08:59 UTC: NOTICE : --- Running action sequence: unpack_snapshot
30 Jul 2016 13:08:59 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
30 Jul 2016 13:09:08 UTC: NOTICE : --- Running action sequence: config_profile_link
30 Jul 2016 13:09:08 UTC: NOTICE : --- Running action sequence: setup_confdir
30 Jul 2016 13:09:08 UTC: NOTICE : --- Running action sequence: portage_overlay
30 Jul 2016 13:09:08 UTC: NOTICE : --- Running action sequence: bind
30 Jul 2016 13:09:08 UTC: NOTICE : --- Running action sequence: chroot_setup
30 Jul 2016 13:09:08 UTC: NOTICE : Setting up chroot...
30 Jul 2016 13:09:08 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
30 Jul 2016 13:09:08 UTC: WARNING : If your build fails look here first as the possible problem.
30 Jul 2016 13:09:08 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
30 Jul 2016 13:09:08 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
30 Jul 2016 13:09:08 UTC: WARNING : You have been warned.
30 Jul 2016 13:09:08 UTC: NOTICE : --- Running action sequence: setup_environment
30 Jul 2016 13:09:08 UTC: NOTICE : --- Running action sequence: build_packages
Copying stage4-chroot.sh to /tmp
copying stage4-chroot.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160730/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160730/tmp
Ensure the file has the executable bit set
Running stage4-chroot.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160730 /tmp/stage4-chroot.sh
/tmp/chroot-functions.sh: line 4: eselect: command not found
emerge --quiet --usepkg --buildpkg --newuse --oneshot --update --newuse sys-apps/portage
/tmp/chroot-functions.sh: line 297: emerge: command not found
30 Jul 2016 13:09:08 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'build_packages', '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']) exited 1
30 Jul 2016 13:09:09 UTC: ERROR : CatalystError: stage4build aborting due to error.
30 Jul 2016 13:09:09 UTC: ERROR : Exception running action sequence build_packages
Traceback (most recent call last):
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1487, in build_packages
cmd(command, 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/stage4/stage4-controller.sh', 'build_packages', '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']) 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 1393, in run
getattr(self, x)()
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1493, in build_packages
"build aborting due to error.")
catalyst.support.CatalystError: stage4build aborting due to error.
30 Jul 2016 13:09:09 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
16.01user 4.90system 0:23.65elapsed 88%CPU (0avgtext+0avgdata 257072maxresident)k
1824inputs+1944216outputs (0major+135295minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20160730.bDBA8N/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2016-07-25 3:14 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2016-07-25 3:14 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
25 Jul 2016 03:13:26 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
25 Jul 2016 03:13:26 UTC: NOTICE : Processing spec file: hardened/stage4-nomultilib-cloud.spec
25 Jul 2016 03:13:26 UTC: NOTICE : Using target: stage4
25 Jul 2016 03:13:26 UTC: NOTICE : Source file specification matching setting is: loose
25 Jul 2016 03:13:26 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
25 Jul 2016 03:13:26 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.xz
25 Jul 2016 03:13:26 UTC: NOTICE : purge(); clearing autoresume ...
25 Jul 2016 03:13:26 UTC: NOTICE : purge(); clearing chroot ...
25 Jul 2016 03:13:26 UTC: NOTICE : Clearing the chroot path ...
25 Jul 2016 03:13:26 UTC: NOTICE : purge(); clearing package cache ...
25 Jul 2016 03:13:26 UTC: NOTICE : purging the pkgcache ...
25 Jul 2016 03:13:26 UTC: NOTICE : purge(); clearing kerncache ...
25 Jul 2016 03:13:26 UTC: NOTICE : --- Running action sequence: unpack
25 Jul 2016 03:13:26 UTC: NOTICE : Clearing the chroot path ...
25 Jul 2016 03:13:26 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.xz
25 Jul 2016 03:13:26 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160725 (this may take some time) ..
Index and archive differ as to next file: ./var/tmp/.keep vs ./var/tmp/portage/._unmerge_/
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
25 Jul 2016 03:13:27 UTC: ERROR : 'pixz' extraction of /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.xz to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160725 failed.
25 Jul 2016 03:13:27 UTC: NOTICE : --- Running action sequence: unpack_snapshot
25 Jul 2016 03:13:27 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
25 Jul 2016 03:14:30 UTC: NOTICE : --- Running action sequence: config_profile_link
25 Jul 2016 03:14:30 UTC: NOTICE : --- Running action sequence: setup_confdir
25 Jul 2016 03:14:30 UTC: NOTICE : --- Running action sequence: portage_overlay
25 Jul 2016 03:14:30 UTC: NOTICE : --- Running action sequence: bind
25 Jul 2016 03:14:30 UTC: NOTICE : --- Running action sequence: chroot_setup
25 Jul 2016 03:14:30 UTC: NOTICE : Setting up chroot...
25 Jul 2016 03:14:30 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
25 Jul 2016 03:14:30 UTC: WARNING : If your build fails look here first as the possible problem.
25 Jul 2016 03:14:30 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
25 Jul 2016 03:14:30 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
25 Jul 2016 03:14:30 UTC: WARNING : You have been warned.
25 Jul 2016 03:14:30 UTC: NOTICE : --- Running action sequence: setup_environment
25 Jul 2016 03:14:30 UTC: NOTICE : --- Running action sequence: build_packages
Copying stage4-chroot.sh to /tmp
copying stage4-chroot.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160725/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160725/tmp
Ensure the file has the executable bit set
Running stage4-chroot.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160725 /tmp/stage4-chroot.sh
/tmp/chroot-functions.sh: line 4: eselect: command not found
emerge --quiet --usepkg --buildpkg --newuse --oneshot --update --newuse sys-apps/portage
/tmp/chroot-functions.sh: line 297: emerge: command not found
25 Jul 2016 03:14:31 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'build_packages', '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']) exited 1
25 Jul 2016 03:14:31 UTC: ERROR : CatalystError: stage4build aborting due to error.
25 Jul 2016 03:14:31 UTC: ERROR : Exception running action sequence build_packages
Traceback (most recent call last):
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1487, in build_packages
cmd(command, 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/stage4/stage4-controller.sh', 'build_packages', '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']) 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 1393, in run
getattr(self, x)()
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1493, in build_packages
"build aborting due to error.")
catalyst.support.CatalystError: stage4build aborting due to error.
25 Jul 2016 03:14:31 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
15.56user 4.99system 1:05.36elapsed 31%CPU (0avgtext+0avgdata 299456maxresident)k
2696inputs+1945872outputs (0major+156231minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20160725.vBvLUx/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2016-07-11 20:17 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2016-07-11 20:17 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
11 Jul 2016 20:17:37 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
11 Jul 2016 20:17:37 UTC: NOTICE : Processing spec file: hardened/stage4-nomultilib-cloud.spec
11 Jul 2016 20:17:37 UTC: NOTICE : Using target: stage4
11 Jul 2016 20:17:37 UTC: NOTICE : Source file specification matching setting is: loose
11 Jul 2016 20:17:37 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
11 Jul 2016 20:17:38 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.xz
11 Jul 2016 20:17:38 UTC: NOTICE : purge(); clearing autoresume ...
11 Jul 2016 20:17:38 UTC: NOTICE : purge(); clearing chroot ...
11 Jul 2016 20:17:38 UTC: NOTICE : Clearing the chroot path ...
11 Jul 2016 20:17:38 UTC: NOTICE : purge(); clearing package cache ...
11 Jul 2016 20:17:38 UTC: NOTICE : purging the pkgcache ...
11 Jul 2016 20:17:38 UTC: NOTICE : purge(); clearing kerncache ...
11 Jul 2016 20:17:38 UTC: NOTICE : --- Running action sequence: unpack
11 Jul 2016 20:17:38 UTC: NOTICE : Clearing the chroot path ...
11 Jul 2016 20:17:38 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.xz
11 Jul 2016 20:17:38 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160711 (this may take some time) ..
tar: ./home/release/tmp/logs/sys-libs:glibc-2.22-r4:20160704-214318.log: Wrote only 3072 of 10240 bytes
tar: ./home/release/tmp/logs/sys-apps\:gawk-4.1.3\:20160704-220338.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/sys-devel\:patch-2.7.5\:20160704-213329.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/sys-libs\:gdbm-1.11\:20160704-212337.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/sys-kernel\:linux-headers-4.3\:20160704-213404.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/sys-apps\:portage-2.2.28\:20160704-212948.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/sys-fs\:eudev-3.1.5\:20160704-212059.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/app-portage\:portage-utils-0.62\:20160704-223117.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/sys-process\:procps-3.3.11-r3\:20160704-213123.log: Cannot write: No space left on device
tar: ./home/release/tmp/logs/dev-lang\:python-2.7.10-r1\:20160704-211851.log: Cannot open: No space left on device
tar: ./home/release/tmp/logs/virtual\:pam-0-r1\:20160704-223239.log: Cannot open: No space left on device
tar: ./home/release/tmp/logs/sys-apps\:sandbox-2.10-r1\:20160704-213530.log: Cannot open: No space left on device
tar: ./home/release/tmp/logs/sys-apps\:kmod-22\:20160704-213022.log: Cannot open: No space left on device
tar: ./home/release/tmp/logs/perl-core\:Data-Dumper-2.154.0\:20160704-214235.log: Cannot open: No space left on device
tar: ./home/release/tmp/logs/perl-core\:CPAN-Meta-2.150.1\:20160704-214300.log: Cannot open: No space left on device
tar: ./home/release/tmp/logs/dev-libs\:libpipeline-1.4.0\:20160704-213054.log: Cannot open: No space left on device
tar: ./home/release/tmp/logs/dev-perl\:libintl-perl-1.240.0\:20160704-211134.log: Cannot open: No space left on device
tar: ./home/release/tmp/logs/sys-libs\:zlib-1.2.8-r1\:20160704-212128.log: Cannot open: No space left on device
tar: ./home/release/tmp/logs/sys-devel\:gcc-config-1.7.3\:20160704-212412.log: Cannot open: No space left on device
tar: ./home/release/tmp/logs/virtual\:package-manager-0\:20160704-212957.log: Cannot open: No space left on device
tar: ./home/release/tmp/logs/perl-core\:File-Temp-0.230.400-r1\:20160704-214245.log: Cannot open: No space left on device
tar: ./home/release/tmp/logs/virtual\:perl-Text-ParseWords-3.290.0-r1\:20160704-213240.log: Cannot open: No space left on device
tar: ./home/release/tmp/logs/virtual\:acl-0-r2\:20160704-215049.log: --- Logging error ---
Traceback (most recent call last):
File "/usr/lib64/python3.4/logging/__init__.py", line 982, in emit
self.flush()
File "/usr/lib64/python3.4/logging/__init__.py", line 962, in flush
self.stream.flush()
OSError: [Errno 28] No space left on device
Call stack:
File "/usr/lib/python-exec/python3.4/catalyst", line 37, in <module>
main(sys.argv[1:])
File "/usr/lib64/python3.4/site-packages/catalyst/main.py", line 276, in main
return _main(parser, opts)
File "/usr/lib64/python3.4/site-packages/catalyst/main.py", line 426, in _main
success = build_target(addlargs)
File "/usr/lib64/python3.4/site-packages/catalyst/main.py", line 113, in build_target
return target.run()
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1393, in run
getattr(self, x)()
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 786, in unpack
log.error('%s', error_msg % unpack_info)
File "/usr/lib64/python3.4/logging/__init__.py", line 1303, in error
self._log(ERROR, msg, args, **kwargs)
File "/usr/lib64/python3.4/site-packages/catalyst/log.py", line 29, in _log
super(CatalystLogger, self)._log(level, line, (), **kwargs)
Message: "'pixz' extraction of /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.xz to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160711 failed."
Arguments: ()
--- Logging error ---
OSError: [Errno 28] No space left on device
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 1393, in run
getattr(self, x)()
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 790, in unpack
data=self.settings["source_path_hash"])
File "/usr/lib64/python3.4/site-packages/catalyst/base/resume.py", line 56, in enable
myf.write(data)
OSError: [Errno 28] No space left on device
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib64/python3.4/logging/__init__.py", line 982, in emit
self.flush()
File "/usr/lib64/python3.4/logging/__init__.py", line 962, in flush
self.stream.flush()
OSError: [Errno 28] No space left on device
Call stack:
File "/usr/lib/python-exec/python3.4/catalyst", line 37, in <module>
main(sys.argv[1:])
File "/usr/lib64/python3.4/site-packages/catalyst/main.py", line 276, in main
return _main(parser, opts)
File "/usr/lib64/python3.4/site-packages/catalyst/main.py", line 426, in _main
success = build_target(addlargs)
File "/usr/lib64/python3.4/site-packages/catalyst/main.py", line 113, in build_target
return target.run()
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1399, in run
log.error('Exception running action sequence %s', x, exc_info=True)
File "/usr/lib64/python3.4/logging/__init__.py", line 1303, in error
self._log(ERROR, msg, args, **kwargs)
File "/usr/lib64/python3.4/site-packages/catalyst/log.py", line 29, in _log
super(CatalystLogger, self)._log(level, line, (), **kwargs)
Message: 'Exception running action sequence unpack'
Arguments: ()
--- Logging error ---
Traceback (most recent call last):
File "/usr/lib64/python3.4/logging/__init__.py", line 982, in emit
self.flush()
File "/usr/lib64/python3.4/logging/__init__.py", line 962, in flush
self.stream.flush()
OSError: [Errno 28] No space left on device
Call stack:
File "/usr/lib/python-exec/python3.4/catalyst", line 37, in <module>
main(sys.argv[1:])
File "/usr/lib64/python3.4/site-packages/catalyst/main.py", line 276, in main
return _main(parser, opts)
File "/usr/lib64/python3.4/site-packages/catalyst/main.py", line 426, in _main
success = build_target(addlargs)
File "/usr/lib64/python3.4/site-packages/catalyst/main.py", line 113, in build_target
return target.run()
File "/usr/lib64/python3.4/site-packages/catalyst/bas
Full build log at /home/release/tmp/run/catalyst-auto.20160711.DyCHCJ/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2016-05-30 3:00 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2016-05-30 3:00 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
/home/release/releng/tools/catalyst-auto: line 82: time: command not found
Full build log at /home/release/tmp/run/catalyst-auto.20160530.6Arzog/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2016-04-30 13:17 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2016-04-30 13:17 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
/release/releng/tools/catalyst-auto: line 80: time: command not found
Full build log at /release/tmp/run/catalyst-auto.ItNQOv/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2016-01-26 3:16 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2016-01-26 3:16 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
>>> Installing (34 of 64) sys-process/cronie-1.5.0::gentoo
>>> Recording sys-process/cronie in "world" favorites file...
>>> Emerging (35 of 64) media-libs/freetype-2.5.5::gentoo
>>> Installing (35 of 64) media-libs/freetype-2.5.5::gentoo
>>> Emerging (36 of 64) dev-python/configobj-5.0.5::gentoo
>>> Installing (36 of 64) dev-python/configobj-5.0.5::gentoo
>>> Emerging (37 of 64) dev-python/cheetah-2.4.4-r1::gentoo
>>> Installing (37 of 64) dev-python/cheetah-2.4.4-r1::gentoo
>>> Emerging (38 of 64) dev-python/jsonpatch-1.9::gentoo
>>> Installing (38 of 64) dev-python/jsonpatch-1.9::gentoo
>>> Emerging (39 of 64) dev-python/jinja-2.7.3::gentoo
>>> Installing (39 of 64) dev-python/jinja-2.7.3::gentoo
>>> Emerging (40 of 64) dev-python/pycparser-2.14::gentoo
>>> Installing (40 of 64) dev-python/pycparser-2.14::gentoo
>>> Emerging (41 of 64) sys-devel/autogen-5.18.1::gentoo
>>> Installing (41 of 64) sys-devel/autogen-5.18.1::gentoo
>>> Emerging (42 of 64) dev-libs/libtasn1-4.5::gentoo
>>> Installing (42 of 64) dev-libs/libtasn1-4.5::gentoo
>>> Emerging (43 of 64) virtual/python-ipaddress-1.0::gentoo
>>> Installing (43 of 64) virtual/python-ipaddress-1.0::gentoo
>>> Emerging (44 of 64) net-misc/dhcpcd-6.10.0::gentoo
>>> Installing (44 of 64) net-misc/dhcpcd-6.10.0::gentoo
>>> Recording net-misc/dhcpcd in "world" favorites file...
>>> Emerging (45 of 64) sys-apps/pciutils-3.3.1::gentoo
>>> Installing (45 of 64) sys-apps/pciutils-3.3.1::gentoo
>>> Recording sys-apps/pciutils in "world" favorites file...
>>> Emerging (46 of 64) sys-block/parted-3.2::gentoo
>>> Installing (46 of 64) sys-block/parted-3.2::gentoo
>>> Recording sys-block/parted in "world" favorites file...
>>> Emerging (47 of 64) sys-power/acpid-2.0.23::gentoo
>>> Installing (47 of 64) sys-power/acpid-2.0.23::gentoo
>>> Recording sys-power/acpid in "world" favorites file...
>>> Emerging (48 of 64) virtual/logger-0::gentoo
>>> Installing (48 of 64) virtual/logger-0::gentoo
>>> Emerging (49 of 64) dev-python/cffi-1.2.1::gentoo
>>> Installing (49 of 64) dev-python/cffi-1.2.1::gentoo
>>> Emerging (50 of 64) virtual/cron-0-r1::gentoo
>>> Installing (50 of 64) virtual/cron-0-r1::gentoo
>>> Emerging (51 of 64) net-libs/gnutls-3.3.17.1::gentoo
>>> Installing (51 of 64) net-libs/gnutls-3.3.17.1::gentoo
>>> Emerging (52 of 64) sys-boot/grub-2.02_beta2-r8::gentoo
>>> Installing (52 of 64) sys-boot/grub-2.02_beta2-r8::gentoo
>>> Recording sys-boot/grub in "world" favorites file...
>>> Emerging (53 of 64) dev-python/cryptography-1.0.2::gentoo
>>> Installing (53 of 64) dev-python/cryptography-1.0.2::gentoo
>>> Emerging (54 of 64) mail-mta/nullmailer-1.13-r5::gentoo
>>> Installing (54 of 64) mail-mta/nullmailer-1.13-r5::gentoo
>>> Emerging (55 of 64) app-admin/logrotate-3.9.1-r1::gentoo
>>> Installing (55 of 64) app-admin/logrotate-3.9.1-r1::gentoo
>>> Recording app-admin/logrotate in "world" favorites file...
>>> Emerging (56 of 64) dev-python/pyopenssl-0.15.1-r1::gentoo
>>> Installing (56 of 64) dev-python/pyopenssl-0.15.1-r1::gentoo
>>> Emerging (57 of 64) virtual/mta-1::gentoo
>>> Installing (57 of 64) virtual/mta-1::gentoo
>>> Emerging (58 of 64) dev-python/ndg-httpsclient-0.4.0::gentoo
>>> Installing (58 of 64) dev-python/ndg-httpsclient-0.4.0::gentoo
>>> Emerging (59 of 64) dev-python/requests-2.8.1::gentoo
>>> Installing (59 of 64) dev-python/requests-2.8.1::gentoo
>>> Emerging (60 of 64) app-emulation/cloud-init-0.7.6-r1::gentoo
>>> Installing (60 of 64) app-emulation/cloud-init-0.7.6-r1::gentoo
>>> Recording app-emulation/cloud-init in "world" favorites file...
>>> Emerging (61 of 64) app-editors/vim-core-7.4.769::gentoo
>>> Failed to emerge app-editors/vim-core-7.4.769, Log file:
>>> '/home/release/tmp/logs/app-editors:vim-core-7.4.769:20160126-031623.log'
--2016-01-26 03:16:23-- http://distfiles.gentoo.org/distfiles/vim-7.4.769.tar.gz
Resolving distfiles.gentoo.org... 64.50.236.52, 156.56.247.195, 137.226.34.46, ...
Connecting to distfiles.gentoo.org|64.50.236.52|:80... connected.
HTTP request sent, awaiting response... 416 Requested Range Not Satisfiable
The file is already fully retrieved; nothing to do.
!!! Fetched file: vim-7.4.769.tar.gz VERIFY FAILED!
!!! Reason: Filesize does not match recorded size
!!! Got: 12189043
!!! Expected: 12189506
Refetching... File renamed to '/usr/portage/distfiles/vim-7.4.769.tar.gz._checksum_failure_.2P_kRq'
--2016-01-26 03:16:23-- https://github.com/vim/vim/archive/v7-4-769.tar.gz
Resolving github.com... 192.30.252.129
Connecting to github.com|192.30.252.129|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/vim/vim/tar.gz/v7-4-769 [following]
--2016-01-26 03:16:23-- https://codeload.github.com/vim/vim/tar.gz/v7-4-769
Resolving codeload.github.com... 192.30.252.163
Connecting to codeload.github.com|192.30.252.163|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2016-01-26 03:16:24 ERROR 404: Not Found.
!!! Couldn't download 'vim-7.4.769.tar.gz'. Aborting.
* Fetch failed for 'app-editors/vim-core-7.4.769', Log file:
* '/home/release/tmp/logs/app-editors:vim-core-7.4.769:20160126-031623.log'
* Messages for package sys-power/acpid-2.0.23:
* 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-boot/grub-2.02_beta2-r8:
* To avoid automounting and auto(un)installing with /boot,
* just export the DONT_MOUNT_BOOT variable.
* Messages for package app-portage/gentoolkit-0.3.0.9-r2:
*
* For further information on gentoolkit, please read the gentoolkit
* guide: https://www.gentoo.org/doc/en/gentoolkit.xml
*
* Another alternative to equery is app-portage/portage-utils
*
* Additional tools that may be of interest:
*
* app-admin/eclean-kernel
* app-portage/diffmask
* app-portage/flaggie
* app-portage/install-mask
* app-portage/portpeek
* app-portage/smart-live-rebuild
* Messages for package dev-util/ctags-5.8:
* You can set the version to be started by /usr/bin/ctags through
* the ctags eselect module. "man ctags.eselect" for details.
* Messages for package app-admin/syslog-ng-3.7.2:
* For detailed documentation please see the upstream website:
* http://www.balabit.com/sites/default/files/documents/syslog-ng-ose-3.7-guides/en/syslog-ng-ose-v3.7-guide-admin/html/index.html
* It is highly recommended that app-admin/logrotate be emerged to
* manage the log files. syslog-ng installs a file in /etc/logrotate.d
* for logrotate to use.
* Messages for package dev-python/jinja-2.7.3:
* For i18n support, please emerge dev-python/Babel.
* Messages for package net-misc/dhcpcd-6.10.0:
*
* dhcpcd has zeroconf support active by default.
* This means it will always obtain an IP address even if no
* DHCP server can be contacted, which will break any existing
* failover support you may have configured in your net configuration.
* This behaviour can be controlled with the noipv4ll configuration
* file option or the -L command line switch.
* See the dhcpcd and dhcpcd.conf man pages for more details.
*
* Dhcpcd has duid enabled by default, and this may cause issues
* with some dhcp servers. For more information, see
* https://bugs.gentoo.org/show_bug.cgi?id=477356
*
* If you activate the lookup-hostname hook to look up your hostname
* using the dns, you need to install net-dns/bind-tools.
* Messages for package sys-power/acpid-2.0.23:
*
* You may wish to read the Gentoo Linux Power Management Guide,
* which can be found online at:
* https://www.gentoo.org/doc/en/power-management-guide.xml
*
* Messages for package sys-boot/grub-2.02_beta2-r8:
* For information on how to configure GRUB2 please refer to the guide:
* https://wiki.gentoo.org/wiki/GRUB2_Quick_Start
*
* You may consider installing the following optional packages:
* sys-boot/os-prober for Detect other operating systems (grub-mkconfig)
* dev-libs/libisoburn for Create rescue media (grub-mkrescue)
* sys-fs/mdadm for Enable RAID device detection
* Messages for package mail-mta/nullmailer-1.13-r5:
* To create an initial setup, please do:
* emerge --config =mail-mta/nullmailer-1.13-r5
* Messages for package app-admin/logrotate-3.9.1-r1:
* If you wish to have logrotate e-mail you updates, please
* emerge virtual/mailx and configure logrotate in
* /etc/logrotate.conf appropriately
*
* Additionally, /etc/logrotate.conf may need to be modified
* for your particular needs. See man logrotate for details.
* Messages for package app-editors/vim-core-7.4.769:
* Fetch failed for 'app-editors/vim-core-7.4.769', Log file:
* '/home/release/tmp/logs/app-editors:vim-core-7.4.769:20160126-031623.log'
26 Jan 2016 03:16:26 UTC: ERROR : CatalystError: cmd() NON-zero return value from: Error in attempt to build packages
26 Jan 2016 03:16:26 UTC: ERROR : CatalystError: stage4build aborting due to error.
26 Jan 2016 03:16:26 UTC: ERROR : Exception running action sequence build_packages
Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/catalyst/base/stagebase.py", line 1413, in run
getattr(self, x)()
File "/usr/lib64/python2.7/site-packages/catalyst/base/stagebase.py", line 1524, in build_packages
"build aborting due to error.")
CatalystError
26 Jan 2016 03:16:26 UTC: NOTICE : Cleaning up... Running unbind()
Full build log at /home/release/tmp/run/catalyst-auto.AdiAKn/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2016-01-18 6:57 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2016-01-18 6:57 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
2015-07-25-python-targets
Title Python 3.4 enabled by default
Author Mike Gilbert <floppym@gentoo.org>
Posted 2015-07-25
Revision 1
Python 3.4 is now enabled by default, replacing Python 3.3 as the
default Python 3 interpreter.
PYTHON_TARGETS will be adjusted to contain python2_7 and python3_4 by
default via your profile.
PYTHON_SINGLE_TARGET will remain set to python2_7 by default.
If you have PYTHON_TARGETS set in make.conf, that setting will still be
respected. You may want to adjust this setting manually.
Once the changes have taken place, a world update should take care of
reinstalling any python libraries you have installed. You should also
switch your default python3 interpreter using eselect python.
For example:
eselect python set --python3 python3.4
emerge -uDv --changed-use @world
2015-08-13-openssh-weak-keys
Title OpenSSH 7.0 disables ssh-dss keys by default
Author Mike Frysinger <vapier@gentoo.org>
Posted 2015-08-13
Revision 1
Starting with the 7.0 release of OpenSSH, support for ssh-dss keys has
been disabled by default at runtime due to their inherit weakness. If
you rely on these key types, you will have to take corrective action or
risk being locked out.
Your best option is to generate new keys using strong algos such as rsa
or ecdsa or ed25519. RSA keys will give you the greatest portability
with other clients/servers while ed25519 will get you the best security
with OpenSSH (but requires recent versions of client & server).
If you are stuck with DSA keys, you can re-enable support locally by
updating your sshd_config and ~/.ssh/config files with lines like so:
PubkeyAcceptedKeyTypes=+ssh-dss
Be aware though that eventually OpenSSH will drop support for DSA keys
entirely, so this is only a stop gap solution.
More details can be found on OpenSSH's website:
http://www.openssh.com/legacy.html
2015-10-21-future-support-of-hardened-sources-kernel
Title Future Support of hardened-sources Kernel
Author Anthony G. Basile <blueness@gentoo.org>
Posted 2015-10-21
Revision 3
For many years, the Grsecurity team [1] has been supporting two versions of
their security patches against the Linux kernel, a stable and a testing
version, and Gentoo has made both of these available to our users through the
hardened-sources package. However, on August 26 of this year, the team
announced they would no longer be making the stable version publicly
available, citing trademark infringement by a major embedded systems company
as the reason. [2] The stable patches are now only available to sponsors of
Grsecurity and can no longer be distributed in Gentoo. However, the team did
assure us that they would continue to release and support the testing version
as they have in the past.
What does this means for users of hardened-sources? Gentoo will continue to
make the testing version available through our hardened-sources package but we
will have to drop support for the 3.x series. In a few days, those ebuilds
will be removed from the tree and you will be required to upgrade to a 4.x
series kernel. Since the hardened-sources package only installs the kernel
source tree, you can continue using a currently built 3.x series kernel but
bear in mind that we cannot support you, nor will upstream. Also keep in mind
that the 4.x series will not be as reliable as the 3.x series was, so
reporting bugs promptly will be even more important. Gentoo will continue to
work closely with upstream to stay on top of any problems, but be prepared for
the occasional "bad" kernel. The more reporting we receive from our users,
the better we will be able to decide which hardened-sources kernels to mark
stable and which to drop.
Refs.
[1] https://grsecurity.net
[2] https://grsecurity.net/announce.php
2016-01-08-some-dhcpcd-hooks-are-now-examples
Title Some dhcpcd hooks are now examples
Author William Hubbs <williamh@gentoo.org>
Posted 2016-01-08
Revision 2
In dhcpcd-6.10.0, the following hooks are no longer installed in
/lib/dhcpcd/dhcpcd-hooks by default:
10-wpa_supplicant
15-timezone
29-lookup-hostname
These are now installed in /usr/share/dhcpcd/hooks, which is an example
directory.
If you were using these hooks before you upgrade to 6.10.0, you will
need to copy them back to the /lib/dhcpcd/dhcpcd-hooks directory after the
upgrade.
>>> Building file list for distfiles cleaning...
>>> Cleaning distfiles...
[ 1.0 M ] LVM2.2.02.88.tgz
[ 119.7 K ] MAKEDEV-3.23-1.tar.gz
[ 2.1 M ] busybox-1.20.2.tar.bz2
[ 994.6 K ] cpio-2.11.tar.bz2
[ 227.3 K ] dmraid-1.0.0.rc16-3.tar.bz2
[ 493.5 K ] fuse-2.8.6.tar.gz
[ 276.3 K ] genkernel-3.4.52.3.tar.xz
[ 6.2 K ] gentoo-headers-4.3-1.tar.xz
[ 3.7 M ] gentoo-headers-base-4.3.tar.xz
[ 3.2 M ] gnupg-1.4.11.tar.bz2
[ 285.8 K ] mdadm-3.1.5.tar.bz2
[ 1.8 M ] nano-2.4.3.tar.gz
[ 879.0 K ] open-iscsi-2.0-872.tar.gz
[ 21.9 K ] openssh-7.1p2-hpnssh14v10.tar.xz
[ 1.4 M ] openssh-7.1p2.tar.gz
[ 407.3 K ] sandbox-2.10.tar.xz
[ 29.7 K ] unionfs-fuse-0.24.tar.bz2
===========
[ 16.9 M ] Total space from 17 files were freed in the distfiles directory
passwd: password expiry information changed.
passwd: password expiry information changed.
removing /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160118/tmp/cloud-prep.sh from the chroot
removing /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160118/tmp/chroot-functions.sh from the chroot
18 Jan 2016 06:56:59 UTC: NOTICE : --- Running action sequence: preclean
Copying stage4-preclean-chroot.sh to /tmp
copying stage4-preclean-chroot.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160118/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160118/tmp
Ensure the file has the executable bit set
Running stage4-preclean-chroot.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160118 /tmp/stage4-preclean-chroot.sh
>>> Regenerating /etc/ld.so.cache...
Skipping depclean operation for stage4
Skipping removal of world file for stage4
removing /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160118/tmp/stage4-preclean-chroot.sh from the chroot
removing /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160118/tmp/chroot-functions.sh from the chroot
18 Jan 2016 06:57:00 UTC: NOTICE : --- Running action sequence: rcupdate
Copying rc-update.sh to /tmp
copying rc-update.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160118/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160118/tmp
Ensure the file has the executable bit set
Running rc-update.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160118 /tmp/rc-update.sh
Adding acpid to default
* service acpid added to runlevel default
Adding cloud-config to default
* service cloud-config added to runlevel default
Adding cloud-final to default
* service cloud-final added to runlevel default
Adding cloud-init-local to default
* service cloud-init-local added to runlevel default
Adding cloud-init to default
* service cloud-init added to runlevel default
Adding cronie to default
* service cronie added to runlevel default
Adding dhcpcd to default
* service dhcpcd added to runlevel default
Adding net.lo to default
* service net.lo added to runlevel default
Adding netmount to default
* rc-update: netmount already installed in runlevel `default'; skipping
Adding sshd to default
* service sshd added to runlevel default
Adding syslog-ng to default
* service syslog-ng added to runlevel default
removing /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160118/tmp/rc-update.sh from the chroot
removing /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160118/tmp/chroot-functions.sh from the chroot
18 Jan 2016 06:57:00 UTC: NOTICE : --- Running action sequence: unmerge
Copying unmerge.sh to /tmp
copying unmerge.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160118/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160118/tmp
Ensure the file has the executable bit set
Running unmerge.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160118 /tmp/unmerge.sh
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse -C sys-kernel/genkernel sys-kernel/gentoo-sources
--- Couldn't find 'sys-kernel/genkernel' to unmerge.
--- Couldn't find 'sys-kernel/gentoo-sources' to unmerge.
18 Jan 2016 06:57:01 UTC: ERROR : CatalystError: cmd() NON-zero return value from: Unmerge script failed.
18 Jan 2016 06:57:02 UTC: ERROR : Exception running action sequence unmerge
Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/catalyst/base/stagebase.py", line 1413, in run
getattr(self, x)()
File "/usr/lib64/python2.7/site-packages/catalyst/base/stagebase.py", line 1452, in unmerge
env=self.env)
File "/usr/lib64/python2.7/site-packages/catalyst/support.py", line 55, in cmd
print_traceback=False)
CatalystError
18 Jan 2016 06:57:02 UTC: NOTICE : Cleaning up... Running unbind()
Full build log at /home/release/tmp/run/catalyst-auto.oO2hD4/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2016-01-15 0:19 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2016-01-15 0:19 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
udev and udev-trigger will be added to your sysinit runlevel, but not
udev-settle. udev-settle should not be added to a runlevel. Instead, if
a service needs this, it should add "need udev-settle" to its
dependencies.
2015-07-25-python-targets
Title Python 3.4 enabled by default
Author Mike Gilbert <floppym@gentoo.org>
Posted 2015-07-25
Revision 1
Python 3.4 is now enabled by default, replacing Python 3.3 as the
default Python 3 interpreter.
PYTHON_TARGETS will be adjusted to contain python2_7 and python3_4 by
default via your profile.
PYTHON_SINGLE_TARGET will remain set to python2_7 by default.
If you have PYTHON_TARGETS set in make.conf, that setting will still be
respected. You may want to adjust this setting manually.
Once the changes have taken place, a world update should take care of
reinstalling any python libraries you have installed. You should also
switch your default python3 interpreter using eselect python.
For example:
eselect python set --python3 python3.4
emerge -uDv --changed-use @world
2015-08-13-openssh-weak-keys
Title OpenSSH 7.0 disables ssh-dss keys by default
Author Mike Frysinger <vapier@gentoo.org>
Posted 2015-08-13
Revision 1
Starting with the 7.0 release of OpenSSH, support for ssh-dss keys has
been disabled by default at runtime due to their inherit weakness. If
you rely on these key types, you will have to take corrective action or
risk being locked out.
Your best option is to generate new keys using strong algos such as rsa
or ecdsa or ed25519. RSA keys will give you the greatest portability
with other clients/servers while ed25519 will get you the best security
with OpenSSH (but requires recent versions of client & server).
If you are stuck with DSA keys, you can re-enable support locally by
updating your sshd_config and ~/.ssh/config files with lines like so:
PubkeyAcceptedKeyTypes=+ssh-dss
Be aware though that eventually OpenSSH will drop support for DSA keys
entirely, so this is only a stop gap solution.
More details can be found on OpenSSH's website:
http://www.openssh.com/legacy.html
2015-10-21-future-support-of-hardened-sources-kernel
Title Future Support of hardened-sources Kernel
Author Anthony G. Basile <blueness@gentoo.org>
Posted 2015-10-21
Revision 3
For many years, the Grsecurity team [1] has been supporting two versions of
their security patches against the Linux kernel, a stable and a testing
version, and Gentoo has made both of these available to our users through the
hardened-sources package. However, on August 26 of this year, the team
announced they would no longer be making the stable version publicly
available, citing trademark infringement by a major embedded systems company
as the reason. [2] The stable patches are now only available to sponsors of
Grsecurity and can no longer be distributed in Gentoo. However, the team did
assure us that they would continue to release and support the testing version
as they have in the past.
What does this means for users of hardened-sources? Gentoo will continue to
make the testing version available through our hardened-sources package but we
will have to drop support for the 3.x series. In a few days, those ebuilds
will be removed from the tree and you will be required to upgrade to a 4.x
series kernel. Since the hardened-sources package only installs the kernel
source tree, you can continue using a currently built 3.x series kernel but
bear in mind that we cannot support you, nor will upstream. Also keep in mind
that the 4.x series will not be as reliable as the 3.x series was, so
reporting bugs promptly will be even more important. Gentoo will continue to
work closely with upstream to stay on top of any problems, but be prepared for
the occasional "bad" kernel. The more reporting we receive from our users,
the better we will be able to decide which hardened-sources kernels to mark
stable and which to drop.
Refs.
[1] https://grsecurity.net
[2] https://grsecurity.net/announce.php
2016-01-08-some-dhcpcd-hooks-are-now-examples
Title Some dhcpcd hooks are now examples
Author William Hubbs <williamh@gentoo.org>
Posted 2016-01-08
Revision 2
In dhcpcd-6.10.0, the following hooks are no longer installed in
/lib/dhcpcd/dhcpcd-hooks by default:
10-wpa_supplicant
15-timezone
29-lookup-hostname
These are now installed in /usr/share/dhcpcd/hooks, which is an example
directory.
If you were using these hooks before you upgrade to 6.10.0, you will
need to copy them back to the /lib/dhcpcd/dhcpcd-hooks directory after the
upgrade.
>>> Building file list for distfiles cleaning...
>>> Cleaning distfiles...
[ 1.0 M ] LVM2.2.02.88.tgz
[ 119.7 K ] MAKEDEV-3.23-1.tar.gz
[ 2.1 M ] busybox-1.20.2.tar.bz2
[ 994.6 K ] cpio-2.11.tar.bz2
[ 227.3 K ] dmraid-1.0.0.rc16-3.tar.bz2
[ 493.5 K ] fuse-2.8.6.tar.gz
[ 276.3 K ] genkernel-3.4.52.3.tar.xz
[ 3.2 M ] gnupg-1.4.11.tar.bz2
[ 285.8 K ] mdadm-3.1.5.tar.bz2
[ 1.8 M ] nano-2.4.3.tar.gz
[ 879.0 K ] open-iscsi-2.0-872.tar.gz
[ 29.7 K ] unionfs-fuse-0.24.tar.bz2
===========
[ 11.3 M ] Total space from 12 files were freed in the distfiles directory
passwd: password expiry information changed.
passwd: password expiry information changed.
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114//tmp/cloud-prep.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114//tmp/chroot-functions.sh from the chroot
--- Running action sequence: preclean
Copying stage4-preclean-chroot.sh to //tmp
copying stage4-preclean-chroot.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114///tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114///tmp
Ensure the file has the executable bit set
Running stage4-preclean-chroot.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114//
>>> Regenerating /etc/ld.so.cache...
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114///tmp/stage4-preclean-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114///tmp/chroot-functions.sh from the chroot
--- Running action sequence: rcupdate
Copying rc-update.sh to /tmp
copying rc-update.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114//tmp
Ensure the file has the executable bit set
Running rc-update.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114/
Adding acpid to default
* service acpid added to runlevel default
Adding cloud-config to default
* service cloud-config added to runlevel default
Adding cloud-final to default
* service cloud-final added to runlevel default
Adding cloud-init-local to default
* service cloud-init-local added to runlevel default
Adding cloud-init to default
* service cloud-init added to runlevel default
Adding cronie to default
* service cronie added to runlevel default
Adding dhcpcd to default
* service dhcpcd added to runlevel default
Adding net.lo to default
* service net.lo added to runlevel default
Adding netmount to default
* rc-update: netmount already installed in runlevel `default'; skipping
Adding sshd to default
* service sshd added to runlevel default
Adding syslog-ng to default
* service syslog-ng added to runlevel default
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114//tmp/rc-update.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114//tmp/chroot-functions.sh from the chroot
--- Running action sequence: unmerge
Copying unmerge.sh to /tmp
copying unmerge.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114//tmp
Ensure the file has the executable bit set
Running unmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114/
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse -C sys-kernel/genkernel sys-kernel/gentoo-sources
--- Couldn't find 'sys-kernel/genkernel' to unmerge.
--- Couldn't find 'sys-kernel/gentoo-sources' to unmerge.
!!! catalyst: Unmerge script failed.
Traceback (most recent call last):
File "/usr/lib64/catalyst/catalyst", line 218, in build_target
mytarget.run()
File "modules/generic_stage_target.py", line 1304, in run
apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1336, in unmerge
env=self.env)
File "/usr/lib64/catalyst//modules/catalyst_support.py", line 541, in cmd
raise CatalystError,myexc
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-nomultilib-20160114/.catalyst_lock'
Full build log at /release/tmp/run/catalyst-auto.B7rM4z/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2015-12-28 4:19 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2015-12-28 4:19 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
28 Dec 2015 04:19:08 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
28 Dec 2015 04:19:08 UTC: NOTICE : Using target: stage4
28 Dec 2015 04:19:08 UTC: ERROR : CatalystError: Ambiguos Filename: /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest
28 Dec 2015 04:19:08 UTC: ERROR : Please specify the correct extension as well
Full build log at /home/release/tmp/run/catalyst-auto.cG2nDx/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2015-12-28 3:00 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2015-12-28 3:00 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
28 Dec 2015 03:00:34 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
28 Dec 2015 03:00:34 UTC: NOTICE : Using target: stage4
28 Dec 2015 03:00:34 UTC: ERROR : CatalystError: Ambiguos Filename: /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest
28 Dec 2015 03:00:34 UTC: ERROR : Please specify the correct extension as well
Full build log at /home/release/tmp/run/catalyst-auto.mFeB9H/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2015-12-26 12:44 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2015-12-26 12:44 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
Catalyst, version 2.0.18
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 "/usr/portage/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+nomultilib-20151225.tar.bz2
Caching snapshot to /release/tmp/snapshots/20151225/
The autoresume path is /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+nomultilib-20151225/
Resume point detected, skipping target path setup operation...
!!! catalyst: Cannot locate specified source_path: /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-20151225.tar.bz2
Traceback (most recent call last):
File "/usr/lib64/catalyst/catalyst", line 216, in build_target
mytarget=targetmap[addlargs["target"]](conf_values, addlargs)
File "modules/stage4_target.py", line 21, in __init__
generic_stage_target.__init__(self,spec,addlargs)
File "modules/generic_stage_target.py", line 170, in __init__
expand=0)
File "/usr/lib64/catalyst//modules/catalyst_support.py", line 571, in file_locate
raise CatalystError, "Cannot locate specified "+myfile+": "+settings[myfile]
CatalystError
!!! catalyst: Error encountered during run of target stage4
Catalyst aborting....
Full build log at /release/tmp/run/catalyst-auto.fMWAyo/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2015-12-25 8:33 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2015-12-25 8:33 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
Catalyst, version 2.0.18
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 "/usr/portage/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+nomultilib-20151225.tar.bz2
Caching snapshot to /release/tmp/snapshots/20151225/
The autoresume path is /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+nomultilib-20151225/
Resume point detected, skipping target path setup operation...
!!! catalyst: Cannot locate specified source_path: /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-20151225.tar.bz2
Traceback (most recent call last):
File "/usr/lib64/catalyst/catalyst", line 216, in build_target
mytarget=targetmap[addlargs["target"]](conf_values, addlargs)
File "modules/stage4_target.py", line 21, in __init__
generic_stage_target.__init__(self,spec,addlargs)
File "modules/generic_stage_target.py", line 170, in __init__
expand=0)
File "/usr/lib64/catalyst//modules/catalyst_support.py", line 571, in file_locate
raise CatalystError, "Cannot locate specified "+myfile+": "+settings[myfile]
CatalystError
!!! catalyst: Error encountered during run of target stage4
Catalyst aborting....
Full build log at /release/tmp/run/catalyst-auto.W52Wn9/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2015-12-25 8:28 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2015-12-25 8:28 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
Catalyst, version 2.0.18
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 "/usr/portage/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+nomultilib-20151225.tar.bz2
Caching snapshot to /release/tmp/snapshots/20151225/
The autoresume path is /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+nomultilib-20151225/
!!! catalyst: Cannot locate specified source_path: /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-20151225.tar.bz2
Traceback (most recent call last):
File "/usr/lib64/catalyst/catalyst", line 216, in build_target
mytarget=targetmap[addlargs["target"]](conf_values, addlargs)
File "modules/stage4_target.py", line 21, in __init__
generic_stage_target.__init__(self,spec,addlargs)
File "modules/generic_stage_target.py", line 170, in __init__
expand=0)
File "/usr/lib64/catalyst//modules/catalyst_support.py", line 571, in file_locate
raise CatalystError, "Cannot locate specified "+myfile+": "+settings[myfile]
CatalystError
!!! catalyst: Error encountered during run of target stage4
Catalyst aborting....
Full build log at /release/tmp/run/catalyst-auto.iIHXmu/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2015-12-24 18:16 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2015-12-24 18:16 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
Catalyst, version 2.0.18
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 "/usr/portage/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+nomultilib-2008.0.tar.bz2
Caching snapshot to /release/tmp/snapshots/20151224/
The autoresume path is /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+cloud-nomultilib-20151224/
!!! catalyst: Cannot locate specified source_path: /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-2008.0.tar.bz2
Traceback (most recent call last):
File "/usr/lib64/catalyst/catalyst", line 216, in build_target
mytarget=targetmap[addlargs["target"]](conf_values, addlargs)
File "modules/stage4_target.py", line 21, in __init__
generic_stage_target.__init__(self,spec,addlargs)
File "modules/generic_stage_target.py", line 170, in __init__
expand=0)
File "/usr/lib64/catalyst//modules/catalyst_support.py", line 571, in file_locate
raise CatalystError, "Cannot locate specified "+myfile+": "+settings[myfile]
CatalystError
!!! catalyst: Error encountered during run of target stage4
Catalyst aborting....
Full build log at /release/tmp/run/catalyst-auto.0ohF4U/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2015-12-18 3:08 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2015-12-18 3:08 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
checking for dlopen in -ldl... ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
no
checking for dlopen in -lsvld... ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
no
checking for dld_link in -ldld... ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
no
checking whether stripping libraries is possible... ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
no
checking if libtool supports shared libraries... no
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for gawk... (cached) gawk
checking for x86_64-pc-linux-gnu-gcc... (cached) x86_64-pc-linux-gnu-gcc
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
checking whether we are using the GNU C compiler... (cached) yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... (cached) yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... (cached) none needed
checking whether x86_64-pc-linux-gnu-gcc understands -c and -o together... (cached) yes
checking dependency style of x86_64-pc-linux-gnu-gcc... (cached) none
checking for a sed that does not truncate output... (cached) /bin/sed
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
checking errno.h usability... ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
no
checking errno.h presence... ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
no
checking for errno.h... no
configure: error: "Missing necessary header"
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/sys-apps/elfix-0.9.2/work/elfix-0.9.2/config.log
* ERROR: sys-apps/elfix-0.9.2::gentoo failed (configure phase):
* econf failed
*
* Call stack:
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
* ebuild.sh, line 90: Called src_configure
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
* environment, line 1972: Called econf '--disable-tests' '--enable-ptpax' '--enable-xtpax'
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
* phase-helpers.sh, line 662: Called __helpers_die 'econf failed'
* isolated-functions.sh, line 117: Called die
* The specific snippet of code:
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
sed: can't read /usr/lib/portage/python3.4/isolated-functions.sh: No such file or directory
*
* If you need support, post the output of `emerge --info '=sys-apps/elfix-0.9.2::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/elfix-0.9.2::gentoo'`.
* The complete build log is located at '/home/release/tmp/logs/sys-apps:elfix-0.9.2:20151218-030759.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/elfix-0.9.2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/elfix-0.9.2/temp/environment'.
* Working directory: '/var/tmp/portage/sys-apps/elfix-0.9.2/work/elfix-0.9.2'
* S: '/var/tmp/portage/sys-apps/elfix-0.9.2/work/elfix-0.9.2'
/usr/lib/portage/python3.4/isolated-functions.sh: line 233: /usr/lib/portage/python3.4/ebuild-ipc: No such file or directory
* The ebuild phase 'configure' has exited unexpectedly. This type of
* behavior is known to be triggered by things such as failed variable
* assignments (bug #190128) or bad substitution errors (bug #200313).
* Normally, before exiting, bash should have displayed an error message
* above. If bash did not produce an error message above, it's possible
* that the ebuild has called `exit` when it should have called `die`
* instead. This behavior may also be triggered by a corrupt bash binary or
* a hardware problem such as memory or cpu malfunction. If the problem is
* not reproducible or it appears to occur randomly, then it is likely to
* be triggered by a hardware problem. If you suspect a hardware problem
* then you should try some basic hardware diagnostics such as memtest.
* Please do not report this as a bug unless it is consistently
* reproducible and you are sure that your bash binary and hardware are
* functioning properly.
[Errno 2] No such file or directory: b'/usr/bin/sandbox':
/usr/bin/sandbox /usr/lib/portage/python3.4/misc-functions.sh die_hooks
Traceback (most recent call last):
File "/usr/lib64/python3.4/site-packages/portage/process.py", line 317, in spawn
File "/usr/lib64/python3.4/site-packages/portage/process.py", line 515, in _exec
File "/usr/lib64/python3.4/site-packages/portage/__init__.py", line 259, in __call__
FileNotFoundError: [Errno 2] No such file or directory: b'/usr/bin/sandbox'
* The ebuild phase 'die_hooks' has exited unexpectedly. This type of
* behavior is known to be triggered by things such as failed variable
* assignments (bug #190128) or bad substitution errors (bug #200313).
* Normally, before exiting, bash should have displayed an error message
* above. If bash did not produce an error message above, it's possible
* that the ebuild has called `exit` when it should have called `die`
* instead. This behavior may also be triggered by a corrupt bash binary or
* a hardware problem such as memory or cpu malfunction. If the problem is
* not reproducible or it appears to occur randomly, then it is likely to
* be triggered by a hardware problem. If you suspect a hardware problem
* then you should try some basic hardware diagnostics such as memtest.
* Please do not report this as a bug unless it is consistently
* reproducible and you are sure that your bash binary and hardware are
* functioning properly.
* Messages for package sys-apps/busybox-1.24.1:
* Could not locate user configfile, so we will save a default one
* Your configuration for sys-apps/busybox-1.24.1 has been saved in
* /etc/portage/savedconfig/sys-apps/busybox-1.24.1 for your editing pleasure.
* You can edit these files by hand and remerge this package with
* USE=savedconfig to customise the configuration.
* You can rename this file/directory to one of the following for
* its configuration to apply to multiple versions:
* ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/
* [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}]
* Messages for package sys-apps/less-481:
* lesspipe offers colorization options. Run 'lesspipe -h' for info.
* Messages for package sys-apps/elfix-0.9.2:
* The ebuild phase 'configure' has exited unexpectedly. This type of
* behavior is known to be triggered by things such as failed variable
* assignments (bug #190128) or bad substitution errors (bug #200313).
* Normally, before exiting, bash should have displayed an error message
* above. If bash did not produce an error message above, it's possible
* that the ebuild has called `exit` when it should have called `die`
* instead. This behavior may also be triggered by a corrupt bash binary or
* a hardware problem such as memory or cpu malfunction. If the problem is
* not reproducible or it appears to occur randomly, then it is likely to
* be triggered by a hardware problem. If you suspect a hardware problem
* then you should try some basic hardware diagnostics such as memtest.
* Please do not report this as a bug unless it is consistently
* reproducible and you are sure that your bash binary and hardware are
* functioning properly.
* ERROR: sys-apps/elfix-0.9.2::gentoo failed (configure phase):
* econf failed
*
* Call stack:
* ebuild.sh, line 90: Called src_configure
* environment, line 1972: Called econf '--disable-tests' '--enable-ptpax' '--enable-xtpax'
* phase-helpers.sh, line 662: Called __helpers_die 'econf failed'
* isolated-functions.sh, line 117: Called die
* The specific snippet of code:
*
* If you need support, post the output of `emerge --info '=sys-apps/elfix-0.9.2::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/elfix-0.9.2::gentoo'`.
* The complete build log is located at '/home/release/tmp/logs/sys-apps:elfix-0.9.2:20151218-030759.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/elfix-0.9.2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/elfix-0.9.2/temp/environment'.
* Working directory: '/var/tmp/portage/sys-apps/elfix-0.9.2/work/elfix-0.9.2'
* S: '/var/tmp/portage/sys-apps/elfix-0.9.2/work/elfix-0.9.2'
18 Dec 2015 03:08:03 UTC: ERROR : CatalystError: cmd() NON-zero return value from: Error in attempt to build packages
18 Dec 2015 03:08:03 UTC: ERROR : CatalystError: stage4build aborting due to error.
18 Dec 2015 03:08:03 UTC: ERROR : Exception running action sequence build_packages
Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/catalyst/base/stagebase.py", line 1397, in run
getattr(self, x)()
File "/usr/lib64/python2.7/site-packages/catalyst/base/stagebase.py", line 1508, in build_packages
"build aborting due to error.")
CatalystError
18 Dec 2015 03:08:03 UTC: NOTICE : Cleaning up... Running unbind()
Full build log at /home/release/tmp/run/catalyst-auto.633O0Y/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
@ 2015-12-18 3:00 catalyst
0 siblings, 0 replies; 39+ messages in thread
From: catalyst @ 2015-12-18 3:00 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
18 Dec 2015 02:58:02 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
18 Dec 2015 02:58:02 UTC: NOTICE : Using target: stage4
18 Dec 2015 02:58:59 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.bz2
>>> Waiting 10 seconds before starting...
>>> (Control-C to abort)...
Purging Caches ... in: 10 9 8 7 6 5 4 3 2 1
18 Dec 2015 02:59:09 UTC: NOTICE : purge(); clearing autoresume ...
18 Dec 2015 02:59:09 UTC: NOTICE : purge(); clearing chroot ...
18 Dec 2015 02:59:09 UTC: NOTICE : Clearing the chroot path ...
18 Dec 2015 02:59:09 UTC: NOTICE : purge(); clearing package cache ...
18 Dec 2015 02:59:09 UTC: NOTICE : purging the pkgcache ...
18 Dec 2015 02:59:09 UTC: NOTICE : purge(); clearing kerncache ...
18 Dec 2015 02:59:09 UTC: NOTICE : --- Running action sequence: unpack
18 Dec 2015 02:59:09 UTC: NOTICE : Clearing the chroot path ...
18 Dec 2015 02:59:09 UTC: NOTICE : Starting None from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.bz2
18 Dec 2015 02:59:09 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20151218 (this may take some time) ..
18 Dec 2015 02:59:15 UTC: NOTICE : --- Running action sequence: unpack_snapshot
18 Dec 2015 02:59:15 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
18 Dec 2015 03:00:37 UTC: NOTICE : --- Running action sequence: config_profile_link
18 Dec 2015 03:00:37 UTC: NOTICE : --- Running action sequence: setup_confdir
18 Dec 2015 03:00:37 UTC: NOTICE : --- Running action sequence: portage_overlay
18 Dec 2015 03:00:37 UTC: NOTICE : --- Running action sequence: bind
18 Dec 2015 03:00:37 UTC: NOTICE : --- Running action sequence: chroot_setup
18 Dec 2015 03:00:37 UTC: NOTICE : Setting up chroot...
18 Dec 2015 03:00:37 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
18 Dec 2015 03:00:37 UTC: WARNING : If your build fails look here first as the possible problem.
18 Dec 2015 03:00:37 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
18 Dec 2015 03:00:37 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
18 Dec 2015 03:00:37 UTC: WARNING : You have been warned.
18 Dec 2015 03:00:37 UTC: NOTICE : --- Running action sequence: setup_environment
18 Dec 2015 03:00:37 UTC: NOTICE : --- Running action sequence: build_packages
Copying stage4-chroot.sh to /tmp
copying stage4-chroot.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20151218/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20151218/tmp
Ensure the file has the executable bit set
Running stage4-chroot.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20151218 /tmp/stage4-chroot.sh
/tmp/chroot-functions.sh: line 4: eselect: command not found
emerge --quiet --usepkg --buildpkg --newuse --oneshot --update --newuse sys-apps/portage
/tmp/chroot-functions.sh: line 295: emerge: command not found
18 Dec 2015 03:00:43 UTC: ERROR : CatalystError: cmd() NON-zero return value from: Error in attempt to build packages
18 Dec 2015 03:00:43 UTC: ERROR : CatalystError: stage4build aborting due to error.
18 Dec 2015 03:00:43 UTC: ERROR : Exception running action sequence build_packages
Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/catalyst/base/stagebase.py", line 1397, in run
getattr(self, x)()
File "/usr/lib64/python2.7/site-packages/catalyst/base/stagebase.py", line 1508, in build_packages
"build aborting due to error.")
CatalystError
18 Dec 2015 03:00:43 UTC: NOTICE : Cleaning up... Running unbind()
Full build log at /home/release/tmp/run/catalyst-auto.7bB4wn/log/hardened_stage4-nomultilib-cloud.log
^ permalink raw reply [flat|nested] 39+ messages in thread
end of thread, other threads:[~2017-12-03 21:12 UTC | newest]
Thread overview: 39+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-11-03 4:44 [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec catalyst
-- strict thread matches above, loose matches on Subject: below --
2017-12-03 21:11 catalyst
2017-12-03 20:48 catalyst
2017-12-03 20:41 catalyst
2017-12-01 6:18 catalyst
2017-11-24 10:07 catalyst
2017-11-17 5:08 catalyst
2017-11-10 4:15 catalyst
2017-10-27 4:00 catalyst
2017-10-20 3:55 catalyst
2017-10-13 3:37 catalyst
2017-10-06 4:26 catalyst
2017-09-28 23:16 catalyst
2017-09-21 11:41 catalyst
2017-09-14 11:37 catalyst
2017-09-08 11:08 catalyst
2017-09-01 8:06 catalyst
2017-03-31 8:21 catalyst
2017-03-01 3:47 catalyst
2017-03-01 3:47 catalyst
2017-03-01 3:47 catalyst
2017-03-01 3:47 catalyst
2016-08-18 17:07 catalyst
2016-07-30 13:09 catalyst
2016-07-25 3:14 catalyst
2016-07-11 20:17 catalyst
2016-05-30 3:00 catalyst
2016-04-30 13:17 catalyst
2016-01-26 3:16 catalyst
2016-01-18 6:57 catalyst
2016-01-15 0:19 catalyst
2015-12-28 4:19 catalyst
2015-12-28 3:00 catalyst
2015-12-26 12:44 catalyst
2015-12-25 8:33 catalyst
2015-12-25 8:28 catalyst
2015-12-24 18:16 catalyst
2015-12-18 3:08 catalyst
2015-12-18 3:00 catalyst
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox