Upgrading Gentoo/ja

This document explains how new Gentoo releases affect existing installs.

思想
Here in Gentoo land, the concept of upgrading is quite different compared to the rest of the Linux world. It is a well-known fact that Gentoo never got in touch with the "classic" way of upgrading software: waiting for a new release, downloading it, burning, putting it in the cdrom drive and then following the upgrade instructions.

Gentoo users know however that this process is extremely frustrating for power users that want to live on the bleeding edge. Even power users from other distributions probably share the same feelings, given the popularity and spread of tools like apt or apt-rpm which make it possible to have quick and frequent updates. However, no distribution is more suited than Gentoo to satisfy these kind of demanding users. From the beginning, Gentoo was designed around the concept of fast, incremental updates.

Ideally, users install software once and never bother with releases: just follow the instructions in A Portage Introduction in the Gentoo handbook that explain how to keep the system up to date. While that's the way things usually go, sometimes changes are made to the core system which require updates to be done manually.

Releases and profiles
A recurring question about the Gentoo release process is: "Why roll out new releases frequently, if they are not intended to let users update software?" There are various reasons:


 * A new release means new Installation CDs with bugfixes and more features
 * A new release provides an updated set of GRP packages, so that users that choose "the fast way" to install (stage3 + precompiled packages) end up with a system that is not outdated
 * Finally, a new release may, from time to time, implement some features that are incompatible with previous releases

When a release includes new incompatible features, or provides a set of core packages and settings that deeply modify the behavior of the system, we say that it provides a new profile.

A profile is a set of configuration files, stored in a subdirectory of, that describe things such as the ebuilds that are considered system packages, the default USE flags, the default mapping for virtual packages, and the architecture on which the system is running.

The profile in use is determined by the symbolic link, which points to a subdirectory of which holds the profile files. For instance, the default 13.0 profile can be found at. The files in the parent directories are part of the profile as well (and are therefore shared by different subprofiles). This is why we call these cascaded profiles.

Profiles obsoleted by new ones are kept in along with the current ones, but they are marked as deprecated. When that happens a file named is put in the profile directory. The content of this file is the name of the profile that should be "upgraded to"; Portage uses this information to automatically warn administrators when they should update to a new profile.

There are various reasons that a new profile may be created: the release of new versions of core packages (such as, , or ) that are incompatible with previous versions, a change in the default USE flags or in the virtual mappings, or maybe a change in system-wide settings.

Releases without profile changes
If a new Gentoo release does not include a new profile then just pretend that it never happened. :)

When the installed packages are upgraded as explained in the Gentoo Handbook, then the system will be exactly the same as one that has been installed using the new release.

Releases with profile changes
If a release (such as 13.0 for ) introduces a new profile, then there is the choice to migrate to the new profile.

Generally, such migrations are not mandatory, and systems can continue to use the old profile - just update the packages as explained in the Gentoo Handbook.

However, Gentoo strongly recommends updating the profile if it becomes deprecated. When this happens, it means that Gentoo developers no longer plan on supporting it.

When a profile migration is apparent, then the upgrade has to be executed manually. The way to update may vary significantly from release to release; it depends on how deep the modifications introduced in the new profile are.

In the simplest case users only have to change the symlink, in the worst case they may have to recompile the entire system from scratch while doing a neat voodoo dance. Migration is usually covered in the release notes. The necessary instructions are explained further in this guide.

Supported profiles
To view the list of supported profiles, call (which can be installed using ) as follows:

Upgrading from older systems
Some systems are too old to just switch the profile. Newer profiles might need more recent Portage versions or other software that cannot be installed anymore because the package definitions (ebuilds) for those older software versions are not available anymore.

If this is the case, the system should first receive older Portage tree snapshots and upgrade at least Portage (but preferably all packages in the system set), gradually increasing the Portage tree snapshot date until it is recent enough to follow the profile switching instructions again:

Older snapshots are often still available on some mirrors on the Internet or on specific locations dedicated for this purpose. It is recommended to verify the integrity of those files to make sure they are not tampered with:

Although the release signing keys might be expired, the signature should still be OK.

Upgrading from (too) old systems
Sometimes, systems are too old to easily upgrade. The upgrade path might need intermediate versions of software (such as portage) that does not exist any more, requiring to update the portage tree in steps (for instance incremental tree updates with steps of 3 to 4 months).

To upgrade such systems, a recent stage3 can be used to update the system. Instructions for that are given in the Updating old systems section.

General instructions
First, run. The utility makes viewing and selecting profiles easy, without needing to create or remove symlinks by hand.

Changing profiles manually is still supported though:

Updating to 2008.0, 2007.0, or 2006.1
Be aware that, if an upgrade from these profiles is selected, that they expect the system to be set to a Unicode locale by default; specifically that  is set in. For this to work, a Unicode locale for the system must be created. Please read the UTF-8 article to learn how to create the proper locale.

Alternatively, if setting a locale is not preferred, then users need to specify UNICODE="no" in, and re-emerge (or wait until the next baselayout update) with the   USE flag. This can be accomplished through:


 * setting  just for, like so:


 * or setting it globally for all packages by adding it to the USE variable in :

Finally, follow the general upgrade instructions for updating the profile.

Updating to 2006.0
To switch to the 2006.0 profile, point the symlink to the new location. Make sure Portage is updated before changing the profile.

