which are probably too experimental to ask Alpine to carry them, while being
very helpful for devices that pmOS targets. The explicit goal is to help
Libcamera development and drop the fork again.
For the dma heaps permissions see the ongoing debate in
https://lore.kernel.org/all/bb372250-e8b8-4458-bc99-dd8365b06991@redhat.com/
It's possible that Libcamera will switch to another solution in a future
release or that memory accounting issues around dma heaps will need to
get fixed in the kernel before the permissions can be set by default by
distros.
Regarding `libcamera: simple:` patches:
- 0001-0003 can likely be dropped once the Libcamera SoftISP gains
support for raw (bayer) streams passthrough (on top of converting to
RGB or YUV formats).
- 0004 will likely be needed until Megi downstream patches for the
Pinephone get improved/upstreamed and Libcamera adopted accordingly.
With these patches libcamera and pipewire based applications should work
on the Librem5, Pinephone and - hopefully soon - devices like the OP6.
See https://gitlab.com/postmarketOS/pmaports/-/merge_requests/5162 for
more context.
[ci:skip-build]: already built successfully in CI
This package is dropped from Alpine and I don't think we need it..?
Signed-off-by: Caleb Connolly <caleb@postmarketos.org>
[ci:skip-build]: already built successfully in CI
Instead of just disabling it on armv7, we can only build it on aarch64
given that the patches applied only are relevant on that architecture
anyway.
[ci:skip-vercheck]: No need to increment pkgrel when only changing
architectures.
[ci:skip-build]: already built successfully in CI
Upgrade to upstrem version 3.24.37-2pureos4.
Apply an explicit list of patches from the PureOS upstream sources.
These upstream patches were skipped in the previous version and are now
applied:
pureos/adaptive/Add-the-view-sidebar-symbolic-icon.patch
pureos/events-Compress-touch-update-events.patch
Remove upstreamed gdk-wayland-Track-last-touch-serial-on-seat.patch.
Add a fixed version of 'Port file chooser to phones' patch:
https://source.puri.sm/Librem5/debs/gtk/-/blob/pureos/byzantium/debian/patches/pureos/adaptive/Port-file-chooser-to-phones.patch
The original did not apply cleanly and was disabled by PureOS upstream:
f7dfd6e7b6
[ci:skip-build] already built successfully in CI
Something seems to have gone wrong in our rebuild and sync of pulseaudio
with alpine upstream. And user feedback points that building armv7 devices
with LTO is actually broken in our builders. In alpine, they enabled lto
in pulseaudio very long ago (f46174365b219fe431890df3df7e7dc488c9451e 08-09-22)
and nobody as complained so far. Since it's not really a phone-specific package,
one would hope that more people upstream would have noticed if it were broken
there. Since nobody has, we assume this is a downstream problem, and just
unconditionally disable lto in our build. We hope this will be just a temporary
workaround, until the patches that prompted the fork are no longer needed, and
we can simply use upstream pulseaudio, that shouldn't be broken.
Fixes#2368
[ci:skip-build] already built successfully in CI
The x86 devicetree patch is included in latest upstream version, which
is already packaged in alpine.
[ci:skip-build]: already built successfully in CI
This old package had a pre-deinstall script to remove the necessary Sxmo
daemons. We move those daemon management to the -dwm and -sway dedicated
postmarketos packages.
The problem is that apk can eventually install/upgrade the -dwm or -sway
package before removing sxmo-common. This cause a deactivation of the
daemons.
To prevent this, we add back an empty sxmo-common to take place of the
old one. This one does not contain the deinstall scripts. We will
remove this in two stable release.
This package originally existed to carry local patches not included
upstream. That is not longer the case, and using the Alpine package
works fine.
Additionally, this package tends to lag behind; Alpine currently ships
2.8.6.
References: https://gitlab.com/postmarketOS/pmaports/-/issues/1611
[ci:skip-build] already built successfully in CI
The forked version includes some new API, but the maintainer wants to
have things as-close-as-possible to upstream. Since APK mostly keeps track
of libraries versions, having the same API version as upstream (there's no
stable ABI for mutter), makes it possible for APK to confuse with non-mobile
mutter. By having an unrealistic API version, we make sure this does not happen
to us.
Fixes#2127
I don't see any packages in pmaports that actually depend on dhcpcd, and
it hasn't been updated in 3 years... (upstream is at version 10.0.0
now...)
NOTE by ollieparanoid: networkmanager in Alpine used dhcpcd before, so
it was part of our default network stack. But that isn't the case
anymore since 2020:
db03cedea9
