When 788f328dc752a75da08d4c6fc27d094ecb4807d5 introduced pulling from
docker by default, "--insecure-options=image" was added for all
docker registries. However, when the user also needs to set "http" as
in "--insecure-options=image,http" it will not be used because the
other argument is added as last disregarding the option was already
set by the user.
Check if the option was set by the user and only add it if it is not
provided. If the user forgets to add "image" then rkt will simply
fail and tell that this option is needed; thus no complex logic of
appending and detecting only "image" is needed. Do the same for the
"--trust-keys-from-https" option to be consistent in allowing to
overwrite it with "--trust-keys-from-https=false".
- Mask sig 0x000406e3, pf_mask 0xc0, revision=0xd6 [Link 1]
- Mask sig 0x000406e3, pf_mask 0xc0, revision=0xda [Bug 722768]
This will basically downgrade microcode for 0x000406e3 back to rev 0x00d6 from 2019-10-03.
Link1: c1d8ba62ab
Signed-off-by: Sayan Chowdhury <sayan@kinvolk.io>
There is no portage-stable/licenses/Apache-2 file because the
correct name for the license is Apache-2.0, and the missing
license file causes the build to fail.
Now that bind-tools are built with gssapi only for AMD, without gssapi
for ARM, we need to get the USE flag requirement relaxed. Profile for
each architecture will instead choose whether to use gssapi.
bind-tools has been disabled since a long time, probably because of
build errors around cross-compilation for ARM. However, bind-tools
binaries should be at least included in ARM images. So enable bind-tools
again for ARM without gssapi included.
To do that, disable gssapi for bind-tools only in the ARM profile, and
enable gssapi only in the AMD profile.
They were needed when Jenkins did not have qemu-static to run compiled
binaries of the target architecture.
Remove the patches as Jenkins is ready now and qemu-static is there to
stay because we need it for SELinux and other things.
The unzip update in the portage-stable branch going along with this PR
suddenly fails to compile because ccache permissions are wrong in one
subfolder.
Disable ccache because it only gives a low hit rate anyway and once a
package is compiled, emerge will reuse the binary package. (A possible
compilation performance regression would be if a kernel patch is tested
and the kernel package needs to be build over and over again without being
able to keep the object files - not sure if this or something similar is
often the case.)
