1 |
Harry Putnam <reader@×××××××.com> writes: |
2 |
|
3 |
> In the course of a full reinstall I've run into several packages that |
4 |
> appear not to be findable... watching emerge race all over the glob |
5 |
> looking for certain packages...there seems to be some problem with |
6 |
> what portage is looking for and pushing those packages out to repos. |
7 |
> |
8 |
> I've already forgotten the other 5 or so packages but the current one |
9 |
> holding up emerge is eject-2.1.5.tar.gz. |
10 |
> |
11 |
> It appears to be standing in the way of installing a number of other X |
12 |
> related packages. |
13 |
> |
14 |
> Is there a current problem with packages being available? |
15 |
> |
16 |
> If so then how can I remove it as a depandency? It seem unlikely that |
17 |
> eject would really prevent X from running but there appears no easy |
18 |
> way to avoid it. |
19 |
|
20 |
I found eject on my own and put in distfiles... then emerged, but I'm |
21 |
having several failures with emerge not finding pkgs. |
22 |
|
23 |
Did that with several other packages as well. |
24 |
|
25 |
I have several mirrors listed in /etc/make.conf but in some cases it |
26 |
seems emerge tries only one and when it fails... emerge just stops. |
27 |
|
28 |
Isn't it supposed to walk thru all my list of mirrors? Or is there |
29 |
something I have to set to make that happen? |
30 |
|
31 |
I've even hit a few (fonts) where the downloaded package does not |
32 |
match the size emerge expects... again it just fails instead of trying |
33 |
the other hosts in the list. |
34 |
|
35 |
I don't think I've ever seen a failure on size from a listed mirror before. |