Upgrade gentoo: Difference between revisions

Latest revision as of 14:43, 4 September 2020

Upgrading to gentoo profile v17.1

Upgrading from:

[11]  default/linux/amd64/17.0/no-multilib (stable) *

To:

[16]  default/linux/amd64/17.1 (stable) *

There are a bunch of steps to follow in gentoo news... so... follow them! Set aside some time for this...

Upgrading to PHP 7

edit /etc/portage/make.conf

# APACHE2_MODULES: update -D PHP5 to -D PHP
# add php7-0 as target
PHP_TARGETS="php5-6 php7-0"

emerge everything
use eselect to select it

Upgrading to gentoo profile v17

bitpost ~ # eselect profile list
Available profile symlink targets:
 [1]   default/linux/amd64/13.0 (stable)
 ...
 [9]   default/linux/amd64/13.0/no-multilib (stable)
 ...
 [12]  default/linux/amd64/17.0 (stable) *
 ...
 [22]  default/linux/amd64/17.0/no-multilib (stable) *
 ...
 [27]  default/linux/amd64/17.1 (exp)
 ...

I started down v17 so I better finish up. But let's go with the base profile (12). I used to use no-multilib (to avoid 32-bit support) but it sounds like there's little harm or cost in it.

Steps are described in eselect:

 eselect news list
 eselect news read 36
 2017-11-30-new-17-profiles
  Title                     New 17.0 profiles in the Gentoo repository
(blah blah blah)
* Rebuild your entire system
    emerge -e @world
Switching the profile from 13.0 to 17.0 modifies the settings of 
GCC 6 to generate PIE executables by default; thus, you need to do 
the rebuilds even if you have already used GCC 6 beforehand.
If you do not follow these steps you may get spurious build
failures when the linker tries unsuccessfully to combine non-PIE
and PIE code.

@@ Line 1: / Line 1: @@
+=== Upgrading to gentoo profile v17.1 ===
+Upgrading from:
+ [11]  default/linux/amd64/17.0/no-multilib (stable) *
+To:
+ [16]  default/linux/amd64/17.1 (stable) *
+There are a bunch of steps to follow in gentoo news... so... follow them!  Set aside some time for this...
 === Upgrading to PHP 7 ===
 * edit /etc/portage/make.conf
@@ Line 7: / Line 16: @@
 * use eselect to select it
-=== Upgrading to v17 profile WAIT UNTIL YOU HAVE TIME TO WORK THROUGH IT ALL over christmas break ===
+=== Upgrading to gentoo profile v17 ===
+ bitpost ~ # eselect profile list
+ Available profile symlink targets:
+  [1]   default/linux/amd64/13.0 (stable)
+  ...
+  [9]   default/linux/amd64/13.0/no-multilib (stable)
+  ...
+  [12]  default/linux/amd64/17.0 (stable) *
+  ...
+  [22]  default/linux/amd64/17.0/no-multilib (stable) *
+  ...
+  [27]  default/linux/amd64/17.1 (exp)
+  ...
+I started down v17 so I better finish up.  But let's go with the base profile (12).  I used to use no-multilib (to avoid 32-bit support) but it sounds like there's little harm or cost in it.
-This is going to get ugly...
+Steps are described in eselect:
-There are selinux and systemd and desktop and no-multilib profiles... i was using no-multilib so I'll go from 13 -> 17
+  eselect news list
- bitpost ~ # eselect news read new
+  eselect news read 36
 -11-30-new-17-profiles
     Title                     New 17.0 profiles in the Gentoo repository
-   Author                    Andreas K. Hüttel <dilfridge@gentoo.org>
+  (blah blah blah)
-   Posted                    2017-11-30
-   Revision                  1
- We have just added (for all arches except arm and mips, these follow
- later) a new set of profiles with release version 17.0 to the Gentoo
- repository. These bring three changes:
-) The default C++ language version for applications is now C++14.
-    This change is mostly relevant to Gentoo developers. It also
-    means, however, that compilers earlier than GCC 6 are masked
-    and not supported for use as a system compiler anymore. Feel
-    free to unmask them if you need them for specific applications.
-) Where supported, GCC will now build position-independent
-    executables (PIE) by default. This improves the overall
-    security fingerprint. The switch from non-PIE to PIE binaries,
-    however, requires some steps by users, as detailed below.
-) Up to now, hardened profiles were separate from the default
-    profile tree. Now they are moving into the 17.0 profile
-    as a feature there, similar to "no-multilib" and "systemd".
- Please migrate away from the 13.0 profiles within the six weeks after
- GCC 6.4.0 has been stabilized on your architecture. The 13.0 profiles
- will be deprecated then and removed in half a year.
- If you are not already running a hardened setup with PIE enabled, then
- switching the profile involves the following steps:
- If not already done,
- * Use gcc-config to select gcc-6.4.0 or later as system compiler
- * Re-source /etc/profile:
-     . /etc/profile
- * Re-emerge libtool
-     emerge -1 sys-devel/libtool
- Then,
- * Select the new profile with eselect
- * Re-emerge, in this sequence, gcc, binutils, and glibc
-     emerge -1 sys-devel/gcc:6.4.0
-     emerge -1 sys-devel/binutils
-     emerge -1 sys-libs/glibc
   * Rebuild your entire system
       emerge -e @world
   Switching the profile from 13.0 to 17.0 modifies the settings of
   GCC 6 to generate PIE executables by default; thus, you need to do