- Users that use a 2.4 kernel or don't want to use NPTL should use the default-linux/alpha/no-nptl profile. More information is available in the alpha release notes.

- The merge of the ppc32 and ppc64 profiles went forward. The ppc32 profile has been changed in a way that offers a minimalistic generic profile for all purposes, located in default-linux/ppc/ppc32. The release-dependent profile is optimized for desktop-usage and located in default-linux/ppc/ppc32/2006.0. There are some subprofiles available for G3 and G4 processors, and G3/Pegasos and G4/Pegasos for the Pegasos Open Desktop Workstation. Make sure to choose the correct subprofile for the system when migrating to a 2006.0 profile.

- Upgrading to the 2.4 -kernel based 2006.0/2.4 profile requires manual user intervention (unmerging java stuff) and an because of the gcc upgrade. Upgrading to the 2.6 -kernel based 2006.0 profile which is not considered stable also requires an entry in to unmask a 2.6 version of  and a full rebuild.

All other archs - There are no fundamental changes in this profile. No specific action needs to be performed.

Updating to 2005.1
To switch to the 2005.1 profile, point the symlink to the new location. Make sure Portage is updated before changing the profile.

All archs - There are no fundamental changes in this profile. No specific action needs to be performed.

- With the 2005.1 release, the ppc and ppc64 profiles were merged and a number of subprofiles for specific subarchitectures were created. Make sure to choose the correct subprofile for the system when migrating to a 2005.1 profile.

Updating to 2005.0
With the introduction of 2005.0, several architectures have decided to define additional profiles. Make sure to read the description of said profiles before deciding to migrate to one of them. Most architectures now also default to the 2.6 kernel tree where 2.4 was chosen previously.

Some architectures require a bit more actions to be completed in order to convert from one profile to another. If that is the case, the step-by-step guides are linked from the table.

To switch to the selected profile, point the symlink to the new location. Make sure Portage is updated before changing the profile!

When an upgrade is planned from a Linux 2.4-based system to a 2.6 kernel, make sure to read our Gentoo Linux 2.6 Migration Guide.

Updating to 2004.3
With the introduction of the 2004.3 profiles, users are not going to see huge modifications of their systems (see below for details). However, Gentoo developers decided to push out this new profile and to deprecate quite a few of the old ones to speed up the adoption of stacked profiles, that is, the profiles that follow the new layout of the directory, for instance  (supported by Portage 2.0.51 or later).

To switch to the 2004.3 profile, point the symlink to the new location:

All archs - As said above, there are no big changes introduced in this profile. However, it should be noted that and  are no longer considered system packages. This means that during a, Portage will try to remove them from the system. If any of those packages are needed, add them to after the profile switch, or manually emerge them.

- is now the default instead of  for newly installed machines. This has no effect on already installed machines, though.

Updating Portage to support cascading profiles
Although this section does not seem to integrate well in this upgrading guide, it is quite important. Any profile listed above this section requires a Portage version that supports cascading profiles. However, some obsoleted profiles don't allow the user to upgrade Portage or the user is using a profile that isn't available anymore - any attempt to upgrade Portage will result in a failure.

To work around this problem, users can set a temporary symbolic link to the obsolete profile, allowing them to upgrade their Portage after which they can continue with the upgrade procedure set forth in this guide. Please substitute  with the respective system architecture:

Updating to 2004.2
To switch to the 2004.2 profile, point the symlink to the new location:

- This profile changes the default X11 implementation from (deprecated) to. This change only touches the default value, and is only relevant for those who have not installed an X server yet. If one is already installed, then it will not affect the system at all; users are free to switch from one X server to the other exactly as before.

- There are no fundamental changes from previous profiles, no specific action needs to be performed.

Updating to 2004.0
To switch to the 2004.0 profile, point the symlink to the new location:

All archs - There are no fundamental changes from previous profiles, no specific action needs to be performed.

Updating from profiles older than 1.4 to 1.4
The instructions for this upgrade are quite complex, and can be found here.

Idea of the upgrade
The idea with this upgrade approach is that we create an intermediate build chroot in which a recent stage3 is extracted. Then, using the tools available in the stage3 chroot we upgrade the packages on the live system.

Preparing the intermediate build chroot
Let's first create the intermediate build chroot location, say, and extract a recent stage3 archive into it.

Next, we create a mount point inside this chroot environment, on which we then bind-mount the live (old) environment.

So now the live (old) system is also reachable within. This will allow us to reach the live (old) system and update the packages even when chrooted inside the intermediate build chroot.

Network, chroot, and update
The new install needs to access the network, so copy over the network related information:

Now chroot into the intermediate build location, and start updating vital packages on the live system, until the live system can be updated from within the live system (rather than through the intermediate build chroot):

Now start building packages into the (old) live system. If Portage is old or missing, it is a good idea to start with that:

Keep this chrooted session open and try to update the (old) live system. When failures occur, use this chrooted session to update packages using the build tools available in the intermediate build chroot (which includes recent, , etc.). Tools can be added as needed to the build chroot.

For some installations it may be necessary to update configuration files in order to install new software. Make the changes in the chroot environment.

To get the system fully up-to-date before exiting the root, build the  set (all packages) into the (old) live system:

Once finished the system should now be up to date!