[gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage4-nomultilib-cloud.spec

udev and udev-trigger will be added to your sysinit runlevel, but not
udev-settle. udev-settle should not be added to a runlevel. Instead, if
a service needs this, it should add "need udev-settle" to its
dependencies.


2015-07-25-python-targets
  Title                     Python 3.4 enabled by default
  Author                    Mike Gilbert <floppym@g.o>
  Posted                    2015-07-25
  Revision                  1

Python 3.4 is now enabled by default, replacing Python 3.3 as the
default Python 3 interpreter.

PYTHON_TARGETS will be adjusted to contain python2_7 and python3_4 by
default via your profile.

PYTHON_SINGLE_TARGET will remain set to python2_7 by default.

If you have PYTHON_TARGETS set in make.conf, that setting will still be
respected. You may want to adjust this setting manually.

Once the changes have taken place, a world update should take care of
reinstalling any python libraries you have installed. You should also
switch your default python3 interpreter using eselect python.

For example:

eselect python set --python3 python3.4
emerge -uDv --changed-use @world

2015-08-13-openssh-weak-keys
  Title                     OpenSSH 7.0 disables ssh-dss keys by default
  Author                    Mike Frysinger <vapier@g.o>
  Posted                    2015-08-13
  Revision                  1

Starting with the 7.0 release of OpenSSH, support for ssh-dss keys has
been disabled by default at runtime due to their inherit weakness.  If
you rely on these key types, you will have to take corrective action or
risk being locked out.

Your best option is to generate new keys using strong algos such as rsa
or ecdsa or ed25519.  RSA keys will give you the greatest portability
with other clients/servers while ed25519 will get you the best security
with OpenSSH (but requires recent versions of client & server).

If you are stuck with DSA keys, you can re-enable support locally by
updating your sshd_config and ~/.ssh/config files with lines like so:
	PubkeyAcceptedKeyTypes=+ssh-dss

Be aware though that eventually OpenSSH will drop support for DSA keys
entirely, so this is only a stop gap solution.

More details can be found on OpenSSH's website:
	http://www.openssh.com/legacy.html

2015-10-21-future-support-of-hardened-sources-kernel
  Title                     Future Support of hardened-sources Kernel
  Author                    Anthony G. Basile <blueness@g.o>
  Posted                    2015-10-21
  Revision                  3

For many years, the Grsecurity team [1] has been supporting two versions of
their security patches against the Linux kernel, a stable and a testing
version, and Gentoo has made both of these available to our users through the
hardened-sources package.  However, on August 26 of this year, the team
announced they would no longer be making the stable version publicly
available, citing trademark infringement by a major embedded systems company
as the reason. [2]  The stable patches are now only available to sponsors of
Grsecurity and can no longer be distributed in Gentoo.  However, the team did
assure us that they would continue to release and support the testing version
as they have in the past.

What does this means for users of hardened-sources?  Gentoo will continue to
make the testing version available through our hardened-sources package but we
will have to drop support for the 3.x series.  In a few days, those ebuilds
will be removed from the tree and you will be required to upgrade to a 4.x
series kernel.  Since the hardened-sources package only installs the kernel
source tree, you can continue using a currently built 3.x series kernel but
bear in mind that we cannot support you, nor will upstream.  Also keep in mind
that the 4.x series will not be as reliable as the 3.x series was, so
reporting bugs promptly will be even more important.  Gentoo will continue to
work closely with upstream to stay on top of any problems, but be prepared for
the occasional "bad" kernel.  The more reporting we receive from our users,
the better we will be able to decide which hardened-sources kernels to mark
stable and which to drop.

Refs.
[1] https://grsecurity.net
[2] https://grsecurity.net/announce.php

2016-01-08-some-dhcpcd-hooks-are-now-examples
  Title                     Some dhcpcd hooks are now examples
  Author                    William Hubbs <williamh@g.o>
  Posted                    2016-01-08
  Revision                  2

In dhcpcd-6.10.0, the following hooks are no longer installed in
/lib/dhcpcd/dhcpcd-hooks by default:

10-wpa_supplicant
15-timezone
29-lookup-hostname

These are now installed in /usr/share/dhcpcd/hooks, which is an example
directory.

If you were using these hooks before you upgrade to 6.10.0, you will
need to copy them back to the /lib/dhcpcd/dhcpcd-hooks directory after the
upgrade.

>>> Building file list for distfiles cleaning...
>>> Cleaning distfiles...
 [    1.0 M ] LVM2.2.02.88.tgz
 [  119.7 K ] MAKEDEV-3.23-1.tar.gz
 [    2.1 M ] busybox-1.20.2.tar.bz2
 [  994.6 K ] cpio-2.11.tar.bz2
 [  227.3 K ] dmraid-1.0.0.rc16-3.tar.bz2
 [  493.5 K ] fuse-2.8.6.tar.gz
 [  276.3 K ] genkernel-3.4.52.3.tar.xz
 [    3.2 M ] gnupg-1.4.11.tar.bz2
 [  285.8 K ] mdadm-3.1.5.tar.bz2
 [    1.8 M ] nano-2.4.3.tar.gz
 [  879.0 K ] open-iscsi-2.0-872.tar.gz
 [   29.7 K ] unionfs-fuse-0.24.tar.bz2
 ===========
 [   11.3 M ] Total space from 12 files were freed in the distfiles directory
passwd: password expiry information changed.
passwd: password expiry information changed.
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114//tmp/cloud-prep.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114//tmp/chroot-functions.sh from the chroot
--- Running action sequence: preclean
Copying stage4-preclean-chroot.sh to //tmp
copying stage4-preclean-chroot.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114///tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114///tmp
Ensure the file has the executable bit set
Running stage4-preclean-chroot.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114//
>>> Regenerating /etc/ld.so.cache...
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114///tmp/stage4-preclean-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114///tmp/chroot-functions.sh from the chroot
--- Running action sequence: rcupdate
Copying rc-update.sh to /tmp
copying rc-update.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114//tmp
Ensure the file has the executable bit set
Running rc-update.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114/
Adding acpid to default
 * service acpid added to runlevel default
Adding cloud-config to default
 * service cloud-config added to runlevel default
Adding cloud-final to default
 * service cloud-final added to runlevel default
Adding cloud-init-local to default
 * service cloud-init-local added to runlevel default
Adding cloud-init to default
 * service cloud-init added to runlevel default
Adding cronie to default
 * service cronie added to runlevel default
Adding dhcpcd to default
 * service dhcpcd added to runlevel default
Adding net.lo to default
 * service net.lo added to runlevel default
Adding netmount to default
 * rc-update: netmount already installed in runlevel `default'; skipping
Adding sshd to default
 * service sshd added to runlevel default
Adding syslog-ng to default
 * service syslog-ng added to runlevel default
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114//tmp/rc-update.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114//tmp/chroot-functions.sh from the chroot
--- Running action sequence: unmerge
Copying unmerge.sh to /tmp
copying unmerge.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114//tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114//tmp
Ensure the file has the executable bit set
Running unmerge.sh in chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114/
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse -C sys-kernel/genkernel sys-kernel/gentoo-sources

--- Couldn't find 'sys-kernel/genkernel' to unmerge.

--- Couldn't find 'sys-kernel/gentoo-sources' to unmerge.

!!! catalyst: Unmerge script failed.

Traceback (most recent call last):
File "/usr/lib64/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 1336, in unmerge
    env=self.env)
File "/usr/lib64/catalyst//modules/catalyst_support.py", line 541, in cmd
    raise CatalystError,myexc
CatalystError
!!! catalyst: Error encountered during run of target stage4
Catalyst aborting....
lockfile does not exist '/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+cloud-nomultilib-20160114/.catalyst_lock'



Full build log at /release/tmp/run/catalyst-auto.B7rM4z/log/hardened_stage4-nomultilib-cloud.log