postmarketos-mkinitfs!30 and specifically postmarketos-mkinitfs@6fdc8937,
changes expected hooks location from /etc/postmarketos-mkinitfs/hooks
to /etc/mkinitfs/hooks, and another commit pushed later adds
/usr/share/mkinitfs/hooks to expected directories. This more or less
breaks new pmOS installs done by running pmbootstrap install on edge branch,
which pull current (2023-06-17T16:57+02:00) device-* packages from
https://mirror.postmarketos.org/postmarketos/master.
Many of those packages which included initfs-hook.sh no longer work in that
case, because they had those hooks in old location, which isn't used
by latest postmarketos-mkinitfs.
Rebuilding the affected packages solves the issue.
[ci:ignore-count]
[ci:skip-build]: already built successfully in CI
mesa-dri-swrast no longer exists and just installs,
mesa-dri-gallium. However, this might not always be the case, so
let's change it before it causes any issues.
[ci:ignore-count]
[ci:skip-build]
At the moment we have Contributor: lines on some packages (but not all of them),
but often they don't represent the actual contributors to the package very well.
E.g. when we added them retroactively to the device packages we only added
the initial contributor (which isn't necessarily the person
who made most of the work for a device...)
The Git history is the most representative source for figuring out
who contributed to a package, so there is no reason to duplicate that
into the APKBUILD.
[skip ci]: way too many packages
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
Anton Bambura