| 1 |
> -----Original Message----- |
| 2 |
> From: Rupert Young (Restart) |
| 3 |
> [mailto:rupert.young@×××××××××××××××××.com] |
| 4 |
> Sent: 22 September 2005 12:25 |
| 5 |
> To: gentoo-user@l.g.o |
| 6 |
> Subject: RE: [gentoo-user] System update problems |
| 7 |
> |
| 8 |
> |
| 9 |
> Thanks. Unless anyone else has any suggestions I will try it. |
| 10 |
> |
| 11 |
> Can anyone else confirm this is the way to go before I try? |
| 12 |
|
| 13 |
It depends how patient you are. The suggested fix will bring your |
| 14 |
machine up to an "as new" condition. On the other hand, it might |
| 15 |
unnecessarily rebuilt packages that may not be broken or need updating |
| 16 |
(yet) and will take years to complete (well, it depends on how fast your |
| 17 |
machine is :-) That said I would think that after a whole year there |
| 18 |
wouldn't be much left in portage, which has not a new ebuild? |
| 19 |
|
| 20 |
As an alternative, if your machine is not totally hosed you could start |
| 21 |
from the bottom up rebuilding the core packages and after a fresh |
| 22 |
--sync, update the whole world. Try re-emerging the gentoo toolkit: |
| 23 |
gcc-config glibc binutils libstdc++. Run # etc-update and # env-update |
| 24 |
&& source /etc/profile as required and rebuild portage; do another |
| 25 |
--sync; and then emerge -upDv world to see what comes up in need for an |
| 26 |
update. |
| 27 |
|
| 28 |
However, if basic compilers, etc. are broken you will not be able to |
| 29 |
re-emerge the toolkit and the solution suggested by Dave remains the |
| 30 |
best option. |
| 31 |
-- |
| 32 |
Regards, |
| 33 |
Mick |
| 34 |
|
| 35 |
-- |
| 36 |
gentoo-user@g.o mailing list |
Archives