[gentoo-releng-autobuilds] [s390-auto] Catalyst fatal build error - stage1.spec

[root]

* Removing dead symlink //usr/share/man/man1/zipdetails.1.bz2
 * Removing dead symlink //usr/share/man/man1/json_pp.1.bz2
 * Removing dead symlink //usr/share/man/man1/corelist.1.bz2
 * Removing dead symlink //usr/share/man/man1/pod2usage.1.bz2
 * Removing dead symlink //usr/share/man/man1/podchecker.1.bz2
 * Removing dead symlink //usr/share/man/man1/podselect.1.bz2
 * Removing dead symlink //usr/share/man/man1/perldoc.1.bz2
 * Removing dead symlink //usr/share/man/man1/prove.1.bz2
 * Removing dead symlink //usr/share/man/man1/pod2man.1.bz2
 * Removing dead symlink //usr/share/man/man1/pod2text.1.bz2
 * Removing dead symlink //usr/share/man/man1/perlpodstyle.1.bz2
 * Messages for package dev-lang/perl-5.20.2:
 * Unable to establish //usr/share/man/man1/ptar.1* symlink
 * Unable to establish //usr/share/man/man1/ptardiff.1* symlink
 * Unable to establish //usr/share/man/man1/ptargrep.1* symlink
 * Unable to establish //usr/share/man/man1/shasum.1* symlink
 * Unable to establish //usr/share/man/man1/cpan.1* symlink
 * Unable to establish //usr/share/man/man1/enc2xs.1* symlink
 * Unable to establish //usr/share/man/man1/piconv.1* symlink
 * Unable to establish //usr/share/man/man1/instmodsh.1* symlink
 * Unable to establish //usr/share/man/man1/xsubpp.1* symlink
 * Unable to establish //usr/share/man/man1/zipdetails.1* symlink
 * Unable to establish //usr/share/man/man1/json_pp.1* symlink
 * Unable to establish //usr/share/man/man1/corelist.1* symlink
 * Unable to establish //usr/share/man/man1/pod2usage.1* symlink
 * Unable to establish //usr/share/man/man1/podchecker.1* symlink
 * Unable to establish //usr/share/man/man1/podselect.1* symlink
 * Unable to establish //usr/share/man/man1/perldoc.1* symlink
 * Unable to establish //usr/share/man/man1/prove.1* symlink
 * Unable to establish //usr/share/man/man1/pod2man.1* symlink
 * Unable to establish //usr/share/man/man1/pod2text.1* symlink
 * Unable to establish //usr/share/man/man1/perlpodstyle.1* symlink
 * Messages for package sys-libs/pam-1.2.1:
 * Some software with pre-loaded PAM libraries might experience
 * warnings or failures related to missing symbols and/or versions
 * after any update. While unfortunate this is a limit of the
 * implementation of PAM and the software, and it requires you to
 * restart the software manually after the update.
 * 
 * You can get a list of such software running a command like
 *   lsof / | egrep -i 'del.*libpam\.so'
 * 
 * Alternatively, simply reboot your system.
 * Messages for package dev-lang/python-exec-2.4.4:
 * This package will overwrite one or more files that may belong to other
 * packages (see list below).
 * 
 * Detected file collision(s):
 * 
 * 	/usr/bin/pydoc
 * 	/usr/bin/2to3
 * 	/usr/bin/python-config
 * 	/usr/bin/python3
 * 	/usr/bin/python2
 * 	/usr/bin/python
 * 
 * Searching all installed packages for file collisions...
 * 
 * Press Ctrl-C to Stop
 * 
 * None of the installed packages claim the file(s).
 * 
 * Package 'dev-lang/python-exec-2.4.4' merged despite file collisions.
 * If necessary, refer to your elog messages for the whole content of the
 * above message.
 * You seem to have just upgraded into the new version of python-exec
 * that uses python-exec.conf for configuration. The ebuild has attempted
 * to convert your previous configuration to the new format, resulting
 * in the following preferences (most preferred version first):
 * 
 *   python3.4
 * 
 * Those interpreters will be preferred when running Python scripts or
 * calling wrapped Python executables (python, python2, pydoc...).
 * If none of the preferred interpreters are supported, python-exec will
 * fall back to the newest supported Python version.
 * 
 * Please note that due to the ambiguous character of the old settings,
 * you may want to modify the preference list yourself. In order to do so,
 * open the following file in your favorite editor:
 * 
 *   /etc/python-exec/python-exec.conf
 * 
 * For more information on the new configuration format, please read
 * the comment on top of the installed configuration file.
 * Messages for package sys-apps/util-linux-2.26.2:
 * The mesg/wall/write tools have been disabled due to USE=-tty-helpers.
 * Messages for package sys-apps/man-db-2.7.6.1-r1:
 * Defaulting to USE=gdbm due to ambiguous berkdb/gdbm USE flag settings
 * Messages for package dev-libs/glib-2.44.1-r1:
 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * Unable to check for the following kernel config options due
 * to absence of any configured kernel sources or compiled
 * config:
 *  - INOTIFY_USER
 * You're on your own to make sure they are set if needed.
 * Messages for package sys-fs/udev-225-r1:
 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * Unable to check for the following kernel config options due
 * to absence of any configured kernel sources or compiled
 * config:
 *  - BLK_DEV_BSG
 *  - DEVTMPFS
 *  - IDE
 *  - INOTIFY_USER
 *  - SYSFS_DEPRECATED
 *  - SYSFS_DEPRECATED_V2
 *  - SIGNALFD
 *  - EPOLL
 *  - FHANDLE
 *  - NET
 *  - FW_LOADER_USER_HELPER
 *  - UNIX
 * You're on your own to make sure they are set if needed.
 * 
 * Starting from version >= 197 the new predictable network interface names are
 * used by default, see:
 * https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
 * https://cgit.freedesktop.org/systemd/systemd/tree/src/udev/udev-builtin-net_id.c
 * 
 * Example command to get the information for the new interface name before booting
 * (replace <ifname> with, for example, eth0):
 * # udevadm test-builtin net_id /sys/class/net/<ifname> 2> /dev/null
 * 
 * You can use either kernel parameter "net.ifnames=0", create empty
 * file /etc/systemd/network/99-default.link, or symlink it to /dev/null
 * to disable the feature.
 * 
 * You need to restart udev as soon as possible to make the upgrade go
 * into effect.
 * The method you use to do this depends on your init system.
 * For sys-apps/openrc users it is:
 * # /etc/init.d/udev --nodeps restart
 * 
 * For more information on udev on Gentoo, upgrading, writing udev rules, and
 * fixing known issues visit:
 * https://wiki.gentoo.org/wiki/Udev
 * https://wiki.gentoo.org/wiki/Udev/upgrade




















emerge --quiet --usepkg --buildpkg --newuse --oneshot --nodeps sys-apps/baselayout
[ebuild  N    ] sys-apps/baselayout-2.3 to /tmp/stage1root/

The following keyword changes are necessary to proceed:
 (see "package.accept_keywords" in the portage(5) man page for more details)
# required by sys-apps/baselayout (argument)
=sys-apps/baselayout-2.3 ~s390

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.

!!! 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 stage1
Catalyst aborting....
lockfile does not exist '/var/tmp/catalyst/tmp/default/stage1-s390-20170120/.catalyst_lock'
Command exited with non-zero status 1
4350.97user 821.34system 54:27.01elapsed 158%CPU (0avgtext+0avgdata 1642896maxresident)k
0inputs+0outputs (2752major+472968817minor)pagefaults 0swaps



Full build log at /tmp/catalyst-auto.20170120.pZzDx8/log/stage1.log