pmaports/device/testing/device-motorola-shamu/APKBUILD
Przemysław Romanik d7c036b978
testing/device-many: rebuild to fix wrong initfs-hook.sh location (MR 4187)
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
2023-06-19 17:00:28 +02:00

25 lines
763 B
Text

# Reference: <https://postmarketos.org/devicepkg>
pkgname=device-motorola-shamu
pkgdesc="Motorola Google Nexus 6"
pkgver=0.4
pkgrel=1
url="https://postmarketos.org"
license="MIT"
arch="armv7"
options="!check !archcheck"
depends="postmarketos-base linux-motorola-shamu mkbootimg msm-fb-refresher"
makedepends="devicepkg-dev"
source="deviceinfo initfs-hook.sh"
build() {
devicepkg_build $startdir $pkgname
}
package() {
devicepkg_package $startdir $pkgname
}
sha512sums="
ad2ae6c1f19ad5cc548b32dbd592c9da876a3964844606c72eb2478208c3f13429148f6a9925786a02a9c33da953cbc011561277a5543d34aeb5f84e11d4788e deviceinfo
c4f4785a9fea1d8b461e1de4dcd04daae45bd9df94f8123655b981de5ac5718f082a59169c39c506aa996c1642f465249fbc8b6e1c0463aeca6abf74ff523d9c initfs-hook.sh
"