From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id C5502138330 for ; Wed, 12 Oct 2016 16:54:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7C112E085C; Wed, 12 Oct 2016 16:54:19 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4D83EE085C for ; Wed, 12 Oct 2016 16:54:19 +0000 (UTC) Received: from professor-x (d108-172-194-175.bchsia.telus.net [108.172.194.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: dolsen) by smtp.gentoo.org (Postfix) with ESMTPSA id 4C28234108B for ; Wed, 12 Oct 2016 16:54:18 +0000 (UTC) Date: Wed, 12 Oct 2016 09:54:14 -0700 From: Brian Dolbec To: gentoo-catalyst@lists.gentoo.org Subject: Re: [gentoo-catalyst] broken catalyst 3.0_rc1 Message-ID: <20161012095414.425733ab.dolsen@gentoo.org> In-Reply-To: References: <20161011125933.7c169f74.dolsen@gentoo.org> Organization: Gentoo Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-catalyst@lists.gentoo.org Reply-to: gentoo-catalyst@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: b11d3c45-04f5-4c3e-abfc-bcc166c8f6d1 X-Archives-Hash: 84aac9ff2220ad962762d7f564078b00 On Wed, 12 Oct 2016 02:49:14 -0400 John Covici wrote: > OK, so that particular error was fixed, but I am running into somekind > of problem and I can't even see what is happening. I have some > packages which need to be emerged after the kernel is compiled, but I > get a terse statement that call back failed, even setting --loglevel=5 > in the genkernel argument does not help. So, how can I see what is > happening inside the callback? I even put verbose on the emerge but > the output disappears. > > Thanks in advance for any suggestions. > > p.s. Looks like there are some python problems also, see below No, those are normal errors caused by the genkernel failure. Otherwise catalyst might hide the some facts of the failure. It helps when we are making code changes to catalyst in case of a catalyst bug. But this time it is not catalyst, but a genkernel/kernel build problem. Sorry, but I'm not a kernel guru, perhaps some of the others here will know what the problem is. > > * BUSYBOX_CONFIG not set. > * INSTALL defaulted to "yes". > * DEBUGCLEANUP defaulted to "yes". > * KERNEL_ARCH=x86 > * > * ERROR: --callback failed! > * > * -- End log... -- > * > * Please consult /var/log/genkernel.log for more information and any > * errors that were reported above. > * > * Report any genkernel bugs to bugs.gentoo.org and > * assign your bug to genkernel@gentoo.org. Please include > * as much information as you can in your bug report; attaching > * /var/log/genkernel.log so that your issue can be dealt with > * effectively. > * > * Please do *not* report compilation failures as genkernel bugs! > * > 12 Oct 2016 01:47:09 EDT: ERROR : CatalystError: > cmd(['/usr/share/catalyst/targets/livecd-stage2/livecd-stage2-controller.sh', > 'kernel', 'gentoo']) exited 1 > 12 Oct 2016 01:47:09 EDT: ERROR : CatalystError: build aborting due > to kernel build error. > Traceback (most recent call last): > File > "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", > line 1512, in build_kernel > self._build_kernel(kname=kname) > File > "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", > line 1548, in _build_kernel > env=self.env) > File > "/usr/lib64/python3.4/site-packages/catalyst/support.py", > line 54, in cmd > print_traceback=False) > catalyst.support.CatalystError: > cmd(['/usr/share/catalyst/targets/livecd-stage2/livecd-stage2-controller.sh', > 'kernel', 'gentoo']) exited 1 > 12 Oct 2016 01:47:09 EDT: ERROR : > Exception running action sequence build_kernel > Traceback (most recent call last): > File > "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", > line 1512, in build_kernel > self._build_kernel(kname=kname) > File > "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", > line 1548, in _build_kernel > env=self.env) > File > "/usr/lib64/python3.4/site-packages/catalyst/support.py", > line 54, in cmd > print_traceback=False) > catalyst.support.CatalystError: > cmd(['/usr/share/catalyst/targets/livecd-stage2/livecd-stage2-controller.sh', > 'kernel', > 'gentoo']) exited 1 > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", > line 1395, in run > getattr(self, x)() > File > "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", > line 1518, in build_kernel > print_traceback=True) > catalyst.support.CatalystError: build aborting due to kernel > build error. > 12 Oct 2016 01:47:09 EDT: NOTICE : Cleaning up... Running unbind() > > On Tue, 11 Oct 2016 15:59:33 -0400, > Brian Dolbec wrote: > > > > On Tue, 11 Oct 2016 15:35:07 -0400 > > John Covici wrote: > > > > > Hi. I am getting the error none type is not iterable when > > > starting a stage2-minimal and I saw someone had this bug in March > > > of this year. Any fix? Should I try the 9999 version instead, > > > although he said he tried git with no joy? > > > > > > Thanks in advance for any suggestions. > > > > > > > Yeah, 9999 should be good. I really need to get another release > > out. > > > > If you still have the issue please let me know. > > > > -- > > Brian Dolbec > > > > > -- Brian Dolbec