1 |
hi there. |
2 |
i marked binutils-2.13.0.90.18 stable for ppc and unmasked it in |
3 |
profiles/default-1.4-ppc/packages. it's unmasked on ppc because the KDE |
4 |
3.1 compile breaks without it. i've compiled kde 3.1 and gnome 2.2 |
5 |
against it. gerk has compiled kde 3.1 (and lots more stuff) against it. |
6 |
it seems to be very stable thus far. |
7 |
|
8 |
as for it being masked, you may have hit a bad rsync mirror. this exact |
9 |
thing happened to me this morning. i did another emerge rsync (different |
10 |
mirror) and the problem was gone. the mirror i had trouble with was in |
11 |
japan. i've written our rsync guy about this. |
12 |
|
13 |
everything should have gone smoothly. you just got bitten by a stale |
14 |
mirror. |
15 |
nall. |
16 |
|
17 |
|
18 |
On Fri, 2003-02-07 at 10:43, Stephan van Maris wrote: |
19 |
> I did a fresh 'emerge sync' a few minutes ago, and tried to update 'world'. |
20 |
> Apparently, gcc-3.2.2 requires binutils-2.13.90.0.18 (I'm running ~ppc) but |
21 |
> portage thinks it's masked. |
22 |
> |
23 |
> After looking around in the ebuild (most of the time adding 'ppc' to the |
24 |
> ebuild does the trick) I found it somewhat strange that binutils-2.13.90.0.18 |
25 |
> was marked 'ppc' (stable) but marked unstable for every other platform. I |
26 |
> looked in packages.mask and there are 2 versions masked, but not the version |
27 |
> I'm trying to install. |
28 |
> |
29 |
> In /usr/portage/profiles/default-ppc-1.4/packages I found out that all |
30 |
> binutils >=2.13.90.0.4 are masked. |
31 |
> |
32 |
> Why is that? How can an ebuild be marked stable on ppc and still be in the |
33 |
> masked packages file? I assume the 'ppc' in the ebuild is a typo and should |
34 |
> be (at least) '~ppc' ... Just curious ... |
35 |
> |
36 |
> Greetings, |
37 |
> |
38 |
> Stephan van Maris |
39 |
> |
40 |
> |
41 |
> -- |
42 |
> gentoo-ppc-dev@g.o mailing list |
43 |
> |