This still comes from the aports hook, where we want to avoid too large patches,
but in pmaports we have big kernel config files that might exceed the
configured 256 kiB limit.
Currently the following files exceed that limit and used git commit
--no-verify to overcome the error (or didn't configure git hooks):
260K ./device/community/linux-postmarketos-qcom-laptop/config-postmarketos-qcom-laptop.aarch64
268K ./main/postmarketos-bootsplash/OpenSans-Regular.svg
336K ./device/downstream/linux-amazon-checkers/0003-Add-missing-kconfig-files.patch
376K ./device/downstream/linux-amazon-austin/silence-power-logspam.patch
Alternatively we can increase the file limit, but i'm not sure what that
solves.
In future for Alpine, I want to move the check to abuild's internal
linting, which makes it visible for all APKBUILDs, consistent with
other of abuild's linters and also shows up on CI.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7603>
Calls are broken for the Librem 5 with pipewire. Switch to pulseaudio
again until this is resolved by depending on
postmarketosbase-ui-audio-pulseaudio and pulseaudio<9990. The later is
needed as otherwise we get a conflict with pipewire-pulse:
ERROR: unable to select packages:
pipewire-pulse-9991.4.9-r1:
breaks: postmarketos-base-ui-audio-pulseaudio-42-r0[!pipewire-pulse]
satisfies: device-purism-librem5-9-r6[pulseaudio>17]
gnome-settings-daemon-99948.1-r3[pulseaudio]
postmarketos-base-ui-audio-pulseaudio-42-r0[pulseaudio]
That pulseaudio<9990 is needed is not great, but doing it like this
inside the device package is the best way to ensure this doesn't affect
any other devices for now, with the intention to have this change
backported to v25.12 before we announce the release. I've created issue
4187 to discuss how to improve the pulseaudio/pipewire packaging in
general so this isn't necessary in the future.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7619>
Compatibility with distros like NixOS that do not use Filesystem
Hierarchy Standard was improved. This should not affect the behavior
in postmarketOS.
Additionally a systemd target file was added.
Changelog:
- openrc: Adopt customizable binary path
- systemd: add target file
- Improve compatibility with non-FHS systems
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7607>
Else systemd/meson may try to generate it at build time, which doesn't
work when the host kernel is a different arch than the target.
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
This builds from upstream now.
- tests are re-enabled
- disable BTF support / drop vmlinux.h dependency, enabling bpf is
enough for mkosi/testing stuff, and getting a sane vmlinux.h that
systemd can compile with seems to be "complicated."
- armhf is re-enabled since we don't enable BTF anymore
- workaround stage0 linking failing on riscv64 by enabling tests
- increase test timeout for main pkg, because running in qemu is slow
- a lot more dependencies are explicitly listed now, because they are
dlopened and abuild doesn't know how to detect these
- meson build options re-arranged / cleaned up (some of these are
implicitly disabled by using -Dlibc=musl)
- tests are skipped for archs that we build in CI/bpo that don't have
native hw, since ~13 of them fail for unknown (or timeout) reasons. 2
of them time out after >1200 seconds and 11 fail for mysterious
reasons.
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7584>
Just pull in postmarketos-artwork-wallpapers-gnome which provides a
gschema override that is updated when the artwork package gets updated -
and won't break every so often.
Usually that package is pulled in via an "install_if" with
postmarketos-base-ui-gnome but since we just want the artwork
subpackage, depending on base-ui-gnome would be quite much and probably
not what we want for Lomiri.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7593>
This is device-agnostic, and allows to not depend on a package that
might end up in alpine in the future. In the process, also remove the
unnecessary postmarketos-test dependency in makedepends. That is just
an empty package.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7553>
This will be removed from unl0kr in the following commits, since at
some point it might be that unl0kr is not packaged in postmarketOS,
and this is a completely device-agnostic test, which is what this
package is for.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7553>
Since this was introduced, we no longer create "initramfs-extra"
unconditionally. So the "extra" files will be included in the
initramfs anyway. In addition, to be able to test the initramfs-extra
split for devices that need it, we require:
* To have one of those devices available for test.
* To modify our test setup to pass a rootfs that can be mounted.
Both are long into the future, if they will ever materialize. So let's
remove this, reducing the complexity.
Signed-off-by: Pablo Correa Gómez <pabloyoyoista@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7553>
Changes are roughly:
- Rebase on-top of 6.12.62
- Add isa1200 driver (from exynos4), and use it on manta (@lat3st)
- Add camera flash for manta (@lat3st)
- Improve manta audio driver to decrease CPU load (@alexmrqt)
- Fix wacom w9000 pen being always active unless inserted (@eisenbahnfan)
- Drop a pm_domain hack, and instead make exynos5 subcmu driver wait
for pm_domain to probe first (@eisenbahnfan)
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7582>
Apparently the user slice and root slice weren't being configured
correctly and oomd was not stepping in during high swap pressure events
before the kernel oom killer showed up to the party. This (hopefully)
properly configures systemd-oomd now... The configuration was inspired
by Fedora.
https://fedoraproject.org/wiki/Changes/EnableSystemdOomd
I used the test in that wiki page to confirm it's now properly configured:
$ systemd-run --user tail /dev/zero
$ journalctl -f
...
systemd[1081]: Started [systemd-run] /usr/bin/tail /dev/zero.
systemd-oomd[517]: Considered 79 cgroups for killing, top candidates were:
systemd-oomd[517]: Path: /user.slice/user-10000.slice/user@10000.service/app.slice/run-p5146-i5147.service
systemd-oomd[517]: Swap Usage: 4.6G
systemd-oomd[517]: Killed /user.slice/user-10000.slice/user@10000.service/app.slice/run-p5146-i5147.service due to memory used (2458>
systemd[1081]: run-p5146-i5147.service: systemd-oomd killed 1 process(es) in this unit.
systemd[1081]: run-p5146-i5147.service: Main process exited, code=killed, status=9/KILL
systemd[1081]: run-p5146-i5147.service: Failed with result 'oom-kill'.
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7556>
