From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 9C9E9138334 for ; Tue, 11 Jun 2019 01:33:38 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CBDFAE0848; Tue, 11 Jun 2019 01:33:36 +0000 (UTC) Received: from thor.jmbsvicetto.name (thor.jmbsvicetto.name [136.243.173.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 88B55E0848 for ; Tue, 11 Jun 2019 01:33:36 +0000 (UTC) Received: by thor.jmbsvicetto.name (Postfix, from userid 0) id 80AEC60B2B; Tue, 11 Jun 2019 01:33:34 +0000 (UTC) From: catalyst@thor.jmbsvicetto.name To: jmbsvicetto@gmail.com,gentoo-releng-autobuilds@lists.gentoo.org Subject: [gentoo-releng-autobuilds] [amd64-experimental] Catalyst non-fatal build error - hardened/stage4-minimal.spec Message-Id: <20190611013334.80AEC60B2B@thor.jmbsvicetto.name> Date: Tue, 11 Jun 2019 01:33:34 +0000 (UTC) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Release Engineering Autobuilds X-BeenThere: gentoo-releng-autobuilds@gentoo.org X-BeenThere: gentoo-releng-autobuilds@lists.gentoo.org Reply-To: gentoo-releng-autobuilds@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply X-Archives-Salt: 0d43dd45-19be-4174-b39c-1713dc2577fe X-Archives-Hash: 205f266a0a8f9d682d20bb96c9cff02a *** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f hardened/stage4-minimal.spec 11 Jun 2019 01:32:55 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf 11 Jun 2019 01:32:55 UTC: NOTICE : conf_values[options] = {'pkgcache', 'clear-autoresume', 'bindist', 'preserve_libs'} 11 Jun 2019 01:32:55 UTC: NOTICE : Processing spec file: hardened/stage4-minimal.spec 11 Jun 2019 01:32:55 UTC: NOTICE : Using target: stage4 11 Jun 2019 01:32:55 UTC: NOTICE : Source file specification matching setting is: loose 11 Jun 2019 01:32:55 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz'] 11 Jun 2019 01:32:55 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.xz 11 Jun 2019 01:32:55 UTC: NOTICE : --- Running action sequence: unpack 11 Jun 2019 01:32:55 UTC: NOTICE : Clearing the chroot path ... 11 Jun 2019 01:32:55 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190611T012607Z 11 Jun 2019 01:32:55 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-latest.tar.xz 11 Jun 2019 01:32:55 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190611T012607Z (this may take some time) .. 11 Jun 2019 01:32:59 UTC: NOTICE : --- Running action sequence: unpack_snapshot 11 Jun 2019 01:32:59 UTC: NOTICE : Unpacking portage tree (this can take a long time) ... 11 Jun 2019 01:33:27 UTC: NOTICE : --- Running action sequence: config_profile_link 11 Jun 2019 01:33:27 UTC: NOTICE : --- Running action sequence: setup_confdir 11 Jun 2019 01:33:27 UTC: NOTICE : --- Running action sequence: portage_overlay 11 Jun 2019 01:33:27 UTC: NOTICE : --- Running action sequence: bind 11 Jun 2019 01:33:27 UTC: NOTICE : --- Running action sequence: chroot_setup 11 Jun 2019 01:33:27 UTC: NOTICE : Setting up chroot... 11 Jun 2019 01:33:27 UTC: WARNING : Overriding certain env variables may cause catastrophic failure. 11 Jun 2019 01:33:27 UTC: WARNING : If your build fails look here first as the possible problem. 11 Jun 2019 01:33:27 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables. 11 Jun 2019 01:33:27 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all. 11 Jun 2019 01:33:27 UTC: WARNING : You have been warned. 11 Jun 2019 01:33:27 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190611T012607Z/etc/portage/make.conf 11 Jun 2019 01:33:27 UTC: NOTICE : STICKY-CONFIG is enabled 11 Jun 2019 01:33:27 UTC: NOTICE : --- Running action sequence: setup_environment 11 Jun 2019 01:33:27 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-20190611T012607Z/tmp copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20190611T012607Z/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-20190611T012607Z /tmp/stage4-chroot.sh >>> Regenerating /etc/ld.so.cache... emerge --quiet --usepkg --buildpkg --binpkg-respect-use=y --newuse --oneshot --update --newuse sys-apps/portage >>> Verifying ebuild manifests >>> Running pre-merge checks for sys-apps/portage-2.3.62-r2 * 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 1) sys-apps/portage-2.3.62-r2::gentoo >>> Failed to emerge sys-apps/portage-2.3.62-r2, Log file: >>> '/home/release/tmp/logs/sys-apps:portage-2.3.62-r2:20190611-013332.log' * Package: sys-apps/portage-2.3.62-r2 * Repository: gentoo * Maintainer: dev-portage@gentoo.org * Upstream: dev-portage@gentoo.org * USE: abi_x86_64 amd64 elibc_glibc ipc kernel_linux native-extensions python_targets_python2_7 python_targets_python3_6 rsync-verify userland_GNU xattr * FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox * Please follow the instructions in the news item: * 2017-12-26-experimental-amd64-17-1-profiles * or choose the 17.0 profile. * ERROR: sys-apps/portage-2.3.62-r2::gentoo failed (setup phase): * ERROR: 17.1 migration has not been performed!! * * Call stack: * ebuild.sh, line 598: Called __source_all_bashrcs * ebuild.sh, line 417: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc' * ebuild.sh, line 474: Called __qa_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc' * ebuild.sh, line 111: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc' * profile.bashrc, line 6: Called die * The specific snippet of code: * die "ERROR: 17.1 migration has not been performed!!" * * If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.62-r2::gentoo'`, * the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.62-r2::gentoo'`. * The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.62-r2:20190611-013332.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.62-r2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.62-r2/temp/die.env'. * Working directory: '/var/tmp/portage/sys-apps/portage-2.3.62-r2/homedir' * S: '/var/tmp/portage/sys-apps/portage-2.3.62-r2/work/portage-2.3.62' * Messages for package sys-apps/portage-2.3.62-r2: * Log file: /home/release/tmp/logs/sys-apps:portage-2.3.62-r2:20190611-013331.log * 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-apps/portage-2.3.62-r2: * Log file: /home/release/tmp/logs/sys-apps:portage-2.3.62-r2:20190611-013332.log * Please follow the instructions in the news item: * 2017-12-26-experimental-amd64-17-1-profiles * or choose the 17.0 profile. * ERROR: sys-apps/portage-2.3.62-r2::gentoo failed (setup phase): * ERROR: 17.1 migration has not been performed!! * * Call stack: * ebuild.sh, line 598: Called __source_all_bashrcs * ebuild.sh, line 417: Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc' * ebuild.sh, line 474: Called __qa_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc' * ebuild.sh, line 111: Called source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc' * profile.bashrc, line 6: Called die * The specific snippet of code: * die "ERROR: 17.1 migration has not been performed!!" * * If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.62-r2::gentoo'`, * the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.62-r2::gentoo'`. * The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.62-r2:20190611-013332.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.62-r2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.62-r2/temp/die.env'. * Working directory: '/var/tmp/portage/sys-apps/portage-2.3.62-r2/homedir' * S: '/var/tmp/portage/sys-apps/portage-2.3.62-r2/work/portage-2.3.62' 11 Jun 2019 01:33:33 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'build_packages', 'net-misc/dhcp', 'sys-boot/grub', 'sys-apps/dmidecode', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-devel/bc', 'sys-power/acpid', 'app-crypt/gentoo-keys']) exited 1 11 Jun 2019 01:33:33 UTC: ERROR : CatalystError: stage4build aborting due to error. 11 Jun 2019 01:33:33 UTC: ERROR : Exception running action sequence build_packages Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1561, in build_packages cmd(command, env=self.env) File "/usr/lib64/python3.6/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', 'net-misc/dhcp', 'sys-boot/grub', 'sys-apps/dmidecode', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-devel/bc', 'sys-power/acpid', 'app-crypt/gentoo-keys']) exited 1 During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1465, in run getattr(self, x)() File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1568, in build_packages "build aborting due to error.") catalyst.support.CatalystError: stage4build aborting due to error. 11 Jun 2019 01:33:33 UTC: NOTICE : Cleaning up... Running unbind() Command exited with non-zero status 2 33.94user 4.45system 0:38.93elapsed 98%CPU (0avgtext+0avgdata 362904maxresident)k 312inputs+3908264outputs (0major+614952minor)pagefaults 0swaps Full build log at /home/release/tmp/run/catalyst-auto.20190611T012607Z.4ssuYw/log/hardened_stage4-minimal.log