public inbox for gentoo-releng-autobuilds@lists.gentoo.org
 help / color / mirror / Atom feed
From: catalyst@guppy.ia64.dev.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [ia64-auto] Catalyst fatal build error - stage3.spec
Date: Wed, 14 Feb 2018 09:21:19 +0000	[thread overview]
Message-ID: <20180214154506.6F692E09A4@pigeon.gentoo.org> (raw)




Envscript support enabled.
Using target: stage3
Building natively for ia64
Source path set to /home/catalyst/tmp/default/stage2-ia64-20180214T031002Z/
	If this is not desired, remove this directory or turn off
	seedcache in the options of catalyst.conf the source path
	will then be /home/catalyst/builds/default/stage2-ia64-20180214T031002Z.tar.bz2

Caching snapshot to /home/catalyst/snapshot_cache/20180214T031002Z/
The autoresume path is /home/catalyst/tmp/default/.autoresume-stage3-ia64-20180214T031002Z/
Location of the package cache is /home/catalyst/packages/default/stage3-ia64-20180214T031002Z/
Checking for processes running in chroot and killing them.
Removing AutoResume Points: ...
Emptying directory /home/catalyst/tmp/default/.autoresume-stage3-ia64-20180214T031002Z/
--- Running action sequence: unpack

Starting rsync from /home/catalyst/tmp/default/stage2-ia64-20180214T031002Z/
to /home/catalyst/tmp/default/stage3-ia64-20180214T031002Z/ (This may take some time) ...

