| 1 |
Hi! |
| 2 |
|
| 3 |
On Tue, Jan 09, 2007 at 10:56:02AM -0500, Kwon wrote: |
| 4 |
> Just did the following to upgrade a system that was built about 6-9 months |
| 5 |
> ago: |
| 6 |
> |
| 7 |
> emerge --sync && emerge os-headers glibc binutils gcc && emerge os-headers |
| 8 |
> glibc binutils gcc && emerge -e system && emerge -e system && emerge -uD |
| 9 |
> world && emerge --update --newuse --deep --buildpkg world && emerge -v |
| 10 |
> depclean &&revdep-rebuild -v && revdep-rebuild ?v |
| 11 |
|
| 12 |
Automatic upgrades like this isn't safe. There few packages which require |
| 13 |
specific MANUAL actions while upgrade. Here is full (I hope) list of such |
| 14 |
packages: http://www.gentoo.org/doc/en/index.xml?catid=upgrade . Every |
| 15 |
time you see one of these packages wanna to major upgrade (first or second |
| 16 |
version number usually) you should read these upgrade guides BEFORE doing |
| 17 |
upgrade. |
| 18 |
|
| 19 |
Complete recompilation of toolchain needed not every 6-9 months, but only |
| 20 |
if one of toolchain packages was upgraded (and I think if just revision |
| 21 |
(-r) number was changed then toolchain recompilation isn't necessary). |
| 22 |
Anyway, there exists more correct and fast way to recompile everything: |
| 23 |
# Recommended: cleanup your "packages" directory (usually |
| 24 |
# /usr/portage/packages/) before continue to avoid installing wrong |
| 25 |
# packages using -k by accident. |
| 26 |
emerge linux-headers glibc binutils gcc-config gcc |
| 27 |
# Here you should choose new gcc if it was installed into new SLOT! |
| 28 |
gcc-config NAME_OR_NUMBER # see `gcc-config -l` |
| 29 |
source /etc/profile |
| 30 |
emerge -1 libtool |
| 31 |
emerge -b glibc binutils gcc portage |
| 32 |
emerge -bke system # avoid 3rd toolchain recompilation |
| 33 |
emerge -ke world # avoid 2nd system recompilation |
| 34 |
|
| 35 |
Also I don't recommend to execute --depclean automatically, it sometimes |
| 36 |
tries to uninstall too much including some important/critical packages. |
| 37 |
|
| 38 |
In addition to your commands I recommend to run glsa-check because there |
| 39 |
can be some old non-ungraded packages in SLOTs which require manual action |
| 40 |
for upgrade (like `emerge -uD "<package-version"`) or delete and which can |
| 41 |
have security holes. |
| 42 |
|
| 43 |
-- |
| 44 |
WBR, Alex. |
| 45 |
-- |
| 46 |
gentoo-hardened@g.o mailing list |
Archives