[gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Joakim Tjernlund]

I am trying to rebuild an old cross sysroot and I got problems.
I cannot make emerge to select my old ebuilds in an overlay over those
in /usr/portage.

What new is since last time I did this is /etc/portage/repos.conf/
I suspect emerge always reads /etc/portage/repos.conf/ no matter
what I set PORTAGE_CONFIGROOT / ROOT to ?

 Jocke

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Zac Medico]

On 05/06/15 09:54, Joakim Tjernlund wrote:
> I am trying to rebuild an old cross sysroot and I got problems.
> I cannot make emerge to select my old ebuilds in an overlay over those
> in /usr/portage.
> 
> What new is since last time I did this is /etc/portage/repos.conf/
> I suspect emerge always reads /etc/portage/repos.conf/ no matter
> what I set PORTAGE_CONFIGROOT / ROOT to ?
> 
>  Jocke
> 

It instantiates 2 config instances, one using /etc/portage/repos.conf
(for build time DEPEND) and another one using
$PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
You can see that it's joined with PORTAGE_CONFIGROOT in the
load_repository_config function:

https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f191113cccd049e11fdbe73493eb1efbf4bf89e#n971
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Joakim Tjernlund]

On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
> On 05/06/15 09:54, Joakim Tjernlund wrote:
> > I am trying to rebuild an old cross sysroot and I got problems.
> > I cannot make emerge to select my old ebuilds in an overlay over those
> > in /usr/portage.
> > 
> > What new is since last time I did this is /etc/portage/repos.conf/
> > I suspect emerge always reads /etc/portage/repos.conf/ no matter
> > what I set PORTAGE_CONFIGROOT / ROOT to ?
> > 
> >  Jocke
> > 
> 
> It instantiates 2 config instances, one using /etc/portage/repos.conf
> (for build time DEPEND) and another one using
> $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
> You can see that it's joined with PORTAGE_CONFIGROOT in the
> load_repository_config function:
> 
> https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f191113cccd049e11fdbe73
> 493eb1efbf4bf89e#n971

I see, doesn't this prevent exactly what I want to do?

I can't see why this should be needed, it only creates a mess, another example:
I tried to specify exact version of my old binutils and while that worked, portage wanted
to pull in a newer binutils-config from the hosts master gentoo repo and
thus the build failed.

If a someone really wants this behaviour, he can just add the hosts master repo
in his PORTAGE_CONFIGROOT IMHO

 Jocke

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Joakim Tjernlund]

On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote:
> On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
> > On 05/06/15 09:54, Joakim Tjernlund wrote:
> > > I am trying to rebuild an old cross sysroot and I got problems.
> > > I cannot make emerge to select my old ebuilds in an overlay over those
> > > in /usr/portage.
> > > 
> > > What new is since last time I did this is /etc/portage/repos.conf/
> > > I suspect emerge always reads /etc/portage/repos.conf/ no matter
> > > what I set PORTAGE_CONFIGROOT / ROOT to ?
> > > 
> > >  Jocke
> > > 
> > 
> > It instantiates 2 config instances, one using /etc/portage/repos.conf
> > (for build time DEPEND) and another one using
> > $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
> > You can see that it's joined with PORTAGE_CONFIGROOT in the
> > load_repository_config function:
> > 
> > https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f191113cccd049e11fdbe
> > 73
> > 493eb1efbf4bf89e#n971
> 
> I see, doesn't this prevent exactly what I want to do?
> 
> I can't see why this should be needed, it only creates a mess, another example:
> I tried to specify exact version of my old binutils and while that worked, portage wanted
> to pull in a newer binutils-config from the hosts master gentoo repo and
> thus the build failed.
> 
> If a someone really wants this behaviour, he can just add the hosts master repo
> in his PORTAGE_CONFIGROOT IMHO
> 

Is there a way to make portage to prefer ebuilds from an overlay/other repo even if the master
repo has newer versions?

 Jocke

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Zac Medico]

On 05/06/15 12:41, Joakim Tjernlund wrote:
> On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote:
>> On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
>>> On 05/06/15 09:54, Joakim Tjernlund wrote:
>>>> I am trying to rebuild an old cross sysroot and I got problems.
>>>> I cannot make emerge to select my old ebuilds in an overlay over those
>>>> in /usr/portage.
>>>>
>>>> What new is since last time I did this is /etc/portage/repos.conf/
>>>> I suspect emerge always reads /etc/portage/repos.conf/ no matter
>>>> what I set PORTAGE_CONFIGROOT / ROOT to ?
>>>>
>>>>  Jocke
>>>>
>>>
>>> It instantiates 2 config instances, one using /etc/portage/repos.conf
>>> (for build time DEPEND) and another one using
>>> $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
>>> You can see that it's joined with PORTAGE_CONFIGROOT in the
>>> load_repository_config function:
>>>
>>> https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f191113cccd049e11fdbe
>>> 73
>>> 493eb1efbf4bf89e#n971
>>
>> I see, doesn't this prevent exactly what I want to do?
>>
>> I can't see why this should be needed, it only creates a mess, another example:
>> I tried to specify exact version of my old binutils and while that worked, portage wanted
>> to pull in a newer binutils-config from the hosts master gentoo repo and
>> thus the build failed.
>>
>> If a someone really wants this behaviour, he can just add the hosts master repo
>> in his PORTAGE_CONFIGROOT IMHO
>>

Maybe emerge --root-deps=rdeps is what you are looking for. This will
cause it to ignore DEPEND.

> 
> Is there a way to make portage to prefer ebuilds from an overlay/other repo even if the master
> repo has newer versions?
> 
>  Jocke
> 

You can use repo atoms in /etc/portage/package.mask. For example,
'sys-devel/binutils-config::gentoo', or '*/*::gentoo'.
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Joakim Tjernlund]

On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
> On 05/06/15 12:41, Joakim Tjernlund wrote:
> > On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote:
> > > On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
> > > > On 05/06/15 09:54, Joakim Tjernlund wrote:
> > > > > I am trying to rebuild an old cross sysroot and I got problems.
> > > > > I cannot make emerge to select my old ebuilds in an overlay over those
> > > > > in /usr/portage.
> > > > > 
> > > > > What new is since last time I did this is /etc/portage/repos.conf/
> > > > > I suspect emerge always reads /etc/portage/repos.conf/ no matter
> > > > > what I set PORTAGE_CONFIGROOT / ROOT to ?
> > > > > 
> > > > >  Jocke
> > > > > 
> > > > 
> > > > It instantiates 2 config instances, one using /etc/portage/repos.conf
> > > > (for build time DEPEND) and another one using
> > > > $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
> > > > You can see that it's joined with PORTAGE_CONFIGROOT in the
> > > > load_repository_config function:
> > > > 
> > > > https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f191113cccd049e11
> > > > fdbe
> > > > 73
> > > > 493eb1efbf4bf89e#n971
> > > 
> > > I see, doesn't this prevent exactly what I want to do?
> > > 
> > > I can't see why this should be needed, it only creates a mess, another example:
> > > I tried to specify exact version of my old binutils and while that worked, portage wanted
> > > to pull in a newer binutils-config from the hosts master gentoo repo and
> > > thus the build failed.
> > > 
> > > If a someone really wants this behaviour, he can just add the hosts master repo
> > > in his PORTAGE_CONFIGROOT IMHO
> > > 
> 
> Maybe emerge --root-deps=rdeps is what you are looking for. This will
> cause it to ignore DEPEND.

That is not the same is it? if I "emerge ncurses" it will build ncurses but still
take the ebuild from the hosts master since it is newer version.

I realize now that I can change what repos are searched by using PORTAGE_REPOSITORIES=/my/own/repos.conf/
but I still find the default behaviour very confusing and I don't see that it is useful.

What is 'extra_files' in load_repository_config()? Can I as a user add those or does portage
add some of its own?
> 
> > 
> > Is there a way to make portage to prefer ebuilds from an overlay/other repo even if the master
> > repo has newer versions?
> > 
> >  Jocke
> > 
> 
> You can use repo atoms in /etc/portage/package.mask. For example,
> 'sys-devel/binutils-config::gentoo', or '*/*::gentoo'.

Nice! Can I also mask everything '*/*::gentoo' and then only unmask sys-devel/binutils-config::gentoo ?

 Jocke

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Zac Medico]

On 05/06/15 13:22, Joakim Tjernlund wrote:
> On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
>> On 05/06/15 12:41, Joakim Tjernlund wrote:
>>> On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote:
>>>> On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
>>>>> On 05/06/15 09:54, Joakim Tjernlund wrote:
>>>>>> I am trying to rebuild an old cross sysroot and I got problems.
>>>>>> I cannot make emerge to select my old ebuilds in an overlay over those
>>>>>> in /usr/portage.
>>>>>>
>>>>>> What new is since last time I did this is /etc/portage/repos.conf/
>>>>>> I suspect emerge always reads /etc/portage/repos.conf/ no matter
>>>>>> what I set PORTAGE_CONFIGROOT / ROOT to ?
>>>>>>
>>>>>>  Jocke
>>>>>>
>>>>>
>>>>> It instantiates 2 config instances, one using /etc/portage/repos.conf
>>>>> (for build time DEPEND) and another one using
>>>>> $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
>>>>> You can see that it's joined with PORTAGE_CONFIGROOT in the
>>>>> load_repository_config function:
>>>>>
>>>>> https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f191113cccd049e11
>>>>> fdbe
>>>>> 73
>>>>> 493eb1efbf4bf89e#n971
>>>>
>>>> I see, doesn't this prevent exactly what I want to do?
>>>>
>>>> I can't see why this should be needed, it only creates a mess, another example:
>>>> I tried to specify exact version of my old binutils and while that worked, portage wanted
>>>> to pull in a newer binutils-config from the hosts master gentoo repo and
>>>> thus the build failed.
>>>>
>>>> If a someone really wants this behaviour, he can just add the hosts master repo
>>>> in his PORTAGE_CONFIGROOT IMHO
>>>>
>>
>> Maybe emerge --root-deps=rdeps is what you are looking for. This will
>> cause it to ignore DEPEND.
> 
> That is not the same is it? if I "emerge ncurses" it will build ncurses but still
> take the ebuild from the hosts master since it is newer version.
> 
> I realize now that I can change what repos are searched by using PORTAGE_REPOSITORIES=/my/own/repos.conf/
> but I still find the default behaviour very confusing and I don't see that it is useful.

The idea is that you have separate repositories configured for each
ROOT. If it's satisfying a build-time DEPEND that will be installed into
ROOT=/, then it's supposed to use the repositories configured for ROOT=/.

> What is 'extra_files' in load_repository_config()? Can I as a user add those or does portage
> add some of its own?

Currently, that argument is only used by repoman, since it uses a
StringIO instance to adjust the config there. Unless you are using the
python API directly, this functionality is currently not exposed to the
user.

>>
>>>
>>> Is there a way to make portage to prefer ebuilds from an overlay/other repo even if the master
>>> repo has newer versions?
>>>
>>>  Jocke
>>>
>>
>> You can use repo atoms in /etc/portage/package.mask. For example,
>> 'sys-devel/binutils-config::gentoo', or '*/*::gentoo'.
> 
> Nice! Can I also mask everything '*/*::gentoo' and then only unmask sys-devel/binutils-config::gentoo ?

Yes.
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Joakim Tjernlund]

On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote:
> On 05/06/15 13:22, Joakim Tjernlund wrote:
> > On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
> > > On 05/06/15 12:41, Joakim Tjernlund wrote:
> > > > On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote:
> > > > > On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
> > > > > > On 05/06/15 09:54, Joakim Tjernlund wrote:
> > > > > > > I am trying to rebuild an old cross sysroot and I got problems.
> > > > > > > I cannot make emerge to select my old ebuilds in an overlay over those
> > > > > > > in /usr/portage.
> > > > > > > 
> > > > > > > What new is since last time I did this is /etc/portage/repos.conf/
> > > > > > > I suspect emerge always reads /etc/portage/repos.conf/ no matter
> > > > > > > what I set PORTAGE_CONFIGROOT / ROOT to ?
> > > > > > > 
> > > > > > >  Jocke
> > > > > > > 
> > > > > > 
> > > > > > It instantiates 2 config instances, one using /etc/portage/repos.conf
> > > > > > (for build time DEPEND) and another one using
> > > > > > $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
> > > > > > You can see that it's joined with PORTAGE_CONFIGROOT in the
> > > > > > load_repository_config function:
> > > > > > 
> > > > > > https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f191113cccd04
> > > > > > 9e11
> > > > > > fdbe
> > > > > > 73
> > > > > > 493eb1efbf4bf89e#n971
> > > > > 
> > > > > I see, doesn't this prevent exactly what I want to do?
> > > > > 
> > > > > I can't see why this should be needed, it only creates a mess, another example:
> > > > > I tried to specify exact version of my old binutils and while that worked, portage wanted
> > > > > to pull in a newer binutils-config from the hosts master gentoo repo and
> > > > > thus the build failed.
> > > > > 
> > > > > If a someone really wants this behaviour, he can just add the hosts master repo
> > > > > in his PORTAGE_CONFIGROOT IMHO
> > > > > 
> > > 
> > > Maybe emerge --root-deps=rdeps is what you are looking for. This will
> > > cause it to ignore DEPEND.
> > 
> > That is not the same is it? if I "emerge ncurses" it will build ncurses but still
> > take the ebuild from the hosts master since it is newer version.
> > 
> > I realize now that I can change what repos are searched by using PORTAGE_REPOSITORIES=/my/own/repos.conf/
> > but I still find the default behaviour very confusing and I don't see that it is useful.
> 
> The idea is that you have separate repositories configured for each
> ROOT. If it's satisfying a build-time DEPEND that will be installed into
> ROOT=/, then it's supposed to use the repositories configured for ROOT=/.

I see, but in my case I only install into my sysroot so I don't want this behaviour.

Can you not add a test for CHOST/CBULID/CTARGET (never remeber which is which) so portage
only adds the hosts repo if they are the same?
Basically only add the master repo if not cross-building?

    Jocke 

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Zac Medico]

On 05/06/15 14:30, Joakim Tjernlund wrote:
> On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote:
>> On 05/06/15 13:22, Joakim Tjernlund wrote:
>>> On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
>>>> On 05/06/15 12:41, Joakim Tjernlund wrote:
>>>>> On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote:
>>>>>> On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
>>>>>>> On 05/06/15 09:54, Joakim Tjernlund wrote:
>>>>>>>> I am trying to rebuild an old cross sysroot and I got problems.
>>>>>>>> I cannot make emerge to select my old ebuilds in an overlay over those
>>>>>>>> in /usr/portage.
>>>>>>>>
>>>>>>>> What new is since last time I did this is /etc/portage/repos.conf/
>>>>>>>> I suspect emerge always reads /etc/portage/repos.conf/ no matter
>>>>>>>> what I set PORTAGE_CONFIGROOT / ROOT to ?
>>>>>>>>
>>>>>>>>  Jocke
>>>>>>>>
>>>>>>>
>>>>>>> It instantiates 2 config instances, one using /etc/portage/repos.conf
>>>>>>> (for build time DEPEND) and another one using
>>>>>>> $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
>>>>>>> You can see that it's joined with PORTAGE_CONFIGROOT in the
>>>>>>> load_repository_config function:
>>>>>>>
>>>>>>> https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f191113cccd04
>>>>>>> 9e11
>>>>>>> fdbe
>>>>>>> 73
>>>>>>> 493eb1efbf4bf89e#n971
>>>>>>
>>>>>> I see, doesn't this prevent exactly what I want to do?
>>>>>>
>>>>>> I can't see why this should be needed, it only creates a mess, another example:
>>>>>> I tried to specify exact version of my old binutils and while that worked, portage wanted
>>>>>> to pull in a newer binutils-config from the hosts master gentoo repo and
>>>>>> thus the build failed.
>>>>>>
>>>>>> If a someone really wants this behaviour, he can just add the hosts master repo
>>>>>> in his PORTAGE_CONFIGROOT IMHO
>>>>>>
>>>>
>>>> Maybe emerge --root-deps=rdeps is what you are looking for. This will
>>>> cause it to ignore DEPEND.
>>>
>>> That is not the same is it? if I "emerge ncurses" it will build ncurses but still
>>> take the ebuild from the hosts master since it is newer version.
>>>
>>> I realize now that I can change what repos are searched by using PORTAGE_REPOSITORIES=/my/own/repos.conf/
>>> but I still find the default behaviour very confusing and I don't see that it is useful.
>>
>> The idea is that you have separate repositories configured for each
>> ROOT. If it's satisfying a build-time DEPEND that will be installed into
>> ROOT=/, then it's supposed to use the repositories configured for ROOT=/.
> 
> I see, but in my case I only install into my sysroot so I don't want this behaviour.

So, why don't you use the --root-deps option?

> Can you not add a test for CHOST/CBULID/CTARGET (never remeber which is which) so portage
> only adds the hosts repo if they are the same?
> Basically only add the master repo if not cross-building?

It would have to be tied to an option like --root-deps. I still suspect
that --root-deps is what you really want.
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Joakim Tjernlund]

On Wed, 2015-05-06 at 14:36 -0700, Zac Medico wrote:
> On 05/06/15 14:30, Joakim Tjernlund wrote:
> > On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote:
> > > On 05/06/15 13:22, Joakim Tjernlund wrote:
> > > > On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
> > > > > On 05/06/15 12:41, Joakim Tjernlund wrote:
> > > > > > On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote:
> > > > > > > On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
> > > > > > > > On 05/06/15 09:54, Joakim Tjernlund wrote:
> > > > > > > > > I am trying to rebuild an old cross sysroot and I got problems.
> > > > > > > > > I cannot make emerge to select my old ebuilds in an overlay over those
> > > > > > > > > in /usr/portage.
> > > > > > > > > 
> > > > > > > > > What new is since last time I did this is /etc/portage/repos.conf/
> > > > > > > > > I suspect emerge always reads /etc/portage/repos.conf/ no matter
> > > > > > > > > what I set PORTAGE_CONFIGROOT / ROOT to ?
> > > > > > > > > 
> > > > > > > > >  Jocke
> > > > > > > > > 
> > > > > > > > 
> > > > > > > > It instantiates 2 config instances, one using /etc/portage/repos.conf
> > > > > > > > (for build time DEPEND) and another one using
> > > > > > > > $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
> > > > > > > > You can see that it's joined with PORTAGE_CONFIGROOT in the
> > > > > > > > load_repository_config function:
> > > > > > > > 
> > > > > > > > https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f191113cc
> > > > > > > > cd04
> > > > > > > > 9e11
> > > > > > > > fdbe
> > > > > > > > 73
> > > > > > > > 493eb1efbf4bf89e#n971
> > > > > > > 
> > > > > > > I see, doesn't this prevent exactly what I want to do?
> > > > > > > 
> > > > > > > I can't see why this should be needed, it only creates a mess, another example:
> > > > > > > I tried to specify exact version of my old binutils and while that worked, portage wanted
> > > > > > > to pull in a newer binutils-config from the hosts master gentoo repo and
> > > > > > > thus the build failed.
> > > > > > > 
> > > > > > > If a someone really wants this behaviour, he can just add the hosts master repo
> > > > > > > in his PORTAGE_CONFIGROOT IMHO
> > > > > > > 
> > > > > 
> > > > > Maybe emerge --root-deps=rdeps is what you are looking for. This will
> > > > > cause it to ignore DEPEND.
> > > > 
> > > > That is not the same is it? if I "emerge ncurses" it will build ncurses but still
> > > > take the ebuild from the hosts master since it is newer version.
> > > > 
> > > > I realize now that I can change what repos are searched by using 
> > > > PORTAGE_REPOSITORIES=/my/own/repos.conf/
> > > > but I still find the default behaviour very confusing and I don't see that it is useful.
> > > 
> > > The idea is that you have separate repositories configured for each
> > > ROOT. If it's satisfying a build-time DEPEND that will be installed into
> > > ROOT=/, then it's supposed to use the repositories configured for ROOT=/.
> > 
> > I see, but in my case I only install into my sysroot so I don't want this behaviour.
> 
> So, why don't you use the --root-deps option?

Just did(and --root-deps=rdeps too) and it didn't work, still wants to use
my newer hosts pkgs. :(

> 
> > Can you not add a test for CHOST/CBULID/CTARGET (never remeber which is which) so portage
> > only adds the hosts repo if they are the same?
> > Basically only add the master repo if not cross-building?
> 
> It would have to be tied to an option like --root-deps. I still suspect
> that --root-deps is what you really want.

No, I really think that portage is over doing things here.
Anyone that is using ROOT and PORTAGE_CONFIGROOT only needs the main repo iff
DEPEND pkgs are installed into /. When cross building you don't what DEPEND installed
into / or having the cross build use any DEPENDS which already are installed in /
In the cross case portage should only use what PORTAGE_CONFIGROOT points to. If the
cross builder wants to use /usr/portage he just adds this to the PORTAGE_CONFIGROOT's repos.conf

 Jocke 

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Joakim Tjernlund]

On Wed, 2015-05-06 at 21:57 +0000, Joakim Tjernlund wrote:
> On Wed, 2015-05-06 at 14:36 -0700, Zac Medico wrote:
> > On 05/06/15 14:30, Joakim Tjernlund wrote:
> > > On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote:
> > > > On 05/06/15 13:22, Joakim Tjernlund wrote:
> > > > > On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
> > > > > > On 05/06/15 12:41, Joakim Tjernlund wrote:
> > > > > > > On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote:
> > > > > > > > On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
> > > > > > > > > On 05/06/15 09:54, Joakim Tjernlund wrote:
> > > > > > > > > > I am trying to rebuild an old cross sysroot and I got problems.
> > > > > > > > > > I cannot make emerge to select my old ebuilds in an overlay over those
> > > > > > > > > > in /usr/portage.
> > > > > > > > > > 
> > > > > > > > > > What new is since last time I did this is /etc/portage/repos.conf/
> > > > > > > > > > I suspect emerge always reads /etc/portage/repos.conf/ no matter
> > > > > > > > > > what I set PORTAGE_CONFIGROOT / ROOT to ?
> > > > > > > > > > 
> > > > > > > > > >  Jocke
> > > > > > > > > > 
> > > > > > > > > 
> > > > > > > > > It instantiates 2 config instances, one using /etc/portage/repos.conf
> > > > > > > > > (for build time DEPEND) and another one using
> > > > > > > > > $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
> > > > > > > > > You can see that it's joined with PORTAGE_CONFIGROOT in the
> > > > > > > > > load_repository_config function:
> > > > > > > > > 
> > > > > > > > > https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f191113
> > > > > > > > > cc
> > > > > > > > > cd04
> > > > > > > > > 9e11
> > > > > > > > > fdbe
> > > > > > > > > 73
> > > > > > > > > 493eb1efbf4bf89e#n971
> > > > > > > > 
> > > > > > > > I see, doesn't this prevent exactly what I want to do?
> > > > > > > > 
> > > > > > > > I can't see why this should be needed, it only creates a mess, another example:
> > > > > > > > I tried to specify exact version of my old binutils and while that worked, portage wanted
> > > > > > > > to pull in a newer binutils-config from the hosts master gentoo repo and
> > > > > > > > thus the build failed.
> > > > > > > > 
> > > > > > > > If a someone really wants this behaviour, he can just add the hosts master repo
> > > > > > > > in his PORTAGE_CONFIGROOT IMHO
> > > > > > > > 
> > > > > > 
> > > > > > Maybe emerge --root-deps=rdeps is what you are looking for. This will
> > > > > > cause it to ignore DEPEND.
> > > > > 
> > > > > That is not the same is it? if I "emerge ncurses" it will build ncurses but still
> > > > > take the ebuild from the hosts master since it is newer version.
> > > > > 
> > > > > I realize now that I can change what repos are searched by using 
> > > > > PORTAGE_REPOSITORIES=/my/own/repos.conf/
> > > > > but I still find the default behaviour very confusing and I don't see that it is useful.
> > > > 
> > > > The idea is that you have separate repositories configured for each
> > > > ROOT. If it's satisfying a build-time DEPEND that will be installed into
> > > > ROOT=/, then it's supposed to use the repositories configured for ROOT=/.
> > > 
> > > I see, but in my case I only install into my sysroot so I don't want this behaviour.
> > 
> > So, why don't you use the --root-deps option?
> 
> Just did(and --root-deps=rdeps too) and it didn't work, still wants to use
> my newer hosts pkgs. :(
> 
> > 
> > > Can you not add a test for CHOST/CBULID/CTARGET (never remeber which is which) so portage
> > > only adds the hosts repo if they are the same?
> > > Basically only add the master repo if not cross-building?
> > 
> > It would have to be tied to an option like --root-deps. I still suspect
> > that --root-deps is what you really want.
> 
> No, I really think that portage is over doing things here.
> Anyone that is using ROOT and PORTAGE_CONFIGROOT only needs the main repo iff
> 

hmm, is ROOT and PORTAGE_CONFIGROOT really useful for non cross builds? Installing DEPEND
into host require you use the same conf as the host(USE mainly I guess)?

 Jocke

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Zac Medico]

On 05/06/15 15:09, Joakim Tjernlund wrote:
> On Wed, 2015-05-06 at 21:57 +0000, Joakim Tjernlund wrote:
>> On Wed, 2015-05-06 at 14:36 -0700, Zac Medico wrote:
>>> On 05/06/15 14:30, Joakim Tjernlund wrote:
>>>> On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote:
>>>>> On 05/06/15 13:22, Joakim Tjernlund wrote:
>>>>>> On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
>>>>>>> On 05/06/15 12:41, Joakim Tjernlund wrote:
>>>>>>>> On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote:
>>>>>>>>> On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
>>>>>>>>>> On 05/06/15 09:54, Joakim Tjernlund wrote:
>>>>>>>>>>> I am trying to rebuild an old cross sysroot and I got problems.
>>>>>>>>>>> I cannot make emerge to select my old ebuilds in an overlay over those
>>>>>>>>>>> in /usr/portage.
>>>>>>>>>>>
>>>>>>>>>>> What new is since last time I did this is /etc/portage/repos.conf/
>>>>>>>>>>> I suspect emerge always reads /etc/portage/repos.conf/ no matter
>>>>>>>>>>> what I set PORTAGE_CONFIGROOT / ROOT to ?
>>>>>>>>>>>
>>>>>>>>>>>  Jocke
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> It instantiates 2 config instances, one using /etc/portage/repos.conf
>>>>>>>>>> (for build time DEPEND) and another one using
>>>>>>>>>> $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
>>>>>>>>>> You can see that it's joined with PORTAGE_CONFIGROOT in the
>>>>>>>>>> load_repository_config function:
>>>>>>>>>>
>>>>>>>>>> https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f191113
>>>>>>>>>> cc
>>>>>>>>>> cd04
>>>>>>>>>> 9e11
>>>>>>>>>> fdbe
>>>>>>>>>> 73
>>>>>>>>>> 493eb1efbf4bf89e#n971
>>>>>>>>>
>>>>>>>>> I see, doesn't this prevent exactly what I want to do?
>>>>>>>>>
>>>>>>>>> I can't see why this should be needed, it only creates a mess, another example:
>>>>>>>>> I tried to specify exact version of my old binutils and while that worked, portage wanted
>>>>>>>>> to pull in a newer binutils-config from the hosts master gentoo repo and
>>>>>>>>> thus the build failed.
>>>>>>>>>
>>>>>>>>> If a someone really wants this behaviour, he can just add the hosts master repo
>>>>>>>>> in his PORTAGE_CONFIGROOT IMHO
>>>>>>>>>
>>>>>>>
>>>>>>> Maybe emerge --root-deps=rdeps is what you are looking for. This will
>>>>>>> cause it to ignore DEPEND.
>>>>>>
>>>>>> That is not the same is it? if I "emerge ncurses" it will build ncurses but still
>>>>>> take the ebuild from the hosts master since it is newer version.
>>>>>>
>>>>>> I realize now that I can change what repos are searched by using 
>>>>>> PORTAGE_REPOSITORIES=/my/own/repos.conf/
>>>>>> but I still find the default behaviour very confusing and I don't see that it is useful.
>>>>>
>>>>> The idea is that you have separate repositories configured for each
>>>>> ROOT. If it's satisfying a build-time DEPEND that will be installed into
>>>>> ROOT=/, then it's supposed to use the repositories configured for ROOT=/.
>>>>
>>>> I see, but in my case I only install into my sysroot so I don't want this behaviour.
>>>
>>> So, why don't you use the --root-deps option?
>>
>> Just did(and --root-deps=rdeps too) and it didn't work, still wants to use
>> my newer hosts pkgs. :(
>>
>>>
>>>> Can you not add a test for CHOST/CBULID/CTARGET (never remeber which is which) so portage
>>>> only adds the hosts repo if they are the same?
>>>> Basically only add the master repo if not cross-building?
>>>
>>> It would have to be tied to an option like --root-deps. I still suspect
>>> that --root-deps is what you really want.
>>
>> No, I really think that portage is over doing things here.
>> Anyone that is using ROOT and PORTAGE_CONFIGROOT only needs the main repo iff
>>
> 
> hmm, is ROOT and PORTAGE_CONFIGROOT really useful for non cross builds?

They are only for cross builds. What else would you use them for?

> Installing DEPEND
> into host require you use the same conf as the host(USE mainly I guess)?

No, they have separate configurations.
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Joakim Tjernlund]

On Wed, 2015-05-06 at 15:19 -0700, Zac Medico wrote:
> On 05/06/15 15:09, Joakim Tjernlund wrote:
> > On Wed, 2015-05-06 at 21:57 +0000, Joakim Tjernlund wrote:
> > > On Wed, 2015-05-06 at 14:36 -0700, Zac Medico wrote:
> > > > On 05/06/15 14:30, Joakim Tjernlund wrote:
> > > > > On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote:
> > > > > > On 05/06/15 13:22, Joakim Tjernlund wrote:
> > > > > > > On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
> > > > > > > > On 05/06/15 12:41, Joakim Tjernlund wrote:
> > > > > > > > > On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote:
> > > > > > > > > > On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
> > > > > > > > > > > On 05/06/15 09:54, Joakim Tjernlund wrote:
> > > > > > > > > > > > I am trying to rebuild an old cross sysroot and I got problems.
> > > > > > > > > > > > I cannot make emerge to select my old ebuilds in an overlay over those
> > > > > > > > > > > > in /usr/portage.
> > > > > > > > > > > > 
> > > > > > > > > > > > What new is since last time I did this is /etc/portage/repos.conf/
> > > > > > > > > > > > I suspect emerge always reads /etc/portage/repos.conf/ no matter
> > > > > > > > > > > > what I set PORTAGE_CONFIGROOT / ROOT to ?
> > > > > > > > > > > > 
> > > > > > > > > > > >  Jocke
> > > > > > > > > > > > 
> > > > > > > > > > > 
> > > > > > > > > > > It instantiates 2 config instances, one using /etc/portage/repos.conf
> > > > > > > > > > > (for build time DEPEND) and another one using
> > > > > > > > > > > $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
> > > > > > > > > > > You can see that it's joined with PORTAGE_CONFIGROOT in the
> > > > > > > > > > > load_repository_config function:
> > > > > > > > > > > 
> > > > > > > > > > > https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f19
> > > > > > > > > > > 1113
> > > > > > > > > > > cc
> > > > > > > > > > > cd04
> > > > > > > > > > > 9e11
> > > > > > > > > > > fdbe
> > > > > > > > > > > 73
> > > > > > > > > > > 493eb1efbf4bf89e#n971
> > > > > > > > > > 
> > > > > > > > > > I see, doesn't this prevent exactly what I want to do?
> > > > > > > > > > 
> > > > > > > > > > I can't see why this should be needed, it only creates a mess, another example:
> > > > > > > > > > I tried to specify exact version of my old binutils and while that worked, portage wanted
> > > > > > > > > > to pull in a newer binutils-config from the hosts master gentoo repo and
> > > > > > > > > > thus the build failed.
> > > > > > > > > > 
> > > > > > > > > > If a someone really wants this behaviour, he can just add the hosts master repo
> > > > > > > > > > in his PORTAGE_CONFIGROOT IMHO
> > > > > > > > > > 
> > > > > > > > 
> > > > > > > > Maybe emerge --root-deps=rdeps is what you are looking for. This will
> > > > > > > > cause it to ignore DEPEND.
> > > > > > > 
> > > > > > > That is not the same is it? if I "emerge ncurses" it will build ncurses but still
> > > > > > > take the ebuild from the hosts master since it is newer version.
> > > > > > > 
> > > > > > > I realize now that I can change what repos are searched by using 
> > > > > > > PORTAGE_REPOSITORIES=/my/own/repos.conf/
> > > > > > > but I still find the default behaviour very confusing and I don't see that it is useful.
> > > > > > 
> > > > > > The idea is that you have separate repositories configured for each
> > > > > > ROOT. If it's satisfying a build-time DEPEND that will be installed into
> > > > > > ROOT=/, then it's supposed to use the repositories configured for ROOT=/.
> > > > > 
> > > > > I see, but in my case I only install into my sysroot so I don't want this behaviour.
> > > > 
> > > > So, why don't you use the --root-deps option?
> > > 
> > > Just did(and --root-deps=rdeps too) and it didn't work, still wants to use
> > > my newer hosts pkgs. :(
> > > 
> > > > 
> > > > > Can you not add a test for CHOST/CBULID/CTARGET (never remeber which is which) so portage
> > > > > only adds the hosts repo if they are the same?
> > > > > Basically only add the master repo if not cross-building?
> > > > 
> > > > It would have to be tied to an option like --root-deps. I still suspect
> > > > that --root-deps is what you really want.
> > > 
> > > No, I really think that portage is over doing things here.
> > > Anyone that is using ROOT and PORTAGE_CONFIGROOT only needs the main repo iff
> > > 
> > 
> > hmm, is ROOT and PORTAGE_CONFIGROOT really useful for non cross builds?
> 
> They are only for cross builds. What else would you use them for?
maybe a small initramfs that needs some tweak to USE but not for
any DEPENDS.
You are saying that ROOT only build for that same arch should never use PORTAGE_CONFIGROOT?
  
> 
> > Installing DEPEND
> > into host require you use the same conf as the host(USE mainly I guess)?
> 
> No, they have separate configurations.

but here you say that are different(as in using PORTAGE_CONFIGROOT with ROOT)? 

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Zac Medico]

On 05/06/15 14:57, Joakim Tjernlund wrote:
> On Wed, 2015-05-06 at 14:36 -0700, Zac Medico wrote:
>> On 05/06/15 14:30, Joakim Tjernlund wrote:
>>> On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote:
>>>> On 05/06/15 13:22, Joakim Tjernlund wrote:
>>>>> On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
>>>>>> On 05/06/15 12:41, Joakim Tjernlund wrote:
>>>>>>> On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote:
>>>>>>>> On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
>>>>>>>>> On 05/06/15 09:54, Joakim Tjernlund wrote:
>>>>>>>>>> I am trying to rebuild an old cross sysroot and I got problems.
>>>>>>>>>> I cannot make emerge to select my old ebuilds in an overlay over those
>>>>>>>>>> in /usr/portage.
>>>>>>>>>>
>>>>>>>>>> What new is since last time I did this is /etc/portage/repos.conf/
>>>>>>>>>> I suspect emerge always reads /etc/portage/repos.conf/ no matter
>>>>>>>>>> what I set PORTAGE_CONFIGROOT / ROOT to ?
>>>>>>>>>>
>>>>>>>>>>  Jocke
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> It instantiates 2 config instances, one using /etc/portage/repos.conf
>>>>>>>>> (for build time DEPEND) and another one using
>>>>>>>>> $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
>>>>>>>>> You can see that it's joined with PORTAGE_CONFIGROOT in the
>>>>>>>>> load_repository_config function:
>>>>>>>>>
>>>>>>>>> https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f191113cc
>>>>>>>>> cd04
>>>>>>>>> 9e11
>>>>>>>>> fdbe
>>>>>>>>> 73
>>>>>>>>> 493eb1efbf4bf89e#n971
>>>>>>>>
>>>>>>>> I see, doesn't this prevent exactly what I want to do?
>>>>>>>>
>>>>>>>> I can't see why this should be needed, it only creates a mess, another example:
>>>>>>>> I tried to specify exact version of my old binutils and while that worked, portage wanted
>>>>>>>> to pull in a newer binutils-config from the hosts master gentoo repo and
>>>>>>>> thus the build failed.
>>>>>>>>
>>>>>>>> If a someone really wants this behaviour, he can just add the hosts master repo
>>>>>>>> in his PORTAGE_CONFIGROOT IMHO
>>>>>>>>
>>>>>>
>>>>>> Maybe emerge --root-deps=rdeps is what you are looking for. This will
>>>>>> cause it to ignore DEPEND.
>>>>>
>>>>> That is not the same is it? if I "emerge ncurses" it will build ncurses but still
>>>>> take the ebuild from the hosts master since it is newer version.
>>>>>
>>>>> I realize now that I can change what repos are searched by using 
>>>>> PORTAGE_REPOSITORIES=/my/own/repos.conf/
>>>>> but I still find the default behaviour very confusing and I don't see that it is useful.
>>>>
>>>> The idea is that you have separate repositories configured for each
>>>> ROOT. If it's satisfying a build-time DEPEND that will be installed into
>>>> ROOT=/, then it's supposed to use the repositories configured for ROOT=/.
>>>
>>> I see, but in my case I only install into my sysroot so I don't want this behaviour.
>>
>> So, why don't you use the --root-deps option?
> 
> Just did(and --root-deps=rdeps too) and it didn't work, still wants to use
> my newer hosts pkgs. :(

It shouldn't do that. It sounds like maybe the [gentoo] config
from/usr/share/portage/config/repos.conf is the source of your problems,
since you $PORTAGE_CONFIGROOT config will always inherit that. Would
that be consistent with your observations?
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Joakim Tjernlund]

On Wed, 2015-05-06 at 15:16 -0700, Zac Medico wrote:
> On 05/06/15 14:57, Joakim Tjernlund wrote:
> > On Wed, 2015-05-06 at 14:36 -0700, Zac Medico wrote:
> > > On 05/06/15 14:30, Joakim Tjernlund wrote:
> > > > On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote:
> > > > > On 05/06/15 13:22, Joakim Tjernlund wrote:
> > > > > > On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
> > > > > > > On 05/06/15 12:41, Joakim Tjernlund wrote:
> > > > > > > > On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote:
> > > > > > > > > On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
> > > > > > > > > > On 05/06/15 09:54, Joakim Tjernlund wrote:
> > > > > > > > > > > I am trying to rebuild an old cross sysroot and I got problems.
> > > > > > > > > > > I cannot make emerge to select my old ebuilds in an overlay over those
> > > > > > > > > > > in /usr/portage.
> > > > > > > > > > > 
> > > > > > > > > > > What new is since last time I did this is /etc/portage/repos.conf/
> > > > > > > > > > > I suspect emerge always reads /etc/portage/repos.conf/ no matter
> > > > > > > > > > > what I set PORTAGE_CONFIGROOT / ROOT to ?
> > > > > > > > > > > 
> > > > > > > > > > >  Jocke
> > > > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > > It instantiates 2 config instances, one using /etc/portage/repos.conf
> > > > > > > > > > (for build time DEPEND) and another one using
> > > > > > > > > > $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
> > > > > > > > > > You can see that it's joined with PORTAGE_CONFIGROOT in the
> > > > > > > > > > load_repository_config function:
> > > > > > > > > > 
> > > > > > > > > > https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f1911
> > > > > > > > > > 13cc
> > > > > > > > > > cd04
> > > > > > > > > > 9e11
> > > > > > > > > > fdbe
> > > > > > > > > > 73
> > > > > > > > > > 493eb1efbf4bf89e#n971
> > > > > > > > > 
> > > > > > > > > I see, doesn't this prevent exactly what I want to do?
> > > > > > > > > 
> > > > > > > > > I can't see why this should be needed, it only creates a mess, another example:
> > > > > > > > > I tried to specify exact version of my old binutils and while that worked, portage wanted
> > > > > > > > > to pull in a newer binutils-config from the hosts master gentoo repo and
> > > > > > > > > thus the build failed.
> > > > > > > > > 
> > > > > > > > > If a someone really wants this behaviour, he can just add the hosts master repo
> > > > > > > > > in his PORTAGE_CONFIGROOT IMHO
> > > > > > > > > 
> > > > > > > 
> > > > > > > Maybe emerge --root-deps=rdeps is what you are looking for. This will
> > > > > > > cause it to ignore DEPEND.
> > > > > > 
> > > > > > That is not the same is it? if I "emerge ncurses" it will build ncurses but still
> > > > > > take the ebuild from the hosts master since it is newer version.
> > > > > > 
> > > > > > I realize now that I can change what repos are searched by using 
> > > > > > PORTAGE_REPOSITORIES=/my/own/repos.conf/
> > > > > > but I still find the default behaviour very confusing and I don't see that it is useful.
> > > > > 
> > > > > The idea is that you have separate repositories configured for each
> > > > > ROOT. If it's satisfying a build-time DEPEND that will be installed into
> > > > > ROOT=/, then it's supposed to use the repositories configured for ROOT=/.
> > > > 
> > > > I see, but in my case I only install into my sysroot so I don't want this behaviour.
> > > 
> > > So, why don't you use the --root-deps option?
> > 
> > Just did(and --root-deps=rdeps too) and it didn't work, still wants to use
> > my newer hosts pkgs. :(
> 
> It shouldn't do that. It sounds like maybe the [gentoo] config
> from/usr/share/portage/config/repos.conf is the source of your problems,
> since you $PORTAGE_CONFIGROOT config will always inherit that. Would
> that be consistent with your observations?

Moving that file out of the way changed things, now I got I profile error:
!!! Unable to parse profile: '/etc/portage/make.profile'
!!! ParseError: Parent 'gentoo:default/linux/amd64/13.0' not found:
'/var/lib/layman/transmode/profiles/gentoo64-server/parent'
!!! Your current profile is invalid. If you have just changed your profile
!!! configuration, you should revert back to the previous configuration.
!!! Allowed actions are limited to --help, --info, --search, --sync, and
!!! --version.

Which I think is a problem in my cross env.
Strange though that it fell into my hosts profile though.

 Jocke

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Joakim Tjernlund]

On Wed, 2015-05-06 at 22:45 +0000, Joakim Tjernlund wrote:
> On Wed, 2015-05-06 at 15:16 -0700, Zac Medico wrote:
> > On 05/06/15 14:57, Joakim Tjernlund wrote:
> > > On Wed, 2015-05-06 at 14:36 -0700, Zac Medico wrote:
> > > > On 05/06/15 14:30, Joakim Tjernlund wrote:
> > > > > On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote:
> > > > > > On 05/06/15 13:22, Joakim Tjernlund wrote:
> > > > > > > On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
> > > > > > > > On 05/06/15 12:41, Joakim Tjernlund wrote:
> > > > > > > > > On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote:
> > > > > > > > > > On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
> > > > > > > > > > > On 05/06/15 09:54, Joakim Tjernlund wrote:
> > > > > > > > > > > > I am trying to rebuild an old cross sysroot and I got problems.
> > > > > > > > > > > > I cannot make emerge to select my old ebuilds in an overlay over those
> > > > > > > > > > > > in /usr/portage.
> > > > > > > > > > > > 
> > > > > > > > > > > > What new is since last time I did this is /etc/portage/repos.conf/
> > > > > > > > > > > > I suspect emerge always reads /etc/portage/repos.conf/ no matter
> > > > > > > > > > > > what I set PORTAGE_CONFIGROOT / ROOT to ?
> > > > > > > > > > > > 
> > > > > > > > > > > >  Jocke
> > > > > > > > > > > > 
> > > > > > > > > > > 
> > > > > > > > > > > It instantiates 2 config instances, one using /etc/portage/repos.conf
> > > > > > > > > > > (for build time DEPEND) and another one using
> > > > > > > > > > > $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
> > > > > > > > > > > You can see that it's joined with PORTAGE_CONFIGROOT in the
> > > > > > > > > > > load_repository_config function:
> > > > > > > > > > > 
> > > > > > > > > > > https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f19
> > > > > > > > > > > 11
> > > > > > > > > > > 13cc
> > > > > > > > > > > cd04
> > > > > > > > > > > 9e11
> > > > > > > > > > > fdbe
> > > > > > > > > > > 73
> > > > > > > > > > > 493eb1efbf4bf89e#n971
> > > > > > > > > > 
> > > > > > > > > > I see, doesn't this prevent exactly what I want to do?
> > > > > > > > > > 
> > > > > > > > > > I can't see why this should be needed, it only creates a mess, another example:
> > > > > > > > > > I tried to specify exact version of my old binutils and while that worked, portage wanted
> > > > > > > > > > to pull in a newer binutils-config from the hosts master gentoo repo and
> > > > > > > > > > thus the build failed.
> > > > > > > > > > 
> > > > > > > > > > If a someone really wants this behaviour, he can just add the hosts master repo
> > > > > > > > > > in his PORTAGE_CONFIGROOT IMHO
> > > > > > > > > > 
> > > > > > > > 
> > > > > > > > Maybe emerge --root-deps=rdeps is what you are looking for. This will
> > > > > > > > cause it to ignore DEPEND.
> > > > > > > 
> > > > > > > That is not the same is it? if I "emerge ncurses" it will build ncurses but still
> > > > > > > take the ebuild from the hosts master since it is newer version.
> > > > > > > 
> > > > > > > I realize now that I can change what repos are searched by using 
> > > > > > > PORTAGE_REPOSITORIES=/my/own/repos.conf/
> > > > > > > but I still find the default behaviour very confusing and I don't see that it is useful.
> > > > > > 
> > > > > > The idea is that you have separate repositories configured for each
> > > > > > ROOT. If it's satisfying a build-time DEPEND that will be installed into
> > > > > > ROOT=/, then it's supposed to use the repositories configured for ROOT=/.
> > > > > 
> > > > > I see, but in my case I only install into my sysroot so I don't want this behaviour.
> > > > 
> > > > So, why don't you use the --root-deps option?
> > > 
> > > Just did(and --root-deps=rdeps too) and it didn't work, still wants to use
> > > my newer hosts pkgs. :(
> > 
> > It shouldn't do that. It sounds like maybe the [gentoo] config
> > from/usr/share/portage/config/repos.conf is the source of your problems,
> > since you $PORTAGE_CONFIGROOT config will always inherit that. Would
> > that be consistent with your observations?
> 
> Moving that file out of the way changed things, now I got I profile error:
> !!! Unable to parse profile: '/etc/portage/make.profile'
> !!! ParseError: Parent 'gentoo:default/linux/amd64/13.0' not found:
> '/var/lib/layman/transmode/profiles/gentoo64-server/parent'
> !!! Your current profile is invalid. If you have just changed your profile
> !!! configuration, you should revert back to the previous configuration.
> !!! Allowed actions are limited to --help, --info, --search, --sync, and
> !!! --version.
> 
> Which I think is a problem in my cross env.

No, this is not it. Portage just bails when reading the host profile which it should not.

Note: defining
  PORTAGE_REPOSITORIES=/my/own/repos.conf
gives the same error.

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Zac Medico]

On 05/07/2015 03:51 AM, Joakim Tjernlund wrote:
> On Wed, 2015-05-06 at 22:45 +0000, Joakim Tjernlund wrote:
>> On Wed, 2015-05-06 at 15:16 -0700, Zac Medico wrote:
>>> On 05/06/15 14:57, Joakim Tjernlund wrote:
>>>> On Wed, 2015-05-06 at 14:36 -0700, Zac Medico wrote:
>>>>> On 05/06/15 14:30, Joakim Tjernlund wrote:
>>>>>> On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote:
>>>>>>> On 05/06/15 13:22, Joakim Tjernlund wrote:
>>>>>>>> On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
>>>>>>>>> On 05/06/15 12:41, Joakim Tjernlund wrote:
>>>>>>>>>> On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote:
>>>>>>>>>>> On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
>>>>>>>>>>>> On 05/06/15 09:54, Joakim Tjernlund wrote:
>>>>>>>>>>>>> I am trying to rebuild an old cross sysroot and I got problems.
>>>>>>>>>>>>> I cannot make emerge to select my old ebuilds in an overlay over those
>>>>>>>>>>>>> in /usr/portage.
>>>>>>>>>>>>>
>>>>>>>>>>>>> What new is since last time I did this is /etc/portage/repos.conf/
>>>>>>>>>>>>> I suspect emerge always reads /etc/portage/repos.conf/ no matter
>>>>>>>>>>>>> what I set PORTAGE_CONFIGROOT / ROOT to ?
>>>>>>>>>>>>>
>>>>>>>>>>>>>  Jocke
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> It instantiates 2 config instances, one using /etc/portage/repos.conf
>>>>>>>>>>>> (for build time DEPEND) and another one using
>>>>>>>>>>>> $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
>>>>>>>>>>>> You can see that it's joined with PORTAGE_CONFIGROOT in the
>>>>>>>>>>>> load_repository_config function:
>>>>>>>>>>>>
>>>>>>>>>>>> https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f19
>>>>>>>>>>>> 11
>>>>>>>>>>>> 13cc
>>>>>>>>>>>> cd04
>>>>>>>>>>>> 9e11
>>>>>>>>>>>> fdbe
>>>>>>>>>>>> 73
>>>>>>>>>>>> 493eb1efbf4bf89e#n971
>>>>>>>>>>>
>>>>>>>>>>> I see, doesn't this prevent exactly what I want to do?
>>>>>>>>>>>
>>>>>>>>>>> I can't see why this should be needed, it only creates a mess, another example:
>>>>>>>>>>> I tried to specify exact version of my old binutils and while that worked, portage wanted
>>>>>>>>>>> to pull in a newer binutils-config from the hosts master gentoo repo and
>>>>>>>>>>> thus the build failed.
>>>>>>>>>>>
>>>>>>>>>>> If a someone really wants this behaviour, he can just add the hosts master repo
>>>>>>>>>>> in his PORTAGE_CONFIGROOT IMHO
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Maybe emerge --root-deps=rdeps is what you are looking for. This will
>>>>>>>>> cause it to ignore DEPEND.
>>>>>>>>
>>>>>>>> That is not the same is it? if I "emerge ncurses" it will build ncurses but still
>>>>>>>> take the ebuild from the hosts master since it is newer version.
>>>>>>>>
>>>>>>>> I realize now that I can change what repos are searched by using 
>>>>>>>> PORTAGE_REPOSITORIES=/my/own/repos.conf/
>>>>>>>> but I still find the default behaviour very confusing and I don't see that it is useful.
>>>>>>>
>>>>>>> The idea is that you have separate repositories configured for each
>>>>>>> ROOT. If it's satisfying a build-time DEPEND that will be installed into
>>>>>>> ROOT=/, then it's supposed to use the repositories configured for ROOT=/.
>>>>>>
>>>>>> I see, but in my case I only install into my sysroot so I don't want this behaviour.
>>>>>
>>>>> So, why don't you use the --root-deps option?
>>>>
>>>> Just did(and --root-deps=rdeps too) and it didn't work, still wants to use
>>>> my newer hosts pkgs. :(
>>>
>>> It shouldn't do that. It sounds like maybe the [gentoo] config
>>> from/usr/share/portage/config/repos.conf is the source of your problems,
>>> since you $PORTAGE_CONFIGROOT config will always inherit that. Would
>>> that be consistent with your observations?
>>
>> Moving that file out of the way changed things, now I got I profile error:
>> !!! Unable to parse profile: '/etc/portage/make.profile'
>> !!! ParseError: Parent 'gentoo:default/linux/amd64/13.0' not found:
>> '/var/lib/layman/transmode/profiles/gentoo64-server/parent'
>> !!! Your current profile is invalid. If you have just changed your profile
>> !!! configuration, you should revert back to the previous configuration.
>> !!! Allowed actions are limited to --help, --info, --search, --sync, and
>> !!! --version.
>>
>> Which I think is a problem in my cross env.
> 
> No, this is not it. Portage just bails when reading the host profile which it should not.
> 
> Note: defining
>   PORTAGE_REPOSITORIES=/my/own/repos.conf
> gives the same error.
> 

According to the error message, your transmode profile inherits a gentoo
profile, so you need the gentoo repository (at least the relevant profile).
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Joakim Tjernlund]

On Thu, 2015-05-07 at 14:09 -0700, Zac Medico wrote:
> On 05/07/2015 03:51 AM, Joakim Tjernlund wrote:
> > On Wed, 2015-05-06 at 22:45 +0000, Joakim Tjernlund wrote:
> > > On Wed, 2015-05-06 at 15:16 -0700, Zac Medico wrote:
> > > > On 05/06/15 14:57, Joakim Tjernlund wrote:
> > > > > On Wed, 2015-05-06 at 14:36 -0700, Zac Medico wrote:
> > > > > > On 05/06/15 14:30, Joakim Tjernlund wrote:
> > > > > > > On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote:
> > > > > > > > On 05/06/15 13:22, Joakim Tjernlund wrote:
> > > > > > > > > On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
> > > > > > > > > > On 05/06/15 12:41, Joakim Tjernlund wrote:
> > > > > > > > > > > On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote:
> > > > > > > > > > > > On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
> > > > > > > > > > > > > On 05/06/15 09:54, Joakim Tjernlund wrote:
> > > > > > > > > > > > > > I am trying to rebuild an old cross sysroot and I got problems.
> > > > > > > > > > > > > > I cannot make emerge to select my old ebuilds in an overlay over those
> > > > > > > > > > > > > > in /usr/portage.
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > What new is since last time I did this is /etc/portage/repos.conf/
> > > > > > > > > > > > > > I suspect emerge always reads /etc/portage/repos.conf/ no matter
> > > > > > > > > > > > > > what I set PORTAGE_CONFIGROOT / ROOT to ?
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > >  Jocke
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > 
> > > > > > > > > > > > > It instantiates 2 config instances, one using /etc/portage/repos.conf
> > > > > > > > > > > > > (for build time DEPEND) and another one using
> > > > > > > > > > > > > $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
> > > > > > > > > > > > > You can see that it's joined with PORTAGE_CONFIGROOT in the
> > > > > > > > > > > > > load_repository_config function:
> > > > > > > > > > > > > 
> > > > > > > > > > > > > https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=
> > > > > > > > > > > > > 0f19
> > > > > > > > > > > > > 11
> > > > > > > > > > > > > 13cc
> > > > > > > > > > > > > cd04
> > > > > > > > > > > > > 9e11
> > > > > > > > > > > > > fdbe
> > > > > > > > > > > > > 73
> > > > > > > > > > > > > 493eb1efbf4bf89e#n971
> > > > > > > > > > > > 
> > > > > > > > > > > > I see, doesn't this prevent exactly what I want to do?
> > > > > > > > > > > > 
> > > > > > > > > > > > I can't see why this should be needed, it only creates a mess, another example:
> > > > > > > > > > > > I tried to specify exact version of my old binutils and while that worked, portage 
> > > > > > > > > > > > wanted
> > > > > > > > > > > > to pull in a newer binutils-config from the hosts master gentoo repo and
> > > > > > > > > > > > thus the build failed.
> > > > > > > > > > > > 
> > > > > > > > > > > > If a someone really wants this behaviour, he can just add the hosts master repo
> > > > > > > > > > > > in his PORTAGE_CONFIGROOT IMHO
> > > > > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > > Maybe emerge --root-deps=rdeps is what you are looking for. This will
> > > > > > > > > > cause it to ignore DEPEND.
> > > > > > > > > 
> > > > > > > > > That is not the same is it? if I "emerge ncurses" it will build ncurses but still
> > > > > > > > > take the ebuild from the hosts master since it is newer version.
> > > > > > > > > 
> > > > > > > > > I realize now that I can change what repos are searched by using 
> > > > > > > > > PORTAGE_REPOSITORIES=/my/own/repos.conf/
> > > > > > > > > but I still find the default behaviour very confusing and I don't see that it is useful.
> > > > > > > > 
> > > > > > > > The idea is that you have separate repositories configured for each
> > > > > > > > ROOT. If it's satisfying a build-time DEPEND that will be installed into
> > > > > > > > ROOT=/, then it's supposed to use the repositories configured for ROOT=/.
> > > > > > > 
> > > > > > > I see, but in my case I only install into my sysroot so I don't want this behaviour.
> > > > > > 
> > > > > > So, why don't you use the --root-deps option?
> > > > > 
> > > > > Just did(and --root-deps=rdeps too) and it didn't work, still wants to use
> > > > > my newer hosts pkgs. :(
> > > > 
> > > > It shouldn't do that. It sounds like maybe the [gentoo] config
> > > > from/usr/share/portage/config/repos.conf is the source of your problems,
> > > > since you $PORTAGE_CONFIGROOT config will always inherit that. Would
> > > > that be consistent with your observations?
> > > 
> > > Moving that file out of the way changed things, now I got I profile error:
> > > !!! Unable to parse profile: '/etc/portage/make.profile'
> > > !!! ParseError: Parent 'gentoo:default/linux/amd64/13.0' not found:
> > > '/var/lib/layman/transmode/profiles/gentoo64-server/parent'
> > > !!! Your current profile is invalid. If you have just changed your profile
> > > !!! configuration, you should revert back to the previous configuration.
> > > !!! Allowed actions are limited to --help, --info, --search, --sync, and
> > > !!! --version.
> > > 
> > > Which I think is a problem in my cross env.
> > 
> > No, this is not it. Portage just bails when reading the host profile which it should not.
> > 
> > Note: defining
> >   PORTAGE_REPOSITORIES=/my/own/repos.conf
> > gives the same error.
> > 
> 
> According to the error message, your transmode profile inherits a gentoo
> profile, so you need the gentoo repository (at least the relevant profile).

I have a my own profile in PORTAGE_CONFIGROOT which does not
reference the host /etc/portage/make.profile at all so I think
portage is using the wrong profile.

Futhermore, it does not understand the host profile, probably
because my own PORTAGE_CONFIGROOT don't have profile-formats = portage-2

 Jocke

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Zac Medico]

On 05/07/2015 11:43 PM, Joakim Tjernlund wrote:
> On Thu, 2015-05-07 at 14:09 -0700, Zac Medico wrote:
>> On 05/07/2015 03:51 AM, Joakim Tjernlund wrote:
>>> On Wed, 2015-05-06 at 22:45 +0000, Joakim Tjernlund wrote:
>>>> On Wed, 2015-05-06 at 15:16 -0700, Zac Medico wrote:
>>>>> On 05/06/15 14:57, Joakim Tjernlund wrote:
>>>>>> On Wed, 2015-05-06 at 14:36 -0700, Zac Medico wrote:
>>>>>>> On 05/06/15 14:30, Joakim Tjernlund wrote:
>>>>>>>> On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote:
>>>>>>>>> On 05/06/15 13:22, Joakim Tjernlund wrote:
>>>>>>>>>> On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
>>>>>>>>>>> On 05/06/15 12:41, Joakim Tjernlund wrote:
>>>>>>>>>>>> On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote:
>>>>>>>>>>>>> On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
>>>>>>>>>>>>>> On 05/06/15 09:54, Joakim Tjernlund wrote:
>>>>>>>>>>>>>>> I am trying to rebuild an old cross sysroot and I got problems.
>>>>>>>>>>>>>>> I cannot make emerge to select my old ebuilds in an overlay over those
>>>>>>>>>>>>>>> in /usr/portage.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> What new is since last time I did this is /etc/portage/repos.conf/
>>>>>>>>>>>>>>> I suspect emerge always reads /etc/portage/repos.conf/ no matter
>>>>>>>>>>>>>>> what I set PORTAGE_CONFIGROOT / ROOT to ?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>  Jocke
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> It instantiates 2 config instances, one using /etc/portage/repos.conf
>>>>>>>>>>>>>> (for build time DEPEND) and another one using
>>>>>>>>>>>>>> $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
>>>>>>>>>>>>>> You can see that it's joined with PORTAGE_CONFIGROOT in the
>>>>>>>>>>>>>> load_repository_config function:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=
>>>>>>>>>>>>>> 0f19
>>>>>>>>>>>>>> 11
>>>>>>>>>>>>>> 13cc
>>>>>>>>>>>>>> cd04
>>>>>>>>>>>>>> 9e11
>>>>>>>>>>>>>> fdbe
>>>>>>>>>>>>>> 73
>>>>>>>>>>>>>> 493eb1efbf4bf89e#n971
>>>>>>>>>>>>>
>>>>>>>>>>>>> I see, doesn't this prevent exactly what I want to do?
>>>>>>>>>>>>>
>>>>>>>>>>>>> I can't see why this should be needed, it only creates a mess, another example:
>>>>>>>>>>>>> I tried to specify exact version of my old binutils and while that worked, portage 
>>>>>>>>>>>>> wanted
>>>>>>>>>>>>> to pull in a newer binutils-config from the hosts master gentoo repo and
>>>>>>>>>>>>> thus the build failed.
>>>>>>>>>>>>>
>>>>>>>>>>>>> If a someone really wants this behaviour, he can just add the hosts master repo
>>>>>>>>>>>>> in his PORTAGE_CONFIGROOT IMHO
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Maybe emerge --root-deps=rdeps is what you are looking for. This will
>>>>>>>>>>> cause it to ignore DEPEND.
>>>>>>>>>>
>>>>>>>>>> That is not the same is it? if I "emerge ncurses" it will build ncurses but still
>>>>>>>>>> take the ebuild from the hosts master since it is newer version.
>>>>>>>>>>
>>>>>>>>>> I realize now that I can change what repos are searched by using 
>>>>>>>>>> PORTAGE_REPOSITORIES=/my/own/repos.conf/
>>>>>>>>>> but I still find the default behaviour very confusing and I don't see that it is useful.
>>>>>>>>>
>>>>>>>>> The idea is that you have separate repositories configured for each
>>>>>>>>> ROOT. If it's satisfying a build-time DEPEND that will be installed into
>>>>>>>>> ROOT=/, then it's supposed to use the repositories configured for ROOT=/.
>>>>>>>>
>>>>>>>> I see, but in my case I only install into my sysroot so I don't want this behaviour.
>>>>>>>
>>>>>>> So, why don't you use the --root-deps option?
>>>>>>
>>>>>> Just did(and --root-deps=rdeps too) and it didn't work, still wants to use
>>>>>> my newer hosts pkgs. :(
>>>>>
>>>>> It shouldn't do that. It sounds like maybe the [gentoo] config
>>>>> from/usr/share/portage/config/repos.conf is the source of your problems,
>>>>> since you $PORTAGE_CONFIGROOT config will always inherit that. Would
>>>>> that be consistent with your observations?
>>>>
>>>> Moving that file out of the way changed things, now I got I profile error:
>>>> !!! Unable to parse profile: '/etc/portage/make.profile'
>>>> !!! ParseError: Parent 'gentoo:default/linux/amd64/13.0' not found:
>>>> '/var/lib/layman/transmode/profiles/gentoo64-server/parent'
>>>> !!! Your current profile is invalid. If you have just changed your profile
>>>> !!! configuration, you should revert back to the previous configuration.
>>>> !!! Allowed actions are limited to --help, --info, --search, --sync, and
>>>> !!! --version.
>>>>
>>>> Which I think is a problem in my cross env.
>>>
>>> No, this is not it. Portage just bails when reading the host profile which it should not.
>>>
>>> Note: defining
>>>   PORTAGE_REPOSITORIES=/my/own/repos.conf
>>> gives the same error.
>>>
>>
>> According to the error message, your transmode profile inherits a gentoo
>> profile, so you need the gentoo repository (at least the relevant profile).
> 
> I have a my own profile in PORTAGE_CONFIGROOT which does not
> reference the host /etc/portage/make.profile at all so I think
> portage is using the wrong profile.

When using ROOT=/foo, it always instantiates 2 profiles, and it uses one
profile for ROOT=/foo and the other profile for ROOT=/.

> Futhermore, it does not understand the host profile, probably
> because my own PORTAGE_CONFIGROOT don't have profile-formats = portage-2

You're saying this beciase of the above ParseError? I think maybe what
you want to do keep the default /usr/share/portage/config/repos.conf and
mask */*::gentoo in $PORTAGE_CONFIGROOT/etc/portage/package.mask.
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Joakim Tjernlund]

On Fri, 2015-05-08 at 11:32 -0700, Zac Medico wrote:
> On 05/07/2015 11:43 PM, Joakim Tjernlund wrote:
> > On Thu, 2015-05-07 at 14:09 -0700, Zac Medico wrote:
> > > On 05/07/2015 03:51 AM, Joakim Tjernlund wrote:
> > > > On Wed, 2015-05-06 at 22:45 +0000, Joakim Tjernlund wrote:
> > > > > On Wed, 2015-05-06 at 15:16 -0700, Zac Medico wrote:
> > > > > > On 05/06/15 14:57, Joakim Tjernlund wrote:
> > > > > > > On Wed, 2015-05-06 at 14:36 -0700, Zac Medico wrote:
> > > > > > > > On 05/06/15 14:30, Joakim Tjernlund wrote:
> > > > > > > > > On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote:
> > > > > > > > > > On 05/06/15 13:22, Joakim Tjernlund wrote:
> > > > > > > > > > > On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
> > > > > > > > > > > > On 05/06/15 12:41, Joakim Tjernlund wrote:
> > > > > > > > > > > > > On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote:
> > > > > > > > > > > > > > On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
> > > > > > > > > > > > > > > On 05/06/15 09:54, Joakim Tjernlund wrote:
> > > > > > > > > > > > > > > > I am trying to rebuild an old cross sysroot and I got problems.
> > > > > > > > > > > > > > > > I cannot make emerge to select my old ebuilds in an overlay over those
> > > > > > > > > > > > > > > > in /usr/portage.
> > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > What new is since last time I did this is /etc/portage/repos.conf/
> > > > > > > > > > > > > > > > I suspect emerge always reads /etc/portage/repos.conf/ no matter
> > > > > > > > > > > > > > > > what I set PORTAGE_CONFIGROOT / ROOT to ?
> > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > >  Jocke
> > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > It instantiates 2 config instances, one using /etc/portage/repos.conf
> > > > > > > > > > > > > > > (for build time DEPEND) and another one using
> > > > > > > > > > > > > > > $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
> > > > > > > > > > > > > > > You can see that it's joined with PORTAGE_CONFIGROOT in the
> > > > > > > > > > > > > > > load_repository_config function:
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py
> > > > > > > > > > > > > > > ?id=
> > > > > > > > > > > > > > > 0f19
> > > > > > > > > > > > > > > 11
> > > > > > > > > > > > > > > 13cc
> > > > > > > > > > > > > > > cd04
> > > > > > > > > > > > > > > 9e11
> > > > > > > > > > > > > > > fdbe
> > > > > > > > > > > > > > > 73
> > > > > > > > > > > > > > > 493eb1efbf4bf89e#n971
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > I see, doesn't this prevent exactly what I want to do?
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > I can't see why this should be needed, it only creates a mess, another example:
> > > > > > > > > > > > > > I tried to specify exact version of my old binutils and while that worked, 
> > > > > > > > > > > > > > portage 
> > > > > > > > > > > > > > wanted
> > > > > > > > > > > > > > to pull in a newer binutils-config from the hosts master gentoo repo and
> > > > > > > > > > > > > > thus the build failed.
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > If a someone really wants this behaviour, he can just add the hosts master repo
> > > > > > > > > > > > > > in his PORTAGE_CONFIGROOT IMHO
> > > > > > > > > > > > > > 
> > > > > > > > > > > > 
> > > > > > > > > > > > Maybe emerge --root-deps=rdeps is what you are looking for. This will
> > > > > > > > > > > > cause it to ignore DEPEND.
> > > > > > > > > > > 
> > > > > > > > > > > That is not the same is it? if I "emerge ncurses" it will build ncurses but still
> > > > > > > > > > > take the ebuild from the hosts master since it is newer version.
> > > > > > > > > > > 
> > > > > > > > > > > I realize now that I can change what repos are searched by using 
> > > > > > > > > > > PORTAGE_REPOSITORIES=/my/own/repos.conf/
> > > > > > > > > > > but I still find the default behaviour very confusing and I don't see that it is useful.
> > > > > > > > > > 
> > > > > > > > > > The idea is that you have separate repositories configured for each
> > > > > > > > > > ROOT. If it's satisfying a build-time DEPEND that will be installed into
> > > > > > > > > > ROOT=/, then it's supposed to use the repositories configured for ROOT=/.
> > > > > > > > > 
> > > > > > > > > I see, but in my case I only install into my sysroot so I don't want this behaviour.
> > > > > > > > 
> > > > > > > > So, why don't you use the --root-deps option?
> > > > > > > 
> > > > > > > Just did(and --root-deps=rdeps too) and it didn't work, still wants to use
> > > > > > > my newer hosts pkgs. :(
> > > > > > 
> > > > > > It shouldn't do that. It sounds like maybe the [gentoo] config
> > > > > > from/usr/share/portage/config/repos.conf is the source of your problems,
> > > > > > since you $PORTAGE_CONFIGROOT config will always inherit that. Would
> > > > > > that be consistent with your observations?
> > > > > 
> > > > > Moving that file out of the way changed things, now I got I profile error:
> > > > > !!! Unable to parse profile: '/etc/portage/make.profile'
> > > > > !!! ParseError: Parent 'gentoo:default/linux/amd64/13.0' not found:
> > > > > '/var/lib/layman/transmode/profiles/gentoo64-server/parent'
> > > > > !!! Your current profile is invalid. If you have just changed your profile
> > > > > !!! configuration, you should revert back to the previous configuration.
> > > > > !!! Allowed actions are limited to --help, --info, --search, --sync, and
> > > > > !!! --version.
> > > > > 
> > > > > Which I think is a problem in my cross env.
> > > > 
> > > > No, this is not it. Portage just bails when reading the host profile which it should not.
> > > > 
> > > > Note: defining
> > > >   PORTAGE_REPOSITORIES=/my/own/repos.conf
> > > > gives the same error.
> > > > 
> > > 
> > > According to the error message, your transmode profile inherits a gentoo
> > > profile, so you need the gentoo repository (at least the relevant profile).
> > 
> > I have a my own profile in PORTAGE_CONFIGROOT which does not
> > reference the host /etc/portage/make.profile at all so I think
> > portage is using the wrong profile.
> 
> When using ROOT=/foo, it always instantiates 2 profiles, and it uses one
> profile for ROOT=/foo and the other profile for ROOT=/.

This makes sense when just using ROOT, not when cross compiling.
If I cross build (or use PORTAGE_REPOSITORIES ?) I don't think it makes
sense to add the hosts profile as it has little to nothing to
do with my cross target.
How would a cross target use the hosts profile sensibly?

> 
> > Futhermore, it does not understand the host profile, probably
> > because my own PORTAGE_CONFIGROOT don't have profile-formats = portage-2
> 
> You're saying this beciase of the above ParseError? I think maybe what
> you want to do keep the default /usr/share/portage/config/repos.conf and
> mask */*::gentoo in $PORTAGE_CONFIGROOT/etc/portage/package.mask.

That is what I am doing now, but that still includes the hosts profile I think ?

 Jocke

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Zac Medico]

On 05/09/2015 06:47 AM, Joakim Tjernlund wrote:
> On Fri, 2015-05-08 at 11:32 -0700, Zac Medico wrote:
>> On 05/07/2015 11:43 PM, Joakim Tjernlund wrote:
>>> On Thu, 2015-05-07 at 14:09 -0700, Zac Medico wrote:
>>>> On 05/07/2015 03:51 AM, Joakim Tjernlund wrote:
>>>>> On Wed, 2015-05-06 at 22:45 +0000, Joakim Tjernlund wrote:
>>>>>> On Wed, 2015-05-06 at 15:16 -0700, Zac Medico wrote:
>>>>>>> On 05/06/15 14:57, Joakim Tjernlund wrote:
>>>>>>>> On Wed, 2015-05-06 at 14:36 -0700, Zac Medico wrote:
>>>>>>>>> On 05/06/15 14:30, Joakim Tjernlund wrote:
>>>>>>>>>> On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote:
>>>>>>>>>>> On 05/06/15 13:22, Joakim Tjernlund wrote:
>>>>>>>>>>>> On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
>>>>>>>>>>>>> On 05/06/15 12:41, Joakim Tjernlund wrote:
>>>>>>>>>>>>>> On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote:
>>>>>>>>>>>>>>> On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
>>>>>>>>>>>>>>>> On 05/06/15 09:54, Joakim Tjernlund wrote:
>>>>>>>>>>>>>>>>> I am trying to rebuild an old cross sysroot and I got problems.
>>>>>>>>>>>>>>>>> I cannot make emerge to select my old ebuilds in an overlay over those
>>>>>>>>>>>>>>>>> in /usr/portage.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> What new is since last time I did this is /etc/portage/repos.conf/
>>>>>>>>>>>>>>>>> I suspect emerge always reads /etc/portage/repos.conf/ no matter
>>>>>>>>>>>>>>>>> what I set PORTAGE_CONFIGROOT / ROOT to ?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>  Jocke
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> It instantiates 2 config instances, one using /etc/portage/repos.conf
>>>>>>>>>>>>>>>> (for build time DEPEND) and another one using
>>>>>>>>>>>>>>>> $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
>>>>>>>>>>>>>>>> You can see that it's joined with PORTAGE_CONFIGROOT in the
>>>>>>>>>>>>>>>> load_repository_config function:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py
>>>>>>>>>>>>>>>> ?id=
>>>>>>>>>>>>>>>> 0f19
>>>>>>>>>>>>>>>> 11
>>>>>>>>>>>>>>>> 13cc
>>>>>>>>>>>>>>>> cd04
>>>>>>>>>>>>>>>> 9e11
>>>>>>>>>>>>>>>> fdbe
>>>>>>>>>>>>>>>> 73
>>>>>>>>>>>>>>>> 493eb1efbf4bf89e#n971
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I see, doesn't this prevent exactly what I want to do?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I can't see why this should be needed, it only creates a mess, another example:
>>>>>>>>>>>>>>> I tried to specify exact version of my old binutils and while that worked, 
>>>>>>>>>>>>>>> portage 
>>>>>>>>>>>>>>> wanted
>>>>>>>>>>>>>>> to pull in a newer binutils-config from the hosts master gentoo repo and
>>>>>>>>>>>>>>> thus the build failed.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> If a someone really wants this behaviour, he can just add the hosts master repo
>>>>>>>>>>>>>>> in his PORTAGE_CONFIGROOT IMHO
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Maybe emerge --root-deps=rdeps is what you are looking for. This will
>>>>>>>>>>>>> cause it to ignore DEPEND.
>>>>>>>>>>>>
>>>>>>>>>>>> That is not the same is it? if I "emerge ncurses" it will build ncurses but still
>>>>>>>>>>>> take the ebuild from the hosts master since it is newer version.
>>>>>>>>>>>>
>>>>>>>>>>>> I realize now that I can change what repos are searched by using 
>>>>>>>>>>>> PORTAGE_REPOSITORIES=/my/own/repos.conf/
>>>>>>>>>>>> but I still find the default behaviour very confusing and I don't see that it is useful.
>>>>>>>>>>>
>>>>>>>>>>> The idea is that you have separate repositories configured for each
>>>>>>>>>>> ROOT. If it's satisfying a build-time DEPEND that will be installed into
>>>>>>>>>>> ROOT=/, then it's supposed to use the repositories configured for ROOT=/.
>>>>>>>>>>
>>>>>>>>>> I see, but in my case I only install into my sysroot so I don't want this behaviour.
>>>>>>>>>
>>>>>>>>> So, why don't you use the --root-deps option?
>>>>>>>>
>>>>>>>> Just did(and --root-deps=rdeps too) and it didn't work, still wants to use
>>>>>>>> my newer hosts pkgs. :(
>>>>>>>
>>>>>>> It shouldn't do that. It sounds like maybe the [gentoo] config
>>>>>>> from/usr/share/portage/config/repos.conf is the source of your problems,
>>>>>>> since you $PORTAGE_CONFIGROOT config will always inherit that. Would
>>>>>>> that be consistent with your observations?
>>>>>>
>>>>>> Moving that file out of the way changed things, now I got I profile error:
>>>>>> !!! Unable to parse profile: '/etc/portage/make.profile'
>>>>>> !!! ParseError: Parent 'gentoo:default/linux/amd64/13.0' not found:
>>>>>> '/var/lib/layman/transmode/profiles/gentoo64-server/parent'
>>>>>> !!! Your current profile is invalid. If you have just changed your profile
>>>>>> !!! configuration, you should revert back to the previous configuration.
>>>>>> !!! Allowed actions are limited to --help, --info, --search, --sync, and
>>>>>> !!! --version.
>>>>>>
>>>>>> Which I think is a problem in my cross env.
>>>>>
>>>>> No, this is not it. Portage just bails when reading the host profile which it should not.
>>>>>
>>>>> Note: defining
>>>>>   PORTAGE_REPOSITORIES=/my/own/repos.conf
>>>>> gives the same error.
>>>>>
>>>>
>>>> According to the error message, your transmode profile inherits a gentoo
>>>> profile, so you need the gentoo repository (at least the relevant profile).
>>>
>>> I have a my own profile in PORTAGE_CONFIGROOT which does not
>>> reference the host /etc/portage/make.profile at all so I think
>>> portage is using the wrong profile.
>>
>> When using ROOT=/foo, it always instantiates 2 profiles, and it uses one
>> profile for ROOT=/foo and the other profile for ROOT=/.
> 
> This makes sense when just using ROOT, not when cross compiling.
> If I cross build (or use PORTAGE_REPOSITORIES ?) I don't think it makes
> sense to add the hosts profile as it has little to nothing to
> do with my cross target.
> How would a cross target use the hosts profile sensibly?

The host profile is only used for packages installed to ROOT=/ in order
to satisfy DEPEND. If you use the emerge --root-deps then the host
profile is used for absolutely nothing (although it is still instantiated).

>>
>>> Futhermore, it does not understand the host profile, probably
>>> because my own PORTAGE_CONFIGROOT don't have profile-formats = portage-2
>>
>> You're saying this beciase of the above ParseError? I think maybe what
>> you want to do keep the default /usr/share/portage/config/repos.conf and
>> mask */*::gentoo in $PORTAGE_CONFIGROOT/etc/portage/package.mask.
> 
> That is what I am doing now, but that still includes the hosts profile I think ?

It will only be used for packages installed to ROOT=/ in order to
satisfy DEPEND, as I have mentioned above.
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Joakim Tjernlund]

On Sat, 2015-05-09 at 09:36 -0700, Zac Medico wrote:
> On 05/09/2015 06:47 AM, Joakim Tjernlund wrote:
> > On Fri, 2015-05-08 at 11:32 -0700, Zac Medico wrote:
> > > On 05/07/2015 11:43 PM, Joakim Tjernlund wrote:
> > > > On Thu, 2015-05-07 at 14:09 -0700, Zac Medico wrote:
> > > > > On 05/07/2015 03:51 AM, Joakim Tjernlund wrote:
> > > > > > On Wed, 2015-05-06 at 22:45 +0000, Joakim Tjernlund wrote:
> > > > > > > On Wed, 2015-05-06 at 15:16 -0700, Zac Medico wrote:
> > > > > > > > On 05/06/15 14:57, Joakim Tjernlund wrote:
> > > > > > > > > On Wed, 2015-05-06 at 14:36 -0700, Zac Medico wrote:
> > > > > > > > > > On 05/06/15 14:30, Joakim Tjernlund wrote:
> > > > > > > > > > > On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote:
> > > > > > > > > > > > On 05/06/15 13:22, Joakim Tjernlund wrote:
> > > > > > > > > > > > > On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
> > > > > > > > > > > > > > On 05/06/15 12:41, Joakim Tjernlund wrote:
> > > > > > > > > > > > > > > On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote:
> > > > > > > > > > > > > > > > On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
> > > > > > > > > > > > > > > > > On 05/06/15 09:54, Joakim Tjernlund wrote:
> > > > > > > > > > > > > > > > > > I am trying to rebuild an old cross sysroot and I got problems.
> > > > > > > > > > > > > > > > > > I cannot make emerge to select my old ebuilds in an overlay over those
> > > > > > > > > > > > > > > > > > in /usr/portage.
> > > > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > > > What new is since last time I did this is /etc/portage/repos.conf/
> > > > > > > > > > > > > > > > > > I suspect emerge always reads /etc/portage/repos.conf/ no matter
> > > > > > > > > > > > > > > > > > what I set PORTAGE_CONFIGROOT / ROOT to ?
> > > > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > > >  Jocke
> > > > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > > It instantiates 2 config instances, one using /etc/portage/repos.conf
> > > > > > > > > > > > > > > > > (for build time DEPEND) and another one using
> > > > > > > > > > > > > > > > > $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
> > > > > > > > > > > > > > > > > You can see that it's joined with PORTAGE_CONFIGROOT in the
> > > > > > > > > > > > > > > > > load_repository_config function:
> > > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > > https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/confi
> > > > > > > > > > > > > > > > > g.py
> > > > > > > > > > > > > > > > > ?id=
> > > > > > > > > > > > > > > > > 0f19
> > > > > > > > > > > > > > > > > 11
> > > > > > > > > > > > > > > > > 13cc
> > > > > > > > > > > > > > > > > cd04
> > > > > > > > > > > > > > > > > 9e11
> > > > > > > > > > > > > > > > > fdbe
> > > > > > > > > > > > > > > > > 73
> > > > > > > > > > > > > > > > > 493eb1efbf4bf89e#n971
> > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > I see, doesn't this prevent exactly what I want to do?
> > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > I can't see why this should be needed, it only creates a mess, another 
> > > > > > > > > > > > > > > > example:
> > > > > > > > > > > > > > > > I tried to specify exact version of my old binutils and while that worked, 
> > > > > > > > > > > > > > > > portage 
> > > > > > > > > > > > > > > > wanted
> > > > > > > > > > > > > > > > to pull in a newer binutils-config from the hosts master gentoo repo and
> > > > > > > > > > > > > > > > thus the build failed.
> > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > If a someone really wants this behaviour, he can just add the hosts master 
> > > > > > > > > > > > > > > > repo
> > > > > > > > > > > > > > > > in his PORTAGE_CONFIGROOT IMHO
> > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > Maybe emerge --root-deps=rdeps is what you are looking for. This will
> > > > > > > > > > > > > > cause it to ignore DEPEND.
> > > > > > > > > > > > > 
> > > > > > > > > > > > > That is not the same is it? if I "emerge ncurses" it will build ncurses but still
> > > > > > > > > > > > > take the ebuild from the hosts master since it is newer version.
> > > > > > > > > > > > > 
> > > > > > > > > > > > > I realize now that I can change what repos are searched by using 
> > > > > > > > > > > > > PORTAGE_REPOSITORIES=/my/own/repos.conf/
> > > > > > > > > > > > > but I still find the default behaviour very confusing and I don't see that it is 
> > > > > > > > > > > > > useful.
> > > > > > > > > > > > 
> > > > > > > > > > > > The idea is that you have separate repositories configured for each
> > > > > > > > > > > > ROOT. If it's satisfying a build-time DEPEND that will be installed into
> > > > > > > > > > > > ROOT=/, then it's supposed to use the repositories configured for ROOT=/.
> > > > > > > > > > > 
> > > > > > > > > > > I see, but in my case I only install into my sysroot so I don't want this behaviour.
> > > > > > > > > > 
> > > > > > > > > > So, why don't you use the --root-deps option?
> > > > > > > > > 
> > > > > > > > > Just did(and --root-deps=rdeps too) and it didn't work, still wants to use
> > > > > > > > > my newer hosts pkgs. :(
> > > > > > > > 
> > > > > > > > It shouldn't do that. It sounds like maybe the [gentoo] config
> > > > > > > > from/usr/share/portage/config/repos.conf is the source of your problems,
> > > > > > > > since you $PORTAGE_CONFIGROOT config will always inherit that. Would
> > > > > > > > that be consistent with your observations?
> > > > > > > 
> > > > > > > Moving that file out of the way changed things, now I got I profile error:
> > > > > > > !!! Unable to parse profile: '/etc/portage/make.profile'
> > > > > > > !!! ParseError: Parent 'gentoo:default/linux/amd64/13.0' not found:
> > > > > > > '/var/lib/layman/transmode/profiles/gentoo64-server/parent'
> > > > > > > !!! Your current profile is invalid. If you have just changed your profile
> > > > > > > !!! configuration, you should revert back to the previous configuration.
> > > > > > > !!! Allowed actions are limited to --help, --info, --search, --sync, and
> > > > > > > !!! --version.
> > > > > > > 
> > > > > > > Which I think is a problem in my cross env.
> > > > > > 
> > > > > > No, this is not it. Portage just bails when reading the host profile which it should not.
> > > > > > 
> > > > > > Note: defining
> > > > > >   PORTAGE_REPOSITORIES=/my/own/repos.conf
> > > > > > gives the same error.
> > > > > > 
> > > > > 
> > > > > According to the error message, your transmode profile inherits a gentoo
> > > > > profile, so you need the gentoo repository (at least the relevant profile).
> > > > 
> > > > I have a my own profile in PORTAGE_CONFIGROOT which does not
> > > > reference the host /etc/portage/make.profile at all so I think
> > > > portage is using the wrong profile.
> > > 
> > > When using ROOT=/foo, it always instantiates 2 profiles, and it uses one
> > > profile for ROOT=/foo and the other profile for ROOT=/.
> > 
> > This makes sense when just using ROOT, not when cross compiling.
> > If I cross build (or use PORTAGE_REPOSITORIES ?) I don't think it makes
> > sense to add the hosts profile as it has little to nothing to
> > do with my cross target.
> > How would a cross target use the hosts profile sensibly?
> 
> The host profile is only used for packages installed to ROOT=/ in order
> to satisfy DEPEND. If you use the emerge --root-deps then the host
> profile is used for absolutely nothing (although it is still instantiated).

I see, it would be nice if it wasn't instantiated when not needed so
one could avoid the error I have seen.

> 
> > > 
> > > > Futhermore, it does not understand the host profile, probably
> > > > because my own PORTAGE_CONFIGROOT don't have profile-formats = portage-2
> > > 
> > > You're saying this beciase of the above ParseError? I think maybe what
> > > you want to do keep the default /usr/share/portage/config/repos.conf and
> > > mask */*::gentoo in $PORTAGE_CONFIGROOT/etc/portage/package.mask.
> > 
> > That is what I am doing now, but that still includes the hosts profile I think ?
> 
> It will only be used for packages installed to ROOT=/ in order to
> satisfy DEPEND, as I have mentioned above.

OK, you always read the host profile in case you need it.
May I suggest you avoid touching the host profile when it not used(cross complies)?

        Jocke

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Zac Medico]

On 05/09/2015 10:08 AM, Joakim Tjernlund wrote:
> On Sat, 2015-05-09 at 09:36 -0700, Zac Medico wrote:
>> On 05/09/2015 06:47 AM, Joakim Tjernlund wrote:
>>> On Fri, 2015-05-08 at 11:32 -0700, Zac Medico wrote:
>>>> On 05/07/2015 11:43 PM, Joakim Tjernlund wrote:
>>>>> On Thu, 2015-05-07 at 14:09 -0700, Zac Medico wrote:
>>>>>> On 05/07/2015 03:51 AM, Joakim Tjernlund wrote:
>>>>>>> On Wed, 2015-05-06 at 22:45 +0000, Joakim Tjernlund wrote:
>>>>>>>> On Wed, 2015-05-06 at 15:16 -0700, Zac Medico wrote:
>>>>>>>>> On 05/06/15 14:57, Joakim Tjernlund wrote:
>>>>>>>>>> On Wed, 2015-05-06 at 14:36 -0700, Zac Medico wrote:
>>>>>>>>>>> On 05/06/15 14:30, Joakim Tjernlund wrote:
>>>>>>>>>>>> On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote:
>>>>>>>>>>>>> On 05/06/15 13:22, Joakim Tjernlund wrote:
>>>>>>>>>>>>>> On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
>>>>>>>>>>>>> The idea is that you have separate repositories configured for each
>>>>>>>>>>>>> ROOT. If it's satisfying a build-time DEPEND that will be installed into
>>>>>>>>>>>>> ROOT=/, then it's supposed to use the repositories configured for ROOT=/.
>>>>>>>>>>>>
>>>>>>>>>>>> I see, but in my case I only install into my sysroot so I don't want this behaviour.
>>>>>>>>>>>
>>>>>>>>>>> So, why don't you use the --root-deps option?
>>>>>>>>>>
>>>>>>>>>> Just did(and --root-deps=rdeps too) and it didn't work, still wants to use
>>>>>>>>>> my newer hosts pkgs. :(
>>>>>>>>>
>>>>>>>>> It shouldn't do that. It sounds like maybe the [gentoo] config
>>>>>>>>> from/usr/share/portage/config/repos.conf is the source of your problems,
>>>>>>>>> since you $PORTAGE_CONFIGROOT config will always inherit that. Would
>>>>>>>>> that be consistent with your observations?
>>>>>>>>
>>>>>>>> Moving that file out of the way changed things, now I got I profile error:
>>>>>>>> !!! Unable to parse profile: '/etc/portage/make.profile'
>>>>>>>> !!! ParseError: Parent 'gentoo:default/linux/amd64/13.0' not found:
>>>>>>>> '/var/lib/layman/transmode/profiles/gentoo64-server/parent'
>>>>>>>> !!! Your current profile is invalid. If you have just changed your profile
>>>>>>>> !!! configuration, you should revert back to the previous configuration.
>>>>>>>> !!! Allowed actions are limited to --help, --info, --search, --sync, and
>>>>>>>> !!! --version.
>>>>>>>>
>>>>>>>> Which I think is a problem in my cross env.
>>>>>>>
>>>>>>> No, this is not it. Portage just bails when reading the host profile which it should not.
>>>>>>>
>>>>>>> Note: defining
>>>>>>>   PORTAGE_REPOSITORIES=/my/own/repos.conf
>>>>>>> gives the same error.
>>>>>>>
>>>>>>
>>>>>> According to the error message, your transmode profile inherits a gentoo
>>>>>> profile, so you need the gentoo repository (at least the relevant profile).
>>>>>
>>>>> I have a my own profile in PORTAGE_CONFIGROOT which does not
>>>>> reference the host /etc/portage/make.profile at all so I think
>>>>> portage is using the wrong profile.
>>>>
>>>> When using ROOT=/foo, it always instantiates 2 profiles, and it uses one
>>>> profile for ROOT=/foo and the other profile for ROOT=/.
>>>
>>> This makes sense when just using ROOT, not when cross compiling.
>>> If I cross build (or use PORTAGE_REPOSITORIES ?) I don't think it makes
>>> sense to add the hosts profile as it has little to nothing to
>>> do with my cross target.
>>> How would a cross target use the hosts profile sensibly?
>>
>> The host profile is only used for packages installed to ROOT=/ in order
>> to satisfy DEPEND. If you use the emerge --root-deps then the host
>> profile is used for absolutely nothing (although it is still instantiated).
> 
> I see, it would be nice if it wasn't instantiated when not needed so
> one could avoid the error I have seen.
> 
>>
>>>>
>>>>> Futhermore, it does not understand the host profile, probably
>>>>> because my own PORTAGE_CONFIGROOT don't have profile-formats = portage-2
>>>>
>>>> You're saying this beciase of the above ParseError? I think maybe what
>>>> you want to do keep the default /usr/share/portage/config/repos.conf and
>>>> mask */*::gentoo in $PORTAGE_CONFIGROOT/etc/portage/package.mask.
>>>
>>> That is what I am doing now, but that still includes the hosts profile I think ?
>>
>> It will only be used for packages installed to ROOT=/ in order to
>> satisfy DEPEND, as I have mentioned above.
> 
> OK, you always read the host profile in case you need it.
> May I suggest you avoid touching the host profile when it not used(cross complies)?

I suppose we could lazily instantiate the config for ROOT=/ at the point
where a a DEPEND needs to be satisfied (or HDEPEND for EAPI 5-hdepend).
See this bug:

	https://bugs.gentoo.org/show_bug.cgi?id=324179
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Joakim Tjernlund]

On Sat, 2015-05-09 at 10:49 -0700, Zac Medico wrote:
> On 05/09/2015 10:08 AM, Joakim Tjernlund wrote:
> > On Sat, 2015-05-09 at 09:36 -0700, Zac Medico wrote:
> > > On 05/09/2015 06:47 AM, Joakim Tjernlund wrote:
> > > > On Fri, 2015-05-08 at 11:32 -0700, Zac Medico wrote:
> > > > > On 05/07/2015 11:43 PM, Joakim Tjernlund wrote:
> > > > > > On Thu, 2015-05-07 at 14:09 -0700, Zac Medico wrote:
> > > > > > > On 05/07/2015 03:51 AM, Joakim Tjernlund wrote:
> > > > > > > > On Wed, 2015-05-06 at 22:45 +0000, Joakim Tjernlund wrote:
> > > > > > > > > On Wed, 2015-05-06 at 15:16 -0700, Zac Medico wrote:
> > > > > > > > > > On 05/06/15 14:57, Joakim Tjernlund wrote:
> > > > > > > > > > > On Wed, 2015-05-06 at 14:36 -0700, Zac Medico wrote:
> > > > > > > > > > > > On 05/06/15 14:30, Joakim Tjernlund wrote:
> > > > > > > > > > > > > On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote:
> > > > > > > > > > > > > > On 05/06/15 13:22, Joakim Tjernlund wrote:
> > > > > > > > > > > > > > > On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
> > > > > > > > > > > > > > The idea is that you have separate repositories configured for each
> > > > > > > > > > > > > > ROOT. If it's satisfying a build-time DEPEND that will be installed into
> > > > > > > > > > > > > > ROOT=/, then it's supposed to use the repositories configured for ROOT=/.
> > > > > > > > > > > > > 
> > > > > > > > > > > > > I see, but in my case I only install into my sysroot so I don't want this behaviour.
> > > > > > > > > > > > 
> > > > > > > > > > > > So, why don't you use the --root-deps option?
> > > > > > > > > > > 
> > > > > > > > > > > Just did(and --root-deps=rdeps too) and it didn't work, still wants to use
> > > > > > > > > > > my newer hosts pkgs. :(
> > > > > > > > > > 
> > > > > > > > > > It shouldn't do that. It sounds like maybe the [gentoo] config
> > > > > > > > > > from/usr/share/portage/config/repos.conf is the source of your problems,
> > > > > > > > > > since you $PORTAGE_CONFIGROOT config will always inherit that. Would
> > > > > > > > > > that be consistent with your observations?
> > > > > > > > > 
> > > > > > > > > Moving that file out of the way changed things, now I got I profile error:
> > > > > > > > > !!! Unable to parse profile: '/etc/portage/make.profile'
> > > > > > > > > !!! ParseError: Parent 'gentoo:default/linux/amd64/13.0' not found:
> > > > > > > > > '/var/lib/layman/transmode/profiles/gentoo64-server/parent'
> > > > > > > > > !!! Your current profile is invalid. If you have just changed your profile
> > > > > > > > > !!! configuration, you should revert back to the previous configuration.
> > > > > > > > > !!! Allowed actions are limited to --help, --info, --search, --sync, and
> > > > > > > > > !!! --version.
> > > > > > > > > 
> > > > > > > > > Which I think is a problem in my cross env.
> > > > > > > > 
> > > > > > > > No, this is not it. Portage just bails when reading the host profile which it should not.
> > > > > > > > 
> > > > > > > > Note: defining
> > > > > > > >   PORTAGE_REPOSITORIES=/my/own/repos.conf
> > > > > > > > gives the same error.
> > > > > > > > 
> > > > > > > 
> > > > > > > According to the error message, your transmode profile inherits a gentoo
> > > > > > > profile, so you need the gentoo repository (at least the relevant profile).
> > > > > > 
> > > > > > I have a my own profile in PORTAGE_CONFIGROOT which does not
> > > > > > reference the host /etc/portage/make.profile at all so I think
> > > > > > portage is using the wrong profile.
> > > > > 
> > > > > When using ROOT=/foo, it always instantiates 2 profiles, and it uses one
> > > > > profile for ROOT=/foo and the other profile for ROOT=/.
> > > > 
> > > > This makes sense when just using ROOT, not when cross compiling.
> > > > If I cross build (or use PORTAGE_REPOSITORIES ?) I don't think it makes
> > > > sense to add the hosts profile as it has little to nothing to
> > > > do with my cross target.
> > > > How would a cross target use the hosts profile sensibly?
> > > 
> > > The host profile is only used for packages installed to ROOT=/ in order
> > > to satisfy DEPEND. If you use the emerge --root-deps then the host
> > > profile is used for absolutely nothing (although it is still instantiated).
> > 
> > I see, it would be nice if it wasn't instantiated when not needed so
> > one could avoid the error I have seen.
> > 
> > > 
> > > > > 
> > > > > > Futhermore, it does not understand the host profile, probably
> > > > > > because my own PORTAGE_CONFIGROOT don't have profile-formats = portage-2
> > > > > 
> > > > > You're saying this beciase of the above ParseError? I think maybe what
> > > > > you want to do keep the default /usr/share/portage/config/repos.conf and
> > > > > mask */*::gentoo in $PORTAGE_CONFIGROOT/etc/portage/package.mask.
> > > > 
> > > > That is what I am doing now, but that still includes the hosts profile I think ?
> > > 
> > > It will only be used for packages installed to ROOT=/ in order to
> > > satisfy DEPEND, as I have mentioned above.
> > 
> > OK, you always read the host profile in case you need it.
> > May I suggest you avoid touching the host profile when it not used(cross complies)?
> 
> I suppose we could lazily instantiate the config for ROOT=/ at the point
> where a a DEPEND needs to be satisfied (or HDEPEND for EAPI 5-hdepend).
> See this bug:
> 
>       https://bugs.gentoo.org/show_bug.cgi?id=324179

Right, seen that bug before :)

However, there may be a another bug in here. Portage is complaining over not being able
to load the hosts profile as the hosts is using "profile-formats = portage-2" and my
CONFIGROOT is not. I don't think my CONFIGROOT should be forced to use "profile-formats = portage-2"
just because the host is?

 Jocke

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Zac Medico]

On 05/10/2015 04:47 AM, Joakim Tjernlund wrote:
> However, there may be a another bug in here. Portage is complaining over not being able
> to load the hosts profile as the hosts is using "profile-formats = portage-2" and my
> CONFIGROOT is not. I don't think my CONFIGROOT should be forced to use "profile-formats = portage-2"
> just because the host is?

It sounds like your profile must by using some feature that is not
supported with the default profile format. Otherwise, why would you
receive an error? These kinds of errors are only triggered when
something about the profile is not supported by the default profile format.
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Joakim Tjernlund]

On Sun, 2015-05-10 at 11:45 -0700, Zac Medico wrote:
> On 05/10/2015 04:47 AM, Joakim Tjernlund wrote:
> > However, there may be a another bug in here. Portage is complaining over not being able
> > to load the hosts profile as the hosts is using "profile-formats = portage-2" and my
> > CONFIGROOT is not. I don't think my CONFIGROOT should be forced to use "profile-formats = portage-2"
> > just because the host is?
> 
> It sounds like your profile must by using some feature that is not
> supported with the default profile format. Otherwise, why would you
> receive an error? These kinds of errors are only triggered when
> something about the profile is not supported by the default profile format.

Yes I do use portage-2 features in my host, I thought this was clear?
Now in my CONFIGROOT I am not and the point I trying to make is that my
CONFIGROOT should not have to worry about what profile format the host is using.

 Jocke

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Zac Medico]

On 05/10/2015 01:08 PM, Joakim Tjernlund wrote:
> On Sun, 2015-05-10 at 11:45 -0700, Zac Medico wrote:
>> On 05/10/2015 04:47 AM, Joakim Tjernlund wrote:
>>> However, there may be a another bug in here. Portage is complaining over not being able
>>> to load the hosts profile as the hosts is using "profile-formats = portage-2" and my
>>> CONFIGROOT is not. I don't think my CONFIGROOT should be forced to use "profile-formats = portage-2"
>>> just because the host is?
>>
>> It sounds like your profile must by using some feature that is not
>> supported with the default profile format. Otherwise, why would you
>> receive an error? These kinds of errors are only triggered when
>> something about the profile is not supported by the default profile format.
> 
> Yes I do use portage-2 features in my host, I thought this was clear?
> Now in my CONFIGROOT I am not and the point I trying to make is that my
> CONFIGROOT should not have to worry about what profile format the host is using.

I don't recall a bug like that being filed yet. Could you please file
one at bugs.gentoo.org?
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Joakim Tjernlund]

On Wed, 2015-05-06 at 15:16 -0700, Zac Medico wrote:
> 
> > > So, why don't you use the --root-deps option?
> > 
> > Just did(and --root-deps=rdeps too) and it didn't work, still wants to use
> > my newer hosts pkgs. :(
> 
> It shouldn't do that. It sounds like maybe the [gentoo] config
> from/usr/share/portage/config/repos.conf is the source of your problems,
> since you $PORTAGE_CONFIGROOT config will always inherit that. Would
> that be consistent with your observations?

hmm, is this file inherited even if I set PORTAGE_REPOSITORIES ?