1 |
Posted 2015-03-28 |
2 |
Revision 1 |
3 |
|
4 |
Starting on 2015-03-29, we are enabling true multilib support on amd64 |
5 |
and masking the old emul-linux-x86 package sets for removal. This |
6 |
change provides our users with the opportunity to build 32-bit libraries |
7 |
from source with all the flexibility given by ebuilds and the security |
8 |
of using mainline ebuilds, rather than relying on pre-packaged binary |
9 |
versions of them. |
10 |
|
11 |
The switch to the new system is likely to require a specific action from |
12 |
the users of our multilib profiles. Since the new system collides with |
13 |
the old one, the Package Manager must be able to clearly satisfy all |
14 |
the dependencies using the new system in order to proceed. This may |
15 |
require unmerging packages installed from third-party repositories that |
16 |
have not been updated to support the new system. |
17 |
|
18 |
In order to enable building necessary 32-bit libraries, users will be |
19 |
required to enable the abi_x86_32 USE flag on respective packages. |
20 |
This can be done using /etc/portage/package.use entries alike |
21 |
the following: |
22 |
|
23 |
sys-libs/zlib abi_x86_32 |
24 |
|
25 |
In most of the cases, Portage will be able to deliver correct |
26 |
suggestions for that when using the --autounmask feature. However, some |
27 |
users may prefer setting ABI_X86 globally to enable 32-bit libraries |
28 |
in all packages that support building them. This can be done using |
29 |
the following package.use entry: |
30 |
|
31 |
*/* abi_x86_32 |
32 |
|
33 |
In case of issues, blockers especially, users are recommended |
34 |
to manually uninstall any emul-linux-x86 packages that may have been |
35 |
installed on their systems. This will aid the Package Manager |
36 |
in choosing the correct dependency resolution path. If using Portage, |
37 |
this can be done using the following command: |
38 |
|
39 |
$ emerge -C 'app-emulation/emul-linux-x86*' |
40 |
|
41 |
Note: 32-bit applications may be temporarily broken after this step. |
42 |
Therefore, it should be followed by a @world upgrade immediately. |
43 |
|
44 |
2015-06-08-udev-init-scripts-changes |
45 |
Title udev-init-scripts-29 important changes |
46 |
Author William Hubbs <williamh@g.o> |
47 |
Posted 2015-06-08 |
48 |
Revision 2 |
49 |
|
50 |
In udev-init-scripts-29 and newer, the udev service script has been |
51 |
split into udev, udev-settle and udev-trigger. |
52 |
|
53 |
This means the settings in /etc/conf.d/udev have also been migrated |
54 |
to the appropriate /etc/conf.d files, so be careful when you update your |
55 |
configuration settings. |
56 |
|
57 |
udev and udev-trigger will be added to your sysinit runlevel, but not |
58 |
udev-settle. udev-settle should not be added to a runlevel. Instead, if |
59 |
a service needs this, it should add "need udev-settle" to its |
60 |
dependencies. |
61 |
|
62 |
|
63 |
2015-07-25-python-targets |
64 |
Title Python 3.4 enabled by default |
65 |
Author Mike Gilbert <floppym@g.o> |
66 |
Posted 2015-07-25 |
67 |
Revision 1 |
68 |
|
69 |
Python 3.4 is now enabled by default, replacing Python 3.3 as the |
70 |
default Python 3 interpreter. |
71 |
|
72 |
PYTHON_TARGETS will be adjusted to contain python2_7 and python3_4 by |
73 |
default via your profile. |
74 |
|
75 |
PYTHON_SINGLE_TARGET will remain set to python2_7 by default. |
76 |
|
77 |
If you have PYTHON_TARGETS set in make.conf, that setting will still be |
78 |
respected. You may want to adjust this setting manually. |
79 |
|
80 |
Once the changes have taken place, a world update should take care of |
81 |
reinstalling any python libraries you have installed. You should also |
82 |
switch your default python3 interpreter using eselect python. |
83 |
|
84 |
For example: |
85 |
|
86 |
eselect python set --python3 python3.4 |
87 |
emerge -uDv --changed-use @world |
88 |
|
89 |
2015-08-13-openssh-weak-keys |
90 |
Title OpenSSH 7.0 disables ssh-dss keys by default |
91 |
Author Mike Frysinger <vapier@g.o> |
92 |
Posted 2015-08-13 |
93 |
Revision 1 |
94 |
|
95 |
Starting with the 7.0 release of OpenSSH, support for ssh-dss keys has |
96 |
been disabled by default at runtime due to their inherit weakness. If |
97 |
you rely on these key types, you will have to take corrective action or |
98 |
risk being locked out. |
99 |
|
100 |
Your best option is to generate new keys using strong algos such as rsa |
101 |
or ecdsa or ed25519. RSA keys will give you the greatest portability |
102 |
with other clients/servers while ed25519 will get you the best security |
103 |
with OpenSSH (but requires recent versions of client & server). |
104 |
|
105 |
If you are stuck with DSA keys, you can re-enable support locally by |
106 |
updating your sshd_config and ~/.ssh/config files with lines like so: |
107 |
PubkeyAcceptedKeyTypes=+ssh-dss |
108 |
|
109 |
Be aware though that eventually OpenSSH will drop support for DSA keys |
110 |
entirely, so this is only a stop gap solution. |
111 |
|
112 |
More details can be found on OpenSSH's website: |
113 |
http://www.openssh.com/legacy.html |
114 |
|
115 |
2015-10-07-openrc-0-18-localmount-and-netmount-changes |
116 |
Title OpenRC-0.18 localmount and netmount changes |
117 |
Author William Hubbs <williamh@g.o> |
118 |
Posted 2015-10-07 |
119 |
Revision 1 |
120 |
|
121 |
The behaviour of localmount and netmount is changing on Linux systems. |
122 |
In the past, these services always started successfully. However, now they |
123 |
will fail if a file system they attempt to mount cannot be mounted. |
124 |
|
125 |
If you have file systems listed in fstab which should not be mounted at |
126 |
boot time, make sure to add noauto to the mount options. If you have |
127 |
file systems that you want to attempt to mount at boot time but failure |
128 |
should be allowed, add nofail to the mount options for these file |
129 |
systems in fstab. |
130 |
|
131 |
>>> Building file list for distfiles cleaning... |
132 |
>>> Cleaning distfiles... |
133 |
[ 1.0 M ] LVM2.2.02.88.tgz |
134 |
[ 2.1 M ] busybox-1.20.2.tar.bz2 |
135 |
[ 994.6 K ] cpio-2.11.tar.bz2 |
136 |
[ 227.3 K ] dmraid-1.0.0.rc16-3.tar.bz2 |
137 |
[ 493.5 K ] fuse-2.8.6.tar.gz |
138 |
[ 272.3 K ] genkernel-3.4.52.2.tar.xz |
139 |
[ 3.2 M ] gnupg-1.4.11.tar.bz2 |
140 |
[ 285.8 K ] mdadm-3.1.5.tar.bz2 |
141 |
[ 879.0 K ] open-iscsi-2.0-872.tar.gz |
142 |
[ 29.7 K ] unionfs-fuse-0.24.tar.bz2 |
143 |
=========== |
144 |
[ 9.4 M ] Total space from 10 files were freed in the distfiles directory |
145 |
passwd: password expiry information changed. |
146 |
passwd: password expiry information changed. |
147 |
20 Dec 2015 15:17:06 UTC: NOTICE : --- Running action sequence: preclean |
148 |
Copying stage4-preclean-chroot.sh to //tmp |
149 |
copying stage4-preclean-chroot.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-cloud-nomultilib-20151219//tmp |
150 |
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-cloud-nomultilib-20151219//tmp |
151 |
Ensure the file has the executable bit set |
152 |
Running stage4-preclean-chroot.sh in chroot: |
153 |
chroot /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-cloud-nomultilib-20151219/ //tmp/stage4-preclean-chroot.sh |
154 |
>>> Regenerating /etc/ld.so.cache... |
155 |
Skipping depclean operation for stage4 |
156 |
Skipping removal of world file for stage4 |
157 |
removing /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-cloud-nomultilib-20151219//tmp/stage4-preclean-chroot.sh from the chroot |
158 |
removing /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-cloud-nomultilib-20151219//tmp/chroot-functions.sh from the chroot |
159 |
20 Dec 2015 15:17:07 UTC: NOTICE : --- Running action sequence: rcupdate |
160 |
Copying rc-update.sh to /tmp |
161 |
copying rc-update.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-cloud-nomultilib-20151219/tmp |
162 |
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-cloud-nomultilib-20151219/tmp |
163 |
Ensure the file has the executable bit set |
164 |
Running rc-update.sh in chroot: |
165 |
chroot /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-cloud-nomultilib-20151219 /tmp/rc-update.sh |
166 |
Adding acpid to default |
167 |
* service acpid added to runlevel default |
168 |
Adding cloud-config to default |
169 |
* service cloud-config added to runlevel default |
170 |
Adding cloud-final to default |
171 |
* service cloud-final added to runlevel default |
172 |
Adding cloud-init-local to default |
173 |
* service cloud-init-local added to runlevel default |
174 |
Adding cloud-init to default |
175 |
* service cloud-init added to runlevel default |
176 |
Adding cronie to default |
177 |
* service cronie added to runlevel default |
178 |
Adding dhcpcd to default |
179 |
* service dhcpcd added to runlevel default |
180 |
Adding net.lo to default |
181 |
* service net.lo added to runlevel default |
182 |
Adding netmount to default |
183 |
* rc-update: netmount already installed in runlevel `default'; skipping |
184 |
Adding sshd to default |
185 |
* service sshd added to runlevel default |
186 |
Adding syslog-ng to default |
187 |
* service syslog-ng added to runlevel default |
188 |
removing /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-cloud-nomultilib-20151219/tmp/rc-update.sh from the chroot |
189 |
removing /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-cloud-nomultilib-20151219/tmp/chroot-functions.sh from the chroot |
190 |
20 Dec 2015 15:17:08 UTC: NOTICE : --- Running action sequence: unmerge |
191 |
20 Dec 2015 15:17:08 UTC: NOTICE : --- Running action sequence: unbind |
192 |
20 Dec 2015 15:17:08 UTC: NOTICE : --- Running action sequence: remove |
193 |
20 Dec 2015 15:17:08 UTC: NOTICE : --- Running action sequence: empty |
194 |
20 Dec 2015 15:17:08 UTC: NOTICE : --- Running action sequence: clean |
195 |
20 Dec 2015 15:17:08 UTC: NOTICE : Cleaning chroot: /var/tmp/* |
196 |
20 Dec 2015 15:17:08 UTC: NOTICE : Cleaning chroot: /tmp/* |
197 |
20 Dec 2015 15:17:08 UTC: NOTICE : --- Running action sequence: capture |
198 |
20 Dec 2015 15:17:08 UTC: NOTICE : Capture target in a tarball |
199 |
20 Dec 2015 15:17:08 UTC: NOTICE : Creating stage tarball... mode: pixz_x |
200 |
|
201 |
|
202 |
|
203 |
|
204 |
Full build log at /home/release/tmp/run/catalyst-auto.5t9Z0X/log/stage4-nomultilib-cloud.log |