This function was changed, so these packages need to be rebuilt to have
the kernel installed under the new filename 'vmlinuz'

Ignacy Kuchciński authored 3 years ago and Alexey Minnekhanov committed 3 years ago

This is required for kernels earlier than 4.7 for bwrap to work for
normal users, and therefore for gnome web (epiphany) and flatpak.

[ci:skip-build] [ci:ignore-count]

Luca Weiss authored 4 years ago and Bart Ribbers committed 4 years ago

These haven't been used since converting the APKBUILDs to use
devicepkg-dev, so remove them.

[ci:skip-build]
[ci:ignore-count]
[ci:skip-vercheck]

Luca Weiss authored 4 years ago and Oliver Smith committed 4 years ago

Mostly the GCC10 yylloc failure was seen but several others have been
observed:

* wireguard script was silently failing
* several gcc10 x86 errors
* a checksum from kernel.org has changed

Now we have 3 different gcc10 yylloc patches:

gcc10-extern_YYLOC_global_declaration.patch:
    Linux < 4.2

linux4.2-gcc10-extern_YYLOC_global_declaration.patch:
    Linux 4.2+

linux4.17-gcc10-extern_YYLOC_global_declaration.patch:
    Linux 4.17+

[ci:skip-build]
[ci:ignore-count]
[ci:skip-vercheck]

Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).

I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.

It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.

[skip ci]: I have verified, that every single one of these kernels builds.
           CI will likely run out of time while downloading source tarballs.

Minecrell authored 4 years ago and Oliver Smith committed 4 years ago

TP:[AL3]:APKBUILD:5:pkgname must not be quoted

[skip ci]: won't finish within 3 hours

Antoine Fontaine authored 4 years ago and Oliver Smith committed 4 years ago

https://gitlab.com/postmarketOS/pmbootstrap/-/issues/1910

[skip ci]: CI fails because it can't download every release tarball to
           check checksums in 3h.

Dolphin von Chips authored 5 years ago and Oliver Smith committed 4 years ago

[skip-ci]: just downloading all kernel sources takes about one hour
           and ollieparanoid wants to merge it now. This already ran
	   successfully with [ci:skip-build] and [ci:skip-vercheck].

Prepare for better device categorization by moving everything to testing
subdir first.

[skip-ci]: chicken-egg problem: passing pmaports CI depends on pmbootstrap MR
				depends on this MR

Related: postmarketos#16