public inbox for gentoo-releng-autobuilds@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst fatal build error - hardened/stage1-selinux-nomultilib.spec
@ 2018-08-05  3:50 catalyst
  0 siblings, 0 replies; 9+ messages in thread
From: catalyst @ 2018-08-05  3:50 UTC (permalink / raw
  To: jmbsvicetto, gentoo-releng-autobuilds




*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f hardened/stage1-selinux-nomultilib.spec
05 Aug 2018 03:49:56 UTC: NOTICE  : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
05 Aug 2018 03:49:56 UTC: NOTICE  : conf_values[options] = {'pkgcache', 'preserve_libs', 'clear-autoresume', 'bindist'}
05 Aug 2018 03:49:56 UTC: NOTICE  : Processing spec file: hardened/stage1-selinux-nomultilib.spec
05 Aug 2018 03:49:56 UTC: NOTICE  : Using target: stage1
05 Aug 2018 03:49:56 UTC: NOTICE  : Source file specification matching setting is: loose
05 Aug 2018 03:49:56 UTC: NOTICE  : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
05 Aug 2018 03:49:57 UTC: NOTICE  : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-selinux+nomultilib-latest.tar.xz
05 Aug 2018 03:49:57 UTC: NOTICE  : stage1 stage path is /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180804T134746Z/tmp/stage1root
05 Aug 2018 03:49:57 UTC: NOTICE  : --- Running action sequence: unpack
05 Aug 2018 03:49:57 UTC: NOTICE  : Clearing the chroot path ...
05 Aug 2018 03:49:57 UTC: NOTICE  : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180804T134746Z
05 Aug 2018 03:49:57 UTC: NOTICE  : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-selinux+nomultilib-latest.tar.xz
05 Aug 2018 03:49:57 UTC: NOTICE  : to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180804T134746Z (this may take some time) ..
05 Aug 2018 03:50:00 UTC: NOTICE  : --- Running action sequence: unpack_snapshot
05 Aug 2018 03:50:00 UTC: NOTICE  : Unpacking portage tree (this can take a long time) ...
05 Aug 2018 03:50:15 UTC: NOTICE  : --- Running action sequence: setup_confdir
05 Aug 2018 03:50:15 UTC: NOTICE  : --- Running action sequence: portage_overlay
05 Aug 2018 03:50:15 UTC: NOTICE  : --- Running action sequence: base_dirs
05 Aug 2018 03:50:15 UTC: NOTICE  : --- Running action sequence: bind
05 Aug 2018 03:50:15 UTC: NOTICE  : --- Running action sequence: chroot_setup
05 Aug 2018 03:50:15 UTC: NOTICE  : Setting up chroot...
05 Aug 2018 03:50:15 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
05 Aug 2018 03:50:15 UTC: WARNING : If your build fails look here first as the possible problem.
05 Aug 2018 03:50:15 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
05 Aug 2018 03:50:15 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
05 Aug 2018 03:50:15 UTC: WARNING : You have been warned.
05 Aug 2018 03:50:15 UTC: NOTICE  : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180804T134746Z/etc/portage/make.conf
05 Aug 2018 03:50:15 UTC: NOTICE  : STICKY-CONFIG is enabled
05 Aug 2018 03:50:15 UTC: NOTICE  : --- Running action sequence: setup_environment
05 Aug 2018 03:50:15 UTC: NOTICE  : --- Running action sequence: run_local
copying make.conf to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180804T134746Z/tmp/stage1root/etc/portage
Copying stage1-chroot.sh to /tmp
copying stage1-chroot.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180804T134746Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180804T134746Z/tmp
Ensure the file has the executable bit set
Running stage1-chroot.sh in chroot:
    chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20180804T134746Z /tmp/stage1-chroot.sh
>>> Regenerating /etc/ld.so.cache...
Adding USE="${USE} build" to make.conf for portage build
emerge --quiet --oneshot --update --newuse sys-apps/portage
[ebuild  N    ] virtual/perl-Scalar-List-Utils-1.420.200_rc-r1 
[ebuild  N    ] virtual/perl-MIME-Base64-3.150.0-r4 
[ebuild  N    ] virtual/perl-libnet-3.80.100_rc-r4 
[ebuild  N    ] virtual/perl-Digest-SHA-5.950.100_rc-r6 
[ebuild  N    ] virtual/perl-Digest-MD5-2.540.0-r3 
[ebuild  N    ] dev-perl/Digest-HMAC-1.30.0-r1 
[ebuild  N    ] dev-perl/Net-SSLeay-1.820.0 
[ebuild  N    ] dev-perl/Authen-SASL-2.160.0-r1 
[ebuild  N    ] dev-perl/IO-Socket-SSL-2.48.0 
[ebuild  N    ] dev-perl/Net-SMTP-SSL-1.30.0 
[ebuild  N    ] dev-perl/Error-0.170.240 
[ebuild  NS   ] dev-lang/python-3.6.5 [2.7.14-r1, 3.5.5]
[ebuild  N    ] dev-vcs/git-2.16.4 
[ebuild     U ] sys-libs/libsepol-9999 [2.8]
[ebuild     U ] sys-libs/libselinux-9999 [2.8]
[ebuild   R   ] sys-apps/portage-2.3.40-r1 

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

sys-libs/libselinux:0

  (sys-libs/libselinux-9999:0/0::gentoo, ebuild scheduled for merge) pulled in by
    >=sys-libs/libselinux-2.0.94[python,python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (sys-apps/portage-2.3.40-r1:0/0::gentoo, ebuild scheduled for merge)
                                                                                                                                                                                                                                                                                                                                                                                                                                                

  (sys-libs/libselinux-2.8:0/0::gentoo, installed) pulled in by
    >=sys-libs/libselinux-2.8:0/0=[python,python_targets_python2_7(-),python_targets_python3_5(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (sys-apps/policycoreutils-2.8:0/0::gentoo, installed)
                                                                                                                                                                                                                                                                                                                 
    >=sys-libs/libselinux-2.7:0/0=[python_targets_python2_7(-),python_targets_python3_5(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (app-admin/setools-4.1.1:0/0::gentoo, installed)
                                                                                                                                                                                                                                                                                                     
    >=sys-libs/libselinux-2.7:=[python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (app-admin/setools-4.1.1:0/0::gentoo, installed)
                                                                                                                                                                                                                                                                                                                                                              
    >=sys-libs/libselinux-2.8:=[python,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (sys-apps/policycoreutils-2.8:0/0::gentoo, installed)
                                                                                                                                                                                                                                                                                                                                                                          



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/shadow-4.6::gentoo
# required by virtual/shadow-0::gentoo
# required by @system
# required by @world (argument)
=sys-libs/libselinux-9999 **
# required by sys-libs/libselinux-2.8::gentoo
# required by @system
# required by @world (argument)
=sys-libs/libsepol-9999 **

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.

 * In order to avoid wasting time, backtracking has terminated early
 * due to the above autounmask change(s). The --autounmask-backtrack=y
 * option can be used to force further backtracking, but there is no
 * guarantee that it will produce a solution.
05 Aug 2018 03:50:22 UTC: ERROR   : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1
05 Aug 2018 03:50:22 UTC: ERROR   : CatalystError: Stage build aborting due to error.
05 Aug 2018 03:50:22 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 1355, 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/stage1/stage1-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 1455, in run
    getattr(self, x)()
  File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1364, in run_local
    print_traceback=False)
catalyst.support.CatalystError: Stage build aborting due to error.
05 Aug 2018 03:50:22 UTC: NOTICE  : Cleaning up... Running unbind()
Command exited with non-zero status 2
30.68user 3.93system 0:26.61elapsed 130%CPU (0avgtext+0avgdata 351172maxresident)k
16inputs+3456440outputs (0major+268988minor)pagefaults 0swaps



Full build log at /home/release/tmp/run/catalyst-auto.20180804T134746Z.GzUfBv/log/hardened_stage1-selinux-nomultilib.log


^ permalink raw reply	[flat|nested] 9+ messages in thread

* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst fatal build error - hardened/stage1-selinux-nomultilib.spec
@ 2019-03-02 16:17 catalyst
  0 siblings, 0 replies; 9+ messages in thread
From: catalyst @ 2019-03-02 16:17 UTC (permalink / raw
  To: jmbsvicetto, gentoo-releng-autobuilds




*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f hardened/stage1-selinux-nomultilib.spec
02 Mar 2019 16:16:20 UTC: NOTICE  : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
02 Mar 2019 16:16:20 UTC: NOTICE  : conf_values[options] = {'bindist', 'preserve_libs', 'pkgcache', 'clear-autoresume'}
02 Mar 2019 16:16:20 UTC: NOTICE  : Processing spec file: hardened/stage1-selinux-nomultilib.spec
02 Mar 2019 16:16:20 UTC: NOTICE  : Using target: stage1
02 Mar 2019 16:16:20 UTC: NOTICE  : Source file specification matching setting is: loose
02 Mar 2019 16:16:20 UTC: NOTICE  : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
02 Mar 2019 16:16:21 UTC: NOTICE  : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-selinux+nomultilib-latest.tar.xz
02 Mar 2019 16:16:21 UTC: NOTICE  : stage1 stage path is /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T160623Z/tmp/stage1root
02 Mar 2019 16:16:21 UTC: NOTICE  : --- Running action sequence: unpack
02 Mar 2019 16:16:21 UTC: NOTICE  : Clearing the chroot path ...
02 Mar 2019 16:16:21 UTC: NOTICE  : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T160623Z
02 Mar 2019 16:16:21 UTC: NOTICE  : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-selinux+nomultilib-latest.tar.xz
02 Mar 2019 16:16:21 UTC: NOTICE  : to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T160623Z (this may take some time) ..
02 Mar 2019 16:16:31 UTC: NOTICE  : --- Running action sequence: unpack_snapshot
02 Mar 2019 16:16:31 UTC: NOTICE  : Unpacking portage tree (this can take a long time) ...
02 Mar 2019 16:17:11 UTC: NOTICE  : --- Running action sequence: setup_confdir
02 Mar 2019 16:17:11 UTC: NOTICE  : --- Running action sequence: portage_overlay
02 Mar 2019 16:17:11 UTC: NOTICE  : --- Running action sequence: base_dirs
02 Mar 2019 16:17:11 UTC: NOTICE  : --- Running action sequence: bind
02 Mar 2019 16:17:11 UTC: NOTICE  : --- Running action sequence: chroot_setup
02 Mar 2019 16:17:11 UTC: NOTICE  : Setting up chroot...
02 Mar 2019 16:17:11 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
02 Mar 2019 16:17:11 UTC: WARNING : If your build fails look here first as the possible problem.
02 Mar 2019 16:17:11 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
02 Mar 2019 16:17:11 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
02 Mar 2019 16:17:11 UTC: WARNING : You have been warned.
02 Mar 2019 16:17:11 UTC: NOTICE  : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T160623Z/etc/portage/make.conf
02 Mar 2019 16:17:11 UTC: NOTICE  : STICKY-CONFIG is enabled
02 Mar 2019 16:17:11 UTC: NOTICE  : --- Running action sequence: setup_environment
02 Mar 2019 16:17:11 UTC: NOTICE  : --- Running action sequence: run_local
copying make.conf to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T160623Z/tmp/stage1root/etc/portage
Copying stage1-chroot.sh to /tmp
copying stage1-chroot.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T160623Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T160623Z/tmp
Ensure the file has the executable bit set
Running stage1-chroot.sh in chroot:
    chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T160623Z /tmp/stage1-chroot.sh
>>> Regenerating /etc/ld.so.cache...
Adding USE="${USE} build" to make.conf for portage build
emerge --quiet --oneshot --update --newuse sys-apps/portage

Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)


 * Last emerge --sync was 210d 3h 12m 13s ago.
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-apps/portage-2.3.40-r1::gentoo
>>> Failed to emerge sys-apps/portage-2.3.40-r1, Log file:
>>>  '/home/release/tmp/logs/sys-apps:portage-2.3.40-r1:20190302-161715.log'
 * Package:    sys-apps/portage-2.3.40-r1
 * Repository: gentoo
 * Maintainer: dev-portage@gentoo.org
 * Upstream:   dev-portage@gentoo.org
 * USE:        abi_x86_64 amd64 build elibc_glibc ipc kernel_linux native-extensions python_targets_python2_7 python_targets_python3_6 rsync-verify selinux userland_GNU xattr
 * FEATURES:   preserve-libs sandbox selinux sesandbox userpriv usersandbox
 * Please follow the instructions in the news item:
 * 2017-12-26-experimental-amd64-17-1-profiles
 * or choose the 17.0 profile.
 * ERROR: sys-apps/portage-2.3.40-r1::gentoo failed (setup phase):
 *   ERROR: 17.1 migration has not been performed!!
 * 
 * Call stack:
 *        ebuild.sh, line 610:  Called __source_all_bashrcs
 *        ebuild.sh, line 429:  Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
 *        ebuild.sh, line 484:  Called source '/var/gentoo/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/portage-2.3.40-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.40-r1::gentoo'`.
 * The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.40-r1:20190302-161715.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.40-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.40-r1/temp/die.env'.
 * Working directory: '/var/tmp/portage/sys-apps/portage-2.3.40-r1/homedir'
 * S: '/var/tmp/portage/sys-apps/portage-2.3.40-r1/work/portage-2.3.40'

 * Messages for package sys-apps/portage-2.3.40-r1:
 * Log file: /home/release/tmp/logs/sys-apps:portage-2.3.40-r1:20190302-161715.log

 * Please follow the instructions in the news item:
 * 2017-12-26-experimental-amd64-17-1-profiles
 * or choose the 17.0 profile.
 * ERROR: sys-apps/portage-2.3.40-r1::gentoo failed (setup phase):
 *   ERROR: 17.1 migration has not been performed!!
 * 
 * Call stack:
 *        ebuild.sh, line 610:  Called __source_all_bashrcs
 *        ebuild.sh, line 429:  Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
 *        ebuild.sh, line 484:  Called source '/var/gentoo/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/portage-2.3.40-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.40-r1::gentoo'`.
 * The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.40-r1:20190302-161715.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.40-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.40-r1/temp/die.env'.
 * Working directory: '/var/tmp/portage/sys-apps/portage-2.3.40-r1/homedir'
 * S: '/var/tmp/portage/sys-apps/portage-2.3.40-r1/work/portage-2.3.40'
02 Mar 2019 16:17:16 UTC: ERROR   : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1
02 Mar 2019 16:17:17 UTC: ERROR   : CatalystError: Stage build aborting due to error.
02 Mar 2019 16:17:17 UTC: ERROR   : Exception running action sequence run_local
Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1355, in run_local
    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/stage1/stage1-controller.sh', 'run']) 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 1455, in run
    getattr(self, x)()
  File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1364, in run_local
    print_traceback=False)
catalyst.support.CatalystError: Stage build aborting due to error.
02 Mar 2019 16:17:17 UTC: NOTICE  : Cleaning up... Running unbind()
Command exited with non-zero status 2
30.02user 4.37system 0:56.48elapsed 60%CPU (0avgtext+0avgdata 352632maxresident)k
1560inputs+3637392outputs (0major+524016minor)pagefaults 0swaps



Full build log at /home/release/tmp/run/catalyst-auto.20190302T160623Z.XUSM3x/log/hardened_stage1-selinux-nomultilib.log


^ permalink raw reply	[flat|nested] 9+ messages in thread

* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst fatal build error - hardened/stage1-selinux-nomultilib.spec
@ 2019-03-02 17:21 catalyst
  0 siblings, 0 replies; 9+ messages in thread
From: catalyst @ 2019-03-02 17:21 UTC (permalink / raw
  To: jmbsvicetto, gentoo-releng-autobuilds




*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f hardened/stage1-selinux-nomultilib.spec
02 Mar 2019 17:20:51 UTC: NOTICE  : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
02 Mar 2019 17:20:51 UTC: NOTICE  : conf_values[options] = {'clear-autoresume', 'bindist', 'preserve_libs', 'pkgcache'}
02 Mar 2019 17:20:51 UTC: NOTICE  : Processing spec file: hardened/stage1-selinux-nomultilib.spec
02 Mar 2019 17:20:51 UTC: NOTICE  : Using target: stage1
02 Mar 2019 17:20:51 UTC: NOTICE  : Source file specification matching setting is: loose
02 Mar 2019 17:20:51 UTC: NOTICE  : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
02 Mar 2019 17:20:52 UTC: NOTICE  : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-selinux+nomultilib-latest.tar.xz
02 Mar 2019 17:20:52 UTC: NOTICE  : stage1 stage path is /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T162037Z/tmp/stage1root
02 Mar 2019 17:20:52 UTC: NOTICE  : --- Running action sequence: unpack
02 Mar 2019 17:20:52 UTC: NOTICE  : Clearing the chroot path ...
02 Mar 2019 17:20:52 UTC: NOTICE  : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T162037Z
02 Mar 2019 17:20:52 UTC: NOTICE  : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-selinux+nomultilib-latest.tar.xz
02 Mar 2019 17:20:52 UTC: NOTICE  : to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T162037Z (this may take some time) ..
02 Mar 2019 17:20:56 UTC: NOTICE  : --- Running action sequence: unpack_snapshot
02 Mar 2019 17:20:56 UTC: NOTICE  : Unpacking portage tree (this can take a long time) ...
02 Mar 2019 17:21:23 UTC: NOTICE  : --- Running action sequence: setup_confdir
02 Mar 2019 17:21:23 UTC: NOTICE  : --- Running action sequence: portage_overlay
02 Mar 2019 17:21:23 UTC: NOTICE  : --- Running action sequence: base_dirs
02 Mar 2019 17:21:23 UTC: NOTICE  : --- Running action sequence: bind
02 Mar 2019 17:21:23 UTC: NOTICE  : --- Running action sequence: chroot_setup
02 Mar 2019 17:21:23 UTC: NOTICE  : Setting up chroot...
02 Mar 2019 17:21:23 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
02 Mar 2019 17:21:23 UTC: WARNING : If your build fails look here first as the possible problem.
02 Mar 2019 17:21:23 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
02 Mar 2019 17:21:23 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
02 Mar 2019 17:21:23 UTC: WARNING : You have been warned.
02 Mar 2019 17:21:23 UTC: NOTICE  : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T162037Z/etc/portage/make.conf
02 Mar 2019 17:21:23 UTC: NOTICE  : STICKY-CONFIG is enabled
02 Mar 2019 17:21:23 UTC: NOTICE  : --- Running action sequence: setup_environment
02 Mar 2019 17:21:23 UTC: NOTICE  : --- Running action sequence: run_local
copying make.conf to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T162037Z/tmp/stage1root/etc/portage
Copying stage1-chroot.sh to /tmp
copying stage1-chroot.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T162037Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T162037Z/tmp
Ensure the file has the executable bit set
Running stage1-chroot.sh in chroot:
    chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190302T162037Z /tmp/stage1-chroot.sh
>>> Regenerating /etc/ld.so.cache...
Adding USE="${USE} build" to make.conf for portage build
emerge --quiet --oneshot --update --newuse sys-apps/portage

Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)


>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-apps/portage-2.3.51-r1::gentoo
>>> Failed to emerge sys-apps/portage-2.3.51-r1, Log file:
>>>  '/home/release/tmp/logs/sys-apps:portage-2.3.51-r1:20190302-172127.log'
 * Package:    sys-apps/portage-2.3.51-r1
 * Repository: gentoo
 * Maintainer: dev-portage@gentoo.org
 * Upstream:   dev-portage@gentoo.org
 * USE:        abi_x86_64 amd64 build elibc_glibc ipc kernel_linux native-extensions python_targets_python2_7 python_targets_python3_6 rsync-verify selinux userland_GNU xattr
 * FEATURES:   preserve-libs sandbox selinux sesandbox userpriv usersandbox
 * Please follow the instructions in the news item:
 * 2017-12-26-experimental-amd64-17-1-profiles
 * or choose the 17.0 profile.
 * ERROR: sys-apps/portage-2.3.51-r1::gentoo failed (setup phase):
 *   ERROR: 17.1 migration has not been performed!!
 * 
 * Call stack:
 *        ebuild.sh, line 610:  Called __source_all_bashrcs
 *        ebuild.sh, line 429:  Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
 *        ebuild.sh, line 484:  Called source '/var/gentoo/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/portage-2.3.51-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.51-r1::gentoo'`.
 * The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.51-r1:20190302-172127.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.51-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.51-r1/temp/die.env'.
 * Working directory: '/var/tmp/portage/sys-apps/portage-2.3.51-r1/homedir'
 * S: '/var/tmp/portage/sys-apps/portage-2.3.51-r1/work/portage-2.3.51'

 * Messages for package sys-apps/portage-2.3.51-r1:
 * Log file: /home/release/tmp/logs/sys-apps:portage-2.3.51-r1:20190302-172127.log

 * Please follow the instructions in the news item:
 * 2017-12-26-experimental-amd64-17-1-profiles
 * or choose the 17.0 profile.
 * ERROR: sys-apps/portage-2.3.51-r1::gentoo failed (setup phase):
 *   ERROR: 17.1 migration has not been performed!!
 * 
 * Call stack:
 *        ebuild.sh, line 610:  Called __source_all_bashrcs
 *        ebuild.sh, line 429:  Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
 *        ebuild.sh, line 484:  Called source '/var/gentoo/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/portage-2.3.51-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.51-r1::gentoo'`.
 * The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.51-r1:20190302-172127.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.51-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.51-r1/temp/die.env'.
 * Working directory: '/var/tmp/portage/sys-apps/portage-2.3.51-r1/homedir'
 * S: '/var/tmp/portage/sys-apps/portage-2.3.51-r1/work/portage-2.3.51'
02 Mar 2019 17:21:28 UTC: ERROR   : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1
02 Mar 2019 17:21:28 UTC: ERROR   : CatalystError: Stage build aborting due to error.
02 Mar 2019 17:21:28 UTC: ERROR   : Exception running action sequence run_local
Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1355, in run_local
    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/stage1/stage1-controller.sh', 'run']) 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 1455, in run
    getattr(self, x)()
  File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1364, in run_local
    print_traceback=False)
catalyst.support.CatalystError: Stage build aborting due to error.
02 Mar 2019 17:21:28 UTC: NOTICE  : Cleaning up... Running unbind()
Command exited with non-zero status 2
30.00user 4.87system 0:37.75elapsed 92%CPU (0avgtext+0avgdata 352668maxresident)k
280inputs+3663600outputs (4major+498147minor)pagefaults 0swaps



Full build log at /home/release/tmp/run/catalyst-auto.20190302T162037Z.utKSjw/log/hardened_stage1-selinux-nomultilib.log


^ permalink raw reply	[flat|nested] 9+ messages in thread

* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst fatal build error - hardened/stage1-selinux-nomultilib.spec
@ 2019-06-11  1:37 catalyst
  0 siblings, 0 replies; 9+ messages in thread
From: catalyst @ 2019-06-11  1:37 UTC (permalink / raw
  To: jmbsvicetto, gentoo-releng-autobuilds




*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f hardened/stage1-selinux-nomultilib.spec
11 Jun 2019 01:36:00 UTC: NOTICE  : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
11 Jun 2019 01:36:00 UTC: NOTICE  : conf_values[options] = {'clear-autoresume', 'preserve_libs', 'pkgcache', 'bindist'}
11 Jun 2019 01:36:00 UTC: NOTICE  : Processing spec file: hardened/stage1-selinux-nomultilib.spec
11 Jun 2019 01:36:00 UTC: NOTICE  : Using target: stage1
11 Jun 2019 01:36:00 UTC: NOTICE  : Source file specification matching setting is: loose
11 Jun 2019 01:36:00 UTC: NOTICE  : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
11 Jun 2019 01:36:01 UTC: NOTICE  : Source path set to /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-selinux+nomultilib-latest.tar.xz
11 Jun 2019 01:36:01 UTC: NOTICE  : stage1 stage path is /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190611T012607Z/tmp/stage1root
11 Jun 2019 01:36:01 UTC: NOTICE  : --- Running action sequence: unpack
11 Jun 2019 01:36:01 UTC: NOTICE  : Clearing the chroot path ...
11 Jun 2019 01:36:01 UTC: NOTICE  : Emptying directory: /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190611T012607Z
11 Jun 2019 01:36:01 UTC: NOTICE  : Starting auto from /home/release/buildroot/amd64-dev/builds/hardened/stage3-amd64-hardened-selinux+nomultilib-latest.tar.xz
11 Jun 2019 01:36:01 UTC: NOTICE  : to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190611T012607Z (this may take some time) ..
11 Jun 2019 01:36:07 UTC: NOTICE  : --- Running action sequence: unpack_snapshot
11 Jun 2019 01:36:07 UTC: NOTICE  : Unpacking portage tree (this can take a long time) ...
11 Jun 2019 01:36:52 UTC: NOTICE  : --- Running action sequence: setup_confdir
11 Jun 2019 01:36:52 UTC: NOTICE  : --- Running action sequence: portage_overlay
11 Jun 2019 01:36:52 UTC: NOTICE  : --- Running action sequence: base_dirs
11 Jun 2019 01:36:52 UTC: NOTICE  : --- Running action sequence: bind
11 Jun 2019 01:36:52 UTC: NOTICE  : --- Running action sequence: chroot_setup
11 Jun 2019 01:36:52 UTC: NOTICE  : Setting up chroot...
11 Jun 2019 01:36:52 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
11 Jun 2019 01:36:52 UTC: WARNING : If your build fails look here first as the possible problem.
11 Jun 2019 01:36:52 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
11 Jun 2019 01:36:52 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
11 Jun 2019 01:36:52 UTC: WARNING : You have been warned.
11 Jun 2019 01:36:52 UTC: NOTICE  : Writing the stage make.conf to: /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190611T012607Z/etc/portage/make.conf
11 Jun 2019 01:36:52 UTC: NOTICE  : STICKY-CONFIG is enabled
11 Jun 2019 01:36:52 UTC: NOTICE  : --- Running action sequence: setup_environment
11 Jun 2019 01:36:52 UTC: NOTICE  : --- Running action sequence: run_local
copying make.conf to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190611T012607Z/tmp/stage1root/etc/portage
Copying stage1-chroot.sh to /tmp
copying stage1-chroot.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190611T012607Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190611T012607Z/tmp
Ensure the file has the executable bit set
Running stage1-chroot.sh in chroot:
    chroot /home/release/buildroot/amd64-dev/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190611T012607Z /tmp/stage1-chroot.sh
>>> Regenerating /etc/ld.so.cache...
Adding USE="${USE} build" to make.conf for portage build
emerge --quiet --oneshot --update --newuse sys-apps/portage
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-apps/portage-2.3.62-r2
 * Determining the location of the kernel source code
 * Unable to find kernel sources at /usr/src/linux
 * Please make sure that /usr/src/linux points at your running kernel, 
 * (or the kernel you wish to build against).
 * Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * Checking for suitable kernel configuration options...
 [ ok ]
>>> Emerging (1 of 1) sys-apps/portage-2.3.62-r2::gentoo
>>> Failed to emerge sys-apps/portage-2.3.62-r2, Log file:
>>>  '/home/release/tmp/logs/sys-apps:portage-2.3.62-r2:20190611-013703.log'
 * Package:    sys-apps/portage-2.3.62-r2
 * Repository: gentoo
 * Maintainer: dev-portage@gentoo.org
 * Upstream:   dev-portage@gentoo.org
 * USE:        abi_x86_64 amd64 build elibc_glibc ipc kernel_linux native-extensions python_targets_python2_7 python_targets_python3_6 rsync-verify selinux userland_GNU xattr
 * FEATURES:   network-sandbox preserve-libs sandbox selinux sesandbox userpriv usersandbox
 * Please follow the instructions in the news item:
 * 2017-12-26-experimental-amd64-17-1-profiles
 * or choose the 17.0 profile.
 * ERROR: sys-apps/portage-2.3.62-r2::gentoo failed (setup phase):
 *   ERROR: 17.1 migration has not been performed!!
 * 
 * Call stack:
 *        ebuild.sh, line 598:  Called __source_all_bashrcs
 *        ebuild.sh, line 417:  Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
 *        ebuild.sh, line 474:  Called __qa_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
 *        ebuild.sh, line 111:  Called source '/var/gentoo/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/portage-2.3.62-r2::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.62-r2::gentoo'`.
 * The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.62-r2:20190611-013703.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.62-r2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.62-r2/temp/die.env'.
 * Working directory: '/var/tmp/portage/sys-apps/portage-2.3.62-r2/homedir'
 * S: '/var/tmp/portage/sys-apps/portage-2.3.62-r2/work/portage-2.3.62'
 * Messages for package sys-apps/portage-2.3.62-r2:
 * Log file: /home/release/tmp/logs/sys-apps:portage-2.3.62-r2:20190611-013702.log
 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * Messages for package sys-apps/portage-2.3.62-r2:
 * Log file: /home/release/tmp/logs/sys-apps:portage-2.3.62-r2:20190611-013703.log
 * Please follow the instructions in the news item:
 * 2017-12-26-experimental-amd64-17-1-profiles
 * or choose the 17.0 profile.
 * ERROR: sys-apps/portage-2.3.62-r2::gentoo failed (setup phase):
 *   ERROR: 17.1 migration has not been performed!!
 * 
 * Call stack:
 *        ebuild.sh, line 598:  Called __source_all_bashrcs
 *        ebuild.sh, line 417:  Called __try_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
 *        ebuild.sh, line 474:  Called __qa_source '/var/gentoo/repos/gentoo/profiles/default/linux/amd64/17.1/profile.bashrc'
 *        ebuild.sh, line 111:  Called source '/var/gentoo/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/portage-2.3.62-r2::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.62-r2::gentoo'`.
 * The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.62-r2:20190611-013703.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.62-r2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.62-r2/temp/die.env'.
 * Working directory: '/var/tmp/portage/sys-apps/portage-2.3.62-r2/homedir'
 * S: '/var/tmp/portage/sys-apps/portage-2.3.62-r2/work/portage-2.3.62'




11 Jun 2019 01:37:04 UTC: ERROR   : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1
11 Jun 2019 01:37:04 UTC: ERROR   : CatalystError: Stage build aborting due to error.
11 Jun 2019 01:37:04 UTC: ERROR   : Exception running action sequence run_local
Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1360, in run_local
    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/stage1/stage1-controller.sh', 'run']) 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 1369, in run_local
    print_traceback=False)
catalyst.support.CatalystError: Stage build aborting due to error.
11 Jun 2019 01:37:04 UTC: NOTICE  : Cleaning up... Running unbind()
Command exited with non-zero status 2
37.07user 5.27system 1:04.36elapsed 65%CPU (0avgtext+0avgdata 358568maxresident)k
336inputs+4434304outputs (0major+609944minor)pagefaults 0swaps



Full build log at /home/release/tmp/run/catalyst-auto.20190611T012607Z.4ssuYw/log/hardened_stage1-selinux-nomultilib.log


^ permalink raw reply	[flat|nested] 9+ messages in thread

* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst fatal build error - hardened/stage1-selinux-nomultilib.spec
@ 2019-06-11  9:26 catalyst
  0 siblings, 0 replies; 9+ messages in thread
From: catalyst @ 2019-06-11  9:26 UTC (permalink / raw
  To: jmbsvicetto, gentoo-releng-autobuilds




*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f hardened/stage1-selinux-nomultilib.spec
11 Jun 2019 09:26:50 UTC: NOTICE  : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
11 Jun 2019 09:26:50 UTC: NOTICE  : conf_values[options] = {'pkgcache', 'clear-autoresume', 'preserve_libs', 'bindist'}
11 Jun 2019 09:26:50 UTC: NOTICE  : Processing spec file: hardened/stage1-selinux-nomultilib.spec
11 Jun 2019 09:26:50 UTC: NOTICE  : Using target: stage1
11 Jun 2019 09:26:50 UTC: NOTICE  : Source file specification matching setting is: loose
11 Jun 2019 09:26:50 UTC: NOTICE  : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
11 Jun 2019 09:26:50 UTC: ERROR   : CatalystError: File Not Found: /home/release/buildroot/amd64-exp/builds/hardened/stage3-amd64-hardened-selinux+nomultilib-latest
Command exited with non-zero status 2
0.22user 0.01system 0:00.29elapsed 79%CPU (0avgtext+0avgdata 18272maxresident)k
0inputs+0outputs (0major+9487minor)pagefaults 0swaps



Full build log at /home/release/tmp/run/catalyst-auto.20190611T092541Z.nNqC3R/log/hardened_stage1-selinux-nomultilib.log


^ permalink raw reply	[flat|nested] 9+ messages in thread

* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst fatal build error - hardened/stage1-selinux-nomultilib.spec
@ 2019-06-14 18:35 catalyst
  0 siblings, 0 replies; 9+ messages in thread
From: catalyst @ 2019-06-14 18:35 UTC (permalink / raw
  To: jmbsvicetto, gentoo-releng-autobuilds




*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f hardened/stage1-selinux-nomultilib.spec
14 Jun 2019 18:35:38 UTC: NOTICE  : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
14 Jun 2019 18:35:38 UTC: NOTICE  : conf_values[options] = {'bindist', 'clear-autoresume', 'preserve_libs', 'pkgcache'}
14 Jun 2019 18:35:38 UTC: NOTICE  : Processing spec file: hardened/stage1-selinux-nomultilib.spec
14 Jun 2019 18:35:38 UTC: NOTICE  : Using target: stage1
14 Jun 2019 18:35:38 UTC: NOTICE  : Source file specification matching setting is: loose
14 Jun 2019 18:35:38 UTC: NOTICE  : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
14 Jun 2019 18:35:38 UTC: ERROR   : CatalystError: File Not Found: /home/release/buildroot/amd64-exp/builds/hardened/stage3-amd64-hardened-selinux+nomultilib-latest
Command exited with non-zero status 2
0.19user 0.03system 0:00.29elapsed 80%CPU (0avgtext+0avgdata 18152maxresident)k
0inputs+0outputs (0major+9487minor)pagefaults 0swaps



Full build log at /home/release/tmp/run/catalyst-auto.20190614T183511Z.BWvov2/log/hardened_stage1-selinux-nomultilib.log


^ permalink raw reply	[flat|nested] 9+ messages in thread

* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst fatal build error - hardened/stage1-selinux-nomultilib.spec
@ 2019-06-15  6:33 catalyst
  0 siblings, 0 replies; 9+ messages in thread
From: catalyst @ 2019-06-15  6:33 UTC (permalink / raw
  To: jmbsvicetto, gentoo-releng-autobuilds







Full build log at /home/release/tmp/run/catalyst-auto.20190614T184237Z.7Vt1sS/log/hardened_stage1-selinux-nomultilib.log


^ permalink raw reply	[flat|nested] 9+ messages in thread

* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst fatal build error - hardened/stage1-selinux-nomultilib.spec
@ 2019-06-15  6:33 catalyst
  0 siblings, 0 replies; 9+ messages in thread
From: catalyst @ 2019-06-15  6:33 UTC (permalink / raw
  To: jmbsvicetto, gentoo-releng-autobuilds







Full build log at /home/release/tmp/run/catalyst-auto.20190614T185156Z.VHU94x/log/hardened_stage1-selinux-nomultilib.log


^ permalink raw reply	[flat|nested] 9+ messages in thread

* [gentoo-releng-autobuilds] [amd64-experimental] Catalyst fatal build error - hardened/stage1-selinux-nomultilib.spec
@ 2019-06-15 20:08 catalyst
  0 siblings, 0 replies; 9+ messages in thread
From: catalyst @ 2019-06-15 20:08 UTC (permalink / raw
  To: jmbsvicetto, gentoo-releng-autobuilds




*** Running command: time catalyst -a -c /etc/catalyst/release/amd64-experimental.conf -f hardened/stage1-selinux-nomultilib.spec
15 Jun 2019 20:07:43 UTC: NOTICE  : Loading configuration file: /etc/catalyst/release/amd64-experimental.conf
15 Jun 2019 20:07:43 UTC: NOTICE  : conf_values[options] = {'bindist', 'pkgcache', 'preserve_libs', 'clear-autoresume'}
15 Jun 2019 20:07:43 UTC: NOTICE  : Processing spec file: hardened/stage1-selinux-nomultilib.spec
15 Jun 2019 20:07:43 UTC: NOTICE  : Using target: stage1
15 Jun 2019 20:07:43 UTC: NOTICE  : Source file specification matching setting is: loose
15 Jun 2019 20:07:43 UTC: NOTICE  : Accepted source file extensions search order: ['tar', 'tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'tar.gz', 'gz']
15 Jun 2019 20:07:56 UTC: NOTICE  : Source path set to /home/release/buildroot/amd64-exp/builds/hardened/stage3-amd64-hardened-selinux+nomultilib-latest.tar.xz
15 Jun 2019 20:07:56 UTC: NOTICE  : stage1 stage path is /home/release/buildroot/amd64-exp/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190615T082957Z/tmp/stage1root
15 Jun 2019 20:07:56 UTC: NOTICE  : --- Running action sequence: unpack
15 Jun 2019 20:07:56 UTC: NOTICE  : Clearing the chroot path ...
15 Jun 2019 20:07:56 UTC: NOTICE  : Emptying directory: /home/release/buildroot/amd64-exp/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190615T082957Z
15 Jun 2019 20:07:56 UTC: NOTICE  : Starting auto from /home/release/buildroot/amd64-exp/builds/hardened/stage3-amd64-hardened-selinux+nomultilib-latest.tar.xz
15 Jun 2019 20:07:56 UTC: NOTICE  : to /home/release/buildroot/amd64-exp/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190615T082957Z (this may take some time) ..
15 Jun 2019 20:08:00 UTC: NOTICE  : --- Running action sequence: unpack_snapshot
15 Jun 2019 20:08:00 UTC: NOTICE  : Unpacking portage tree (this can take a long time) ...
15 Jun 2019 20:08:20 UTC: NOTICE  : --- Running action sequence: setup_confdir
15 Jun 2019 20:08:20 UTC: NOTICE  : --- Running action sequence: portage_overlay
15 Jun 2019 20:08:20 UTC: NOTICE  : --- Running action sequence: base_dirs
15 Jun 2019 20:08:20 UTC: NOTICE  : --- Running action sequence: bind
15 Jun 2019 20:08:20 UTC: NOTICE  : --- Running action sequence: chroot_setup
15 Jun 2019 20:08:20 UTC: NOTICE  : Setting up chroot...
15 Jun 2019 20:08:20 UTC: WARNING : Overriding certain env variables may cause catastrophic failure.
15 Jun 2019 20:08:20 UTC: WARNING : If your build fails look here first as the possible problem.
15 Jun 2019 20:08:20 UTC: WARNING : Catalyst assumes you know what you are doing when setting these variables.
15 Jun 2019 20:08:20 UTC: WARNING : Catalyst Maintainers use VERY minimal envscripts, if used at all.
15 Jun 2019 20:08:20 UTC: WARNING : You have been warned.
15 Jun 2019 20:08:20 UTC: NOTICE  : Writing the stage make.conf to: /home/release/buildroot/amd64-exp/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190615T082957Z/etc/portage/make.conf
15 Jun 2019 20:08:20 UTC: NOTICE  : STICKY-CONFIG is enabled
15 Jun 2019 20:08:20 UTC: NOTICE  : --- Running action sequence: setup_environment
15 Jun 2019 20:08:20 UTC: NOTICE  : --- Running action sequence: run_local
copying make.conf to /home/release/buildroot/amd64-exp/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190615T082957Z/tmp/stage1root/etc/portage
Copying stage1-chroot.sh to /tmp
copying stage1-chroot.sh to /home/release/buildroot/amd64-exp/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190615T082957Z/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-exp/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190615T082957Z/tmp
Ensure the file has the executable bit set
Running stage1-chroot.sh in chroot:
    chroot /home/release/buildroot/amd64-exp/tmp/hardened/stage1-amd64-hardened-selinux+nomultilib-20190615T082957Z /tmp/stage1-chroot.sh
>>> Regenerating /etc/ld.so.cache...
Adding USE="${USE} build" to make.conf for portage build
emerge --quiet --oneshot --update --newuse sys-apps/portage

Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)


>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-apps/portage-2.3.66-r1
 * Determining the location of the kernel source code
 * Unable to find kernel sources at /usr/src/linux
 * Please make sure that /usr/src/linux points at your running kernel, 
 * (or the kernel you wish to build against).
 * Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * Checking for suitable kernel configuration options...
 [ ok ]
>>> Emerging (1 of 1) sys-apps/portage-2.3.66-r1::gentoo
>>> Failed to emerge sys-apps/portage-2.3.66-r1, Log file:
>>>  '/home/release/tmp/logs/sys-apps:portage-2.3.66-r1:20190615-200826.log'
 * Package:    sys-apps/portage-2.3.66-r1
 * Repository: gentoo
 * Maintainer: dev-portage@gentoo.org
 * Upstream:   dev-portage@gentoo.org
 * USE:        abi_x86_64 amd64 build elibc_glibc ipc kernel_linux native-extensions python_targets_python2_7 python_targets_python3_6 rsync-verify selinux userland_GNU xattr
 * FEATURES:   network-sandbox preserve-libs sandbox selinux sesandbox 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/portage-2.3.66-r1::gentoo failed (setup phase):
 *   ERROR: 17.1 migration has not been performed!!
 * 
 * Call stack:
 *        ebuild.sh, line 598:  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/portage-2.3.66-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.66-r1::gentoo'`.
 * The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.66-r1:20190615-200826.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.66-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.66-r1/temp/die.env'.
 * Working directory: '/var/tmp/portage/sys-apps/portage-2.3.66-r1/homedir'
 * S: '/var/tmp/portage/sys-apps/portage-2.3.66-r1/work/portage-2.3.66'
 * Messages for package sys-apps/portage-2.3.66-r1:
 * Log file: /home/release/tmp/logs/sys-apps:portage-2.3.66-r1:20190615-200826.log
 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * Messages for package sys-apps/portage-2.3.66-r1:
 * Log file: /home/release/tmp/logs/sys-apps:portage-2.3.66-r1:20190615-200826.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/portage-2.3.66-r1::gentoo failed (setup phase):
 *   ERROR: 17.1 migration has not been performed!!
 * 
 * Call stack:
 *        ebuild.sh, line 598:  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/portage-2.3.66-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.66-r1::gentoo'`.
 * The complete build log is located at '/home/release/tmp/logs/sys-apps:portage-2.3.66-r1:20190615-200826.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/portage-2.3.66-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.66-r1/temp/die.env'.
 * Working directory: '/var/tmp/portage/sys-apps/portage-2.3.66-r1/homedir'
 * S: '/var/tmp/portage/sys-apps/portage-2.3.66-r1/work/portage-2.3.66'




15 Jun 2019 20:08:27 UTC: ERROR   : CatalystError: cmd(['/usr/share/catalyst/targets/stage1/stage1-controller.sh', 'run']) exited 1
15 Jun 2019 20:08:27 UTC: ERROR   : CatalystError: Stage build aborting due to error.
15 Jun 2019 20:08:27 UTC: ERROR   : Exception running action sequence run_local
Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1360, in run_local
    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/stage1/stage1-controller.sh', 'run']) 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 1369, in run_local
    print_traceback=False)
catalyst.support.CatalystError: Stage build aborting due to error.
15 Jun 2019 20:08:27 UTC: NOTICE  : Cleaning up... Running unbind()
Command exited with non-zero status 2
37.22user 5.75system 0:44.66elapsed 96%CPU (0avgtext+0avgdata 358568maxresident)k
43928inputs+4431872outputs (0major+634278minor)pagefaults 0swaps



Full build log at /home/release/tmp/run/catalyst-auto.20190615T082957Z.eaQaxh/log/hardened_stage1-selinux-nomultilib.log


^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2019-06-15 20:08 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-06-14 18:35 [gentoo-releng-autobuilds] [amd64-experimental] Catalyst fatal build error - hardened/stage1-selinux-nomultilib.spec catalyst
  -- strict thread matches above, loose matches on Subject: below --
2019-06-15 20:08 catalyst
2019-06-15  6:33 catalyst
2019-06-15  6:33 catalyst
2019-06-11  9:26 catalyst
2019-06-11  1:37 catalyst
2019-03-02 17:21 catalyst
2019-03-02 16:17 catalyst
2018-08-05  3:50 catalyst

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox