1 |
On 05/07/2015 11:43 PM, Joakim Tjernlund wrote: |
2 |
> On Thu, 2015-05-07 at 14:09 -0700, Zac Medico wrote: |
3 |
>> On 05/07/2015 03:51 AM, Joakim Tjernlund wrote: |
4 |
>>> On Wed, 2015-05-06 at 22:45 +0000, Joakim Tjernlund wrote: |
5 |
>>>> On Wed, 2015-05-06 at 15:16 -0700, Zac Medico wrote: |
6 |
>>>>> On 05/06/15 14:57, Joakim Tjernlund wrote: |
7 |
>>>>>> On Wed, 2015-05-06 at 14:36 -0700, Zac Medico wrote: |
8 |
>>>>>>> On 05/06/15 14:30, Joakim Tjernlund wrote: |
9 |
>>>>>>>> On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote: |
10 |
>>>>>>>>> On 05/06/15 13:22, Joakim Tjernlund wrote: |
11 |
>>>>>>>>>> On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote: |
12 |
>>>>>>>>>>> On 05/06/15 12:41, Joakim Tjernlund wrote: |
13 |
>>>>>>>>>>>> On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote: |
14 |
>>>>>>>>>>>>> On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote: |
15 |
>>>>>>>>>>>>>> On 05/06/15 09:54, Joakim Tjernlund wrote: |
16 |
>>>>>>>>>>>>>>> I am trying to rebuild an old cross sysroot and I got problems. |
17 |
>>>>>>>>>>>>>>> I cannot make emerge to select my old ebuilds in an overlay over those |
18 |
>>>>>>>>>>>>>>> in /usr/portage. |
19 |
>>>>>>>>>>>>>>> |
20 |
>>>>>>>>>>>>>>> What new is since last time I did this is /etc/portage/repos.conf/ |
21 |
>>>>>>>>>>>>>>> I suspect emerge always reads /etc/portage/repos.conf/ no matter |
22 |
>>>>>>>>>>>>>>> what I set PORTAGE_CONFIGROOT / ROOT to ? |
23 |
>>>>>>>>>>>>>>> |
24 |
>>>>>>>>>>>>>>> Jocke |
25 |
>>>>>>>>>>>>>>> |
26 |
>>>>>>>>>>>>>> |
27 |
>>>>>>>>>>>>>> It instantiates 2 config instances, one using /etc/portage/repos.conf |
28 |
>>>>>>>>>>>>>> (for build time DEPEND) and another one using |
29 |
>>>>>>>>>>>>>> $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND). |
30 |
>>>>>>>>>>>>>> You can see that it's joined with PORTAGE_CONFIGROOT in the |
31 |
>>>>>>>>>>>>>> load_repository_config function: |
32 |
>>>>>>>>>>>>>> |
33 |
>>>>>>>>>>>>>> https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id= |
34 |
>>>>>>>>>>>>>> 0f19 |
35 |
>>>>>>>>>>>>>> 11 |
36 |
>>>>>>>>>>>>>> 13cc |
37 |
>>>>>>>>>>>>>> cd04 |
38 |
>>>>>>>>>>>>>> 9e11 |
39 |
>>>>>>>>>>>>>> fdbe |
40 |
>>>>>>>>>>>>>> 73 |
41 |
>>>>>>>>>>>>>> 493eb1efbf4bf89e#n971 |
42 |
>>>>>>>>>>>>> |
43 |
>>>>>>>>>>>>> I see, doesn't this prevent exactly what I want to do? |
44 |
>>>>>>>>>>>>> |
45 |
>>>>>>>>>>>>> I can't see why this should be needed, it only creates a mess, another example: |
46 |
>>>>>>>>>>>>> I tried to specify exact version of my old binutils and while that worked, portage |
47 |
>>>>>>>>>>>>> wanted |
48 |
>>>>>>>>>>>>> to pull in a newer binutils-config from the hosts master gentoo repo and |
49 |
>>>>>>>>>>>>> thus the build failed. |
50 |
>>>>>>>>>>>>> |
51 |
>>>>>>>>>>>>> If a someone really wants this behaviour, he can just add the hosts master repo |
52 |
>>>>>>>>>>>>> in his PORTAGE_CONFIGROOT IMHO |
53 |
>>>>>>>>>>>>> |
54 |
>>>>>>>>>>> |
55 |
>>>>>>>>>>> Maybe emerge --root-deps=rdeps is what you are looking for. This will |
56 |
>>>>>>>>>>> cause it to ignore DEPEND. |
57 |
>>>>>>>>>> |
58 |
>>>>>>>>>> That is not the same is it? if I "emerge ncurses" it will build ncurses but still |
59 |
>>>>>>>>>> take the ebuild from the hosts master since it is newer version. |
60 |
>>>>>>>>>> |
61 |
>>>>>>>>>> I realize now that I can change what repos are searched by using |
62 |
>>>>>>>>>> PORTAGE_REPOSITORIES=/my/own/repos.conf/ |
63 |
>>>>>>>>>> but I still find the default behaviour very confusing and I don't see that it is useful. |
64 |
>>>>>>>>> |
65 |
>>>>>>>>> The idea is that you have separate repositories configured for each |
66 |
>>>>>>>>> ROOT. If it's satisfying a build-time DEPEND that will be installed into |
67 |
>>>>>>>>> ROOT=/, then it's supposed to use the repositories configured for ROOT=/. |
68 |
>>>>>>>> |
69 |
>>>>>>>> I see, but in my case I only install into my sysroot so I don't want this behaviour. |
70 |
>>>>>>> |
71 |
>>>>>>> So, why don't you use the --root-deps option? |
72 |
>>>>>> |
73 |
>>>>>> Just did(and --root-deps=rdeps too) and it didn't work, still wants to use |
74 |
>>>>>> my newer hosts pkgs. :( |
75 |
>>>>> |
76 |
>>>>> It shouldn't do that. It sounds like maybe the [gentoo] config |
77 |
>>>>> from/usr/share/portage/config/repos.conf is the source of your problems, |
78 |
>>>>> since you $PORTAGE_CONFIGROOT config will always inherit that. Would |
79 |
>>>>> that be consistent with your observations? |
80 |
>>>> |
81 |
>>>> Moving that file out of the way changed things, now I got I profile error: |
82 |
>>>> !!! Unable to parse profile: '/etc/portage/make.profile' |
83 |
>>>> !!! ParseError: Parent 'gentoo:default/linux/amd64/13.0' not found: |
84 |
>>>> '/var/lib/layman/transmode/profiles/gentoo64-server/parent' |
85 |
>>>> !!! Your current profile is invalid. If you have just changed your profile |
86 |
>>>> !!! configuration, you should revert back to the previous configuration. |
87 |
>>>> !!! Allowed actions are limited to --help, --info, --search, --sync, and |
88 |
>>>> !!! --version. |
89 |
>>>> |
90 |
>>>> Which I think is a problem in my cross env. |
91 |
>>> |
92 |
>>> No, this is not it. Portage just bails when reading the host profile which it should not. |
93 |
>>> |
94 |
>>> Note: defining |
95 |
>>> PORTAGE_REPOSITORIES=/my/own/repos.conf |
96 |
>>> gives the same error. |
97 |
>>> |
98 |
>> |
99 |
>> According to the error message, your transmode profile inherits a gentoo |
100 |
>> profile, so you need the gentoo repository (at least the relevant profile). |
101 |
> |
102 |
> I have a my own profile in PORTAGE_CONFIGROOT which does not |
103 |
> reference the host /etc/portage/make.profile at all so I think |
104 |
> portage is using the wrong profile. |
105 |
|
106 |
When using ROOT=/foo, it always instantiates 2 profiles, and it uses one |
107 |
profile for ROOT=/foo and the other profile for ROOT=/. |
108 |
|
109 |
> Futhermore, it does not understand the host profile, probably |
110 |
> because my own PORTAGE_CONFIGROOT don't have profile-formats = portage-2 |
111 |
|
112 |
You're saying this beciase of the above ParseError? I think maybe what |
113 |
you want to do keep the default /usr/share/portage/config/repos.conf and |
114 |
mask */*::gentoo in $PORTAGE_CONFIGROOT/etc/portage/package.mask. |
115 |
-- |
116 |
Thanks, |
117 |
Zac |