[gentoo-catalyst] catalyst & arm

[gentoo-catalyst] catalyst & arm

[Alan Hourihane]

Hi,

I'm trying to build with catalyst on arm for a basic stage3, but I need
to build from a fairly old stage3 as a seed. Don't ask why :-)

I'm getting this error...

Is there any simple way to get past this ??

Thanks,

Alan.

Catalyst, version 2.0.6
Copyright 2003-2008 Gentoo Foundation
Distributed under the GNU General Public License version 2

Using default Catalyst configuration file, /etc/catalyst/catalyst.conf
Setting sharedir to config file value "/usr/lib/catalyst"
Setting snapshot_cache to config file value
"/var/tmp/catalyst/snapshot_cache"
Setting hash_function to config file value "crc32"
Setting storedir to config file value "/var/tmp/catalyst"
Setting portdir to config file value "/usr/portage"
Setting distdir to config file value "/usr/portage/distfiles"
Setting options to config file value "autoresume kerncache
metadata_overlay pkgcache seedcache snapcache"
Autoresuming support enabled.
Kernel cache support enabled.
Package cache support enabled.
Seed cache support enabled.
Snapshot cache support enabled.
Envscript support enabled.

	WARNING: No value set for key pkgcache_path...deleting

	WARNING: No value set for key portage_overlay...deleting

	WARNING: No value set for key chost...deleting

	WARNING: No value set for key ldflags...deleting

	WARNING: No value set for key portage_confdir...deleting
Using target: stage3
Building natively for arm
Source path set to /var/tmp/catalyst/builds/stage3-arm-20040510.tar.bz2
Caching snapshot to /var/tmp/catalyst/snapshot_cache/20090919/
The autoresume path
is /var/tmp/catalyst/tmp/default/.autoresume-stage3-arm-20090919/
Location of the package cache
is /var/tmp/catalyst/packages/default/stage3-arm-20090919/
Location of the kerncache
is /var/tmp/catalyst/kerncache/default/stage3-arm-20090919/
Checking for processes running in chroot and killing them.
/proc is still mounted; performing auto-bind-umount... Auto-unbind
successful...
--- Running action sequence: unpack
Referenced SEEDCACHE does not appear to be a directory, trying to
untar...
Resume point detected, skipping unpack operation...
--- Running action sequence: unpack_snapshot
Valid snapshot cache, skipping unpack of portage tree...
--- Running action sequence: config_profile_link
Resume point detected, skipping config_profile_link operation...
--- Running action sequence: setup_confdir
--- Running action sequence: portage_overlay
--- Running action sequence: base_dirs
--- Running action sequence: bind
--- Running action sequence: chroot_setup
/usr/lib/portage/pym/portage_util.py:45: DeprecationWarning: DEPRECATION
NOTICE: The portage_util module was replaced by portage.util
Resume point detected, skipping chroot_setup operation...
--- Running action sequence: setup_environment
--- Running action sequence: run_local
copying stage3-chroot.sh
to /var/tmp/catalyst/tmp/default/stage3-arm-20090919/tmp/
copying chroot-functions.sh
to /var/tmp/catalyst/tmp/default/stage3-arm-20090919/tmp/
Running stage3-chroot.sh in
chroot /var/tmp/catalyst/tmp/default/stage3-arm-20090919/
Traceback (most recent call last):
  File "/usr/sbin/env-update", line 10, in ?
    import portage
  File "/usr/lib/portage/pym/portage.py", line 6132, in ?
    portdb=portdbapi(settings["PORTDIR"])
  File "/usr/lib/portage/pym/portage.py", line 4432, in __init__
    self.auxdbmodule  =
self.mysettings.load_best_module("portdbapi.auxdbmodule")
  File "/usr/lib/portage/pym/portage.py", line 1307, in load_best_module
    return load_mod(best_mod)
  File "/usr/lib/portage/pym/portage.py", line 34, in load_mod
    mod = __import__(modname)
ImportError: No module named cache.metadata_overlay
emerge --quiet --usepkg --buildpkg --newuse --oneshot --nodeps
virtual/portage
Traceback (most recent call last):
  File "/usr/bin/emerge", line 14, in ?
    import portage
  File "/usr/lib/portage/pym/portage.py", line 6132, in ?
    portdb=portdbapi(settings["PORTDIR"])
  File "/usr/lib/portage/pym/portage.py", line 4432, in __init__
    self.auxdbmodule  =
self.mysettings.load_best_module("portdbapi.auxdbmodule")
  File "/usr/lib/portage/pym/portage.py", line 1307, in load_best_module
    return load_mod(best_mod)
  File "/usr/lib/portage/pym/portage.py", line 34, in load_mod
    mod = __import__(modname)
ImportError: No module named cache.metadata_overlay

!!! catalyst: run script failed.


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

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

!!! catalyst: Error encountered during run of target stage3

Catalyst aborting....

Re: [gentoo-catalyst] catalyst & arm

[Andrew Gaffney]

On 09/20/2009 01:13 PM, Alan Hourihane wrote:
> ImportError: No module named cache.metadata_overlay

You're getting this because you're using portage-2.2_rc41 (or thereabouts),
which introduces a number of incompatibilities with the way that catalyst
assumed portage-2.1.x worked.

You can bypass this error by removing 'metadata_overlay' from 'options' in
/etc/catalyst/catalyst.conf. It really doesn't even make sense to have the
option anymore, since portage uses it by default these days.

-- 
Andrew Gaffney                                 http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer            Catalyst/Genkernel + Release Engineering Lead

Re: [gentoo-catalyst] catalyst & arm

[Alan Hourihane]

On Sun, 2009-09-20 at 14:41 -0500, Andrew Gaffney wrote:
> On 09/20/2009 01:13 PM, Alan Hourihane wrote:
> > ImportError: No module named cache.metadata_overlay
> 
> You're getting this because you're using portage-2.2_rc41 (or thereabouts),
> which introduces a number of incompatibilities with the way that catalyst
> assumed portage-2.1.x worked.
> 
> You can bypass this error by removing 'metadata_overlay' from 'options' in
> /etc/catalyst/catalyst.conf. It really doesn't even make sense to have the
> option anymore, since portage uses it by default these days.
> 

Hi Andrew,

Thanks for the response, removing that didn't seem to make much
difference....

Catalyst, version 2.0.6
Copyright 2003-2008 Gentoo Foundation
Distributed under the GNU General Public License version 2

Using default Catalyst configuration file, /etc/catalyst/catalyst.conf
Setting sharedir to config file value "/usr/lib/catalyst"
Setting snapshot_cache to config file value
"/var/tmp/catalyst/snapshot_cache"
Setting hash_function to config file value "crc32"
Setting storedir to config file value "/var/tmp/catalyst"
Setting portdir to config file value "/usr/portage"
Setting distdir to config file value "/usr/portage/distfiles"
Setting options to config file value "autoresume kerncache pkgcache
seedcache snapcache"
Autoresuming support enabled.
Kernel cache support enabled.
Package cache support enabled.
Seed cache support enabled.
Snapshot cache support enabled.
Envscript support enabled.

	WARNING: No value set for key pkgcache_path...deleting

	WARNING: No value set for key portage_overlay...deleting

	WARNING: No value set for key chost...deleting

	WARNING: No value set for key ldflags...deleting

	WARNING: No value set for key portage_confdir...deleting
Using target: stage3
Building natively for arm
Source path set to /var/tmp/catalyst/builds/stage3-arm-20040510.tar.bz2
Caching snapshot to /var/tmp/catalyst/snapshot_cache/20090919/
The autoresume path
is /var/tmp/catalyst/tmp/default/.autoresume-stage3-arm-20090919/
Location of the package cache
is /var/tmp/catalyst/packages/default/stage3-arm-20090919/
Location of the kerncache
is /var/tmp/catalyst/kerncache/default/stage3-arm-20090919/
Checking for processes running in chroot and killing them.
--- Running action sequence: unpack
Referenced SEEDCACHE does not appear to be a directory, trying to
untar...
Resume point detected, skipping unpack operation...
--- Running action sequence: unpack_snapshot
Valid snapshot cache, skipping unpack of portage tree...
--- Running action sequence: config_profile_link
Resume point detected, skipping config_profile_link operation...
--- Running action sequence: setup_confdir
--- Running action sequence: portage_overlay
--- Running action sequence: base_dirs
--- Running action sequence: bind
--- Running action sequence: chroot_setup
/usr/lib/portage/pym/portage_util.py:45: DeprecationWarning: DEPRECATION
NOTICE: The portage_util module was replaced by portage.util
Resume point detected, skipping chroot_setup operation...
--- Running action sequence: setup_environment
--- Running action sequence: run_local
copying stage3-chroot.sh
to /var/tmp/catalyst/tmp/default/stage3-arm-20090919/tmp/
copying chroot-functions.sh
to /var/tmp/catalyst/tmp/default/stage3-arm-20090919/tmp/
Running stage3-chroot.sh in
chroot /var/tmp/catalyst/tmp/default/stage3-arm-20090919/
Traceback (most recent call last):
  File "/usr/sbin/env-update", line 10, in ?
    import portage
  File "/usr/lib/portage/pym/portage.py", line 6132, in ?
    portdb=portdbapi(settings["PORTDIR"])
  File "/usr/lib/portage/pym/portage.py", line 4432, in __init__
    self.auxdbmodule  =
self.mysettings.load_best_module("portdbapi.auxdbmodule")
  File "/usr/lib/portage/pym/portage.py", line 1307, in load_best_module
    return load_mod(best_mod)
  File "/usr/lib/portage/pym/portage.py", line 34, in load_mod
    mod = __import__(modname)
ImportError: No module named cache.metadata_overlay
emerge --quiet --usepkg --buildpkg --newuse --oneshot --nodeps
virtual/portage
Traceback (most recent call last):
  File "/usr/bin/emerge", line 14, in ?
    import portage
  File "/usr/lib/portage/pym/portage.py", line 6132, in ?
    portdb=portdbapi(settings["PORTDIR"])
  File "/usr/lib/portage/pym/portage.py", line 4432, in __init__
    self.auxdbmodule  =
self.mysettings.load_best_module("portdbapi.auxdbmodule")
  File "/usr/lib/portage/pym/portage.py", line 1307, in load_best_module
    return load_mod(best_mod)
  File "/usr/lib/portage/pym/portage.py", line 34, in load_mod
    mod = __import__(modname)
ImportError: No module named cache.metadata_overlay

!!! catalyst: run script failed.


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

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

!!! catalyst: Error encountered during run of target stage3

Catalyst aborting....


Alan.

Re: [gentoo-catalyst] catalyst & arm

[Andrew Gaffney]

On 09/20/2009 03:22 PM, Alan Hourihane wrote:
> On Sun, 2009-09-20 at 14:41 -0500, Andrew Gaffney wrote:
>> On 09/20/2009 01:13 PM, Alan Hourihane wrote:
>>> ImportError: No module named cache.metadata_overlay
>>
>> You're getting this because you're using portage-2.2_rc41 (or thereabouts),
>> which introduces a number of incompatibilities with the way that catalyst
>> assumed portage-2.1.x worked.
>>
>> You can bypass this error by removing 'metadata_overlay' from 'options' in
>> /etc/catalyst/catalyst.conf. It really doesn't even make sense to have the
>> option anymore, since portage uses it by default these days.
> 
> Hi Andrew,
> 
> Thanks for the response, removing that didn't seem to make much
> difference....

Run catalyst with -a so it clears the autoresume points.

-- 
Andrew Gaffney                                 http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer            Catalyst/Genkernel + Release Engineering Lead

Re: [gentoo-catalyst] catalyst & arm

[Alan Hourihane]

On Sun, 2009-09-20 at 15:26 -0500, Andrew Gaffney wrote:
> On 09/20/2009 03:22 PM, Alan Hourihane wrote:
> > On Sun, 2009-09-20 at 14:41 -0500, Andrew Gaffney wrote:
> >> On 09/20/2009 01:13 PM, Alan Hourihane wrote:
> >>> ImportError: No module named cache.metadata_overlay
> >>
> >> You're getting this because you're using portage-2.2_rc41 (or thereabouts),
> >> which introduces a number of incompatibilities with the way that catalyst
> >> assumed portage-2.1.x worked.
> >>
> >> You can bypass this error by removing 'metadata_overlay' from 'options' in
> >> /etc/catalyst/catalyst.conf. It really doesn't even make sense to have the
> >> option anymore, since portage uses it by default these days.
> > 
> > Hi Andrew,
> > 
> > Thanks for the response, removing that didn't seem to make much
> > difference....
> 
> Run catalyst with -a so it clears the autoresume points.

Thanks again.

Got furthur now, by switching to a stage1 seed to generate a stage2, but
getting this with python...

I'm wondering where the portage seed is and I can try and generate my
own stage1 ??

Thanks,

Alan.

running build_scripts
creating build/scripts-2.5
copying and
adjusting /var/tmp/portage/dev-lang/python-2.5.4-r3/work/Python-2.5.4/Tools/scripts/pydoc -> build/scripts-2.5
copying and
adjusting /var/tmp/portage/dev-lang/python-2.5.4-r3/work/Python-2.5.4/Tools/scripts/idle -> build/scripts-2.5
copying and
adjusting /var/tmp/portage/dev-lang/python-2.5.4-r3/work/Python-2.5.4/Lib/smtpd.py -> build/scripts-2.5
changing mode of build/scripts-2.5/pydoc from 644 to 755
changing mode of build/scripts-2.5/idle from 644 to 755
changing mode of build/scripts-2.5/smtpd.py from 644 to 755
make: *** [sharedmods] Error 1
 * 
 * ERROR: dev-lang/python-2.5.4-r3 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 4011:  Called die
 * The specific snippet of code:
 *       emake || die "emake failed"
 *  The die message:
 *   emake failed
 * 
 * If you need support, post the topmost build error, and the call stack
if relevant.
 * A complete build log is located at
'/var/tmp/portage/dev-lang/python-2.5.4-r3/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/dev-lang/python-2.5.4-r3/temp/environment'.
 * 

Re: [gentoo-catalyst] catalyst & arm

[Mike Frysinger]

[-- Attachment #1: Type: Text/Plain, Size: 216 bytes --]

On Monday 21 September 2009 15:30:21 Alan Hourihane wrote:
> Got furthur now, by switching to a stage1 seed to generate a stage2, but
> getting this with python...

you've snipped the actual error from the log
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [gentoo-catalyst] catalyst & arm

[Alan Hourihane]

On Tue, 2009-09-22 at 14:01 -0400, Mike Frysinger wrote:
> On Monday 21 September 2009 15:30:21 Alan Hourihane wrote:
> > Got furthur now, by switching to a stage1 seed to generate a stage2, but
> > getting this with python...
> 
> you've snipped the actual error from the log

That's all there was.

Alan.