From: catalyst@thor.jmbsvicetto.name
To: jmbsvicetto@gmail.com,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [x86-auto] Catalyst fatal build error - stage3.spec
Date: Wed, 21 Feb 2018 04:27:18 +0000 (UTC) [thread overview]
Message-ID: <20180221042718.CF94B600C5@thor.jmbsvicetto.name> (raw)
*** Running command: time catalyst -a -c /etc/catalyst/release/x86-auto.conf -f stage3.spec
21 Feb 2018 04:25:28 UTC: NOTICE : Loading configuration file: /etc/catalyst/release/x86-auto.conf
21 Feb 2018 04:25:28 UTC: NOTICE : conf_values[options] = {'preserve_libs', 'pkgcache', 'bindist', 'clear-autoresume'}
21 Feb 2018 04:25:28 UTC: NOTICE : Processing spec file: stage3.spec
21 Feb 2018 04:25:29 UTC: NOTICE : Using target: stage3
21 Feb 2018 04:25:29 UTC: NOTICE : Source file specification matching setting is: loose
21 Feb 2018 04:25:29 UTC: NOTICE : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
21 Feb 2018 04:25:29 UTC: NOTICE : Source path set to /home/release/buildroot/x86-dev/builds/default/stage2-i486-20180221T030003Z.tar.xz
21 Feb 2018 04:25:29 UTC: NOTICE : --- Running action sequence: unpack
21 Feb 2018 04:25:29 UTC: NOTICE : Clearing the chroot path ...
21 Feb 2018 04:25:29 UTC: NOTICE : Emptying directory: /home/release/buildroot/x86-dev/tmp/default/stage3-i486-20180221T030003Z
21 Feb 2018 04:25:29 UTC: NOTICE : Starting auto from /home/release/buildroot/x86-dev/builds/default/stage2-i486-20180221T030003Z.tar.xz
21 Feb 2018 04:25:29 UTC: NOTICE : to /home/release/buildroot/x86-dev/tmp/default/stage3-i486-20180221T030003Z (this may take some time) ..
21 Feb 2018 04:25:31 UTC: NOTICE : --- Running action sequence: unpack_snapshot
21 Feb 2018 04:25:31 UTC: NOTICE : Unpacking portage tree (this can take a long time) ...
21 Feb 2018 04:25:38 UTC: NOTICE : --- Running action sequence: setup_confdir
21 Feb 2018 04:25:38 UTC: NOTICE : --- Running action sequence: portage_overlay
21 Feb 2018 04:25:38 UTC: NOTICE : --- Running action sequence: base_dirs
21 Feb 2018 04:25:38 UTC: NOTICE : --- Running action sequence: bind
21 Feb 2018 04:25:38 UTC: NOTICE : --- Running action sequence: chroot_setup
21 Feb 2018 04:25:38 UTC: NOTICE : Setting up chroot...
21 Feb 2018 04:25:38 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
21 Feb 2018 04:25:38 UTC: WARNING : If your build fails look here first as the possible problem.
21 Feb 2018 04:25:38 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
21 Feb 2018 04:25:38 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
21 Feb 2018 04:25:38 UTC: WARNING : You have been warned.
21 Feb 2018 04:25:38 UTC: NOTICE : Writing the stage make.conf to: /home/release/buildroot/x86-dev/tmp/default/stage3-i486-20180221T030003Z/etc/portage/make.conf
21 Feb 2018 04:25:38 UTC: NOTICE : STICKY-CONFIG is enabled
21 Feb 2018 04:25:38 UTC: NOTICE : --- Running action sequence: setup_environment
21 Feb 2018 04:25:38 UTC: NOTICE : --- Running action sequence: run_local
Copying stage3-chroot.sh to /tmp
copying stage3-chroot.sh to /home/release/buildroot/x86-dev/tmp/default/stage3-i486-20180221T030003Z/tmp
copying chroot-functions.sh to /home/release/buildroot/x86-dev/tmp/default/stage3-i486-20180221T030003Z/tmp
Ensure the file has the executable bit set
Running stage3-chroot.sh in chroot:
setarch linux32 chroot /home/release/buildroot/x86-dev/tmp/default/stage3-i486-20180221T030003Z /tmp/stage3-chroot.sh
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot --update --newuse sys-apps/portage
>>> Emerging binary (1 of 5) sys-apps/install-xattr-0.5::gentoo
>>> Installing (1 of 5) sys-apps/install-xattr-0.5::gentoo
>>> Emerging binary (2 of 5) sys-apps/attr-2.4.47-r2::gentoo
>>> Installing (2 of 5) sys-apps/attr-2.4.47-r2::gentoo
>>> Emerging binary (3 of 5) dev-python/pyxattr-0.5.5::gentoo
>>> Installing (3 of 5) dev-python/pyxattr-0.5.5::gentoo
>>> Emerging binary (4 of 5) dev-python/pyblake2-1.1.0::gentoo
>>> Installing (4 of 5) dev-python/pyblake2-1.1.0::gentoo
>>> Emerging binary (5 of 5) sys-apps/portage-2.3.24-r1::gentoo
>>> Installing (5 of 5) sys-apps/portage-2.3.24-r1::gentoo
emerge --quiet --usepkg --buildpkg --newuse -e --update --deep --with-bdeps=y @system
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-libs/glibc-2.25-r10
>>> Running pre-merge checks for sys-devel/gcc-6.4.0-r1
>>> Running pre-merge checks for sys-libs/pam-1.2.1-r2
>>> Running pre-merge checks for net-misc/openssh-7.5_p1-r4
>>> Running pre-merge checks for sys-fs/eudev-3.2.5
*
* As of 2013-01-29, eudev-3.2.5 provides the new interface renaming functionality,
* as described in the URL below:
* https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
*
* This functionality is enabled BY DEFAULT because eudev has no means of synchronizing
* between the default or user-modified choice of sys-fs/udev. If you wish to disable
* this new iface naming, please be sure that /etc/udev/rules.d/80-net-name-slot.rules
* exists: touch /etc/udev/rules.d/80-net-name-slot.rules
*
>>> Emerging binary (1 of 187) virtual/libintl-0-r2::gentoo
>>> Installing (1 of 187) virtual/libintl-0-r2::gentoo
>>> Emerging binary (2 of 187) sys-libs/ncurses-6.0-r1::gentoo
>>> Installing (2 of 187) sys-libs/ncurses-6.0-r1::gentoo
>>> Emerging binary (3 of 187) dev-lang/python-exec-2.4.5::gentoo
>>> Installing (3 of 187) dev-lang/python-exec-2.4.5::gentoo
>>> Emerging binary (4 of 187) app-arch/bzip2-1.0.6-r8::gentoo
>>> Installing (4 of 187) app-arch/bzip2-1.0.6-r8::gentoo
>>> Emerging binary (5 of 187) sys-devel/gnuconfig-20170101::gentoo
>>> Installing (5 of 187) sys-devel/gnuconfig-20170101::gentoo
>>> Emerging binary (6 of 187) sys-apps/gentoo-functions-0.12::gentoo
>>> Installing (6 of 187) sys-apps/gentoo-functions-0.12::gentoo
>>> Emerging binary (7 of 187) virtual/libiconv-0-r2::gentoo
>>> Installing (7 of 187) virtual/libiconv-0-r2::gentoo
>>> Emerging binary (8 of 187) app-misc/c_rehash-1.7-r1::gentoo
>>> Installing (8 of 187) app-misc/c_rehash-1.7-r1::gentoo
>>> Emerging binary (9 of 187) app-misc/mime-types-9::gentoo
>>> Installing (9 of 187) app-misc/mime-types-9::gentoo
>>> Emerging binary (10 of 187) app-arch/gzip-1.8::gentoo
>>> Installing (10 of 187) app-arch/gzip-1.8::gentoo
>>> Emerging binary (11 of 187) app-misc/editor-wrapper-4::gentoo
>>> Installing (11 of 187) app-misc/editor-wrapper-4::gentoo
>>> Emerging binary (12 of 187) net-libs/libmnl-1.0.4::gentoo
>>> Installing (12 of 187) net-libs/libmnl-1.0.4::gentoo
>>> Emerging binary (13 of 187) sys-apps/debianutils-4.8.3::gentoo
>>> Installing (13 of 187) sys-apps/debianutils-4.8.3::gentoo
>>> Emerging binary (14 of 187) app-text/manpager-1::gentoo
>>> Installing (14 of 187) app-text/manpager-1::gentoo
>>> Emerging (15 of 187) sys-apps/opentmpfiles-0.1.3::gentoo
>>> Failed to emerge sys-apps/opentmpfiles-0.1.3, Log file:
>>> '/var/tmp/portage/sys-apps/opentmpfiles-0.1.3/temp/build.log'
* Package: sys-apps/opentmpfiles-0.1.3
* Repository: gentoo
* USE: abi_x86_32 elibc_glibc kernel_linux userland_GNU x86
* FEATURES: preserve-libs sandbox userpriv usersandbox
gzip: error while loading shared libraries: cannot make segment writable for relocation: Permission denied
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
* ERROR: sys-apps/opentmpfiles-0.1.3::gentoo failed (unpack phase):
* unpack: failure unpacking opentmpfiles-0.1.3.tar.gz
*
* Call stack:
* ebuild.sh, line 124: Called src_unpack
* environment, line 396: Called default
* phase-functions.sh, line 853: Called default_src_unpack
* phase-functions.sh, line 880: Called __eapi0_src_unpack
* phase-helpers.sh, line 740: Called unpack 'opentmpfiles-0.1.3.tar.gz'
* phase-helpers.sh, line 387: Called __unpack_tar 'gzip -d'
* phase-helpers.sh, line 318: Called __assert_sigpipe_ok 'unpack: failure unpacking opentmpfiles-0.1.3.tar.gz'
* isolated-functions.sh, line 41: Called __helpers_die 'unpack: failure unpacking opentmpfiles-0.1.3.tar.gz'
* isolated-functions.sh, line 117: Called die
* The specific snippet of code:
* die "$@"
*
* If you need support, post the output of `emerge --info '=sys-apps/opentmpfiles-0.1.3::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/opentmpfiles-0.1.3::gentoo'`.
* The complete build log is located at '/var/tmp/portage/sys-apps/opentmpfiles-0.1.3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/opentmpfiles-0.1.3/temp/environment'.
* Working directory: '/var/tmp/portage/sys-apps/opentmpfiles-0.1.3/work'
* S: '/var/tmp/portage/sys-apps/opentmpfiles-0.1.3/work/opentmpfiles-0.1.3'
* Messages for package sys-fs/eudev-3.2.5:
*
* As of 2013-01-29, eudev-3.2.5 provides the new interface renaming functionality,
* as described in the URL below:
* https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
*
* This functionality is enabled BY DEFAULT because eudev has no means of synchronizing
* between the default or user-modified choice of sys-fs/udev. If you wish to disable
* this new iface naming, please be sure that /etc/udev/rules.d/80-net-name-slot.rules
* exists: touch /etc/udev/rules.d/80-net-name-slot.rules
*
* Messages for package sys-apps/opentmpfiles-0.1.3:
* ERROR: sys-apps/opentmpfiles-0.1.3::gentoo failed (unpack phase):
* unpack: failure unpacking opentmpfiles-0.1.3.tar.gz
*
* Call stack:
* ebuild.sh, line 124: Called src_unpack
* environment, line 396: Called default
* phase-functions.sh, line 853: Called default_src_unpack
* phase-functions.sh, line 880: Called __eapi0_src_unpack
* phase-helpers.sh, line 740: Called unpack 'opentmpfiles-0.1.3.tar.gz'
* phase-helpers.sh, line 387: Called __unpack_tar 'gzip -d'
* phase-helpers.sh, line 318: Called __assert_sigpipe_ok 'unpack: failure unpacking opentmpfiles-0.1.3.tar.gz'
* isolated-functions.sh, line 41: Called __helpers_die 'unpack: failure unpacking opentmpfiles-0.1.3.tar.gz'
* isolated-functions.sh, line 117: Called die
* The specific snippet of code:
* die "$@"
*
* If you need support, post the output of `emerge --info '=sys-apps/opentmpfiles-0.1.3::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/opentmpfiles-0.1.3::gentoo'`.
* The complete build log is located at '/var/tmp/portage/sys-apps/opentmpfiles-0.1.3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/opentmpfiles-0.1.3/temp/environment'.
* Working directory: '/var/tmp/portage/sys-apps/opentmpfiles-0.1.3/work'
* S: '/var/tmp/portage/sys-apps/opentmpfiles-0.1.3/work/opentmpfiles-0.1.3'
21 Feb 2018 04:27:18 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage3/stage3-controller.sh', 'run']) exited 1
21 Feb 2018 04:27:18 UTC: ERROR : CatalystError: Stage build aborting due to error.
21 Feb 2018 04:27:18 UTC: ERROR : Exception running action sequence run_local
Traceback (most recent call last):
File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1354, in run_local
env=self.env)
File "/usr/lib64/python3.5/site-packages/catalyst/support.py", line 54, in cmd
print_traceback=False)
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage3/stage3-controller.sh', 'run']) exited 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1454, in run
getattr(self, x)()
File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1363, in run_local
print_traceback=False)
catalyst.support.CatalystError: Stage build aborting due to error.
21 Feb 2018 04:27:18 UTC: NOTICE : Cleaning up... Running unbind()
Command exited with non-zero status 2
65.52user 22.77system 1:49.89elapsed 80%CPU (0avgtext+0avgdata 317500maxresident)k
16inputs+2285752outputs (0major+3000755minor)pagefaults 0swaps
Full build log at /home/release/tmp/run/catalyst-auto.20180221T030003Z.Pb6BBV/log/stage3.log
next reply other threads:[~2018-02-21 4:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 4:27 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-15 2:57 [gentoo-releng-autobuilds] [x86-auto] Catalyst fatal build error - stage3.spec catalyst
2020-05-13 4:40 catalyst
2020-03-17 14:07 catalyst
2018-04-18 4:11 catalyst
2018-04-11 4:12 catalyst
2018-04-04 4:11 catalyst
2018-02-14 4:33 catalyst
2018-02-07 5:21 catalyst
2018-01-31 5:39 catalyst
2018-01-17 5:14 catalyst
2018-01-10 3:43 catalyst
2018-01-03 5:23 catalyst
2017-12-27 23:08 catalyst
2017-12-27 5:42 catalyst
2017-12-20 5:40 catalyst
2015-11-25 5:49 catalyst
2015-07-29 6:05 catalyst
2015-03-18 5:28 catalyst
2014-12-10 6:38 catalyst
2012-08-28 10:46 catalyst
2012-01-17 11:08 catalyst
2011-12-27 9:05 catalyst
2011-12-20 9:06 catalyst
2011-05-10 9:04 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=20180221042718.CF94B600C5@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