- Mar 03, 2025
-
-
[ci:skip-build]: already built successfully in CI
-
[ci:skip-build]: already built successfully in CI
-
pam_dump_runtime_dir isn't needed with systemd. if a user install this module, this might break with logind integration.. [ci:skip-build]: already built successfully in CI
-
As we compile package only for aarch64 Signed-off-by:
David Heidelberg <david@ixit.cz>
-
[ci:skip-build]: already built successfully in CI
-
(S805X) Tested on Xiaomi Mi TV Stick (S805Y). Signed-off-by:
Ferass El Hafidi <funderscore@postmarketos.org> [ci:skip-build]: already built successfully in CI
-
1. dependencies useful for all X11 DEs/WMs moved to x11 subpackage 2. add dmenu-based power key menu with options for shutdown, reboot, and screenshot 3. handle power and screenlock keys using i3 directly, instead of acpi/evtest 4. add mouse key emulation via Shift+keyboard-keys [ci:skip-build]: already built successfully in CI
-
- Mar 02, 2025
-
-
[ci:skip-build]: already built successfully in CI
-
- Mar 01, 2025
-
-
More detail in the included patch but tl;dr patches a dummy mmap function in the PCM audio driver that causes a kernel panic when used by pulse. [ci:skip-build]: already built successfully in CI
-
-
These kernel modules are now built-in. [ci:skip-build]: already built successfully in CI
-
-
pmbootstrap > 3.3.1 is stricter with the dependencies, it will only install packages that are in makedepends during builds. Before it also installed packages from depends. Add postmarketos-mvcfg to makedepends, as it gets used in build(). postmarketos-mvcfg will be removed in the future (see issue 3580), but let's unbreak the build first. Related: pmbootstrap issue 2574 [ci:skip-build]: already built successfully in CI
-
- Feb 28, 2025
-
-
Package auto-update authored
-
- Feb 27, 2025
-
-
-
Reverts 82a8d551 (device-nokia-n900: drop partition resize cmdline option (MR 6164)) since it seems resizing does not actually take place automatically, at least as far as the N900 is concerned [ci:skip-build]: already built successfully in CI
-
There are some notable changes: - systemd-journal-upload is now available, but not tested - pam files now live under `/usr/lib/pam.d`. users can easily override configuration by putting files under /etc/pam.d with the same name. - journalctl should now work for `wheel` groups without privilege esclation to root. ACLs' for /var/log/journal should hopefully be set correctly now. - /bin/udevadm /sbin/{init,udevd} are now provided by the APKBUILD itself - The split-usr backport lives now in the downstream release.
-
The current -systemd subpackage isn't getting installed due to the invalid install_if statement. As abuild's fork in pmOS for systemd specifies a default_systemd() and systemd() function, overriding it here isn't needed. The -systemd subpackage contains configuration for gnome-session in systemd mode. - By placing a file into systemd/user/gnome-session@phosh.target.d, we generate a valid gnome-session@phosh.target. - The first invokation of gnome-session by phosh-session includes the arg `--session phosh`. When gnome-session sees a running systemd user manager via dbus, it will signal to systemd to start `gnome-session@phosh.target`. As we switched to tinydm/autologin for phosh on systemd-edge, this will only work when autologin also tries to load pam_systemd.so. [ci:skip-build]: already built successfully in CI
-
Package auto-update authored
-
- Feb 26, 2025
-
-
Package auto-update authored
-
- Feb 25, 2025
-
-
Package auto-update authored
-
- Feb 24, 2025
-
-
Package auto-update authored
-
- Feb 23, 2025
-
-
David Wronek authored
It seems like these packages have been missed during the community move. Fixes: postmarketOS/pmaports!6210 Signed-off-by:
David Wronek <david@mainlining.org> [ci:skip-vercheck]: no changes to packages
-
-
Keep symlinks for mdt around until the kernel is using the new paths.
-
As required by new kernel version due to different paths.
-
Update the close-to-mainline linux kernel fork for the MSM8930 processor to 6.13.0. According to wctrl, this also makes WiFi work, if you place the drivers in the initramfs. Haven't tried that. [ci:skip-build]: already built successfully in CI
-
kded currently doesn't start with the session, but when I rename the systemd unit file to plasma-kded6.service, it starts automatically. [ci:skip-build]: already built successfully in CI
-
1. disable USB-gadget as this device has a UART available in HW 2. disable the fb detection (used for pbsplash), as I am not progressing with getting HDMI working. Signed-off-by:
Robert Eckelmann <longnoserob@postmarketos.org> [ci:skip-build]: already built successfully in CI
-
[ci:skip-build]: already built successfully in CI
-
Signed-off-by:
Ferass El Hafidi <funderscore@postmarketos.org> [ci:skip-build]: already built successfully in CI
-
Since we have aports-qa-bot now set up to ping maintainers, let's make it explicit that I maintain these packages. Clean up CODEOWNERS as well for my entries which anyways contain my username which is not used on gitlab.p.o. [ci:skip-vercheck] # even though Maintainer line is embedded in .apk, it doesn't make sense to mass rebuild these packages just for that. [ci:ignore-count] [ci:skip-build]: already built successfully in CI
-
And add Maintainer line for myself.
-
And add Maintainer line for myself.
-
Jens Reidel authored
Signed-off-by:
Jens Reidel <adrian@travitia.xyz> [ci:skip-build]: already built successfully in CI
-
- Feb 22, 2025
-
-
Luca Weiss authored
The kernel doesn't compile anymore due to updated toolchain: scripts/Makefile.lib:414: *** prerequisites cannot be defined in recipes. Stop. make[3]: *** [../scripts/Makefile.modbuiltin:54: techpack/audio/dsp] Error 2 Remove it since mainline kernel is working better anyways.
-
Luca Weiss authored
Also fold the nonfree-firmware subpackage into the main package as per updated packaging guidelines since this APKBUILD was created.
-
-
- Feb 21, 2025
-
-
Clayton Craft authored
I evaluated using systemd/zram-generator but decided against it for the following reasons: 1) it was more difficult to configure using the existing deviceinfo var we have for zram_pct, this meant that we would ultimately couldn't have a consistent way to configure zram stuff for all supported init systems 2) it's a Rust app, and was failing to build in CI for armv7, riscv64, and armhf with some weird qemu crashes, failed tests, etc 3) zram-init Just Works, upstream ships a unit file for it so they support running under systemd already [ci:skip-build]: already built successfully in CI
-