Always make sure openssh server w/ PAM support is installed. This also
drops an implicit dependency on `openssh-client`, this was pulled in
previously by `depends="openssh"`.

fixes #3570

This allows safer installation of packages, since the upgrade doesn't
fail with a half-installed system if the download fails while installing.

Note that this will only take effect when Alpine upgrades to apk-tools 3.

Closes: #3383
See: https://gitlab.alpinelinux.org/alpine/apk-tools/-/issues/10891

This allows re-using it elsewhere, like in pmos-base-systemd

logbookd isn't needed on systemd, so only depend on it when using openrc

[ci:skip-build]: already built successfully in CI

achill (fossdd) authored 3 months ago and Alexey Minnekhanov committed 2 months ago

For example systemd makes use of the color for the presentation color
when showing the OS name on the console

Raymond Hackley authored 8 months ago and Oliver Smith committed 3 months ago

[ci:skip-build]: already built successfully in CI

Split -nofde into a separate package to resolve the cyclic depenency:
postmarketos-base -> postmarketos-initramfs -> postmarketos-base-nofde

Fixes: issue 3236
[ci:skip-build]: already built successfully in CI

Fix the following error during "pmbootstrap install":

  ERROR: unable to select packages:
    sudo-1.9.16_p1-r1:
      conflicts: doas-sudo-shim-0.1.1-r1[cmd:sudo=1.9.16_p1-r1]
      breaks: doas-sudo-shim-0.1.1-r1[!sudo]
      satisfies: postmarketos-base-38-r0[sudo-virt]
                 postmarketos-base-nofde-38-r0[sudo-virt]
    doas-sudo-shim-0.1.1-r1:
      conflicts: sudo-1.9.16_p1-r1[cmd:sudo=0.1.1-r1]
      satisfies: postmarketos-base-doas-38-r0[doas-sudo-shim]
                 postmarketos-base-38-r0[sudo-virt]
                 postmarketos-base-nofde-38-r0[sudo-virt]

How the error gets triggered:
* postmarketos-base depends on sudo-virt. During "pmbootstrap install",
  pmbootstrap has to resolve this to a sudo implementation (sudo, doas,
  ...).
* pmbootstrap does this by looking at the packages that get installed
  at the same time. Before this patch we did not install doas-sudo-shim
  directly through _pmb_recommends, only indirectly through a
  postmarketos-base-doas subpackage that pulls doas-sudo-shim in via
  install_if.
* pmbootstrap cannot look at install_if as it resolves dependencies,
  so it has to pick one and goes for "sudo".
* pmbootstrap tells apk to install a list of packages including "sudo",
  and because apk also resolves install_if correctly, the solver fails
  at the conflict between "doas-sudo-shim" and "sudo". (This only fails
  since apk-tools-static 2.14.6-r0, apparently beforehand apk just
  installed "doas-sudo-shim" in this scenario.)

Teaching pmbootstrap to look at install_if while resolving packages
would be one way to fix this. But it would be a lot of effort, not
feasible to quickly stop the problem at hand that breaks "pmbootstrap
install" for all edge installs. IMHO it is not worth implementing this
at all in pmbootstrap, as it is just supposed to do some more or less
basic package resolving until apk takes over and does it properly.

Put doas-sudo-shim in _pmb_recommends so pmbootstrap knows that this is
the sudo implementation we want without looking at install_if.

Remove the now obsolete postmarketos-base-doas subpackage. This will
lead to doas-sudo-shim getting removed for old installations on upgrade,
but it can easily be installed back (doas add doas-sudo-shim). I'll make
an edge post about it and put it in the v24.12 release notes. If we
don't remove it here, we would need to keep this legacy subpackage
around forever and I'd rather avoid that to reduce maintenance effort.

Another alternative to this was removing sudo-virt from depends="". But
that would lead to sudo getting uninstalled for users upgrading from
old releases from before we had doas in pmb_recommends, so I've decided
against it.

Fixes: pmaports issue 3340

Anjan Momi authored 4 months ago and Clayton Craft committed 4 months ago

closes #3294

Fixes issues with games on proton and steam failing to launch.

https://archlinux.org/news/increasing-the-default-vmmax_map_count-value/
[ci:skip-build]: already built successfully in CI

Since either url or source change

Jakko authored 6 months ago and Pablo Correa Gomez committed 6 months ago

Since mesa upgrade from 24.0.9 to 24.1.2 PulseAudio Volume Control
"pavucontrol" needs "mesa-gles" to start on some devices. There is no
direct dependency, however. Instead it's "libepoxy", a Direct Rendering
Manager runtime library, that calls the necessary mesa library.

Other than user interface MATE, where e.g. "mate-session-manager" draws
in "mesa-gles", and other than mesa packages like "mesa-gl" that gets drawn
in by e.g. "xorg-server", there is no direct connection between Xfce4 and
"mesa-gles".

Adding package "mesa-gles" to "postmarketos-base-mesa" is a straightforward
fix for this issue.

Fixes #3042
[ci:skip-build]: already built successfully in CI

achill (fossdd) authored 6 months ago and Pablo Correa Gomez committed 6 months ago

This reproduces the same bahaviour as with sudo. And well, the user is
root anyways.

Fixes #3188
[ci:skip-build]: already built successfully in CI

Aster Boese authored 6 months ago and Pablo Correa Gomez committed 6 months ago

[ci:skip-build]: already built successfully in CI

From https://www.man7.org/linux/man-pages/man5/os-release.5.html:

        /usr/lib/os-release is the recommended place to store OS release
        information as of vendor trees. /etc/os-release should be a
        relative symlink to /usr/lib/os-release, to provide
        compatibility with applications only looking at /etc/. A
        relative symlink instead of an symlink is necessary to avoid
        breaking the link in a chroot initrd environment such as dracut.
[ci:skip-build]: already built successfully in CI

Raymond Hackley authored 8 months ago and Pablo Correa Gomez committed 8 months ago

Fixes #2951

[ci:skip-build]: already built successfully in CI

Jane Rachinger authored 9 months ago and Clayton Craft committed 8 months ago

Co-authored-by: Clayton Craft <clayton@craftyguy.net>

Caleb Connolly authored 11 months ago and Clayton Craft committed 9 months ago

We plan to make a lot of changes to the initramfs which will require
incresaing the size. There are some devices that have literally no free
space for this, so make a -minimal initramfs fork that can continue to
support those while we update the regular initramfs.

Signed-off-by: Caleb Connolly <caleb@postmarketos.org>

All these config update are there since 2020. Having them there
serves no purpose, apart from increasing packaging complexity and
have some unnecessary files under /etc

See pmbootstrap!2304

[ci:skip-build]: already built successfully in CI

Pablo Correa Gomez authored 1 year ago and Newbyte committed 1 year ago

This was enabled in the "default" runlevel during upgrades, which is an
error, since it depends on bootmisc, which is in "boot" runlevel

Fixes #2473

[ci:skip-build]: Already built successfully in CI.

And enable it by default, since it's a sensible thing to do.

This makes the bootmisc config file unnecessary, since it was only
used before to make sure that /tmp was wiped on every boot.

Mounting /tmp as a tmpfs will be skipped if:
* The user or maintainer configured deviceinfo_tmp_as_tmpfs_size=0
* If they didn't but the device has less than 2GB of RAM
* And in any case, if it is already mounted, to respect users that
  might have it in /etc/fstab

The options for mounting /tmp has been copied from my local debian
tmp.mount service. The only real difference is that we are mounting it
after /etc/fstab, and they do so before.

Fixes #2233

Ensure that we don't have two logging daemons running!

Signed-off-by: Caleb Connolly <caleb@connolly.tech>

Martijn Braam authored 1 year ago and Clayton Craft committed 1 year ago

Use logbookd to replace the busybox in-memory logger. The default
configuration of logbookd still logs in-memory but writes out the log on
shutdown or manual trigger.

The logread command is also replaced by a drop-in replacement for the
busybox tool.

Clayton Craft authored 1 year ago and Oliver Smith committed 1 year ago

The post-upgrade script in pmos-base isn't symlinked to the post-install
script, so zram-init wasn't being enabled on systems that upgraded to
the pmos-base version that intro'd this feature. I think this should
have been enabled by default on upgraded systems. There's a deviceinfo
toggle for it, so users who won't want to use this can set that var to
disable it, in that case having the service enabled is basically a
no-op.

Update by Oliver: add a comment to mention the deviceinfo variable

[ci:skip-build]: already built successfully in CI

Pablo Correa Gomez authored 1 year ago and Oliver Smith committed 1 year ago

This greatly simplifies the trigger, since now we can monitor a
directory.

In addition, depend on the latest devicepkg-utils

Pablo Correa Gomez authored 1 year ago and Oliver Smith committed 1 year ago

So that old installations that run setup-timezone without "-i" do not
need to execute manual steps to get sensible timezone configurations.

See https://gitlab.com/postmarketOS/pmaports/-/issues/2168 for more context

Fixes #2168
[ci:skip-build]: already built successfully in CI

Raymond Hackley authored 2 years ago and Oliver Smith committed 1 year ago

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

Clayton Craft authored 2 years ago and Pablo Correa Gomez committed 2 years ago

Changes the dependency from pmos-mkinitfs to pmos-initramfs, so now the
dependency chain for boot config packages is:

    base -> postmarketos-initramfs -> postmarketos-mkinitfs -> boot-deploy

Sorting dependencies this way makes sense because "base" just needs an
initramfs, it doesn't care about the implementation (that currently uses
"postmarketos-mkinitfs.")

[ci:ignore-count]
[ci:skip-build] already successfully built in CI

Anton Bambura authored 2 years ago and Oliver Smith committed 2 years ago

Related: discussion in MR 3791
[ci:skip-build]: already built successfully in CI

Clayton Craft authored 2 years ago and Newbyte committed 2 years ago

This installs zram-init and sets it to start on boot for all
devices/UIs. The included conf.d/zram-init also allows diabling using
zram swap or overriding the size by using a deviceinfo var.

I did an analysis of the pmos base install size with the 'none' UI
selected, after depending on zram-init, and the following new package is
installed:
        zram-init-11.1-r1 installed size: 40 KiB

These packages are dependencies of zram-init, however they are already
installed in the base image (with 'none' UI) so they are not counted
above:
        util-linux-misc-2.38.1-r0 installed size: 6816 KiB
        e2fsprogs-extra-1.46.5-r4 installed size: 1324 KiB

So this seems like a very small price to pay for the benefit of not
making the logic/implementation more complicated than this.

     * Starting busybox syslog ... [ ok ]
    ssh-keygen: generating new host keys: RSA ECDSA ED25519
     * Starting sshd ... [ ok ]
    zram swap: activating with size: 243 MB
     * Loading zram module...
     [ ok ]
     * Swap->zram0
     [ ok ]
     * Starting local ... [ ok ]

This change introduces one new deviceinfo variable:
deviceinfo_zram_swap_pct: percentage of RAM to use for zram swap

Default percentages if the second var is unset are explained in the
zram-init file this commit adds. A value of 0 disables zram swap.

fixes #1133