* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2016-04-30 13:17 catalyst
0 siblings, 0 replies; 28+ 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-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2016-05-30 3:00 catalyst
0 siblings, 0 replies; 28+ 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-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2016-07-25 3:11 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2016-07-25 3:11 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
25 Jul 2016 03:10:17 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
25 Jul 2016 03:10:17 UTC: NOTICE : Processing spec file: hardened/stage4-minimal.spec
25 Jul 2016 03:10:17 UTC: NOTICE : Using target: stage4
25 Jul 2016 03:10:17 UTC: NOTICE : Source file specification matching setting is: loose
25 Jul 2016 03:10:17 UTC: NOTICE : Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
25 Jul 2016 03:10:18 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.xz
25 Jul 2016 03:10:18 UTC: NOTICE : purge(); clearing autoresume ...
25 Jul 2016 03:10:18 UTC: NOTICE : purge(); clearing chroot ...
25 Jul 2016 03:10:18 UTC: NOTICE : Clearing the chroot path ...
25 Jul 2016 03:10:18 UTC: NOTICE : purge(); clearing package cache ...
25 Jul 2016 03:10:18 UTC: NOTICE : purging the pkgcache ...
25 Jul 2016 03:10:18 UTC: NOTICE : purge(); clearing kerncache ...
25 Jul 2016 03:10:18 UTC: NOTICE : --- Running action sequence: unpack
25 Jul 2016 03:10:18 UTC: NOTICE : Clearing the chroot path ...
25 Jul 2016 03:10:18 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.xz
25 Jul 2016 03:10:18 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20160725 (this may take some time) ..
Index and archive differ as to next file: ./var/tmp/.keep vs ./var/tmp/portage/._unmerge_/
tar: Child returned status 1
tar: Error is not recoverable: exiting now
25 Jul 2016 03:10:19 UTC: ERROR : 'pixz' extraction of /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.xz to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20160725 failed.
25 Jul 2016 03:10:19 UTC: NOTICE : --- Running action sequence: unpack_snapshot
25 Jul 2016 03:10:19 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
25 Jul 2016 03:11:49 UTC: NOTICE : --- Running action sequence: config_profile_link
25 Jul 2016 03:11:49 UTC: NOTICE : --- Running action sequence: setup_confdir
25 Jul 2016 03:11:49 UTC: NOTICE : --- Running action sequence: portage_overlay
25 Jul 2016 03:11:49 UTC: NOTICE : --- Running action sequence: bind
25 Jul 2016 03:11:49 UTC: NOTICE : --- Running action sequence: chroot_setup
25 Jul 2016 03:11:49 UTC: NOTICE : Setting up chroot...
25 Jul 2016 03:11:49 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
25 Jul 2016 03:11:49 UTC: WARNING : If your build fails look here first as the possible problem.
25 Jul 2016 03:11:49 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
25 Jul 2016 03:11:49 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
25 Jul 2016 03:11:49 UTC: WARNING : You have been warned.
25 Jul 2016 03:11:49 UTC: NOTICE : --- Running action sequence: setup_environment
25 Jul 2016 03:11:49 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+minimal-20160725/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-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:11:49 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'build_packages', 'app-admin/sudo', 'net-misc/dhcp', 'sys-boot/grub', 'sys-apps/dmidecode', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-apps/lsb-release', 'sys-devel/bc', 'sys-power/acpid']) exited 1
25 Jul 2016 03:11:50 UTC: ERROR : CatalystError: stage4build aborting due to error.
25 Jul 2016 03:11:50 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/sudo', 'net-misc/dhcp', 'sys-boot/grub', 'sys-apps/dmidecode', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-apps/lsb-release', 'sys-devel/bc', 'sys-power/acpid']) 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:11:50 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
18.92user 4.81system 1:32.37elapsed 25%CPU (0avgtext+0avgdata 309540maxresident)k
712inputs+1975840outputs (0major+239297minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20160725.vBvLUx/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2016-07-30 13:08 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2016-07-30 13:08 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
30 Jul 2016 13:06:31 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
30 Jul 2016 13:06:31 UTC: NOTICE : Processing spec file: hardened/stage4-minimal.spec
30 Jul 2016 13:06:31 UTC: NOTICE : Using target: stage4
30 Jul 2016 13:06:31 UTC: NOTICE : Source file specification matching setting is: loose
30 Jul 2016 13:06:31 UTC: NOTICE : Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
30 Jul 2016 13:06:32 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-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:06:42 UTC: NOTICE : purge(); clearing autoresume ...
30 Jul 2016 13:06:42 UTC: NOTICE : purge(); clearing chroot ...
30 Jul 2016 13:06:42 UTC: NOTICE : Clearing the chroot path ...
30 Jul 2016 13:06:42 UTC: NOTICE : purge(); clearing package cache ...
30 Jul 2016 13:06:42 UTC: NOTICE : purging the pkgcache ...
30 Jul 2016 13:06:42 UTC: NOTICE : purge(); clearing kerncache ...
30 Jul 2016 13:06:42 UTC: NOTICE : --- Running action sequence: unpack
30 Jul 2016 13:06:42 UTC: NOTICE : Clearing the chroot path ...
30 Jul 2016 13:06:42 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.xz
30 Jul 2016 13:06:42 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20160730 (this may take some time) ..
Index and archive differ as to next file: ./var/tmp/.keep vs ./var/tmp/portage/._unmerge_/
tar: Child returned status 1
tar: Error is not recoverable: exiting now
30 Jul 2016 13:06:43 UTC: ERROR : 'pixz' extraction of /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.xz to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20160730 failed.
30 Jul 2016 13:06:43 UTC: NOTICE : --- Running action sequence: unpack_snapshot
30 Jul 2016 13:06:43 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
30 Jul 2016 13:07:54 UTC: NOTICE : --- Running action sequence: config_profile_link
30 Jul 2016 13:07:54 UTC: NOTICE : --- Running action sequence: setup_confdir
30 Jul 2016 13:07:54 UTC: NOTICE : --- Running action sequence: portage_overlay
30 Jul 2016 13:07:54 UTC: NOTICE : --- Running action sequence: bind
30 Jul 2016 13:07:54 UTC: NOTICE : --- Running action sequence: chroot_setup
30 Jul 2016 13:07:54 UTC: NOTICE : Setting up chroot...
30 Jul 2016 13:07:54 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
30 Jul 2016 13:07:54 UTC: WARNING : If your build fails look here first as the possible problem.
30 Jul 2016 13:07:54 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
30 Jul 2016 13:07:54 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
30 Jul 2016 13:07:54 UTC: WARNING : You have been warned.
30 Jul 2016 13:07:59 UTC: NOTICE : --- Running action sequence: setup_environment
30 Jul 2016 13:07:59 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+minimal-20160730/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-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:07:59 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'build_packages', 'app-admin/sudo', 'net-misc/dhcp', 'sys-boot/grub', 'sys-apps/dmidecode', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-apps/lsb-release', 'sys-devel/bc', 'sys-power/acpid']) exited 1
30 Jul 2016 13:08:00 UTC: ERROR : CatalystError: stage4build aborting due to error.
30 Jul 2016 13:08:00 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/sudo', 'net-misc/dhcp', 'sys-boot/grub', 'sys-apps/dmidecode', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-apps/lsb-release', 'sys-devel/bc', 'sys-power/acpid']) 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:08:00 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
18.41user 4.45system 1:28.40elapsed 25%CPU (0avgtext+0avgdata 309536maxresident)k
1496inputs+1974192outputs (0major+242043minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20160730.bDBA8N/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2016-08-18 17:06 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2016-08-18 17:06 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-latest.tar.bz2
Caching snapshot to /release/tmp/snapshots/20160818/
The autoresume path is /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+minimal-20160818/
Location of the package cache is /release/buildroot/amd64-dev/packages/hardened/stage4-amd64-hardened+minimal-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+minimal-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+minimal-20160818/
clearing chroot ...
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-20160818/
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20160818/
Starting tar extract from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.bz2
to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-20160818//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-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/python2.7/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/python2.7/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/python2.7/isolated-functions.sh: line 264: echo: write error: No space left on device
*
/usr/lib/portage/python2.7/isolated-functions.sh: line 264: echo: write error: No space left on device
* Call stack:
/usr/lib/portage/python2.7/isolated-functions.sh: line 264: echo: write error: No space left on device
* ebuild.sh, line 780: Called __ebuild_main 'unpack'
/usr/lib/portage/python2.7/isolated-functions.sh: line 264: echo: write error: No space left on device
* phase-functions.sh, line 1005: Called __dyn_unpack
/usr/lib/portage/python2.7/isolated-functions.sh: line 264: echo: write error: No space left on device
* phase-functions.sh, line 240: Called die
/usr/lib/portage/python2.7/isolated-functions.sh: line 264: echo: write error: No space left on device
* The specific snippet of code:
/usr/lib/portage/python2.7/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/python2.7/isolated-functions.sh: line 264: echo: write error: No space left on device
*
/usr/lib/portage/python2.7/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/python2.7/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/python2.7/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/python2.7/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/python2.7/isolated-functions.sh: line 264: echo: write error: No space left on device
* Working directory: '/usr/lib64/python2.7/site-packages'
/usr/lib/portage/python2.7/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+minimal-20160818/.catalyst_lock'
Command exited with non-zero status 1
35.61user 6.21system 0:24.48elapsed 170%CPU (0avgtext+0avgdata 716976maxresident)k
2768inputs+1800472outputs (7major+425104minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20160818.Cog4eh/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-03-01 3:47 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-03-01 3:47 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
!!! existing preserved libs found
Emerging packages using stage4 use flags
emerge --quiet --usepkg --buildpkg --newuse app-admin/sudo net-misc/dhcp sys-boot/grub sys-apps/dmidecode sys-apps/gptfdisk sys-apps/iproute2 sys-apps/lsb-release sys-devel/bc sys-power/acpid
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-power/acpid-2.0.28
* Determining the location of the kernel source code
* Unable to find kernel sources at /usr/src/linux
* Please make sure that /usr/src/linux points at your running kernel,
* (or the kernel you wish to build against).
* Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Checking for suitable kernel configuration options...
[ ok ]
>>> Emerging (1 of 23) sys-apps/dmidecode-2.12-r1::gentoo
>>> Installing (1 of 23) sys-apps/dmidecode-2.12-r1::gentoo
>>> Recording sys-apps/dmidecode in "world" favorites file...
>>> Emerging (2 of 23) sys-libs/efivar-30::gentoo
>>> Installing (2 of 23) sys-libs/efivar-30::gentoo
>>> Emerging (3 of 23) net-dns/libidn-1.33::gentoo
>>> Installing (3 of 23) net-dns/libidn-1.33::gentoo
>>> Emerging (4 of 23) dev-libs/nettle-3.2-r1::gentoo
>>> Installing (4 of 23) dev-libs/nettle-3.2-r1::gentoo
>>> Emerging (5 of 23) dev-scheme/guile-1.8.8-r3::gentoo
>>> Installing (5 of 23) dev-scheme/guile-1.8.8-r3::gentoo
>>> Emerging (6 of 23) virtual/libudev-215-r1::gentoo
>>> Installing (6 of 23) virtual/libudev-215-r1::gentoo
>>> Emerging (7 of 23) sys-apps/lsb-release-1.4::gentoo
>>> Installing (7 of 23) sys-apps/lsb-release-1.4::gentoo
>>> Recording sys-apps/lsb-release in "world" favorites file...
>>> Emerging (8 of 23) sys-devel/bc-1.06.95-r1::gentoo
>>> Installing (8 of 23) sys-devel/bc-1.06.95-r1::gentoo
>>> Recording sys-devel/bc in "world" favorites file...
>>> Emerging (9 of 23) media-libs/freetype-2.6.3-r1::gentoo
>>> Installing (9 of 23) media-libs/freetype-2.6.3-r1::gentoo
>>> Emerging (10 of 23) sys-apps/pciutils-3.4.1::gentoo
>>> Installing (10 of 23) sys-apps/pciutils-3.4.1::gentoo
>>> Emerging (11 of 23) sys-devel/autogen-5.18.4::gentoo
>>> Installing (11 of 23) sys-devel/autogen-5.18.4::gentoo
>>> Emerging (12 of 23) dev-libs/libtasn1-4.9-r1::gentoo
>>> Installing (12 of 23) dev-libs/libtasn1-4.9-r1::gentoo
>>> Emerging (13 of 23) app-admin/metalog-3-r1::gentoo
>>> Installing (13 of 23) app-admin/metalog-3-r1::gentoo
>>> Emerging (14 of 23) net-misc/dhcp-4.3.4::gentoo
>>> Installing (14 of 23) net-misc/dhcp-4.3.4::gentoo
>>> Recording net-misc/dhcp in "world" favorites file...
>>> Emerging (15 of 23) sys-apps/gptfdisk-1.0.1::gentoo
>>> Installing (15 of 23) sys-apps/gptfdisk-1.0.1::gentoo
>>> Recording sys-apps/gptfdisk in "world" favorites file...
>>> Emerging (16 of 23) sys-power/acpid-2.0.28::gentoo
>>> Installing (16 of 23) sys-power/acpid-2.0.28::gentoo
>>> Recording sys-power/acpid in "world" favorites file...
>>> Emerging (17 of 23) sys-boot/efibootmgr-14::gentoo
>>> Installing (17 of 23) sys-boot/efibootmgr-14::gentoo
>>> Emerging (18 of 23) net-libs/gnutls-3.3.26::gentoo
>>> Installing (18 of 23) net-libs/gnutls-3.3.26::gentoo
>>> Emerging (19 of 23) virtual/logger-0::gentoo
>>> Installing (19 of 23) virtual/logger-0::gentoo
>>> Emerging (20 of 23) mail-mta/nullmailer-1.13-r5::gentoo
>>> Installing (20 of 23) mail-mta/nullmailer-1.13-r5::gentoo
>>> Emerging (21 of 23) sys-boot/grub-2.02_beta3-r1::gentoo
>>> Installing (21 of 23) sys-boot/grub-2.02_beta3-r1::gentoo
>>> Recording sys-boot/grub in "world" favorites file...
>>> Emerging (22 of 23) virtual/mta-1::gentoo
>>> Installing (22 of 23) virtual/mta-1::gentoo
>>> Emerging (23 of 23) app-admin/sudo-1.8.18_p1::gentoo
>>> Installing (23 of 23) app-admin/sudo-1.8.18_p1::gentoo
>>> Recording app-admin/sudo in "world" favorites file...
* Messages for package sys-power/acpid-2.0.28:
* 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-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 mail-mta/nullmailer-1.13-r5:
* To create an initial setup, please do:
* emerge --config =mail-mta/nullmailer-1.13-r5
* 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-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.
!!! existing preserved libs found
removing /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170220/tmp/stage4-chroot.sh from the chroot
removing /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170220/tmp/chroot-functions.sh from the chroot
20 Feb 2017 13:46:59 UTC: NOTICE : --- Running action sequence: build_kernel
Copying pre-kmerge.sh to /tmp
copying pre-kmerge.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170220/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170220/tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170220 /tmp/pre-kmerge.sh
>>> 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.
!!! existing preserved libs found
removing /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170220/tmp/pre-kmerge.sh from the chroot
removing /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170220/tmp/chroot-functions.sh from the chroot
Copying kmerge.sh to /tmp
copying kmerge.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170220/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170220/tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170220 /tmp/kmerge.sh
>>> Regenerating /etc/ld.so.cache...
Genkernel version 3.4.52.4 found ... OK
emerge --quiet --usepkg --buildpkg --newuse hardened-sources
>>> Verifying ebuild manifests
>>> 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*
*
!!! existing preserved libs found
Adjusting /usr/src/linux to point to /usr/src/linux-4.8.17-hardened-r2
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+minimal-20170220 --no-mountboot --kerneldir=/usr/src/linux --modulespackage=/tmp/kerncache/gentoo-modules-hardened+minimal-20170220.tar.bz2 --minkernpackage=/tmp/kerncache/gentoo-kernel-initrd-hardened+minimal-20170220.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
^[[33;01m*^[[0m ^[[0;01mWARNING^[[0m: No mounted /boot partition detected!
^[[33;01m*^[[0m Run mount /boot to mount it!
^[[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...
Command exited with non-zero status 1
4876.62user 611.01system 207:00:43elapsed 0%CPU (0avgtext+0avgdata 657960maxresident)k
4104inputs+18063512outputs (3major+498053230minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20170220.EFjx1c/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-03-01 3:47 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-03-01 3:47 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
01 Mar 2017 03:47:23 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
01 Mar 2017 03:47:24 UTC: NOTICE : Processing spec file: hardened/stage4-minimal.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.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
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.18user 0.00system 0:00.33elapsed 54%CPU (0avgtext+0avgdata 14840maxresident)k
8inputs+8outputs (0major+7202minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20170213.X83Cxb/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-03-01 3:47 catalyst
0 siblings, 0 replies; 28+ 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-minimal.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.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
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.31elapsed 51%CPU (0avgtext+0avgdata 14756maxresident)k
8inputs+8outputs (0major+7199minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20170206.RiXK15/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-03-01 3:47 catalyst
0 siblings, 0 replies; 28+ 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-minimal.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.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
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.14user 0.02system 0:00.27elapsed 57%CPU (0avgtext+0avgdata 14868maxresident)k
8inputs+8outputs (0major+7204minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20170130.GAEpMk/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-09-01 5:57 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-09-01 5:57 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-20170831/
>>> 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/sudo net-misc/dhcp sys-boot/grub sys-apps/dmidecode sys-apps/gptfdisk sys-apps/iproute2 sys-apps/lsb-release sys-devel/bc sys-power/acpid
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-power/acpid-2.0.28
* Determining the location of the kernel source code
* Unable to find kernel sources at /usr/src/linux
* Please make sure that /usr/src/linux points at your running kernel,
* (or the kernel you wish to build against).
* Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Checking for suitable kernel configuration options...
[ ok ]
>>> Emerging (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Installing (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Recording sys-apps/dmidecode in "world" favorites file...
>>> Emerging (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Installing (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Emerging (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Installing (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Emerging (4 of 22) virtual/libudev-232::gentoo
>>> Installing (4 of 22) virtual/libudev-232::gentoo
>>> Emerging (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Installing (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Recording sys-apps/lsb-release in "world" favorites file...
>>> Emerging (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Installing (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Recording sys-devel/bc in "world" favorites file...
>>> Emerging (7 of 22) media-libs/freetype-2.8::gentoo
>>> Installing (7 of 22) media-libs/freetype-2.8::gentoo
>>> Emerging (8 of 22) sys-libs/efivar-30::gentoo
>>> Installing (8 of 22) sys-libs/efivar-30::gentoo
>>> Emerging (9 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Installing (9 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Emerging (10 of 22) net-dns/libidn2-2.0.2::gentoo
>>> Installing (10 of 22) net-dns/libidn2-2.0.2::gentoo
>>> Emerging (11 of 22) dev-libs/libtasn1-4.10-r2::gentoo
>>> Installing (11 of 22) dev-libs/libtasn1-4.10-r2::gentoo
>>> Emerging (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Installing (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Emerging (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Installing (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Recording net-misc/dhcp in "world" favorites file...
>>> Emerging (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Installing (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Recording sys-apps/gptfdisk in "world" favorites file...
>>> Emerging (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Installing (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Recording sys-power/acpid in "world" favorites file...
>>> Emerging (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Installing (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Emerging (17 of 22) net-libs/gnutls-3.5.13::gentoo
>>> Installing (17 of 22) net-libs/gnutls-3.5.13::gentoo
>>> Emerging (18 of 22) virtual/logger-0::gentoo
>>> Installing (18 of 22) virtual/logger-0::gentoo
>>> Emerging (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Installing (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Emerging (20 of 22) sys-boot/grub-2.02::gentoo
>>> Installing (20 of 22) sys-boot/grub-2.02::gentoo
>>> Recording sys-boot/grub in "world" favorites file...
>>> Emerging (21 of 22) virtual/mta-1::gentoo
>>> Installing (21 of 22) virtual/mta-1::gentoo
>>> Emerging (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Installing (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Recording app-admin/sudo in "world" favorites file...
* Messages for package sys-power/acpid-2.0.28:
* 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-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 mail-mta/nullmailer-2.0-r1:
* To create an initial setup, please do:
* emerge --config =mail-mta/nullmailer-2.0-r1
* 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 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+minimal-20170831//tmp/stage4-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170831//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+minimal-20170831//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170831//tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170831/
>>> 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+minimal-20170831//tmp/pre-kmerge.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170831//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+minimal-20170831//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170831//tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170831/
>>> 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+minimal-20170831/.catalyst_lock'
Command exited with non-zero status 1
1129.84user 410.48system 18:00.71elapsed 142%CPU (0avgtext+0avgdata 792064maxresident)k
1080inputs+4313408outputs (0major+114819964minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20170831.IkLA0t/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-09-08 5:45 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-09-08 5:45 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170907//tmp
Ensure the file has the executable bit set
Running stage4-chroot.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170907/
>>> 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/sudo net-misc/dhcp sys-boot/grub sys-apps/dmidecode sys-apps/gptfdisk sys-apps/iproute2 sys-apps/lsb-release sys-devel/bc sys-power/acpid
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-power/acpid-2.0.28
* Determining the location of the kernel source code
* Unable to find kernel sources at /usr/src/linux
* Please make sure that /usr/src/linux points at your running kernel,
* (or the kernel you wish to build against).
* Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Checking for suitable kernel configuration options...
[ ok ]
>>> Emerging (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Installing (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Recording sys-apps/dmidecode in "world" favorites file...
>>> Emerging (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Installing (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Emerging (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Installing (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Emerging (4 of 22) virtual/libudev-232::gentoo
>>> Installing (4 of 22) virtual/libudev-232::gentoo
>>> Emerging (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Installing (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Recording sys-apps/lsb-release in "world" favorites file...
>>> Emerging (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Installing (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Recording sys-devel/bc in "world" favorites file...
>>> Emerging (7 of 22) media-libs/freetype-2.8::gentoo
>>> Installing (7 of 22) media-libs/freetype-2.8::gentoo
>>> Emerging (8 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Installing (8 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Emerging (9 of 22) sys-libs/efivar-30::gentoo
>>> Installing (9 of 22) sys-libs/efivar-30::gentoo
>>> Emerging (10 of 22) net-dns/libidn2-2.0.2::gentoo
>>> Installing (10 of 22) net-dns/libidn2-2.0.2::gentoo
>>> Emerging (11 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Installing (11 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Emerging (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Installing (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Emerging (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Installing (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Recording net-misc/dhcp in "world" favorites file...
>>> Emerging (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Installing (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Recording sys-apps/gptfdisk in "world" favorites file...
>>> Emerging (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Installing (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Recording sys-power/acpid in "world" favorites file...
>>> Emerging (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Installing (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Emerging (17 of 22) net-libs/gnutls-3.5.13::gentoo
>>> Installing (17 of 22) net-libs/gnutls-3.5.13::gentoo
>>> Emerging (18 of 22) virtual/logger-0::gentoo
>>> Installing (18 of 22) virtual/logger-0::gentoo
>>> Emerging (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Installing (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Emerging (20 of 22) sys-boot/grub-2.02::gentoo
>>> Installing (20 of 22) sys-boot/grub-2.02::gentoo
>>> Recording sys-boot/grub in "world" favorites file...
>>> Emerging (21 of 22) virtual/mta-1::gentoo
>>> Installing (21 of 22) virtual/mta-1::gentoo
>>> Emerging (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Installing (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Recording app-admin/sudo in "world" favorites file...
* Messages for package sys-power/acpid-2.0.28:
* 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-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 mail-mta/nullmailer-2.0-r1:
* To create an initial setup, please do:
* emerge --config =mail-mta/nullmailer-2.0-r1
* 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 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+minimal-20170907//tmp/stage4-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-20170907//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-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+minimal-20170907//tmp/pre-kmerge.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-20170907//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170907//tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-20170907/.catalyst_lock'
Command exited with non-zero status 1
1135.41user 410.31system 18:07.87elapsed 142%CPU (0avgtext+0avgdata 794496maxresident)k
2632inputs+4313664outputs (0major+114919989minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20170907.0gPRKO/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-09-14 11:00 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-09-14 11:00 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
>>> 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
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-apps/file-5.31::gentoo
>>> Installing (1 of 1) sys-apps/file-5.31::gentoo
Emerging packages using stage4 use flags
emerge --quiet --usepkg --buildpkg --newuse app-admin/sudo net-misc/dhcp sys-boot/grub sys-apps/dmidecode sys-apps/gptfdisk sys-apps/iproute2 sys-apps/lsb-release sys-devel/bc sys-power/acpid
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-power/acpid-2.0.28
* Determining the location of the kernel source code
* Unable to find kernel sources at /usr/src/linux
* Please make sure that /usr/src/linux points at your running kernel,
* (or the kernel you wish to build against).
* Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Checking for suitable kernel configuration options...
[ ok ]
>>> Emerging (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Installing (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Recording sys-apps/dmidecode in "world" favorites file...
>>> Emerging (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Installing (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Emerging (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Installing (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Emerging (4 of 22) virtual/libudev-232::gentoo
>>> Installing (4 of 22) virtual/libudev-232::gentoo
>>> Emerging (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Installing (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Recording sys-apps/lsb-release in "world" favorites file...
>>> Emerging (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Installing (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Recording sys-devel/bc in "world" favorites file...
>>> Emerging (7 of 22) media-libs/freetype-2.8::gentoo
>>> Installing (7 of 22) media-libs/freetype-2.8::gentoo
>>> Emerging (8 of 22) sys-libs/efivar-30::gentoo
>>> Installing (8 of 22) sys-libs/efivar-30::gentoo
>>> Emerging (9 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Installing (9 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Emerging (10 of 22) net-dns/libidn2-2.0.2::gentoo
>>> Installing (10 of 22) net-dns/libidn2-2.0.2::gentoo
>>> Emerging (11 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Installing (11 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Emerging (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Installing (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Emerging (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Installing (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Recording net-misc/dhcp in "world" favorites file...
>>> Emerging (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Installing (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Recording sys-apps/gptfdisk in "world" favorites file...
>>> Emerging (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Installing (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Recording sys-power/acpid in "world" favorites file...
>>> Emerging (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Installing (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Emerging (17 of 22) net-libs/gnutls-3.5.13::gentoo
>>> Installing (17 of 22) net-libs/gnutls-3.5.13::gentoo
>>> Emerging (18 of 22) virtual/logger-0::gentoo
>>> Installing (18 of 22) virtual/logger-0::gentoo
>>> Emerging (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Installing (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Emerging (20 of 22) sys-boot/grub-2.02::gentoo
>>> Installing (20 of 22) sys-boot/grub-2.02::gentoo
>>> Recording sys-boot/grub in "world" favorites file...
>>> Emerging (21 of 22) virtual/mta-1::gentoo
>>> Installing (21 of 22) virtual/mta-1::gentoo
>>> Emerging (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Installing (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Recording app-admin/sudo in "world" favorites file...
* Messages for package sys-power/acpid-2.0.28:
* 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-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 mail-mta/nullmailer-2.0-r1:
* To create an initial setup, please do:
* emerge --config =mail-mta/nullmailer-2.0-r1
* 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 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+minimal-20170914//tmp/stage4-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-20170914//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-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+minimal-20170914//tmp/pre-kmerge.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-20170914//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170914//tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-20170914/.catalyst_lock'
Command exited with non-zero status 1
1143.30user 394.91system 18:31.25elapsed 138%CPU (0avgtext+0avgdata 808528maxresident)k
112inputs+4391760outputs (0major+117454296minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20170914.TzyYrd/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-09-21 11:03 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-09-21 11:03 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-apps/portage-2.3.8::gentoo
>>> Installing (1 of 1) sys-apps/portage-2.3.8::gentoo
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/file-5.31::gentoo
>>> Installing (1 of 1) sys-apps/file-5.31::gentoo
Emerging packages using stage4 use flags
emerge --quiet --usepkg --buildpkg --newuse app-admin/sudo net-misc/dhcp sys-boot/grub sys-apps/dmidecode sys-apps/gptfdisk sys-apps/iproute2 sys-apps/lsb-release sys-devel/bc sys-power/acpid
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-power/acpid-2.0.28
* Determining the location of the kernel source code
* Unable to find kernel sources at /usr/src/linux
* Please make sure that /usr/src/linux points at your running kernel,
* (or the kernel you wish to build against).
* Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Checking for suitable kernel configuration options...
[ ok ]
>>> Emerging (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Installing (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Recording sys-apps/dmidecode in "world" favorites file...
>>> Emerging (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Installing (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Emerging (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Installing (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Emerging (4 of 22) virtual/libudev-232::gentoo
>>> Installing (4 of 22) virtual/libudev-232::gentoo
>>> Emerging (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Installing (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Recording sys-apps/lsb-release in "world" favorites file...
>>> Emerging (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Installing (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Recording sys-devel/bc in "world" favorites file...
>>> Emerging (7 of 22) media-libs/freetype-2.8::gentoo
>>> Installing (7 of 22) media-libs/freetype-2.8::gentoo
>>> Emerging (8 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Installing (8 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Emerging (9 of 22) sys-libs/efivar-30::gentoo
>>> Installing (9 of 22) sys-libs/efivar-30::gentoo
>>> Emerging (10 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Installing (10 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Emerging (11 of 22) net-dns/libidn2-2.0.2::gentoo
>>> Installing (11 of 22) net-dns/libidn2-2.0.2::gentoo
>>> Emerging (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Installing (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Emerging (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Installing (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Recording net-misc/dhcp in "world" favorites file...
>>> Emerging (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Installing (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Recording sys-apps/gptfdisk in "world" favorites file...
>>> Emerging (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Installing (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Recording sys-power/acpid in "world" favorites file...
>>> Emerging (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Installing (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Emerging (17 of 22) net-libs/gnutls-3.5.13::gentoo
>>> Installing (17 of 22) net-libs/gnutls-3.5.13::gentoo
>>> Emerging (18 of 22) virtual/logger-0::gentoo
>>> Installing (18 of 22) virtual/logger-0::gentoo
>>> Emerging (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Installing (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Emerging (20 of 22) sys-boot/grub-2.02::gentoo
>>> Installing (20 of 22) sys-boot/grub-2.02::gentoo
>>> Recording sys-boot/grub in "world" favorites file...
>>> Emerging (21 of 22) virtual/mta-1::gentoo
>>> Installing (21 of 22) virtual/mta-1::gentoo
>>> Emerging (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Installing (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Recording app-admin/sudo in "world" favorites file...
* Messages for package sys-power/acpid-2.0.28:
* 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-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 mail-mta/nullmailer-2.0-r1:
* To create an initial setup, please do:
* emerge --config =mail-mta/nullmailer-2.0-r1
* 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 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+minimal-20170921//tmp/stage4-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-20170921//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-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+minimal-20170921//tmp/pre-kmerge.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-20170921//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170921//tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-20170921/.catalyst_lock'
Command exited with non-zero status 1
1172.16user 426.89system 19:08.59elapsed 139%CPU (0avgtext+0avgdata 789888maxresident)k
40inputs+4589912outputs (0major+118957735minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20170921.JtAixy/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-09-28 22:00 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-09-28 22:00 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-latest.tar.bz2
Caching snapshot to /release/tmp/snapshots/20170928/
The autoresume path is /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+minimal-20170928/
Location of the package cache is /release/buildroot/amd64-dev/packages/hardened/stage4-amd64-hardened+minimal-20170928/
Checking for processes running in chroot and killing them.
Removing AutoResume Points: ...
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+minimal-20170928/
>>> 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+minimal-20170928/
clearing chroot ...
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170928/
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+minimal-20170928/
Emptying directory /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170928/
Starting tar extract from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.bz2
to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170928/ (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+minimal-20170928//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170928//tmp
Ensure the file has the executable bit set
Running stage4-chroot.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20170928/
>>> 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.)
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-apps/portage-2.3.8::gentoo
>>> Installing (1 of 1) sys-apps/portage-2.3.8::gentoo
Bringing system up to date using profile specific use flags
emerge --quiet --usepkg --buildpkg --newuse -u @system
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-devel/gcc-5.4.0-r3
>>> Emerging (1 of 3) sys-apps/net-tools-1.60_p20161110235919::gentoo
>>> Installing (1 of 3) sys-apps/net-tools-1.60_p20161110235919::gentoo
>>> Emerging (2 of 3) sys-apps/file-5.32::gentoo
>>> Installing (2 of 3) sys-apps/file-5.32::gentoo
>>> Emerging (3 of 3) sys-devel/gcc-5.4.0-r3::gentoo
* The ebuild phase 'compile' 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.
* The ebuild phase 'die_hooks' has been aborted since PORTAGE_BUILDDIR
* does not exist: '/var/tmp/portage/sys-devel/gcc-5.4.0-r3'
* Messages for package sys-devel/gcc-5.4.0-r3:
* The ebuild phase 'compile' 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.
Traceback (most recent call last):
File "/usr/lib/python-exec/python3.4/emerge", line 50, in <module>
File "/usr/lib64/python3.4/site-packages/_emerge/main.py", line 1250, in emerge_main
File "/usr/lib64/python3.4/site-packages/_emerge/actions.py", line 3297, in run_action
File "/usr/lib64/python3.4/site-packages/_emerge/actions.py", line 540, in action_build
File "/usr/lib64/python3.4/site-packages/_emerge/Scheduler.py", line 1039, in merge
File "/usr/lib64/python3.4/site-packages/_emerge/Scheduler.py", line 1444, in _merge
File "/usr/lib64/python3.4/site-packages/_emerge/Scheduler.py", line 1422, in _main_loop
File "/usr/lib64/python3.4/site-packages/portage/util/_eventloop/EventLoop.py", line 263, in iteration
File "/usr/lib64/python3.4/site-packages/portage/util/_eventloop/EventLoop.py", line 534, in _run_timeouts
File "/usr/lib64/python3.4/site-packages/portage/util/_eventloop/EventLoop.py", line 496, in _run_idle_callbacks
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 74, in _async_wait_cb
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 57, in wait
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook
File "/usr/lib64/python3.4/site-packages/_emerge/EbuildPhase.py", line 349, in _die_hooks_exit
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 57, in wait
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook
File "/usr/lib64/python3.4/site-packages/_emerge/TaskSequence.py", line 47, in _task_exit_handler
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 57, in wait
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook
File "/usr/lib64/python3.4/site-packages/_emerge/CompositeTask.py", line 134, in _default_final_exit
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 57, in wait
File "/usr/lib64/python3.4/site-packages/_emerge/AsynchronousTask.py", line 175, in _wait_hook
File "/usr/lib64/python3.4/site-packages/_emerge/EbuildBuild.py", line 307, in _build_exit
File "/usr/lib64/python3.4/site-packages/_emerge/EbuildBuild.py", line 302, in _unlock_builddir
File "/usr/lib64/python3.4/site-packages/portage/elog/__init__.py", line 176, in elog_process
File "/usr/lib64/python3.4/site-packages/portage/elog/mod_save_summary.py", line 37, in process
File "/usr/lib64/python3.4/site-packages/portage/util/__init__.py", line 1425, in ensure_dirs
File "/usr/lib64/python3.4/site-packages/portage/__init__.py", line 250, in __call__
File "/usr/lib64/python3.4/os.py", line 227, in makedirs
File "/usr/lib64/python3.4/os.py", line 227, in makedirs
File "/usr/lib64/python3.4/os.py", line 237, in makedirs
FileNotFoundError: [Errno 2] No such file or directory: b'/var'
emergelog(): [Errno 2] No such file or directory: b'/var/log/emerge.log'
!!! 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+minimal-20170928/.catalyst_lock'
Command exited with non-zero status 1
5768.95user 515.27system 1:53:42elapsed 92%CPU (0avgtext+0avgdata 3223168maxresident)k
6008inputs+8753400outputs (20major+121026937minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20170928.r9Ro52/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-10-05 23:36 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-10-05 23:36 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-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/sudo net-misc/dhcp sys-boot/grub sys-apps/dmidecode sys-apps/gptfdisk sys-apps/iproute2 sys-apps/lsb-release sys-devel/bc sys-power/acpid
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-power/acpid-2.0.28
* Determining the location of the kernel source code
* Unable to find kernel sources at /usr/src/linux
* Please make sure that /usr/src/linux points at your running kernel,
* (or the kernel you wish to build against).
* Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Checking for suitable kernel configuration options...
[ ok ]
>>> Emerging (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Installing (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Recording sys-apps/dmidecode in "world" favorites file...
>>> Emerging (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Installing (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Emerging (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Installing (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Emerging (4 of 22) virtual/libudev-232::gentoo
>>> Installing (4 of 22) virtual/libudev-232::gentoo
>>> Emerging (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Installing (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Recording sys-apps/lsb-release in "world" favorites file...
>>> Emerging (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Installing (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Recording sys-devel/bc in "world" favorites file...
>>> Emerging (7 of 22) media-libs/freetype-2.8::gentoo
>>> Installing (7 of 22) media-libs/freetype-2.8::gentoo
>>> Emerging (8 of 22) sys-libs/efivar-30::gentoo
>>> Installing (8 of 22) sys-libs/efivar-30::gentoo
>>> Emerging (9 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Installing (9 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Emerging (10 of 22) net-dns/libidn2-2.0.4::gentoo
>>> Installing (10 of 22) net-dns/libidn2-2.0.4::gentoo
>>> Emerging (11 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Installing (11 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Emerging (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Installing (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Emerging (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Installing (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Recording net-misc/dhcp in "world" favorites file...
>>> Emerging (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Installing (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Recording sys-apps/gptfdisk in "world" favorites file...
>>> Emerging (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Installing (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Recording sys-power/acpid in "world" favorites file...
>>> Emerging (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Installing (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Emerging (17 of 22) net-libs/gnutls-3.5.13::gentoo
>>> Installing (17 of 22) net-libs/gnutls-3.5.13::gentoo
>>> Emerging (18 of 22) virtual/logger-0::gentoo
>>> Installing (18 of 22) virtual/logger-0::gentoo
>>> Emerging (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Installing (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Emerging (20 of 22) sys-boot/grub-2.02::gentoo
>>> Installing (20 of 22) sys-boot/grub-2.02::gentoo
>>> Recording sys-boot/grub in "world" favorites file...
>>> Emerging (21 of 22) virtual/mta-1::gentoo
>>> Installing (21 of 22) virtual/mta-1::gentoo
>>> Emerging (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Installing (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Recording app-admin/sudo in "world" favorites file...
* Messages for package sys-power/acpid-2.0.28:
* 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-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 mail-mta/nullmailer-2.0-r1:
* To create an initial setup, please do:
* emerge --config =mail-mta/nullmailer-2.0-r1
* 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 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+minimal-20171005//tmp/stage4-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171005//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+minimal-20171005//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171005//tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171005/
>>> 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+minimal-20171005//tmp/pre-kmerge.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171005//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+minimal-20171005//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171005//tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171005/
>>> 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+minimal-20171005/.catalyst_lock'
Command exited with non-zero status 1
1129.99user 406.63system 18:04.48elapsed 141%CPU (0avgtext+0avgdata 864848maxresident)k
1608inputs+4327512outputs (0major+114959917minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171005.CXcBxW/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-10-12 22:59 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-10-12 22:59 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-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/sudo net-misc/dhcp sys-boot/grub sys-apps/dmidecode sys-apps/gptfdisk sys-apps/iproute2 sys-apps/lsb-release sys-devel/bc sys-power/acpid
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-power/acpid-2.0.28
* Determining the location of the kernel source code
* Unable to find kernel sources at /usr/src/linux
* Please make sure that /usr/src/linux points at your running kernel,
* (or the kernel you wish to build against).
* Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Checking for suitable kernel configuration options...
[ ok ]
>>> Emerging (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Installing (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Recording sys-apps/dmidecode in "world" favorites file...
>>> Emerging (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Installing (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Emerging (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Installing (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Emerging (4 of 22) virtual/libudev-232::gentoo
>>> Installing (4 of 22) virtual/libudev-232::gentoo
>>> Emerging (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Installing (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Recording sys-apps/lsb-release in "world" favorites file...
>>> Emerging (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Installing (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Recording sys-devel/bc in "world" favorites file...
>>> Emerging (7 of 22) media-libs/freetype-2.8::gentoo
>>> Installing (7 of 22) media-libs/freetype-2.8::gentoo
>>> Emerging (8 of 22) sys-libs/efivar-30::gentoo
>>> Installing (8 of 22) sys-libs/efivar-30::gentoo
>>> Emerging (9 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Installing (9 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Emerging (10 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Installing (10 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Emerging (11 of 22) net-dns/libidn2-2.0.4::gentoo
>>> Installing (11 of 22) net-dns/libidn2-2.0.4::gentoo
>>> Emerging (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Installing (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Emerging (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Installing (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Recording net-misc/dhcp in "world" favorites file...
>>> Emerging (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Installing (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Recording sys-apps/gptfdisk in "world" favorites file...
>>> Emerging (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Installing (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Recording sys-power/acpid in "world" favorites file...
>>> Emerging (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Installing (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Emerging (17 of 22) net-libs/gnutls-3.5.13::gentoo
>>> Installing (17 of 22) net-libs/gnutls-3.5.13::gentoo
>>> Emerging (18 of 22) virtual/logger-0::gentoo
>>> Installing (18 of 22) virtual/logger-0::gentoo
>>> Emerging (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Installing (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Emerging (20 of 22) sys-boot/grub-2.02::gentoo
>>> Installing (20 of 22) sys-boot/grub-2.02::gentoo
>>> Recording sys-boot/grub in "world" favorites file...
>>> Emerging (21 of 22) virtual/mta-1::gentoo
>>> Installing (21 of 22) virtual/mta-1::gentoo
>>> Emerging (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Installing (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Recording app-admin/sudo in "world" favorites file...
* Messages for package sys-power/acpid-2.0.28:
* 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-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 mail-mta/nullmailer-2.0-r1:
* To create an initial setup, please do:
* emerge --config =mail-mta/nullmailer-2.0-r1
* 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 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+minimal-20171012//tmp/stage4-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171012//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+minimal-20171012//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171012//tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171012/
>>> 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+minimal-20171012//tmp/pre-kmerge.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171012//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+minimal-20171012//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171012//tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171012/
>>> 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+minimal-20171012/.catalyst_lock'
Command exited with non-zero status 1
1127.32user 402.78system 18:09.69elapsed 140%CPU (0avgtext+0avgdata 843216maxresident)k
1656inputs+4327480outputs (0major+114832596minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171012.TzNcCv/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-10-19 23:11 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-10-19 23:11 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-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/sudo net-misc/dhcp sys-boot/grub sys-apps/dmidecode sys-apps/gptfdisk sys-apps/iproute2 sys-apps/lsb-release sys-devel/bc sys-power/acpid
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-power/acpid-2.0.28
* Determining the location of the kernel source code
* Unable to find kernel sources at /usr/src/linux
* Please make sure that /usr/src/linux points at your running kernel,
* (or the kernel you wish to build against).
* Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Checking for suitable kernel configuration options...
[ ok ]
>>> Emerging (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Installing (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Recording sys-apps/dmidecode in "world" favorites file...
>>> Emerging (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Installing (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Emerging (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Installing (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Emerging (4 of 22) virtual/libudev-232::gentoo
>>> Installing (4 of 22) virtual/libudev-232::gentoo
>>> Emerging (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Installing (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Recording sys-apps/lsb-release in "world" favorites file...
>>> Emerging (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Installing (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Recording sys-devel/bc in "world" favorites file...
>>> Emerging (7 of 22) media-libs/freetype-2.8::gentoo
>>> Installing (7 of 22) media-libs/freetype-2.8::gentoo
>>> Emerging (8 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Installing (8 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Emerging (9 of 22) sys-libs/efivar-30::gentoo
>>> Installing (9 of 22) sys-libs/efivar-30::gentoo
>>> Emerging (10 of 22) net-dns/libidn2-2.0.4::gentoo
>>> Installing (10 of 22) net-dns/libidn2-2.0.4::gentoo
>>> Emerging (11 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Installing (11 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Emerging (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Installing (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Emerging (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Installing (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Recording net-misc/dhcp in "world" favorites file...
>>> Emerging (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Installing (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Recording sys-apps/gptfdisk in "world" favorites file...
>>> Emerging (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Installing (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Recording sys-power/acpid in "world" favorites file...
>>> Emerging (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Installing (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Emerging (17 of 22) net-libs/gnutls-3.5.15::gentoo
>>> Installing (17 of 22) net-libs/gnutls-3.5.15::gentoo
>>> Emerging (18 of 22) virtual/logger-0::gentoo
>>> Installing (18 of 22) virtual/logger-0::gentoo
>>> Emerging (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Installing (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Emerging (20 of 22) sys-boot/grub-2.02::gentoo
>>> Installing (20 of 22) sys-boot/grub-2.02::gentoo
>>> Recording sys-boot/grub in "world" favorites file...
>>> Emerging (21 of 22) virtual/mta-1::gentoo
>>> Installing (21 of 22) virtual/mta-1::gentoo
>>> Emerging (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Installing (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Recording app-admin/sudo in "world" favorites file...
* Messages for package sys-power/acpid-2.0.28:
* 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-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 mail-mta/nullmailer-2.0-r1:
* To create an initial setup, please do:
* emerge --config =mail-mta/nullmailer-2.0-r1
* 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 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+minimal-20171019//tmp/stage4-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171019//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+minimal-20171019//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171019//tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171019/
>>> 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+minimal-20171019//tmp/pre-kmerge.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171019//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+minimal-20171019//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171019//tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171019/
>>> 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: 11 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+minimal-20171019/.catalyst_lock'
Command exited with non-zero status 1
1129.26user 403.60system 18:14.37elapsed 140%CPU (0avgtext+0avgdata 806112maxresident)k
2096inputs+4328976outputs (0major+114966662minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171019.XFbnjd/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-10-26 23:17 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-10-26 23:17 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-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/sudo net-misc/dhcp sys-boot/grub sys-apps/dmidecode sys-apps/gptfdisk sys-apps/iproute2 sys-apps/lsb-release sys-devel/bc sys-power/acpid
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-power/acpid-2.0.28
* Determining the location of the kernel source code
* Unable to find kernel sources at /usr/src/linux
* Please make sure that /usr/src/linux points at your running kernel,
* (or the kernel you wish to build against).
* Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Checking for suitable kernel configuration options...
[ ok ]
>>> Emerging (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Installing (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Recording sys-apps/dmidecode in "world" favorites file...
>>> Emerging (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Installing (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Emerging (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Installing (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Emerging (4 of 22) virtual/libudev-232::gentoo
>>> Installing (4 of 22) virtual/libudev-232::gentoo
>>> Emerging (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Installing (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Recording sys-apps/lsb-release in "world" favorites file...
>>> Emerging (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Installing (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Recording sys-devel/bc in "world" favorites file...
>>> Emerging (7 of 22) media-libs/freetype-2.8::gentoo
>>> Installing (7 of 22) media-libs/freetype-2.8::gentoo
>>> Emerging (8 of 22) sys-libs/efivar-30::gentoo
>>> Installing (8 of 22) sys-libs/efivar-30::gentoo
>>> Emerging (9 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Installing (9 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Emerging (10 of 22) net-dns/libidn2-2.0.4::gentoo
>>> Installing (10 of 22) net-dns/libidn2-2.0.4::gentoo
>>> Emerging (11 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Installing (11 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Emerging (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Installing (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Emerging (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Installing (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Recording net-misc/dhcp in "world" favorites file...
>>> Emerging (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Installing (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Recording sys-apps/gptfdisk in "world" favorites file...
>>> Emerging (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Installing (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Recording sys-power/acpid in "world" favorites file...
>>> Emerging (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Installing (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Emerging (17 of 22) net-libs/gnutls-3.5.15::gentoo
>>> Installing (17 of 22) net-libs/gnutls-3.5.15::gentoo
>>> Emerging (18 of 22) virtual/logger-0::gentoo
>>> Installing (18 of 22) virtual/logger-0::gentoo
>>> Emerging (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Installing (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Emerging (20 of 22) sys-boot/grub-2.02::gentoo
>>> Installing (20 of 22) sys-boot/grub-2.02::gentoo
>>> Recording sys-boot/grub in "world" favorites file...
>>> Emerging (21 of 22) virtual/mta-1::gentoo
>>> Installing (21 of 22) virtual/mta-1::gentoo
>>> Emerging (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Installing (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Recording app-admin/sudo in "world" favorites file...
* Messages for package sys-power/acpid-2.0.28:
* 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-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 mail-mta/nullmailer-2.0-r1:
* To create an initial setup, please do:
* emerge --config =mail-mta/nullmailer-2.0-r1
* 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 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+minimal-20171026//tmp/stage4-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171026//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+minimal-20171026//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171026//tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171026/
>>> 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+minimal-20171026//tmp/pre-kmerge.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171026//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+minimal-20171026//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171026//tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171026/
>>> 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: 11 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+minimal-20171026/.catalyst_lock'
Command exited with non-zero status 1
1136.74user 400.30system 18:12.80elapsed 140%CPU (0avgtext+0avgdata 830496maxresident)k
1672inputs+4328936outputs (0major+115021432minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171026.LrbDkj/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-11-03 0:00 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-11-03 0:00 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-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/sudo net-misc/dhcp sys-boot/grub sys-apps/dmidecode sys-apps/gptfdisk sys-apps/iproute2 sys-apps/lsb-release sys-devel/bc sys-power/acpid
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-power/acpid-2.0.28
* Determining the location of the kernel source code
* Unable to find kernel sources at /usr/src/linux
* Please make sure that /usr/src/linux points at your running kernel,
* (or the kernel you wish to build against).
* Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Checking for suitable kernel configuration options...
[ ok ]
>>> Emerging (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Installing (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Recording sys-apps/dmidecode in "world" favorites file...
>>> Emerging (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Installing (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Emerging (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Installing (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Emerging (4 of 22) virtual/libudev-232::gentoo
>>> Installing (4 of 22) virtual/libudev-232::gentoo
>>> Emerging (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Installing (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Recording sys-apps/lsb-release in "world" favorites file...
>>> Emerging (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Installing (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Recording sys-devel/bc in "world" favorites file...
>>> Emerging (7 of 22) media-libs/freetype-2.8::gentoo
>>> Installing (7 of 22) media-libs/freetype-2.8::gentoo
>>> Emerging (8 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Installing (8 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Emerging (9 of 22) sys-libs/efivar-30::gentoo
>>> Installing (9 of 22) sys-libs/efivar-30::gentoo
>>> Emerging (10 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Installing (10 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Emerging (11 of 22) net-dns/libidn2-2.0.4::gentoo
>>> Installing (11 of 22) net-dns/libidn2-2.0.4::gentoo
>>> Emerging (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Installing (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Emerging (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Installing (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Recording net-misc/dhcp in "world" favorites file...
>>> Emerging (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Installing (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Recording sys-apps/gptfdisk in "world" favorites file...
>>> Emerging (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Installing (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Recording sys-power/acpid in "world" favorites file...
>>> Emerging (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Installing (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Emerging (17 of 22) net-libs/gnutls-3.5.15::gentoo
>>> Installing (17 of 22) net-libs/gnutls-3.5.15::gentoo
>>> Emerging (18 of 22) virtual/logger-0::gentoo
>>> Installing (18 of 22) virtual/logger-0::gentoo
>>> Emerging (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Installing (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Emerging (20 of 22) sys-boot/grub-2.02::gentoo
>>> Installing (20 of 22) sys-boot/grub-2.02::gentoo
>>> Recording sys-boot/grub in "world" favorites file...
>>> Emerging (21 of 22) virtual/mta-1::gentoo
>>> Installing (21 of 22) virtual/mta-1::gentoo
>>> Emerging (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Installing (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Recording app-admin/sudo in "world" favorites file...
* Messages for package sys-power/acpid-2.0.28:
* 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-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 mail-mta/nullmailer-2.0-r1:
* To create an initial setup, please do:
* emerge --config =mail-mta/nullmailer-2.0-r1
* 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 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+minimal-20171102//tmp/stage4-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171102//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+minimal-20171102//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171102//tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171102/
>>> 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+minimal-20171102//tmp/pre-kmerge.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171102//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+minimal-20171102//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171102//tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171102/
>>> 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: 11 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+minimal-20171102/.catalyst_lock'
Command exited with non-zero status 1
1135.58user 402.71system 18:22.22elapsed 139%CPU (0avgtext+0avgdata 800240maxresident)k
1208inputs+4339880outputs (0major+115145174minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171102.I7IfWF/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-11-09 23:33 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-11-09 23:33 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-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/sudo net-misc/dhcp sys-boot/grub sys-apps/dmidecode sys-apps/gptfdisk sys-apps/iproute2 sys-apps/lsb-release sys-devel/bc sys-power/acpid
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-power/acpid-2.0.28
* Determining the location of the kernel source code
* Unable to find kernel sources at /usr/src/linux
* Please make sure that /usr/src/linux points at your running kernel,
* (or the kernel you wish to build against).
* Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Checking for suitable kernel configuration options...
[ ok ]
>>> Emerging (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Installing (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Recording sys-apps/dmidecode in "world" favorites file...
>>> Emerging (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Installing (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Emerging (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Installing (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Emerging (4 of 22) virtual/libudev-232::gentoo
>>> Installing (4 of 22) virtual/libudev-232::gentoo
>>> Emerging (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Installing (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Recording sys-apps/lsb-release in "world" favorites file...
>>> Emerging (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Installing (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Recording sys-devel/bc in "world" favorites file...
>>> Emerging (7 of 22) media-libs/freetype-2.8::gentoo
>>> Installing (7 of 22) media-libs/freetype-2.8::gentoo
>>> Emerging (8 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Installing (8 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Emerging (9 of 22) sys-libs/efivar-30::gentoo
>>> Installing (9 of 22) sys-libs/efivar-30::gentoo
>>> Emerging (10 of 22) net-dns/libidn2-2.0.4::gentoo
>>> Installing (10 of 22) net-dns/libidn2-2.0.4::gentoo
>>> Emerging (11 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Installing (11 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Emerging (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Installing (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Emerging (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Installing (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Recording net-misc/dhcp in "world" favorites file...
>>> Emerging (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Installing (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Recording sys-apps/gptfdisk in "world" favorites file...
>>> Emerging (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Installing (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Recording sys-power/acpid in "world" favorites file...
>>> Emerging (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Installing (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Emerging (17 of 22) net-libs/gnutls-3.5.15::gentoo
>>> Installing (17 of 22) net-libs/gnutls-3.5.15::gentoo
>>> Emerging (18 of 22) virtual/logger-0::gentoo
>>> Installing (18 of 22) virtual/logger-0::gentoo
>>> Emerging (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Installing (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Emerging (20 of 22) sys-boot/grub-2.02::gentoo
>>> Installing (20 of 22) sys-boot/grub-2.02::gentoo
>>> Recording sys-boot/grub in "world" favorites file...
>>> Emerging (21 of 22) virtual/mta-1::gentoo
>>> Installing (21 of 22) virtual/mta-1::gentoo
>>> Emerging (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Installing (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Recording app-admin/sudo in "world" favorites file...
* Messages for package sys-power/acpid-2.0.28:
* 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-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 mail-mta/nullmailer-2.0-r1:
* To create an initial setup, please do:
* emerge --config =mail-mta/nullmailer-2.0-r1
* 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 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+minimal-20171109//tmp/stage4-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171109//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+minimal-20171109//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171109//tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171109/
>>> 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+minimal-20171109//tmp/pre-kmerge.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171109//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+minimal-20171109//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171109//tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171109/
>>> 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: 11 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+minimal-20171109/.catalyst_lock'
Command exited with non-zero status 1
1139.22user 403.79system 18:10.42elapsed 141%CPU (0avgtext+0avgdata 847664maxresident)k
2232inputs+4345456outputs (0major+115229441minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171109.gB4av2/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-11-17 0:18 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-11-17 0:18 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-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+minimal-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/sudo net-misc/dhcp sys-boot/grub sys-apps/dmidecode sys-apps/gptfdisk sys-apps/iproute2 sys-apps/lsb-release sys-devel/bc sys-power/acpid
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-power/acpid-2.0.28
* Determining the location of the kernel source code
* Unable to find kernel sources at /usr/src/linux
* Please make sure that /usr/src/linux points at your running kernel,
* (or the kernel you wish to build against).
* Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Checking for suitable kernel configuration options...
[ ok ]
>>> Emerging (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Installing (1 of 22) sys-apps/dmidecode-3.0::gentoo
>>> Recording sys-apps/dmidecode in "world" favorites file...
>>> Emerging (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Installing (2 of 22) dev-libs/libunistring-0.9.7::gentoo
>>> Emerging (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Installing (3 of 22) dev-libs/nettle-3.3-r2::gentoo
>>> Emerging (4 of 22) virtual/libudev-232::gentoo
>>> Installing (4 of 22) virtual/libudev-232::gentoo
>>> Emerging (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Installing (5 of 22) sys-apps/lsb-release-1.4::gentoo
>>> Recording sys-apps/lsb-release in "world" favorites file...
>>> Emerging (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Installing (6 of 22) sys-devel/bc-1.06.95-r1::gentoo
>>> Recording sys-devel/bc in "world" favorites file...
>>> Emerging (7 of 22) media-libs/freetype-2.8::gentoo
>>> Installing (7 of 22) media-libs/freetype-2.8::gentoo
>>> Emerging (8 of 22) sys-libs/efivar-30::gentoo
>>> Installing (8 of 22) sys-libs/efivar-30::gentoo
>>> Emerging (9 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Installing (9 of 22) sys-apps/pciutils-3.4.1::gentoo
>>> Emerging (10 of 22) net-dns/libidn2-2.0.4::gentoo
>>> Installing (10 of 22) net-dns/libidn2-2.0.4::gentoo
>>> Emerging (11 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Installing (11 of 22) dev-libs/libtasn1-4.12-r1::gentoo
>>> Emerging (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Installing (12 of 22) app-admin/metalog-3-r1::gentoo
>>> Emerging (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Installing (13 of 22) net-misc/dhcp-4.3.5::gentoo
>>> Recording net-misc/dhcp in "world" favorites file...
>>> Emerging (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Installing (14 of 22) sys-apps/gptfdisk-1.0.1::gentoo
>>> Recording sys-apps/gptfdisk in "world" favorites file...
>>> Emerging (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Installing (15 of 22) sys-power/acpid-2.0.28::gentoo
>>> Recording sys-power/acpid in "world" favorites file...
>>> Emerging (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Installing (16 of 22) sys-boot/efibootmgr-14::gentoo
>>> Emerging (17 of 22) net-libs/gnutls-3.5.15::gentoo
>>> Installing (17 of 22) net-libs/gnutls-3.5.15::gentoo
>>> Emerging (18 of 22) virtual/logger-0::gentoo
>>> Installing (18 of 22) virtual/logger-0::gentoo
>>> Emerging (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Installing (19 of 22) mail-mta/nullmailer-2.0-r1::gentoo
>>> Emerging (20 of 22) sys-boot/grub-2.02::gentoo
>>> Installing (20 of 22) sys-boot/grub-2.02::gentoo
>>> Recording sys-boot/grub in "world" favorites file...
>>> Emerging (21 of 22) virtual/mta-1::gentoo
>>> Installing (21 of 22) virtual/mta-1::gentoo
>>> Emerging (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Installing (22 of 22) app-admin/sudo-1.8.20_p2::gentoo
>>> Recording app-admin/sudo in "world" favorites file...
* Messages for package sys-power/acpid-2.0.28:
* 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-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 mail-mta/nullmailer-2.0-r1:
* To create an initial setup, please do:
* emerge --config =mail-mta/nullmailer-2.0-r1
* 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 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+minimal-20171116//tmp/stage4-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171116//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+minimal-20171116//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171116//tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171116/
>>> 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+minimal-20171116//tmp/pre-kmerge.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171116//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+minimal-20171116//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171116//tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171116/
>>> 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+minimal-20171116/.catalyst_lock'
Command exited with non-zero status 1
1145.90user 410.18system 18:20.97elapsed 141%CPU (0avgtext+0avgdata 853024maxresident)k
1464inputs+4351160outputs (0major+115817846minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171116.lVaiZi/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-12-03 20:41 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-12-03 20:41 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
03 Dec 2017 20:41:08 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
03 Dec 2017 20:41:08 UTC: NOTICE : Processing spec file: hardened/stage4-minimal.spec
03 Dec 2017 20:41:08 UTC: NOTICE : Using target: stage4
03 Dec 2017 20:41:08 UTC: NOTICE : Source file specification matching setting is: strict
03 Dec 2017 20:41:08 UTC: NOTICE : Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
03 Dec 2017 20:41:09 UTC: NOTICE : Source path set to /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.bz2
03 Dec 2017 20:41:09 UTC: NOTICE : Removing AutoResume Points ...
03 Dec 2017 20:41:09 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+minimal-20171203
03 Dec 2017 20:41:09 UTC: NOTICE : purge(); clearing autoresume ...
03 Dec 2017 20:41:09 UTC: NOTICE : Removing AutoResume Points ...
03 Dec 2017 20:41:09 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+minimal-20171203
03 Dec 2017 20:41:09 UTC: NOTICE : purge(); clearing chroot ...
03 Dec 2017 20:41:09 UTC: NOTICE : Clearing the chroot path ...
03 Dec 2017 20:41:09 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171203
03 Dec 2017 20:41:09 UTC: NOTICE : purge(); clearing package cache ...
03 Dec 2017 20:41:09 UTC: NOTICE : purging the pkgcache ...
03 Dec 2017 20:41:09 UTC: NOTICE : purge(); clearing kerncache ...
03 Dec 2017 20:41:09 UTC: NOTICE : --- Running action sequence: unpack
03 Dec 2017 20:41:09 UTC: NOTICE : Referenced SEEDCACHE does not appear to be a directory, trying to untar...
03 Dec 2017 20:41:09 UTC: NOTICE : Resume: "seed source" unpack resume point is disabled
03 Dec 2017 20:41:09 UTC: NOTICE : Resume: Target chroot is invalid, cleaning up...
03 Dec 2017 20:41:09 UTC: NOTICE : Removing AutoResume Points ...
03 Dec 2017 20:41:09 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+minimal-20171203
03 Dec 2017 20:41:09 UTC: NOTICE : Clearing the chroot path ...
03 Dec 2017 20:41:09 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171203
03 Dec 2017 20:41:09 UTC: NOTICE : Starting auto from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.bz2
03 Dec 2017 20:41:09 UTC: NOTICE : to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171203 (this may take some time) ..
03 Dec 2017 20:41:14 UTC: NOTICE : --- Running action sequence: unpack_snapshot
03 Dec 2017 20:41:14 UTC: NOTICE : --- Running action sequence: config_profile_link
03 Dec 2017 20:41:14 UTC: NOTICE : --- Running action sequence: setup_confdir
03 Dec 2017 20:41:14 UTC: NOTICE : --- Running action sequence: portage_overlay
03 Dec 2017 20:41:14 UTC: NOTICE : --- Running action sequence: bind
03 Dec 2017 20:41:14 UTC: NOTICE : --- Running action sequence: chroot_setup
03 Dec 2017 20:41:14 UTC: NOTICE : Setting up chroot...
03 Dec 2017 20:41:14 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
03 Dec 2017 20:41:14 UTC: WARNING : If your build fails look here first as the possible problem.
03 Dec 2017 20:41:14 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
03 Dec 2017 20:41:14 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
03 Dec 2017 20:41:14 UTC: WARNING : You have been warned.
03 Dec 2017 20:41:14 UTC: NOTICE : Writing the stage make.conf to: /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171203/etc/portage/make.conf
03 Dec 2017 20:41:14 UTC: NOTICE : STICKY-CONFIG is enabled
03 Dec 2017 20:41:14 UTC: NOTICE : --- Running action sequence: setup_environment
03 Dec 2017 20:41:14 UTC: NOTICE : --- Running action sequence: build_packages
03 Dec 2017 20:41:14 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 1437, in run
getattr(self, x)()
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1533, in build_packages
cmd(command, env=self.env)
File "/usr/lib64/python3.4/site-packages/catalyst/support.py", line 47, in cmd
proc = Popen(args, env=env)
File "/usr/lib64/python3.4/subprocess.py", line 856, in __init__
restore_signals, start_new_session)
File "/usr/lib64/python3.4/subprocess.py", line 1460, in _execute_child
raise child_exception_type(errno_num, err_msg)
FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib64/catalyst/targets/stage4/stage4-controller.sh'
03 Dec 2017 20:41:14 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
30.64user 5.36system 0:06.85elapsed 525%CPU (0avgtext+0avgdata 819120maxresident)k
8inputs+1975832outputs (0major+121672minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171203.PJy7an/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-12-03 20:47 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-12-03 20:47 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
03 Dec 2017 20:47:48 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
03 Dec 2017 20:47:48 UTC: NOTICE : Processing spec file: hardened/stage4-minimal.spec
03 Dec 2017 20:47:48 UTC: NOTICE : Using target: stage4
03 Dec 2017 20:47:48 UTC: NOTICE : Source file specification matching setting is: strict
03 Dec 2017 20:47:48 UTC: NOTICE : Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
03 Dec 2017 20:47:49 UTC: NOTICE : Source path set to /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.bz2
03 Dec 2017 20:47:49 UTC: NOTICE : Removing AutoResume Points ...
03 Dec 2017 20:47:49 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+minimal-20171203
03 Dec 2017 20:47:49 UTC: NOTICE : purge(); clearing autoresume ...
03 Dec 2017 20:47:49 UTC: NOTICE : Removing AutoResume Points ...
03 Dec 2017 20:47:49 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+minimal-20171203
03 Dec 2017 20:47:49 UTC: NOTICE : purge(); clearing chroot ...
03 Dec 2017 20:47:49 UTC: NOTICE : Clearing the chroot path ...
03 Dec 2017 20:47:49 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171203
03 Dec 2017 20:47:51 UTC: NOTICE : purge(); clearing package cache ...
03 Dec 2017 20:47:51 UTC: NOTICE : purging the pkgcache ...
03 Dec 2017 20:47:51 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/packages/hardened/stage4-amd64-hardened+minimal-20171203/
03 Dec 2017 20:47:51 UTC: NOTICE : purge(); clearing kerncache ...
03 Dec 2017 20:47:51 UTC: NOTICE : --- Running action sequence: unpack
03 Dec 2017 20:47:51 UTC: NOTICE : Referenced SEEDCACHE does not appear to be a directory, trying to untar...
03 Dec 2017 20:47:51 UTC: NOTICE : Resume: "seed source" unpack resume point is disabled
03 Dec 2017 20:47:51 UTC: NOTICE : Resume: Target chroot is invalid, cleaning up...
03 Dec 2017 20:47:51 UTC: NOTICE : Removing AutoResume Points ...
03 Dec 2017 20:47:51 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+minimal-20171203
03 Dec 2017 20:47:51 UTC: NOTICE : Clearing the chroot path ...
03 Dec 2017 20:47:51 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171203
03 Dec 2017 20:47:51 UTC: NOTICE : Starting auto from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.bz2
03 Dec 2017 20:47:51 UTC: NOTICE : to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171203 (this may take some time) ..
03 Dec 2017 20:47:56 UTC: NOTICE : --- Running action sequence: unpack_snapshot
03 Dec 2017 20:47:56 UTC: NOTICE : --- Running action sequence: config_profile_link
03 Dec 2017 20:47:56 UTC: NOTICE : --- Running action sequence: setup_confdir
03 Dec 2017 20:47:56 UTC: NOTICE : --- Running action sequence: portage_overlay
03 Dec 2017 20:47:56 UTC: NOTICE : --- Running action sequence: bind
03 Dec 2017 20:47:56 UTC: NOTICE : --- Running action sequence: chroot_setup
03 Dec 2017 20:47:56 UTC: NOTICE : Setting up chroot...
03 Dec 2017 20:47:56 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
03 Dec 2017 20:47:56 UTC: WARNING : If your build fails look here first as the possible problem.
03 Dec 2017 20:47:56 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
03 Dec 2017 20:47:56 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
03 Dec 2017 20:47:56 UTC: WARNING : You have been warned.
03 Dec 2017 20:47:56 UTC: NOTICE : Writing the stage make.conf to: /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171203/etc/portage/make.conf
03 Dec 2017 20:47:56 UTC: NOTICE : STICKY-CONFIG is enabled
03 Dec 2017 20:47:56 UTC: NOTICE : --- Running action sequence: setup_environment
03 Dec 2017 20:47:56 UTC: NOTICE : --- Running action sequence: build_packages
03 Dec 2017 20:47:56 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 1437, in run
getattr(self, x)()
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1533, in build_packages
cmd(command, env=self.env)
File "/usr/lib64/python3.4/site-packages/catalyst/support.py", line 47, in cmd
proc = Popen(args, env=env)
File "/usr/lib64/python3.4/subprocess.py", line 856, in __init__
restore_signals, start_new_session)
File "/usr/lib64/python3.4/subprocess.py", line 1460, in _execute_child
raise child_exception_type(errno_num, err_msg)
FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib64/catalyst/targets/stage4/stage4-controller.sh'
03 Dec 2017 20:47:56 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
31.38user 6.28system 0:08.58elapsed 438%CPU (0avgtext+0avgdata 793280maxresident)k
8inputs+1975832outputs (0major+124358minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171203.SmV1sP/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-12-03 21:11 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-12-03 21:11 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
03 Dec 2017 21:11:39 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
03 Dec 2017 21:11:39 UTC: NOTICE : Processing spec file: hardened/stage4-minimal.spec
03 Dec 2017 21:11:39 UTC: NOTICE : Using target: stage4
03 Dec 2017 21:11:39 UTC: NOTICE : Source file specification matching setting is: strict
03 Dec 2017 21:11:39 UTC: NOTICE : Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
03 Dec 2017 21:11:40 UTC: NOTICE : Source path set to /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.bz2
03 Dec 2017 21:11:40 UTC: NOTICE : Removing AutoResume Points ...
03 Dec 2017 21:11:40 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+minimal-20171203
03 Dec 2017 21:11:40 UTC: NOTICE : purge(); clearing autoresume ...
03 Dec 2017 21:11:40 UTC: NOTICE : Removing AutoResume Points ...
03 Dec 2017 21:11:40 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+minimal-20171203
03 Dec 2017 21:11:40 UTC: NOTICE : purge(); clearing chroot ...
03 Dec 2017 21:11:40 UTC: NOTICE : Clearing the chroot path ...
03 Dec 2017 21:11:40 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171203
03 Dec 2017 21:11:42 UTC: NOTICE : purge(); clearing package cache ...
03 Dec 2017 21:11:42 UTC: NOTICE : purging the pkgcache ...
03 Dec 2017 21:11:42 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/packages/hardened/stage4-amd64-hardened+minimal-20171203/
03 Dec 2017 21:11:42 UTC: NOTICE : purge(); clearing kerncache ...
03 Dec 2017 21:11:42 UTC: NOTICE : --- Running action sequence: unpack
03 Dec 2017 21:11:42 UTC: NOTICE : Referenced SEEDCACHE does not appear to be a directory, trying to untar...
03 Dec 2017 21:11:42 UTC: NOTICE : Resume: "seed source" unpack resume point is disabled
03 Dec 2017 21:11:42 UTC: NOTICE : Resume: Target chroot is invalid, cleaning up...
03 Dec 2017 21:11:42 UTC: NOTICE : Removing AutoResume Points ...
03 Dec 2017 21:11:42 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+minimal-20171203
03 Dec 2017 21:11:42 UTC: NOTICE : Clearing the chroot path ...
03 Dec 2017 21:11:42 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171203
03 Dec 2017 21:11:42 UTC: NOTICE : Starting auto from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.bz2
03 Dec 2017 21:11:42 UTC: NOTICE : to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171203 (this may take some time) ..
03 Dec 2017 21:11:47 UTC: NOTICE : --- Running action sequence: unpack_snapshot
03 Dec 2017 21:11:47 UTC: NOTICE : --- Running action sequence: config_profile_link
03 Dec 2017 21:11:47 UTC: NOTICE : --- Running action sequence: setup_confdir
03 Dec 2017 21:11:47 UTC: NOTICE : --- Running action sequence: portage_overlay
03 Dec 2017 21:11:47 UTC: NOTICE : --- Running action sequence: bind
03 Dec 2017 21:11:47 UTC: NOTICE : --- Running action sequence: chroot_setup
03 Dec 2017 21:11:47 UTC: NOTICE : Setting up chroot...
03 Dec 2017 21:11:47 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
03 Dec 2017 21:11:47 UTC: WARNING : If your build fails look here first as the possible problem.
03 Dec 2017 21:11:47 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
03 Dec 2017 21:11:47 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
03 Dec 2017 21:11:47 UTC: WARNING : You have been warned.
03 Dec 2017 21:11:47 UTC: NOTICE : Writing the stage make.conf to: /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171203/etc/portage/make.conf
03 Dec 2017 21:11:47 UTC: NOTICE : STICKY-CONFIG is enabled
03 Dec 2017 21:11:47 UTC: NOTICE : --- Running action sequence: setup_environment
03 Dec 2017 21:11:47 UTC: NOTICE : --- Running action sequence: build_packages
03 Dec 2017 21:11:47 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 1437, in run
getattr(self, x)()
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1533, in build_packages
cmd(command, env=self.env)
File "/usr/lib64/python3.4/site-packages/catalyst/support.py", line 47, in cmd
proc = Popen(args, env=env)
File "/usr/lib64/python3.4/subprocess.py", line 856, in __init__
restore_signals, start_new_session)
File "/usr/lib64/python3.4/subprocess.py", line 1460, in _execute_child
raise child_exception_type(errno_num, err_msg)
FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib64/catalyst/targets/stage4/stage4-controller.sh'
03 Dec 2017 21:11:47 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
31.80user 6.51system 0:09.15elapsed 418%CPU (0avgtext+0avgdata 775744maxresident)k
632inputs+1975832outputs (0major+134737minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171203.3rjEdu/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-12-06 7:50 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-12-06 7:50 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
06 Dec 2017 07:49:50 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
06 Dec 2017 07:49:50 UTC: NOTICE : Processing spec file: hardened/stage4-minimal.spec
06 Dec 2017 07:49:50 UTC: NOTICE : Using target: stage4
06 Dec 2017 07:49:50 UTC: NOTICE : Source file specification matching setting is: loose
06 Dec 2017 07:49:50 UTC: NOTICE : Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
06 Dec 2017 07:49:51 UTC: NOTICE : Source path set to /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.bz2
06 Dec 2017 07:49:51 UTC: NOTICE : Removing AutoResume Points ...
06 Dec 2017 07:49:51 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+minimal-20171206
06 Dec 2017 07:49:51 UTC: NOTICE : purge(); clearing autoresume ...
06 Dec 2017 07:49:51 UTC: NOTICE : Removing AutoResume Points ...
06 Dec 2017 07:49:51 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+minimal-20171206
06 Dec 2017 07:49:51 UTC: NOTICE : purge(); clearing chroot ...
06 Dec 2017 07:49:51 UTC: NOTICE : Clearing the chroot path ...
06 Dec 2017 07:49:51 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171206
06 Dec 2017 07:49:51 UTC: NOTICE : purge(); clearing package cache ...
06 Dec 2017 07:49:51 UTC: NOTICE : purging the pkgcache ...
06 Dec 2017 07:49:51 UTC: NOTICE : purge(); clearing kerncache ...
06 Dec 2017 07:49:51 UTC: NOTICE : --- Running action sequence: unpack
06 Dec 2017 07:49:51 UTC: NOTICE : Referenced SEEDCACHE does not appear to be a directory, trying to untar...
06 Dec 2017 07:49:51 UTC: NOTICE : Resume: "seed source" unpack resume point is disabled
06 Dec 2017 07:49:51 UTC: NOTICE : Resume: Target chroot is invalid, cleaning up...
06 Dec 2017 07:49:51 UTC: NOTICE : Removing AutoResume Points ...
06 Dec 2017 07:49:51 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/.autoresume-stage4-amd64-hardened+minimal-20171206
06 Dec 2017 07:49:51 UTC: NOTICE : Clearing the chroot path ...
06 Dec 2017 07:49:51 UTC: NOTICE : Emptying directory: /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171206
06 Dec 2017 07:49:51 UTC: NOTICE : Starting auto from /release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.bz2
06 Dec 2017 07:49:51 UTC: NOTICE : to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171206 (this may take some time) ..
06 Dec 2017 07:50:01 UTC: NOTICE : --- Running action sequence: unpack_snapshot
06 Dec 2017 07:50:01 UTC: NOTICE : --- Running action sequence: config_profile_link
06 Dec 2017 07:50:01 UTC: NOTICE : --- Running action sequence: setup_confdir
06 Dec 2017 07:50:01 UTC: NOTICE : --- Running action sequence: portage_overlay
06 Dec 2017 07:50:01 UTC: NOTICE : --- Running action sequence: bind
06 Dec 2017 07:50:01 UTC: NOTICE : --- Running action sequence: chroot_setup
06 Dec 2017 07:50:01 UTC: NOTICE : Setting up chroot...
06 Dec 2017 07:50:01 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
06 Dec 2017 07:50:01 UTC: WARNING : If your build fails look here first as the possible problem.
06 Dec 2017 07:50:01 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
06 Dec 2017 07:50:01 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
06 Dec 2017 07:50:01 UTC: WARNING : You have been warned.
06 Dec 2017 07:50:01 UTC: NOTICE : Writing the stage make.conf to: /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171206/etc/portage/make.conf
06 Dec 2017 07:50:01 UTC: NOTICE : STICKY-CONFIG is enabled
06 Dec 2017 07:50:01 UTC: NOTICE : --- Running action sequence: setup_environment
06 Dec 2017 07:50:01 UTC: NOTICE : --- 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+minimal-20171206/tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171206/tmp
Ensure the file has the executable bit set
Running stage4-chroot.sh in chroot:
chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171206 /tmp/stage4-chroot.sh
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot --update --newuse sys-apps/portage
!!! '--load-avg=4' is not a valid package atom.
!!! Please check ebuild(5) for full details.
06 Dec 2017 07:50:03 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'build_packages', 'app-admin/sudo', 'net-misc/dhcp', 'sys-boot/grub', 'sys-apps/dmidecode', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-apps/lsb-release', 'sys-devel/bc', 'sys-power/acpid']) exited 1
06 Dec 2017 07:50:04 UTC: ERROR : CatalystError: stage4build aborting due to error.
06 Dec 2017 07:50:04 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 1533, 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/sudo', 'net-misc/dhcp', 'sys-boot/grub', 'sys-apps/dmidecode', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-apps/lsb-release', 'sys-devel/bc', 'sys-power/acpid']) 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 1437, in run
getattr(self, x)()
File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1540, in build_packages
"build aborting due to error.")
catalyst.support.CatalystError: stage4build aborting due to error.
06 Dec 2017 07:50:04 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
33.07user 6.05system 0:13.86elapsed 282%CPU (0avgtext+0avgdata 935696maxresident)k
2304inputs+1976136outputs (0major+199193minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171206.SbBadX/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-12-07 0:22 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-12-07 0:22 UTC (permalink / raw
To: releng, gentoo-releng-autobuilds
07 Dec 2017 00:22:47 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
07 Dec 2017 00:22:47 UTC: NOTICE : Processing spec file: hardened/stage4-minimal.spec
07 Dec 2017 00:22:47 UTC: NOTICE : Using target: stage4
07 Dec 2017 00:22:47 UTC: NOTICE : Source file specification matching setting is: loose
07 Dec 2017 00:22:47 UTC: NOTICE : Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
07 Dec 2017 00:22:47 UTC: ERROR : CatalystError: File Not Found: /release/buildroot/amd64-dev/snapshots/portage-20171206
Command exited with non-zero status 2
0.20user 0.01system 0:00.27elapsed 82%CPU (0avgtext+0avgdata 69184maxresident)k
8inputs+8outputs (0major+9585minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20171206.07iZP5/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-12-11 10:22 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-12-11 10:22 UTC (permalink / raw
To: jmbsvicetto, 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-minimal.spec
Command exited with non-zero status 2
0.04user 0.00system 0:00.04elapsed 83%CPU (0avgtext+0avgdata 15076maxresident)k
0inputs+8outputs (0major+3317minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20171211T030001Z.2ifcWb/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
* [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec
@ 2017-12-11 22:03 catalyst
0 siblings, 0 replies; 28+ messages in thread
From: catalyst @ 2017-12-11 22:03 UTC (permalink / raw
To: jmbsvicetto, gentoo-releng-autobuilds
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 12136 bytes --]
installed gettext catalog files (*.mo), but also lines of translations
in an always shipped file (e.g., *.desktop).
If you want English with a set LINGUAS, it is suggested to list it with
the desired country code, in case the default is not the usual "en_US".
It is also common to list "en" then, in case a package is natively
written in a different language, but does provide an English translation
for whichever country. A list of LINGUAS language codes is available at:
http://www.gnu.org/software/gettext/manual/gettext.html#Language-Codes
If you have per-package customizations of the LINGUAS USE_EXPAND, you
should also rename those. This typically means changing linguas_* to
l10n_*, and possibly updating the syntax as described above.
https://wiki.gentoo.org/wiki/Localization/Guide has also been updated to
reflect this change.
2016-08-11-grub2_multislot_default
Title Grub2 multislot default setting is changing
Author William Hubbs <williamh@gentoo.org>
Author Ian Stakenvicius <axs@gentoo.org>
Posted 2016-08-11
Revision 1
The multislot use flag in sys-boot/grub-2.x is no longer enabled by
default.
When the flag is enabled, all upstream binaries and documentation are
renamed to "grub2" so as not to collide with grub-0. Now that the use
flag is no longer default-enabled, these names will revert back to
their upstream defaults. For example, grub2-mkconfig will become
grub-mkconfig, grub2-install will become grub-install, etc.
If you wish to retain the previous naming scheme, please make sure to
explicitly enable USE="multislot" on sys-boot/grub in the usual manner.
2017-10-13-openrc-service-binary-removal
Title OpenRC "service" binary removal
Author William Hubbs <williamh@gentoo.org>
Posted 2017-10-13
Revision 1
OpenRC 0.33 will remove the "service" binary, which was just a copy of
the "rc-service" binary.
If you only use rc-service this will not affect you. However, if you
still need the "service" command, you should install
sys-apps/init-system-helpers.
2017-11-30-new-17-profiles
Title New 17.0 profiles in the Gentoo repository
Author Andreas K. Hüttel <dilfridge@gentoo.org>
Posted 2017-11-30
Revision 1
We have just added (for all arches except arm and mips, these follow
later) a new set of profiles with release version 17.0 to the Gentoo
repository. These bring three changes:
1) The default C++ language version for applications is now C++14.
This change is mostly relevant to Gentoo developers. It also
means, however, that compilers earlier than GCC 6 are masked
and not supported for use as a system compiler anymore. Feel
free to unmask them if you need them for specific applications.
2) Where supported, GCC will now build position-independent
executables (PIE) by default. This improves the overall
security fingerprint. The switch from non-PIE to PIE binaries,
however, requires some steps by users, as detailed below.
3) Up to now, hardened profiles were separate from the default
profile tree. Now they are moving into the 17.0 profile
as a feature there, similar to "no-multilib" and "systemd".
Please migrate away from the 13.0 profiles within the six weeks after
GCC 6.4.0 has been stabilized on your architecture. The 13.0 profiles
will be deprecated then and removed in half a year.
If you are not already running a hardened setup with PIE enabled, then
switching the profile involves the following steps:
If not already done,
* Use gcc-config to select gcc-6.4.0 or later as system compiler
* Re-source /etc/profile:
. /etc/profile
* Re-emerge libtool
emerge -1 sys-devel/libtool
Then,
* Select the new profile with eselect
* Re-emerge, in this sequence, gcc, binutils, and glibc
emerge -1 sys-devel/gcc:6.4.0
emerge -1 sys-devel/binutils
emerge -1 sys-libs/glibc
* Rebuild your entire system
emerge -e @world
Switching the profile from 13.0 to 17.0 modifies the settings of
GCC 6 to generate PIE executables by default; thus, you need to do
the rebuilds even if you have already used GCC 6 beforehand.
If you do not follow these steps you may get spurious build
failures when the linker tries unsuccessfully to combine non-PIE
and PIE code.
./tmp/cloud-prep.sh: line 73: eclean-dist: command not found
passwd: password expiry information changed.
passwd: password expiry information changed.
migraging pax
removing /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171211T114953Z/tmp/cloud-prep.sh from the chroot
removing /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171211T114953Z/tmp/chroot-functions.sh from the chroot
11 Dec 2017 22:02:48 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+minimal-20171211T114953Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171211T114953Z/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+minimal-20171211T114953Z /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+minimal-20171211T114953Z/tmp/stage4-preclean-chroot.sh from the chroot
removing /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171211T114953Z/tmp/chroot-functions.sh from the chroot
11 Dec 2017 22:02:49 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+minimal-20171211T114953Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171211T114953Z/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+minimal-20171211T114953Z /tmp/rc-update.sh
Adding acpid to default
* service acpid 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
removing /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171211T114953Z/tmp/rc-update.sh from the chroot
removing /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171211T114953Z/tmp/chroot-functions.sh from the chroot
11 Dec 2017 22:02:49 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+minimal-20171211T114953Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171211T114953Z/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+minimal-20171211T114953Z /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.
sys-kernel/gentoo-sources: 4.12.12 none none
All selected packages: =sys-kernel/gentoo-sources-4.12.12
>>> Unmerging (1 of 1) sys-kernel/gentoo-sources-4.12.12...
* Messages for package sys-kernel/gentoo-sources-4.12.12:
* Log file: /home/release/tmp/logs/sys-kernel:gentoo-sources-4.12.12:20171211-220256.log
* Note: Even though you have successfully unmerged
* your kernel package, directories in kernel source location:
* /usr/src/linux-4.12.12-gentoo
* with modified files will remain behind. By design, package managers
* will not remove these modified files and the directories they reside in.
* For more detailed kernel removal instructions, please see:
* https://wiki.gentoo.org/wiki/Kernel/Removal
removing /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171211T114953Z/tmp/unmerge.sh from the chroot
removing /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171211T114953Z/tmp/chroot-functions.sh from the chroot
11 Dec 2017 22:03:08 UTC: NOTICE : --- Running action sequence: unbind
11 Dec 2017 22:03:08 UTC: NOTICE : --- Running action sequence: remove
11 Dec 2017 22:03:08 UTC: NOTICE : livecd: removing /etc/*-
11 Dec 2017 22:03:08 UTC: NOTICE : livecd: removing /etc/*.old
11 Dec 2017 22:03:08 UTC: NOTICE : livecd: removing /etc/ssh/ssh_host_*
11 Dec 2017 22:03:08 UTC: NOTICE : livecd: removing /root/.*history
11 Dec 2017 22:03:08 UTC: NOTICE : livecd: removing /root/.lesshst
11 Dec 2017 22:03:08 UTC: NOTICE : livecd: removing /root/.ssh/known_hosts
11 Dec 2017 22:03:08 UTC: NOTICE : livecd: removing /root/.viminfo
11 Dec 2017 22:03:08 UTC: NOTICE : livecd: removing /usr/share/genkernel
11 Dec 2017 22:03:08 UTC: NOTICE : livecd: removing /usr/lib64/python*/site-packages/gentoolkit/test/eclean/testdistfiles.tar.gz
11 Dec 2017 22:03:08 UTC: NOTICE : --- Running action sequence: empty
11 Dec 2017 22:03:08 UTC: WARNING : not a directory or does not exist, skipping "empty" operation: /root/.ccache
11 Dec 2017 22:03:08 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171211T114953Z//tmp
11 Dec 2017 22:03:08 UTC: WARNING : not a directory or does not exist, skipping "empty" operation: /usr/portage/distfiles
11 Dec 2017 22:03:08 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171211T114953Z//usr/src
11 Dec 2017 22:03:09 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171211T114953Z//var/cache/edb/dep
11 Dec 2017 22:03:09 UTC: WARNING : not a directory or does not exist, skipping "empty" operation: /var/cache/genkernel
11 Dec 2017 22:03:09 UTC: WARNING : not a directory or does not exist, skipping "empty" operation: /var/cache/portage/distfiles
11 Dec 2017 22:03:09 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171211T114953Z//var/empty
11 Dec 2017 22:03:09 UTC: WARNING : not a directory or does not exist, skipping "empty" operation: /var/run
11 Dec 2017 22:03:09 UTC: WARNING : not a directory or does not exist, skipping "empty" operation: /var/state
11 Dec 2017 22:03:09 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20171211T114953Z//var/tmp
11 Dec 2017 22:03:09 UTC: NOTICE : --- Running action sequence: clean
11 Dec 2017 22:03:09 UTC: NOTICE : Cleaning chroot: /var/tmp/*
11 Dec 2017 22:03:09 UTC: NOTICE : Cleaning chroot: /tmp/*
11 Dec 2017 22:03:09 UTC: ERROR : Exception running action sequence clean
Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/catalyst/base/stagebase.py", line 1437, in run
getattr(self, x)()
File "/usr/lib64/python2.7/site-packages/catalyst/base/stagebase.py", line 1210, in clean
self.settings["portage_prefix"]])
TypeError: all args must be strings
11 Dec 2017 22:03:09 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
10721.60user 1046.44system 1:41:56elapsed 192%CPU (0avgtext+0avgdata 919696maxresident)k
126328inputs+30519360outputs (628major+719578426minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20171211T114953Z.Q1rViw/log/hardened_stage4-minimal.log
^ permalink raw reply [flat|nested] 28+ messages in thread
end of thread, other threads:[~2017-12-11 22:03 UTC | newest]
Thread overview: 28+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-03-01 3:47 [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-minimal.spec catalyst
-- strict thread matches above, loose matches on Subject: below --
2017-12-11 22:03 catalyst
2017-12-11 10:22 catalyst
2017-12-07 0:22 catalyst
2017-12-06 7:50 catalyst
2017-12-03 21:11 catalyst
2017-12-03 20:47 catalyst
2017-12-03 20:41 catalyst
2017-11-17 0:18 catalyst
2017-11-09 23:33 catalyst
2017-11-03 0:00 catalyst
2017-10-26 23:17 catalyst
2017-10-19 23:11 catalyst
2017-10-12 22:59 catalyst
2017-10-05 23:36 catalyst
2017-09-28 22:00 catalyst
2017-09-21 11:03 catalyst
2017-09-14 11:00 catalyst
2017-09-08 5:45 catalyst
2017-09-01 5:57 catalyst
2017-03-01 3:47 catalyst
2017-03-01 3:47 catalyst
2017-03-01 3:47 catalyst
2016-08-18 17:06 catalyst
2016-07-30 13:08 catalyst
2016-07-25 3:11 catalyst
2016-05-30 3:00 catalyst
2016-04-30 13:17 catalyst
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox