pmaports/device/testing/device-motorola-condor/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

29 lines
1 KiB
Text

# Reference: <https://postmarketos.org/devicepkg>
pkgname=device-motorola-condor
pkgdesc="Motorola Moto E (1st gen)"
pkgver=0.1
pkgrel=4
url="https://postmarketos.org"
license="MIT"
arch="armv7"
options="!check !archcheck"
depends="postmarketos-base linux-motorola-condor mkbootimg msm-fb-refresher"
makedepends="devicepkg-dev"
source="deviceinfo initfs-hook.sh 90-android-touch-dev.rules"
build() {
devicepkg_build $startdir $pkgname
}
package() {
devicepkg_package $startdir $pkgname
install -D -m644 "$srcdir"/90-android-touch-dev.rules \
"$pkgdir"/etc/udev/rules.d/90-android-touch-dev.rules
}
sha512sums="
f16f3498fcd54e0022d71daa6f291b661a95e3c9b6b47c2effb177fe85f21beb6f8995f59d0c1954b3602116b6c991077503b69f44ad9eb3a1550ff8dfabbbdb deviceinfo
a009171a9f95ad15f28b22549f8618711b42fabbad473e416b905c60131265a02ab7eb33c4e57f2201b859152a603c77c3c9bec955ab3998cd385858f076c8ec initfs-hook.sh
568d407c3e96b45d740af8617f0e389d36a7091dceccae8f77288fdc45fb7a5ed418c28f31d7fe5a51d92337a40b2dd741b1b18ad02e3fbae91f9a2035d62c95 90-android-touch-dev.rules
"