We need to tell openrc-settingsd which ntp service to use, otherwise
it'll default to busybox ntpd which we don't want.
Additionally make sure openrc-settingsd service gets launched at boot
with the post-install/post-upgrade script.
[ci:skip-build]: already built successfully in CI
Get the githooks from alpine, with the following changes:
* Make it possible to parse the additionally nested "device" folder
with the exceptions mentioned in our COMMITSTYLE
* Ignore "device/*" as a possible prefix for the commit
* Replace abuild references with pmbootstrap
Relates #2055
[ci:skip-build]: already built successfully in CI
deviceinfo allows to disable the framebuffer which automatically
skips the splash on boot. Honor this setting as well for the shutdown
splash. Also honor the PMOS_NOSPLASH cmdline parameter as well.
[ci:skip-build]: already built successfully in CI
Angler and Bullhead support is in early stage other msm899{2,4} does not
use the package yet => safe to use rc kernels to get closer to
qcom/for-next git tree.
Kernel 6.2 and 6.3 got few memory map fixes for angler and bullhead.
* Added 3 not yet merged patches for angler:
- add regulators
- memory overlap fixes
- proper cont_splash_mem setup
* Removed 0004-arm64-dts-qcom-msm8992-Don-t-use-sfpb-mutex.patch
(already applied and backported to 6.1 stable), thus renumber the
following patch.
* config
- Enable zram with lzo-rle, add pmb:kconfigcheck-zram (fixes warning:
zramctl: /dev/zram0: failed to set algorithm: Invalid argument)
- Enable crc32, lz4hc, zstd.
Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
[ci:skip-build]: already built successfully in CI
Make it easier to look up the librem5-base version that was used in the
device-purism-librem5 package, e.g. for writing service pack release
notes:
> Purism Librem 5 Phone (librem5-base: 58pureos1)
[ci:skip-build]: already built successfully in CI
The only thing we define in the config file is "SpacesAftertabs": true
besides the version. Apparently it works fine if the version is
removed, and it avoids an error if the version changed (as it just did
now):
> Version from config file is not the same as the version of the binary
> Binary: 2.7.0, Config 2.6.0
We removed the "install_if" of the APK plugin on GS so that one could
use GNOME Software exclusively for flatpak
[ci:skip-vercheck]
[ci:skip-build]: already built successfully in CI
Update from librem5-bae 56 to 58, which includes the following changes
from Purism
* default: gadget: Use CDC-NCM instead of CDC-ECM
* defaults: Add an initramfs script to reencrypt LUKS rootfs
* defaults: librem5-pm: Add rules for EM7565 and SIM7912G
* defaults: pulse: Reduce fragment size to 22 ms
* defaults: Switch USB PM timeouts back to 2s for devices and 0 for hub
* defaults: Enable WiFi powersave with brcmfmac driver
* defaults: usb_gadget: Run service as a dependency of UDC device unit
* defaults: usb_gadget: Set Before= relation to network.target
* defaults: librem5-pm: Enable NO_SUSPEND quirk and adjust PM properties
* d/control: Bump Librem 5 kernel dependency to 6.1.19pureos1
Note, that this update doesn't fix the modem disapearing modem during
suspend. So we keep the current workarounds we have.
Signed-off-by: Alistair Francis <alistair@alistair23.me>
[ci:skip-build] already built successfully in CI
Not everyone's setup includes "pmbootstrap" as a command in $PATH.
Currently, in such setups, $ pmbootstrap ci kconfig (and potentially
other testcases) in the pmaports repository do not work as they expect
the "pmbootstrap" command to exist. Resolve this by checking whether
PMBOOTSTRAP_CMD is set and use that as command for invoking pmbootstrap.
If it isn't set (because you're using an old pmbootstrap version or
invoking a script directly for some reason), fall back to the old
behaviour as to not break compatibility.
Depends on pmbootstrap patch that sets PMBOOTSTRAP_CMD to argv[0]:
https://lists.sr.ht/~postmarketos/pmbootstrap-devel/patches/39995
sudo-ldap is providing cmd:sudo/sudo-virt.
Replace files from sudo-ldap to solve conflict about /etc/sudoers
Fixes#2032
[ci:skip-build]: already built successfully in CI
Previously this was set in the project settings, but according to the
GitLab documentation this can now be set using this file since GitLab
version 14.8. Keep it here to make sure it's version controlled as well.
Clayton Craft