def override_chost(self):
if self.settings.has_key("chost"):
--
1.7.8.6
08-05-2012, 10:56 PM
Richard Farina
make.conf and make.profile moved to /etc/portage so stop cleaning it to avoid multiple fatal errors
Sorry that was a little iffy on the git send email, it's been a while.
An example of some of the errors solved by this patch is :
http://slexy.org/view/s20oDYzxrC
I was completely unable to build stage2 before this change (and stage1
completed but was REALLY ugly at the end).
Has anyone else run into this yet? I mean the issue can't get much more
obvious, we clean out /etc/portage near the end of each stage but
/etc/portage/make.conf and /etc/portage/make.profile are rather required....
Thanks!
-Zero
On 07/27/2012 04:57 AM, Rick Farina wrote:
> Signed-off-by: Rick Farina <sidhayn@gmail.com>
> ---
> modules/stage1_target.py | 3 +--
> modules/stage2_target.py | 1 -
> 2 files changed, 1 insertions(+), 3 deletions(-)
>
> diff --git a/modules/stage1_target.py b/modules/stage1_target.py
> index 32e6334..560efdb 100644
> --- a/modules/stage1_target.py
> +++ b/modules/stage1_target.py
> @@ -31,8 +31,7 @@ class stage1_target(generic_stage_target):
> "/usr/lib/python2.2/lib-tk", "/usr/lib/python2.3/test",
> "/usr/lib/python2.3/email", "/usr/lib/python2.3/lib-tk",
> "/usr/lib/python2.4/test", "/usr/lib/python2.4/email",
> - "/usr/lib/python2.4/lib-tk", "/usr/share/zoneinfo",
> - "/etc/portage"])
> + "/usr/lib/python2.4/lib-tk", "/usr/share/zoneinfo"])
>
> # XXX: How do these override_foo() functions differ from the ones in generic_stage_target and why aren't they in stage3_target?
>
> diff --git a/modules/stage2_target.py b/modules/stage2_target.py
> index f529721..97ea7fe 100644
> --- a/modules/stage2_target.py
> +++ b/modules/stage2_target.py
> @@ -35,7 +35,6 @@ class stage2_target(generic_stage_target):
>
> def set_cleanables(self):
> generic_stage_target.set_cleanables(self)
> - self.settings["cleanables"].extend(["/etc/portage"])
>
> def override_chost(self):
> if self.settings.has_key("chost"):
08-06-2012, 10:37 AM
"Jorge Manuel B. S. Vicetto"
make.conf and make.profile moved to /etc/portage so stop cleaning it to avoid multiple fatal errors
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05-08-2012 22:56, Richard Farina wrote:
> Sorry that was a little iffy on the git send email, it's been a
> while.
>
> An example of some of the errors solved by this patch is :
> http://slexy.org/view/s20oDYzxrC
The answer to my question on IRC is that you are using autoresume:
...
The autoresume path is
/mnt/storage/catalyst/tmp/default/.autoresume-stage2-amd64-2012.0/
...
So as I thought we need to review the logic in chroot_setup and
config_profile_link in modules/generic_stage_target.py
> I was completely unable to build stage2 before this change (and
> stage1 completed but was REALLY ugly at the end).
>
> Has anyone else run into this yet? I mean the issue can't get much
> more obvious, we clean out /etc/portage near the end of each stage
> but /etc/portage/make.conf and /etc/portage/make.profile are rather
> required....
Yes, but we are supposed to create them at the start of every stage -
except we're currently not doing it if autoresume is enabled.
> Thanks!
>
> -Zero
- --
Regards,
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
Gentoo- forums / Userrel / Devrel / KDE / Elections / RelEng
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
make.conf and make.profile moved to /etc/portage so stop cleaning it to avoid multiple fatal errors
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/06/2012 06:37 AM, Jorge Manuel B. S. Vicetto wrote:
> On 05-08-2012 22:56, Richard Farina wrote:
>> Sorry that was a little iffy on the git send email, it's been a
>> while.
>
>> An example of some of the errors solved by this patch is :
>> http://slexy.org/view/s20oDYzxrC
>
>
> The answer to my question on IRC is that you are using autoresume:
>
> ...
> The autoresume path is
> /mnt/storage/catalyst/tmp/default/.autoresume-stage2-amd64-2012.0/
> ...
>
> So as I thought we need to review the logic in chroot_setup and
> config_profile_link in modules/generic_stage_target.py
>
>> I was completely unable to build stage2 before this change (and
>> stage1 completed but was REALLY ugly at the end).
>
>> Has anyone else run into this yet? I mean the issue can't get much
>> more obvious, we clean out /etc/portage near the end of each stage
>> but /etc/portage/make.conf and /etc/portage/make.profile are rather
>> required....
>
> Yes, but we are supposed to create them at the start of every stage -
> except we're currently not doing it if autoresume is enabled.
So my workaround for now is to simply not use autoresume?
Thanks,
Rick
>
>> Thanks!
>
>> -Zero
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
make.conf and make.profile moved to /etc/portage so stop cleaning it to avoid multiple fatal errors
