1 |
Fabian, |
2 |
|
3 |
Thanks a lot, changing the SYNC variable back fixed it. I am new to |
4 |
gentoo-prefix and was not aware that it uses a different tree. |
5 |
|
6 |
Best, |
7 |
|
8 |
Martin |
9 |
|
10 |
On Wed, Sep 21, 2011 at 2:13 PM, Fabian Groffen <grobian@g.o> wrote: |
11 |
> Hi Martin, |
12 |
> |
13 |
> On 21-09-2011 14:06:47 -0400, Martin Luessi wrote: |
14 |
>> I just successfully installed a gentoo prefix setup on CentOS (amd64). |
15 |
>> I was silly and used "eselect profile" after the instllation and this |
16 |
>> seems to have broken the instllation. I tried to fix it by having |
17 |
>> "$EPREFIX/etc/make.profile" point to |
18 |
>> "$EPREFIX/usr/portage/profiles/prefix/linux/amd64". However, now |
19 |
>> portage tries to install masked packages, e.g., |
20 |
>> |
21 |
>> emerge -a portage |
22 |
>> .. |
23 |
>> [ebuild N *] sys-apps/sandbox-2.5 USE="(-multilib)" |
24 |
>> [ebuild U *] sys-apps/portage-9999 [2.2.01.19295] USE="-python2% -python3%" |
25 |
>> |
26 |
>> The following keyword changes are necessary to proceed: |
27 |
>> #required by sys-apps/portage-9999, required by portage (argument) |
28 |
>> >=sys-apps/sandbox-2.5 ** |
29 |
>> #required by portage (argument) |
30 |
>> >=sys-apps/portage-9999 ** |
31 |
>> |
32 |
>> On the other hand, if I set "EMERGE_DEFAULT_OPTS="--autounmask=n" all |
33 |
>> versions of portage seem to be masked. I have not manually unmasked or |
34 |
>> masked any packages and have no idea why this is happening. Any tips |
35 |
>> on how to fix this are greatly appreciated. |
36 |
> |
37 |
> I think you messed with your SYNC variable. There is no portage-9999 in |
38 |
> the Prefix tree, so I think you synced up a gx86 tree. |
39 |
> |
40 |
> Make sure portageq envvar SYNC returns a prefix mirror, |
41 |
> e.g. rsync://rsync.prefix.freens.org/gentoo-portage-prefix |
42 |
> |
43 |
> |
44 |
> -- |
45 |
> Fabian Groffen |
46 |
> Gentoo on a different level |
47 |
> |