Upgrade gentoo - Revision history

M at 14:43, 4 September 2020

2020-09-04T14:43:55Z

← Older revision		Revision as of 14:43, 4 September 2020
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 ===		=== Upgrading to PHP 7 ===
	* edit /etc/portage/make.conf		* edit /etc/portage/make.conf

M at 23:45, 18 January 2018

2018-01-18T23:45:34Z

@@ Line 7: / Line 7: @@
 * use eselect to select it
-=== Upgrading gentoo profile ===
+=== Upgrading to gentoo profile v17 ===
   bitpost ~ # eselect profile list
   Available profile symlink targets:
    [1]   default/linux/amd64/13.0 (stable)
-   [2]   default/linux/amd64/13.0/selinux (dev)
+   ...
    [9]   default/linux/amd64/13.0/no-multilib (stable)
-   [10]  default/linux/amd64/13.0/systemd (stable)
+   ...
-  [11]  default/linux/amd64/13.0/x32 (dev)
+   [12]  default/linux/amd64/17.0 (stable) *
-   [12]  default/linux/amd64/17.0 (stable)
+   ...
    [22]  default/linux/amd64/17.0/no-multilib (stable) *
-   [23]  default/linux/amd64/17.0/no-multilib/hardened (dev)
+   ...
    [27]  default/linux/amd64/17.1 (exp)
-   [28]  default/linux/amd64/17.1/selinux (exp)
+   ...
-  [29]  default/linux/amd64/17.1/hardened (exp)
-  [30]  default/linux/amd64/17.1/desktop (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
@@ Line 70: / Line 29: @@
 -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)
   * 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

M at 23:27, 18 January 2018

2018-01-18T23:27:11Z

@@ Line 7: / Line 7: @@
 * use eselect to select it
-=== Upgrading to v17 profile WAIT UNTIL YOU HAVE TIME TO WORK THROUGH IT ALL over christmas break ===
+=== Upgrading gentoo profile ===
-This is going to get ugly...
+Go with the base profile.  I used to use no-multilib (to avoid 32-bit support) but it sounds like there's little harm or cost in it.
-There are selinux and systemd and desktop and no-multilib profiles... i was using no-multilib so I'll go from 13 -> 17
-  bitpost ~ # eselect news read new
+ bitpost ~ # eselect profile list
--11-30-new-17-profiles
+ Available profile symlink targets:
     Title                     New 17.0 profiles in the Gentoo repository
     Author                    Andreas K. Hüttel <dilfridge@gentoo.org>

M at 22:33, 9 December 2017

2017-12-09T22:33:00Z

← Older revision		Revision as of 22:33, 9 December 2017
Line 4:		Line 4:
	# add php7-0 as target		# add php7-0 as target
	PHP_TARGETS="php5-6 php7-0"		PHP_TARGETS="php5-6 php7-0"
	* emerge		* emerge everything
	* use eselect to select it		* use eselect to select it

	=== Upgrading to v17 profile ===		=== Upgrading to v17 profile WAIT UNTIL YOU HAVE TIME TO WORK THROUGH IT ALL over christmas break ===

	This is going to get ugly...		This is going to get ugly...

M at 21:33, 9 December 2017

2017-12-09T21:33:58Z

← Older revision		Revision as of 21:33, 9 December 2017
Line 9:		Line 9:
	=== Upgrading to v17 profile ===		=== Upgrading to v17 profile ===

			This is going to get ugly...
			There are selinux and systemd and desktop and no-multilib profiles... i was using no-multilib so I'll go from 13 -> 17
	bitpost ~ # eselect news read new		bitpost ~ # eselect news read new
	2017-11-30-new-17-profiles		2017-11-30-new-17-profiles

M: Created page with "=== 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 * use esele..."

2017-12-09T21:31:49Z

Created page with "=== 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 * use esele..."

New page

=== 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
* use eselect to select it

=== Upgrading to v17 profile ===

bitpost ~ # eselect news read new
2017-11-30-new-17-profiles
Title New 17.0 profiles in the Gentoo repository
Author Andreas K. Hüttel <dilfridge@gentoo.org>
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:
1) 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.
2) 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.
3) 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
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.