GitLab

The incorrect shell parameter parsing of microcom has been fixed upstream
(slightly different to the patch of Alpine). Therefore, there is no need to
still patch it.

While working on the upgrade to busybox 1.31.0 I noticed that the
default busybox configuration files in `configs/` enable -R by default
while we don't. Since the option seems useful I decided to enable it our
busybox version as well.

Notable changes:

* udhcpc: upstream prefers -b over -n now. Since we set -b instead of -n
  by default this is not desired as it would not allow users to
  overwrite the -b without recompiling busybox. I therefore reverted the
  upstream commit introducing this change [0].

[0]: https://git.busybox.net/busybox/commit/?id=87e216294af9eec39c0c1d553555f8a98c15db38

Notable changes:

* The sysklogd -Z option has been removed in favor of -t option
  which has been added by upstream.
* Our own nologin.c applet has been replaced by an upstream
  nologin shell applet.
* New bc applet.

OK ncopa@

Fixes #9279
Fixes #7818

This reverts commit 2979bb1d.

References:
qemu/include/qemu/timer.h
qemu/include/hw/s390x/tod.h

Thanks to David Hildenbrand.

The busyboxconfig-extras configuration file didn't enable a few network
options which are enabled in the busyboxconfig configuration file. Most
importantly, support for IPv6 was disabled. The other options don't seem
as important to me but I enabled them for consistency anyhow.

Fixes #9590

Fixes #5083
Fixes #6742

fixes #9334

fixes dad.if-up getting stuck

should be installed if libssl1.1 is installed, not libressl-libssl.

build against libtls-standalone and openssl 1.1

Without this change a mail with the following body is sent on rotation:

	* Stopping busybox acpid ... [ ok ]
	* Starting busybox acpid ... [ ok ]

The quiet flag seems to have been accidentally removed in commit
040774a6 before that it was present.

* Remove all patches already applied upstream
	* 0001-ash-add-support-for-command_not_found_handle-hook-fu.patch
	* 0001-cat-fix-cat-e-and-cat-v-erroneously-numbering-1st-li.patch
	* 0001-wget-emit-a-message-that-certificate-verification-is.patch
	* 0015-ash-introduce-a-config-option-to-search-current-dire.patch
	* 0016-top-handle-much-larger-VSZ-values.patch
	* 0017-ifupdown-do-not-fail-if-interface-disappears-during-.patch
* Rename config option for command_not_found hook
	* upstream patch adding this hook slightly differs from our
	  downstream patch in this regard
* Rebase some patches manually:
	* external_ssl_client.patch
	* 0006-ping-make-ping-work-without-root-privileges.patch
	* 0007-fbsplash-support-image-and-bar-alignment-and-positio.patch
* Add support for `-e` to our ssl_client
	* See https://git.busybox.net/busybox/commit/?id=403f2999f94937ba3f37db6d093832f636815bb9
* Update the configuration file
* Regenerate all patches using `git format-patch --no-numbered --no-signature`
  to reduce the diff for future upgrades.

Fixes #9215

This was broken in commit dc6cfb7c which just removed
opt_complementary (due to that being removed in bb). Add proper
getopt flag to get correct behaviour.

busybox now requires ssl on the target host. Fix busybox dependency
and adjust bootstrap build order accordingly.

ref #9037

fix busybox wget https support by using an external ssl_client helper
for https.

Disable the use of external openssl. This was fixed to check
certificates as a temporary solution. openssl can not produce any useful
error messages on certificate errors. It is big. So we simply disable
its use.

For dynamic busybox we disable the internal ssl_client and the internal
(broken) tls code, and build our own ssl_client which properly verifies
the certificates.

For the static busybox we enable the internal ssl_client and tls code,
but we only allow its use with --no-check-certificates. This is so we
still can fetch things from https in an emergency situation.

We auto-install ssl_client if both libssl and busybox are installed. This
is to keep backwards compatibility.

* Rename --network to --net, to match util-linux and the help text
* -t, -S and -G should take mandatory integer options, but are defined
  as simple flags, causing problems such as:

    https://github.com/linuxkit/linuxkit/issues/567
    https://github.com/gliderlabs/docker-alpine/issues/359
    https://github.com/kontena/pharos-cluster/pull/81

These patches have been accepted upstream by Busybox.
Signed-off-by: Euan Harris <euan.harris@docker.com>

apparently it makes ifupdown segfault

ref #8751

See http://lists.busybox.net/pipermail/busybox/2018-January/086146.html for rationale.

This commit updates $license variable in all APKBUILDs to comply with
short names specified by SPDX version 3.0 [1] where possible. It was
done using find-and-replace method on substrings inside $license
variables.

Only license names were updated, not "expressions" specifying relation
between the licenses (e.g. "X and Y", "X or Y", "X and (Y or Z)") or
exceptions (e.g. "X with exceptions").

Many licenses have a version or multiple variants, e.g. MPL-2.0,
BSD-2-Clause, BSD-3-Clause. However, $license in many aports do not
contain license version or variant. Since there's no way how to infer
this information just from abuild, it were left without the variant
suffix or version, i.e. non SPDX compliant.

GNU licenses (AGPL, GFDL, GPL, LGPL) are especially complicated. They
exist in two variants: -only (formerly e.g. GPL-2.0) and -or-later
(formerly e.g. GPL-2.0+). We did not systematically noted distinguish
between these variants, so GPL-2.0, GPL2, GPLv2 etc. may mean
GPL-2.0-only or GPL-2.0-or-later. Thus GNU licenses without "+" (e.g.
GPL2+) were left without the variant suffix, i.e. non SPDX compliant.

Note: This commit just fixes format of the license names, no
verification has been done if the specified license information is
actually correct!

[1]: https://spdx.org/licenses/

ref #8209