--- Running action sequence: unpack_snapshot
Valid snapshot cache, skipping unpack of portage tree...
--- Running action sequence: setup_confdir
Configuring /etc/portage...
--- Running action sequence: portage_overlay
--- Running action sequence: base_dirs
--- 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: run_local
Copying stage3-chroot.sh to /tmp
copying stage3-chroot.sh to /home/catalyst/tmp/default/stage3-ia64-20180214T031002Z//tmp
copying chroot-functions.sh to /home/catalyst/tmp/default/stage3-ia64-20180214T031002Z//tmp
Ensure the file has the executable bit set
Running stage3-chroot.sh in chroot /home/catalyst/tmp/default/stage3-ia64-20180214T031002Z/
>>> Regenerating /etc/ld.so.cache...
Updating portage with USE=""
emerge --quiet --usepkg --buildpkg --newuse --oneshot --update --newuse sys-apps/portage
>>> Verifying ebuild manifests
>>> Emerging (1 of 16) app-misc/mime-types-9::gentoo
>>> Installing (1 of 16) app-misc/mime-types-9::gentoo
>>> Emerging (2 of 16) app-misc/c_rehash-1.7-r1::gentoo
>>> Installing (2 of 16) app-misc/c_rehash-1.7-r1::gentoo
>>> Emerging (3 of 16) sys-apps/install-xattr-0.5::gentoo
>>> Installing (3 of 16) sys-apps/install-xattr-0.5::gentoo
>>> Emerging (4 of 16) sys-apps/debianutils-4.8.3::gentoo
>>> Installing (4 of 16) sys-apps/debianutils-4.8.3::gentoo
>>> Emerging (5 of 16) app-arch/unzip-6.0_p21-r2::gentoo
>>> Installing (5 of 16) app-arch/unzip-6.0_p21-r2::gentoo
>>> Emerging (6 of 16) sys-apps/attr-2.4.47-r2::gentoo
>>> Installing (6 of 16) sys-apps/attr-2.4.47-r2::gentoo
>>> Emerging (7 of 16) sys-libs/gdbm-1.13-r2::gentoo
>>> Installing (7 of 16) sys-libs/gdbm-1.13-r2::gentoo
>>> Emerging (8 of 16) dev-libs/openssl-1.0.2n::gentoo
>>> Installing (8 of 16) dev-libs/openssl-1.0.2n::gentoo
>>> Emerging (9 of 16) app-misc/ca-certificates-20161130.3.30.2::gentoo
>>> Installing (9 of 16) app-misc/ca-certificates-20161130.3.30.2::gentoo
>>> Emerging (10 of 16) dev-lang/python-3.5.4-r1::gentoo
>>> Installing (10 of 16) dev-lang/python-3.5.4-r1::gentoo
>>> Emerging (11 of 16) dev-lang/python-2.7.14-r1::gentoo
>>> Installing (11 of 16) dev-lang/python-2.7.14-r1::gentoo
>>> Emerging (12 of 16) dev-python/pyblake2-1.1.0::gentoo
>>> Installing (12 of 16) dev-python/pyblake2-1.1.0::gentoo
>>> Emerging (13 of 16) dev-python/setuptools-36.7.2::gentoo
>>> Installing (13 of 16) dev-python/setuptools-36.7.2::gentoo
>>> Emerging (14 of 16) dev-python/certifi-2017.4.17::gentoo
>>> Installing (14 of 16) dev-python/certifi-2017.4.17::gentoo
>>> Emerging (15 of 16) dev-python/pyxattr-0.5.5::gentoo
>>> Installing (15 of 16) dev-python/pyxattr-0.5.5::gentoo
>>> Emerging (16 of 16) sys-apps/portage-2.3.19-r1::gentoo
>>> Installing (16 of 16) sys-apps/portage-2.3.19-r1::gentoo
 * Messages for package app-misc/ca-certificates-20161130.3.30.2:
 * You should run update-ca-certificates manually after etc-update
 * To prevent applications relying on system's trusted root certificate store
 * from using CAs where at least one major browser vendor Gentoo is following
 * has decided to apply trust level restrictions, the following
 * certificate(s) were removed:
 * mozilla/CA_WoSign_ECC_Root.crt removed; see https://bugs.gentoo.org/598072 for details
 * mozilla/WoSign.crt removed; see https://bugs.gentoo.org/598072 for details
 * mozilla/StartCom_Certification_Authority_2.crt removed; see https://bugs.gentoo.org/598072 for details
 * mozilla/StartCom_Certification_Authority.crt removed; see https://bugs.gentoo.org/598072 for details
 * mozilla/StartCom_Certification_Authority_G2.crt removed; see https://bugs.gentoo.org/598072 for details
 * mozilla/WoSign_China.crt removed; see https://bugs.gentoo.org/598072 for details
 * mozilla/Certification_Authority_of_WoSign_G2.crt removed; see https://bugs.gentoo.org/598072 for details
 * Messages for package dev-python/pyblake2-1.1.0:
 * Could not find a UTF-8 locale. This may trigger build failures in
 * some python packages. Please ensure that a UTF-8 locale is listed in
 * /etc/locale.gen and run locale-gen.
 * Messages for package dev-python/setuptools-36.7.2:
 * Could not find a UTF-8 locale. This may trigger build failures in
 * some python packages. Please ensure that a UTF-8 locale is listed in
 * /etc/locale.gen and run locale-gen.
 * Messages for package dev-python/certifi-2017.4.17:
 * Could not find a UTF-8 locale. This may trigger build failures in
 * some python packages. Please ensure that a UTF-8 locale is listed in
 * /etc/locale.gen and run locale-gen.
 * Messages for package dev-python/pyxattr-0.5.5:
 * Could not find a UTF-8 locale. This may trigger build failures in
 * some python packages. Please ensure that a UTF-8 locale is listed in
 * /etc/locale.gen and run locale-gen.
 * Messages for package sys-apps/portage-2.3.19-r1:
 * Could not find a UTF-8 locale. This may trigger build failures in
 * some python packages. Please ensure that a UTF-8 locale is listed in
 * /etc/locale.gen and run locale-gen.












