We used to use this param when the MM systemd unit was vendored in
pmaports but it was dropped when we switched to the upstream unit. This
also sets the param in openrc installs.
Fixes#4194
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7840>
The pmb:gpu-accel option is deprecated in favour of pmb:drm. However, it
doesn't do anything when applied to packages that aren't UI packages
(base-ui packages aren't UI packages), so just remove it instead of
replacing it with the proper option.
[ci:skip-vercheck]: Doesn't affect resulting package, only read by
pmbootstrap during `init`.
Signed-off-by: Stefan Hansson <newbyte@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7847>
Previously the process was that once a branch is EOL, the
notification-commit was cherry-picked from the branch before.
However that makes less sense, since the package then doesn't go
through the same mass updates as pmaports master does, e.g. it still
referenced gitlab.com & -gtk3, and doesn't allow changes by contributors
other than the one cherry-picking it.
Adapted from c088d806ea25 ("main/postmarketos-upgrade-gtk3: new aport")
See https://gitlab.postmarketos.org/postmarketOS/pmaports/-/issues/4197.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7769>
I contacted Mark who confirmed that he is not likely to return to
contributing to postmarketOS any time soon and is okay with me
removing his maintainer line.
Signed-off-by: Stefan Hansson <newbyte@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7825>
This "size"/factor/percentage represents the total amount of
**uncompressed** data that is allowed to be written to the zram-backed
swap device. It is **not** the amount of RAM to use for zram swap (as I
had previously and erroneously thought.) What this means is that if we
set the percent to 50% on a device with 3GB of RAM then up to 1.5GB of
*uncompressed* data can be written to it, BUT since compression algos
usually do better than a ratio of 1:1... less than 1.5GB of RAM will
actually be occupied by this data when it is compressed.
A 1.5:1 compression ratio seems relatively safe to assume, even if we
use lz4 (which is less "good" at compressing than zstd), so I propose we
set the size to 150%. Some distros (PureOS) set this higher (200%), but
I think we should be somewhat conservative since we want to avoid any
thrashing in case the compression ratio at runtime ends up being less
than 2:1 for some reason.
This does set a limit of 50% for devices with >32GB of RAM, to
reduce overhead with using a larger amount of zram swap. The kernel
documentation for zram suggests there's a 0.1% overhead, so if we let
this amount get large then it could be tens or hundreds of MB of RAM
"wasted." The amount I chose is kinda arbitrary, I think this can be
improved later. At the very least, users can change this amount in the
deviceinfo variable.
Fixes#4250
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7754>
This is meant to replace zram-init. It's much simpler, since it only
sets up zram swap and doesn't try to do all the things that zram-init
does. This also lets us add additional logic, such as selecting
different default algorithms based on the runtime CPU arch and
conditionally applying sysctl settings that might be inappropriate when
*not* using zram swap.
To create zramstart, I took the zram-configurator, which reads config
from deviceinfo vars, and extended it to create the zram swap device.
zramstart and zramstop were inspired by what Fedora does. The sysctl
config is from the work done here:
https://source.puri.sm/Librem5/librem5-base/-/merge_requests/381
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7754>
* Set Co-Mainatiner as maintainer, if they exist
* Add me as co-maintainer of QEMU packages to fulfill main requirements
* Add people interested in maintainance to their packages
* device-google-snow now has no maintainer, if someone is interested,
please add yourself as maintainer, otherwise it has to be dropped
As we all know they are inactive nowadays, the maintainer variables
should reflect the reality who cares/is responsible about a package, and
inactive members are not. And waiting for a inactive maintainer 2 weeks
is just staling the MR.
Thanks for all the work Minecrell & Jenneron, and feel free to add
yourself again if you're back again.
[skip ci]: too many false positives :p
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7748>
So we can read the complete output in the logs. This was initially
done to avoid the output from being interrupted, and therfore easier
to read. However, it avoids kernel logs to be collected, which is an
important part of the tests, and necessary for debugging. So let dmesg
be as default.
Signed-off-by: Pablo Correa Gómez <pabloyoyoista@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7489>
Busybox su and login are not aware of PAM, so on a system
with linux-pam installed, they entirely ignore any rules.
These issues can be mitigated by removing the suid binary
that the symlinks point to and require, which is installed
by busybox-suid. Because busybox-suid handles more than su
and login, this commit replaces all the tools we use that
would be called through it.
Note that this does not remove Busybox su and login, as they
are in Busybox itself. This commit instead only removes the
suid interface that they would normally be called from.
See https://gitlab.alpinelinux.org/alpine/aports/-/issues/11730
for more information.
Signed-off-by: Aster Boese <asterboese@mailbox.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7724>
This is a workaround for https://github.com/flatpak/flatpak/issues/6449
By requiring that system time is sync'd with NTP before the flatpak
helper is started, we can make sure that system time is always greater
than the flathub.org repo gpg key creation time, and prevent the
helper/flatpak from creating broken repo config that requires manual
intervention to fix.
Fixes#3816
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7711>
It is true that Phosh originally was developed for the Librem 5,
but at this point that is more of a "fun fact" than relevant
information with Purism no longer funding Phosh development and
the Librem 5 losing prominence. Replace it with something more
descriptive.
Signed-off-by: Stefan Hansson <newbyte@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7704>
It has no other packages depending on it and _if_ somebody has _some_
use of it, it should be in Alpine.
This package hasn't been touched since the initial inclusion in 2019,
and also the upstream repo had it's last activity in 2017.
Rel: 322cec513c ("main/columbiad: new package (full screen launcher) (!364)")
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7695>
MTP transfers write files to the home folder of the user.
If no GID and UID are specified, uMTP-responder will use the GID/UID
under which it is running at the time of the file transfer.
This causes users to not be able to access the files on the device after transfering.
This patch adds a systemd generator that:
1) reads /etc/default_user, and appends config to
/etc/umtprd/umtprd.conf to set the MTP default user/group. If this
file doesn't exist, 10000:10000 is the fallback uid:gid.
2) installs this config to /run/umtprd/umptrd.conf
3) adds a unit override to /run for umtprd.service that runs the daemon
with this modified config
The generator is used instead of hardcoding a uid and gid in umtprd.conf
so that this can support immutable installs or situations where the
default UID/GID is not 10000.
Co-authored-by: Dylan Van Assche <dylan@postmarketos.org>
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7658>
