From: catalyst@thor.jmbsvicetto.name
To: jmbsvicetto@gmail.com,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [amd64-auto] Catalyst non-fatal build error - hardened/stage4-nomultilib-minimal.spec
Date: Tue, 16 Jul 2019 03:40:11 +0000 (UTC) [thread overview]
Message-ID: <20190716034013.5EBC7603D4@thor.jmbsvicetto.name> (raw)
*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-auto.conf -f hardened/stage4-nomultilib-minimal.spec
16 Jul 2019 03:39:09 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/amd64-auto.conf
16 Jul 2019 03:39:09 UTC: NOTICE : conf_values[options] = {'pkgcache', 'clear-autoresume', 'preserve_libs', 'bindist'}
16 Jul 2019 03:39:09 UTC: NOTICE : Processing spec file: hardened/stage4-nomultilib-minimal.spec
16 Jul 2019 03:39:09 UTC: NOTICE : Using target: stage4
16 Jul 2019 03:39:09 UTC: NOTICE : Source file specification matching setting is: loose
16 Jul 2019 03:39:09 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
16 Jul 2019 03:39:09 UTC: NOTICE : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.xz
16 Jul 2019 03:39:09 UTC: NOTICE : --- Running action sequence: unpack
16 Jul 2019 03:39:09 UTC: NOTICE : Clearing the chroot path ...
16 Jul 2019 03:39:09 UTC: NOTICE : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-nomultilib-20190716T030312Z
16 Jul 2019 03:39:09 UTC: NOTICE : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened+nomultilib-latest.tar.xz
16 Jul 2019 03:39:09 UTC: NOTICE : to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-nomultilib-20190716T030312Z (this may take some time) ..
16 Jul 2019 03:39:13 UTC: NOTICE : --- Running action sequence: unpack_snapshot
16 Jul 2019 03:39:13 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
16 Jul 2019 03:39:42 UTC: NOTICE : --- Running action sequence: config_profile_link
16 Jul 2019 03:39:42 UTC: NOTICE : --- Running action sequence: setup_confdir
16 Jul 2019 03:39:42 UTC: NOTICE : --- Running action sequence: portage_overlay
16 Jul 2019 03:39:42 UTC: NOTICE : --- Running action sequence: bind
16 Jul 2019 03:39:42 UTC: NOTICE : --- Running action sequence: chroot_setup
16 Jul 2019 03:39:42 UTC: NOTICE : Setting up chroot...
16 Jul 2019 03:39:42 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
16 Jul 2019 03:39:42 UTC: WARNING : If your build fails look here first as the possible problem.
16 Jul 2019 03:39:42 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
16 Jul 2019 03:39:42 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
16 Jul 2019 03:39:42 UTC: WARNING : You have been warned.
16 Jul 2019 03:39:42 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-nomultilib-20190716T030312Z/etc/portage/make.conf
16 Jul 2019 03:39:42 UTC: NOTICE : STICKY-CONFIG is enabled
16 Jul 2019 03:39:42 UTC: NOTICE : --- Running action sequence: setup_environment
16 Jul 2019 03:39:42 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-nomultilib-20190716T030312Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-nomultilib-20190716T030312Z/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-nomultilib-20190716T030312Z /tmp/stage4-chroot.sh
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --binpkg-respect-use=y --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 --binpkg-respect-use=y --newuse -u @system
>>> Emerging binary (1 of 3) sys-apps/busybox-1.29.3::gentoo
>>> Failed to emerge sys-apps/busybox-1.29.3, Log file:
>>> '/home/release/tmp/logs/sys-apps:busybox-1.29.3:20190716-034010.log'
>>> Extracting info
* Package: sys-apps/busybox-1.29.3
* Repository: gentoo
* USE: kernel_linux userland_GNU elibc_glibc amd64 ipv6 abi_x86_64
* FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox
* Please follow the instructions in the news item:
* 2019-06-05-amd64-17-1-profiles-are-now-stable
* or choose the 17.0 profile.
* ERROR: sys-apps/busybox-1.29.3::gentoo failed (setup phase):
* ERROR: 17.1 migration has not been performed!!
*
* Call stack:
* ebuild.sh, line 780: Called __ebuild_main 'setup'
* phase-functions.sh, line 988: Called __source_all_bashrcs
* ebuild.sh, line 417: Called __try_source '/var/db/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 474: Called __qa_source '/var/db/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 111: Called source '/var/db/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/busybox-1.29.3::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/busybox-1.29.3::gentoo'`.
* The complete build log is located at '/home/release/tmp/logs/sys-apps:busybox-1.29.3:20190716-034010.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/busybox-1.29.3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/busybox-1.29.3/temp/environment'.
* Working directory: '/var/tmp/portage/sys-apps/busybox-1.29.3/homedir'
* S: '/var/tmp/portage/sys-apps/busybox-1.29.3/work/busybox-1.29.3'
* Messages for package sys-apps/busybox-1.29.3:
* Log file: /home/release/tmp/logs/sys-apps:busybox-1.29.3:20190716-034010.log
* Please follow the instructions in the news item:
* 2019-06-05-amd64-17-1-profiles-are-now-stable
* or choose the 17.0 profile.
* ERROR: sys-apps/busybox-1.29.3::gentoo failed (setup phase):
* ERROR: 17.1 migration has not been performed!!
*
* Call stack:
* ebuild.sh, line 780: Called __ebuild_main 'setup'
* phase-functions.sh, line 988: Called __source_all_bashrcs
* ebuild.sh, line 417: Called __try_source '/var/db/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 474: Called __qa_source '/var/db/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 111: Called source '/var/db/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/busybox-1.29.3::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/busybox-1.29.3::gentoo'`.
* The complete build log is located at '/home/release/tmp/logs/sys-apps:busybox-1.29.3:20190716-034010.log'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/busybox-1.29.3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/busybox-1.29.3/temp/environment'.
* Working directory: '/var/tmp/portage/sys-apps/busybox-1.29.3/homedir'
* S: '/var/tmp/portage/sys-apps/busybox-1.29.3/work/busybox-1.29.3'
16 Jul 2019 03:40:11 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'build_packages', 'net-misc/dhcp', 'net-misc/iputils', 'sys-boot/grub', 'sys-apps/gptfdisk', 'sys-apps/iproute2', 'sys-devel/bc', 'sys-power/acpid', 'app-crypt/gentoo-keys']) exited 1
16 Jul 2019 03:40:11 UTC: ERROR : CatalystError: stage4build aborting due to error.
16 Jul 2019 03:40:11 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', 'net-misc/iputils', 'sys-boot/grub', '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.
16 Jul 2019 03:40:11 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
32.90user 4.63system 1:02.56elapsed 59%CPU (0avgtext+0avgdata 351692maxresident)k
576inputs+3680840outputs (0major+363296minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20190716T030312Z.9vULzE/log/hardened_stage4-nomultilib-minimal.log
next reply other threads:[~2019-07-16 3:40 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 3:40 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-28 3:00 [gentoo-releng-autobuilds] [amd64-auto] Catalyst non-fatal build error - hardened/stage4-nomultilib-minimal.spec catalyst
2020-09-21 3:00 catalyst
2020-09-14 3:00 catalyst
2020-09-07 3:00 catalyst
2020-08-31 3:00 catalyst
2020-08-24 3:00 catalyst
2020-08-17 3:00 catalyst
2020-08-10 3:02 catalyst
2020-08-03 3:00 catalyst
2020-07-27 3:00 catalyst
2020-07-20 3:00 catalyst
2020-07-13 3:00 catalyst
2020-07-06 3:00 catalyst
2020-06-29 5:05 catalyst
2020-06-29 3:00 catalyst
2020-06-22 3:00 catalyst
2020-06-18 0:57 catalyst
2020-06-15 3:00 catalyst
2020-06-15 0:59 catalyst
2020-06-08 3:00 catalyst
2020-06-01 3:00 catalyst
2020-05-25 3:00 catalyst
2020-05-18 3:00 catalyst
2020-05-12 21:56 catalyst
2020-05-11 16:26 catalyst
2020-05-11 11:35 catalyst
2020-05-11 3:01 catalyst
2020-05-07 13:03 catalyst
2020-05-04 3:13 catalyst
2020-04-27 3:00 catalyst
2020-04-13 4:01 catalyst
2020-04-06 3:58 catalyst
2020-03-30 3:59 catalyst
2020-03-23 3:57 catalyst
2020-03-16 3:56 catalyst
2020-03-09 3:57 catalyst
2020-03-02 3:54 catalyst
2020-02-24 3:44 catalyst
2020-02-17 3:42 catalyst
2020-02-10 3:37 catalyst
2020-02-03 3:38 catalyst
2020-01-27 3:38 catalyst
2020-01-20 3:39 catalyst
2020-01-13 3:40 catalyst
2019-12-30 6:15 catalyst
2019-12-09 1:58 catalyst
2019-07-16 3:02 catalyst
2019-07-16 2:56 catalyst
2019-07-16 2:51 catalyst
2019-05-31 11:23 catalyst
2019-05-29 20:00 catalyst
2019-05-27 14:05 catalyst
2018-09-25 3:03 catalyst
2018-09-24 20:07 catalyst
2018-08-14 16:27 catalyst
2018-08-12 11:37 catalyst
2018-08-11 9:51 catalyst
2018-08-11 9:48 catalyst
2018-07-16 22:32 catalyst
2018-07-16 22:31 catalyst
2018-07-02 11:49 catalyst
2018-06-28 7:22 catalyst
2018-06-25 18:58 catalyst
2018-06-18 8:15 catalyst
2018-05-30 2:38 catalyst
2018-05-30 2:37 catalyst
2018-05-30 2:37 catalyst
2018-02-21 0:02 catalyst
2018-02-06 10:18 catalyst
2018-02-03 22:12 catalyst
2018-01-29 4:43 catalyst
2018-01-22 5:11 catalyst
2018-01-15 18:15 catalyst
2018-01-07 17:33 catalyst
2018-01-05 12:20 catalyst
2018-01-04 13:40 catalyst
2018-01-01 11:17 catalyst
2017-12-28 18:05 catalyst
2017-12-26 21:58 catalyst
2017-12-24 21:59 catalyst
2017-12-23 3:45 catalyst
2017-12-21 21:58 catalyst
2017-12-19 21:54 catalyst
2017-12-17 22:45 catalyst
2017-12-15 7:26 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=20190716034013.5EBC7603D4@thor.jmbsvicetto.name \
--to=catalyst@thor.jmbsvicetto.name \
--cc=gentoo-releng-autobuilds@lists.gentoo.org \
--cc=jmbsvicetto@gmail.com \
/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