1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
|
5 |
Christopher E schrieb: |
6 |
> Hello there all, |
7 |
Hello back ^^ |
8 |
> |
9 |
> I am now having a emerge issue, I am trying for the first TIME to |
10 |
> update all of what I have done to the latest and best updates :-) any |
11 |
> how I did: |
12 |
> |
13 |
> First I did the below in a xterm in gnome this when good: |
14 |
> "emerge sync" |
15 |
Yes, right command |
16 |
> |
17 |
> Then I did the following command and it did about 10 emerges then it |
18 |
> stoped and said it could not resovle and it tryed it on all of the |
19 |
> selected mirrors, so I rebooted after trying it again with the same |
20 |
> issue but this time I have 10 less to download: |
21 |
> "emerge --update --newuse --deep world |
22 |
Kinda "wrong". You better add "-a" (or "-p") to see what will happen. |
23 |
Don't trust portage blindly! |
24 |
And: what wasn't portage able to resolve? Dependencies or the mirror |
25 |
to fetch the file from? If it's the latter, don't worry, just use |
26 |
another mirror. |
27 |
> |
28 |
> Ok now I am not able to get a xterm up in gnome and when I try the |
29 |
> above to things in a vt the first one works and then I do the next and |
30 |
> get the same issue and I even just tryed to emerge just one thing and |
31 |
> got the same issue what is this and why? I would send you it but I am |
32 |
> in gnome and can not get xterm open to get the errors right |
33 |
You could check "/var/log/emerge.log" to see what portage has emerged |
34 |
and what package is causing your problem. As long as emerge works in a |
35 |
VT this is ok. |
36 |
|
37 |
Jannis Achstetter |
38 |
-----BEGIN PGP SIGNATURE----- |
39 |
Version: GnuPG v1.4.3 (GNU/Linux) |
40 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
41 |
|
42 |
iD8DBQFEWOr2snofy59UleQRAmIXAJ9I/Sx0HkY1VrAEiTPzRZlbxoocugCfTCsI |
43 |
Av60nKVVMQOJDXZxvUONOZI= |
44 |
=+3YF |
45 |
-----END PGP SIGNATURE----- |