emerge --quiet --usepkg --buildpkg --newuse -e @system
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-fs/static-dev-0.1

 * We have detected that you currently use udev or devfs or devtmpfs
 * and this ebuild cannot install to the same mount-point.
 * ERROR: sys-fs/static-dev-0.1::gentoo failed (pretend phase):
 *   Cannot install on udev/devfs tmpfs.
 * 
 * Call stack:
 *               ebuild.sh, line 124:  Called pkg_pretend
 *   static-dev-0.1.ebuild, line  38:  Called abort
 *   static-dev-0.1.ebuild, line  22:  Called die
 * The specific snippet of code:
 *   	die "Cannot install on udev/devfs tmpfs."
 * 
 * If you need support, post the output of `emerge --info '=sys-fs/static-dev-0.1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-fs/static-dev-0.1::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-fs/static-dev-0.1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-fs/static-dev-0.1/temp/die.env'.
 * Working directory: '/var/tmp/portage/sys-fs/static-dev-0.1/homedir'
 * S: '/var/tmp/portage/sys-fs/static-dev-0.1/work/static-dev-0.1'
>>> 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
 * Messages for package sys-fs/static-dev-0.1:
 * We have detected that you currently use udev or devfs or devtmpfs
 * and this ebuild cannot install to the same mount-point.
 * ERROR: sys-fs/static-dev-0.1::gentoo failed (pretend phase):
 *   Cannot install on udev/devfs tmpfs.
 * 
 * Call stack:
 *               ebuild.sh, line 124:  Called pkg_pretend
 *   static-dev-0.1.ebuild, line  38:  Called abort
 *   static-dev-0.1.ebuild, line  22:  Called die
 * The specific snippet of code:
 *   	die "Cannot install on udev/devfs tmpfs."
 * 
 * If you need support, post the output of `emerge --info '=sys-fs/static-dev-0.1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-fs/static-dev-0.1::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-fs/static-dev-0.1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-fs/static-dev-0.1/temp/die.env'.
 * Working directory: '/var/tmp/portage/sys-fs/static-dev-0.1/homedir'
 * S: '/var/tmp/portage/sys-fs/static-dev-0.1/work/static-dev-0.1'



!!! catalyst: run script failed.


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1244, in run_local
    "run script failed.",env=self.env)
  File "/usr/lib/catalyst/modules/catalyst_support.py", line 541, in cmd
    raise CatalystError,myexc
CatalystError
None

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

Traceback (most recent call last):
File "/usr/lib/catalyst/catalyst", line 218, in build_target
    mytarget.run()
File "modules/generic_stage_target.py", line 1304, in run
    apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1249, in run_local
    raise CatalystError,"Stage build aborting due to error."
CatalystError
!!! catalyst: Error encountered during run of target stage3
Catalyst aborting....
lockfile does not exist '/home/catalyst/tmp/default/stage3-ia64-20180214T031002Z/.catalyst_lock'
Command exited with non-zero status 1
1903.03user 185.05system 25:55.65elapsed 134%CPU (0avgtext+0avgdata 207552maxresident)k
0inputs+0outputs (0major+34210655minor)pagefaults 0swaps



Full build log at /tmp/catalyst-auto.20180214T031002Z.iZKowv/log/stage3.log


             reply	other threads:[~2018-02-14 15:45 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14  9:21 catalyst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-30  7:20 [gentoo-releng-autobuilds] [ia64-auto] Catalyst fatal build error - stage3.spec catalyst
2019-09-29  7:35 catalyst
2019-09-21  6:48 catalyst
2019-09-20  6:53 catalyst
2019-09-19  6:43 catalyst
2019-09-18  6:47 catalyst
2019-09-17  6:52 catalyst
2019-09-16  7:39 catalyst
2019-09-15  6:52 catalyst
2019-09-14  6:48 catalyst
2019-09-13  6:46 catalyst
2019-09-13  1:27 catalyst
2019-09-12  6:51 catalyst
2019-09-11  6:52 catalyst
2019-09-10  6:48 catalyst
2019-09-09  7:15 catalyst
2019-09-08  6:52 catalyst
2019-09-07  6:49 catalyst
2019-09-06  6:47 catalyst
2018-05-22 13:11 catalyst
2018-02-19  9:47 catalyst
2018-02-18 10:50 catalyst
2018-02-17  9:38 catalyst
2018-02-16  9:23 catalyst
2018-02-15  9:22 catalyst
2018-02-13  9:36 catalyst
2018-02-12  9:22 catalyst
2018-01-30  7:21 catalyst
2018-01-29 12:57 catalyst
2018-01-28 13:11 catalyst
2016-02-23 13:33 catalyst
2016-02-16 12:59 catalyst
2016-02-09 13:05 catalyst
2016-02-02 13:01 catalyst
2016-01-26 12:48 catalyst
2016-01-12 12:19 catalyst
2015-02-24  7:28 catalyst
2013-08-28  1:09 catalyst
2012-07-17 15:11 catalyst
2011-05-17 18:58 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=20180214154506.6F692E09A4@pigeon.gentoo.org \
    --to=catalyst@guppy.ia64.dev.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