Upgrade Instructions/Next

Introduction

The goal of these instructions is to provide Funtoo Linux users with a reliable, consistent set of instructions for upgrading Funtoo Linux from 1.4 to Next.

Note that while Portage has some ability to upgrade packages, it is not perfect at performing complex updates right now. One of the primary motivations to have official Funtoo releases is for the purpose of identifying these upgrade challenges and implement improvements to Portage and associated tools to make the process better. Before Portage can be made better, we need to start documenting the various commands required to perform these updates, and that is where these instructions come in.

Overview

With the intended purpose of these instructions in mind, it is recommended to perform a fresh install of Funtoo Linux Next if possible. This is not practical or feasible, follow the steps in this documentation to upgrade Funtoo Linux. The process is straightforward.

Please assist in ensuring that these instructions are complete, make changes to the page that are needed to make these instructions 100% reliable, and if the instructions seem to not work properly, please consider opening a bug at https://bugs.funtoo.org or asking for assistance at https://forums.funtoo.org or #funtoo on freenode. Do not make major changes to this document without first opening a bug related to the issue so your changes can be reviewed. Thank you!

Set Release and Sync

Use your favorite editor in /etc/ego.conf, set the release to Next:

   /etc/ego.conf

[global]

release = next

Then, run ego sync:

root # ego sync

Then, run epro build next:

root # epro build next

Upgrade Toolchain

Funtoo next, gcc has been updated to 11.3.0 series by default, so lets take advantage of that, and also update binutils and glibc. Note that multiple versions of gcc, 11.3.0 and 9.2.0, may get pulled in in while upgrading gcc. Only 11.3.0 is needed in Funtoo next, so once 11.3.0 is installed, you may cancel the emerge of older versions of gcc to save time.

root # emerge -u1 gcc binutils glibc
root # source /etc/profile

World Update

Before starting the world update, it is a good idea to upgrade python. Do so as follows:

root # emerge -u =dev-lang/python-3*

Once this is done, we will temporarily want to tell emerge to build python modules for versions 2.7, 3.6 and 3.7. We are doing this so that dependencies resolve correctly for installed packages still using python-3.6, and will "undo" this setting and rebuild these packages later:

root # export PYTHON_TARGETS="python3_7 python3_9"

At this point, you should be all set to perform a world update. We will exclude perl from upgrading now as we will do that near the end of the install.

root # emerge -auDN @world --jobs=3 --exclude dev-lang/perl

It seems that excluding perl can cause some issues with the dep graph currently. If that is the case you can try the complete world update.

root # emerge -auDN @world --jobs=3

Enjoy!