public inbox for gentoo-releng-autobuilds@lists.gentoo.org
 help / color / mirror / Atom feed
From: catalyst@nightheron.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec
Date: Thu, 28 Sep 2017 23:16:46 +0000 (UTC)	[thread overview]
Message-ID: <20170928231646.DEE1133B3C@nightheron.gentoo.org> (raw)




 * for logrotate to use.
 * Messages for package dev-python/jinja-2.9.5:
 * For i18n support, please emerge dev-python/Babel.
 * Messages for package net-misc/dhcpcd-6.11.3:
 * 
 * dhcpcd has zeroconf support active by default.
 * This means it will always obtain an IP address even if no
 * DHCP server can be contacted, which will break any existing
 * failover support you may have configured in your net configuration.
 * This behaviour can be controlled with the noipv4ll configuration
 * file option or the -L command line switch.
 * See the dhcpcd and dhcpcd.conf man pages for more details.
 * 
 * Dhcpcd has duid enabled by default, and this may cause issues
 * with some dhcp servers. For more information, see
 * https://bugs.gentoo.org/show_bug.cgi?id=477356
 * 
 * If you activate the lookup-hostname hook to look up your hostname
 * using the dns, you need to install net-dns/bind-tools.
 * Messages for package sys-power/acpid-2.0.28:
 * 
 * You may wish to read the Gentoo Linux Power Management Guide,
 * which can be found online at:
 * https://wiki.gentoo.org/wiki/Power_management/Guide
 * 
 * You should reboot the system now to get /run mounted with tmpfs!
 * Messages for package dev-util/ctags-20161028:
 * You can set the version to be started by /usr/bin/ctags through
 * the ctags eselect module. "man ctags.eselect" for details.
 * Messages for package mail-mta/nullmailer-2.0-r1:
 * To create an initial setup, please do:
 * emerge --config =mail-mta/nullmailer-2.0-r1
 * Messages for package app-admin/logrotate-3.12.2:
 * The logrotate binary is now installed under /usr/bin. Please
 * update your links
 * 
 * If you wish to have logrotate e-mail you updates, please
 * emerge virtual/mailx and configure logrotate in
 * /etc/logrotate.conf appropriately
 * 
 * Additionally, /etc/logrotate.conf may need to be modified
 * for your particular needs.  See man logrotate for details.
 * Messages for package sys-boot/grub-2.02:
 * For information on how to configure GRUB2 please refer to the guide:
 *     https://wiki.gentoo.org/wiki/GRUB2_Quick_Start
 * 
 * You may consider installing the following optional packages:
 *   sys-boot/os-prober for Detect other operating systems (grub-mkconfig)
 *   dev-libs/libisoburn for Create rescue media (grub-mkrescue)
 *   sys-fs/mdadm for Enable RAID device detection
 * Messages for package dev-python/ndg-httpsclient-0.4.0:
 * The following *-nspkg.pth files were found installed:
 * 
 *   /usr/lib64/python3.4/site-packages/ndg_httpsclient-0.4.0-py3.4-nspkg.pth
 *   /usr/lib64/python2.7/site-packages/ndg_httpsclient-0.4.0-py2.7-nspkg.pth
 * 
 * The presence of those files may break namespaces in Python 3.5+. Please
 * read our documentation on reliable handling of namespaces and update
 * the ebuild accordingly:
 * 
 *   https://wiki.gentoo.org/wiki/Project:Python/Namespace_packages
 * Messages for package app-emulation/cloud-init-0.7.9:
 * cloud-init-local needs to be run in the boot runlevel because it
 * modifies services in the default runlevel.  When a runlevel is started
 * it is cached, so modifications that happen to the current runlevel
 * while you are in it are not acted upon.
 * Messages for package app-vim/gentoo-syntax-20170225:
 * Note for developers and anyone else who edits ebuilds:
 *     This release of gentoo-syntax now contains filetype rules to set
 *     fileencoding for ebuilds and ChangeLogs to utf-8 as per GLEP 31.
 *     If you find this feature breaks things, please submit a bug and
 *     assign it to vim@gentoo.org. You can use the 'ignore-glep31' USE
 *     flag to remove these rules.
 * Messages for package app-admin/sudo-1.8.20_p2:
 * To use the -A (askpass) option, you need to install a compatible
 * password program from the following list. Starred packages will
 * automatically register for the use with sudo (but will not force
 * the -A option):
 * 
 *  [*] net-misc/ssh-askpass-fullscreen
 *      net-misc/x11-ssh-askpass
 * 
 * You can override the choice by setting the SUDO_ASKPASS environmnent
 * variable to the program you want to use.






























removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928//tmp/stage4-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928//tmp/chroot-functions.sh from the chroot
--- Running action sequence: build_kernel
Copying pre-kmerge.sh to /tmp
copying pre-kmerge.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928//tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928/
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot genkernel
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-kernel/genkernel-3.4.52.4-r2
>>> Emerging (1 of 2) app-arch/cpio-2.12-r1::gentoo
>>> Installing (1 of 2) app-arch/cpio-2.12-r1::gentoo
>>> Emerging (2 of 2) sys-kernel/genkernel-3.4.52.4-r2::gentoo
>>> Installing (2 of 2) sys-kernel/genkernel-3.4.52.4-r2::gentoo
 * Messages for package sys-kernel/genkernel-3.4.52.4-r2:
 * Documentation is available in the genkernel manual page
 * as well as the following URL:
 * https://wiki.gentoo.org/wiki/Genkernel
 * This package is known to not work with reiser4.  If you are running
 * reiser4 and have a problem, do not file a bug.  We know it does not
 * work and we don't plan on fixing it since reiser4 is the one that is
 * broken in this regard.  Try using a sane filesystem like ext4.
 * The LUKS support has changed from versions prior to 3.4.4.  Now,
 * you use crypt_root=/dev/blah instead of real_root=luks:/dev/blah.


removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928//tmp/pre-kmerge.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928//tmp/chroot-functions.sh from the chroot
Copying kmerge.sh to /tmp
copying kmerge.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928//tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928/
>>> Regenerating /etc/ld.so.cache...
Genkernel version 3.4.52.4 found ... continuing
emerge --quiet --usepkg --buildpkg --newuse hardened-sources
[ebuild  N    ] sys-kernel/hardened-sources-4.8.17-r2 

The following mask changes are necessary to proceed:
 (see "package.unmask" in the portage(5) man page for more details)
# required by hardened-sources (argument)
# /usr/portage/profiles/package.mask:
# Anthony G. Basile <blueness@gentoo.org> (27 Aug 2017)
# Upstream is no longer providing public patches
=sys-kernel/hardened-sources-4.8.17-r2

Use --autounmask-write to write changes to config files (honoring
CONFIG_PROTECT). Carefully examine the list of proposed changes,
paying special attention to mask or keyword changes that may expose
experimental or unstable packages.

 * IMPORTANT: 10 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.


!!! catalyst: Runscript kernel build failed


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1457, in build_kernel
    self._build_kernel(kname=kname)
  File "modules/generic_stage_target.py", line 1501, in _build_kernel
    "Runscript kernel build failed",env=self.env)
  File "/usr/lib64/catalyst//modules/catalyst_support.py", line 541, in cmd
    raise CatalystError,myexc
CatalystError
None

!!! catalyst: build aborting due to kernel build error.

Traceback (most recent call last):
File "/usr/lib64/catalyst/catalyst", line 218, in build_target
    mytarget.run()
File "modules/generic_stage_target.py", line 1333, in run
    apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1462, in build_kernel
    "build aborting due to kernel build error."
CatalystError
!!! catalyst: Error encountered during run of target stage4
Catalyst aborting....
lockfile does not exist '/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20170928/.catalyst_lock'
Command exited with non-zero status 1
8584.46user 1345.54system 1:13:07elapsed 226%CPU (0avgtext+0avgdata 3222944maxresident)k
7073inputs+15677921outputs (0major+341421025minor)pagefaults 0swaps



Full build log at /release/tmp/run/catalyst-auto.20170928.r9Ro52/log/hardened_stage4-nomultilib-cloud.log


             reply	other threads:[~2017-09-28 23:16 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28 23:16 catalyst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-12-03 21:11 [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec catalyst
2017-12-03 20:48 catalyst
2017-12-03 20:41 catalyst
2017-12-01  6:18 catalyst
2017-11-24 10:07 catalyst
2017-11-17  5:08 catalyst
2017-11-10  4:15 catalyst
2017-11-03  4:44 catalyst
2017-10-27  4:00 catalyst
2017-10-20  3:55 catalyst
2017-10-13  3:37 catalyst
2017-10-06  4:26 catalyst
2017-09-21 11:41 catalyst
2017-09-14 11:37 catalyst
2017-09-08 11:08 catalyst
2017-09-01  8:06 catalyst
2017-03-31  8:21 catalyst
2017-03-01  3:47 catalyst
2017-03-01  3:47 catalyst
2017-03-01  3:47 catalyst
2017-03-01  3:47 catalyst
2016-08-18 17:07 catalyst
2016-07-30 13:09 catalyst
2016-07-25  3:14 catalyst
2016-07-11 20:17 catalyst
2016-05-30  3:00 catalyst
2016-04-30 13:17 catalyst
2016-01-26  3:16 catalyst
2016-01-18  6:57 catalyst
2016-01-15  0:19 catalyst
2015-12-28  4:19 catalyst
2015-12-28  3:00 catalyst
2015-12-26 12:44 catalyst
2015-12-25  8:33 catalyst
2015-12-25  8:28 catalyst
2015-12-24 18:16 catalyst
2015-12-18  3:08 catalyst
2015-12-18  3:00 catalyst

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170928231646.DEE1133B3C@nightheron.gentoo.org \
    --to=catalyst@nightheron.gentoo.org \
    --cc=gentoo-releng-autobuilds@lists.gentoo.org \
    --cc=releng@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox