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

Nikita Travkin authored 5 months ago and Newbyte committed 5 months ago

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

Barnabás Czémán authored 6 months ago and Robert Eckelmann committed 5 months ago

Switch to lk2nd-msm8974 because separate appended
dtb image build is not needed anymore.

Barnabás Czémán authored 6 months ago and Robert Eckelmann committed 5 months ago

Custom lk2nd build for motorla-ali is not needed anymore.

Barnabás Czémán authored 6 months ago and Robert Eckelmann committed 5 months ago

Remove old lk2nd-msm8953 package in favor of lk2nd package.

Barnabás Czémán authored 6 months ago and Robert Eckelmann committed 5 months ago

lk2nd 19.0 supports new platforms and simplifies image formats.

Oliver Smith authored 6 months ago and Newbyte committed 5 months ago

Follow up to MR 5562, which introduced category:librem5. Add the related
option, so CI actually enforces this category for the Librem 5.

[ci:skip-vercheck]: no need to rebuild for this

Oliver Smith authored 6 months ago and Newbyte committed 5 months ago

Use check=True instead of running check_returncode() afterwards, it has
the same effect and is shorter.

Oliver Smith authored 6 months ago and Newbyte committed 5 months ago

pmbootstrap used to exit with 0 if "pmbootstrap lint" failed. This was
the case in 2.3.x too, but I assumed this was a regression and fixed it
recently in pmbootstrap MR 2398.

It turns out that the CI code relied on this assumption, it captured the
output of "pmbootstrap lint", and only after it is done it checks if the
output wasn't empty and prints it in that case followed by exit 1.

Now that pmbootstrap actually exits with 1, CI already fails at
"common.run_pmbootstrap" and doesn't get to the part where it would be
printed.

I think "exit 1" on error is actually the right thing to do in
pmbootstrap, so I'll leave that in. Adjust CI to just run "pmbootstrap
lint", removing the additional output capture logic that isn't used
anywhere besides here. This also has the advantage that we get the
output "live", without buffering it completely first.

Jakko authored 5 months ago and Clayton Craft committed 5 months ago

Qemu by default starts a GTK window in VGA resolution 640x480. The content
adapts to this resolution, thus X11 shows up in resolution 640x480 as well.

This resolution causes some handling issues. In Xfce4 the shutdown button of
the menu isn't reachable. Even worse in MATE, where the "Apply" button for
changing the resolution is out of the screen, making it difficult to change
the resolution.

The default resolution for X11 can be set by a config file. The Qemu GTK
window resolution remains independently at default 640x480. Setting the X11
resolution to default 800x600 mitigates the issue: Most of the screen content
becomes accessible while font size and button sizes are still large enough.
From this point the user can adjust the resolutions of the Qemu GTK window
and X11 content as desired.
[ci:skip-build]: already built successfully in CI

Luca Weiss authored 5 months ago and Clayton Craft committed 5 months ago

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

This adds the wlr and GTK portal backends so that apps using portals will work OOTB.

The GTK backend is added because the wlr backend does not provide some essential portals, e.g. for camera
[ci:skip-build]: already built successfully in CI

fixes #3251

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

This reverts 62214096, which basically broke installkenrel because
the kernel build system is hardcoded to look for installkernel in /
sbin/installkernel.

We'll have to move then once usr merge is complete and the symlink is
created for /sbin
[ci:skip-build]: already built successfully in CI

Luca Weiss authored 5 months ago and Newbyte committed 5 months ago

Some kconfig changes to reduce kernel size to avoid conflict of 0x8000
(kernel load address) + uncompressed kernel size (arch/arm/boot/Image) +
compressed kernel size (arch/arm/boot/zImage) being bigger than
0x1e00000 (tags address).

This causes mostly silent boot failures, with CONFIG_DEBUG_LL messages
such as "no ATAGS support: can't continue" or "Error: invalid dtb and
unrecognized/unsupported machine ID" can be seen on UART, though they're
not very clear that the kernel image is essentially too big for what lk
is setting up.

Manual kconfig changes:
* Convert some =y to =m to reduce kernel size, mostly NFS_FS and CIFS
  since those are quite big and there's no point in having them
  built-in.
* Disable EXT2_FS & EXT3_FS - handled by EXT4 driver
* Disable PCI - unused
[ci:skip-build]: already built successfully in CI

Update the bot email address, and don't enable the script for local CI
since it relies on protected GitLab CI variables. This could be fixed in
the future by safely handling these not being available.

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

Per the flatpak manpage, repos can be configured OOTB by dropping config under /etc/flatpak/remotes.d. Using the install script requires doing stuff over the internet, which may not always work at image build time. By using the drop-in file, we avoid having to connect to flathub.

The manpage only mentions /etc/flatpak, and nothing about /usr ...

Clayton Craft authored 5 months ago and Luca Weiss committed 5 months ago

Quite a messy upgrade due to changes in both abuild and in the upstream
gcc APKBUILD breaking various things. Pmbootstrap also seems to
misbehave in GitLab CI making it difficult to validate.

Manual fixups:
* Set !tracedeps - changed behavior in abuild
* Manually add "so:" dependencies to avoid issues with !tracedeps set
  (becomes obvious with crossdirect)
* Add back makedepends="$makedepends_build $makedepends_host"
* Disable move of some files into usr/lib to avoid
  ERROR: gcc-aarch64-14.2.0-r4: trying to overwrite usr/lib/libgcc_s.so.1 owned by libgcc-14.2.0-r4.

[ci:skip-build] # pmbootstrap bugs will prohibit this from building
                # anyways, don't even attempt

Co-developed-by: Luca Weiss <luca@lucaweiss.eu>

Jens Reidel authored 5 months ago and Newbyte committed 5 months ago

And re-enable riscv64 as the latest commits have added
support for riscv64.

Signed-off-by: Jens Reidel <adrian@travitia.xyz>
[ci:skip-build]: already built successfully in CI

Clayton Craft authored 5 months ago and Newbyte committed 5 months ago

Technically this option can be configured in the Gitlab UI, but I spent
about 3 hours debugging a CI failure caused by it being too low and
I don't want to risk forgetting this can happen later if/when someone
decides to lower it in the UI. By setting it here, we can have some
context/history about why.

This fixes the CI in !5688

Also see:
https://docs.gitlab.com/17.4/ee/user/project/repository/monorepos/index.html#shallow-cloning
[ci:skip-build]: already built successfully in CI

Clayton Craft authored 5 months ago and Newbyte committed 5 months ago

I was confused for a while about why the SHA printed by CI differed from
the actual upstream/master SHA:

     commit upstream/master: f822b7ee0d06f05ff6d2eb37bcf4a1825569be692
     real upstream/master: 822b7ee0

Barnabás Czémán authored 6 months ago and Newbyte committed 5 months ago

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

Barnabás Czémán authored 6 months ago and Newbyte committed 5 months ago

With the new changes in lk2nd that allow us to support extlinux.conf,
we can now generate image that would be generic to these devices.

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

Luca Weiss authored 5 months ago and Newbyte committed 5 months ago

mozjs102-dev has been removed from aports in September 2023[0] so
obviously noone has ever run this in the last year. Remove it.

[0] https://gitlab.alpinelinux.org/alpine/aports/-/commit/14107fd2b47f1ab899b0ca9e525b8970f1e1f4c9
[ci:skip-build]: already built successfully in CI

Luca Weiss authored 5 months ago and Newbyte committed 5 months ago

Prepare to remove the gnome-shell-extension-pinenote package.

Luca Weiss authored 5 months ago and Newbyte committed 5 months ago

The package was renamed/replaced in Alpine with:
https://gitlab.alpinelinux.org/alpine/aports/-/commit/6f4fa0525cecbd37a6a9d49c64e545348f521ed7

Luca Weiss authored 5 months ago and Clayton Craft committed 5 months ago

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

Richard Acayan authored 5 months ago and Pablo Correa Gomez committed 5 months ago

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

Include Qualcomm display subsystem and Adreno GPU driver, along
with panel driver into initramfs.

And mark devices as GPU accelerated to allow using all the UIs.

This release has several little but neat fixes not really worth
mentioning, but most notable features are:

* Xiaomi Mi PAD 4 and PLUS (clover) *both* now have proper panel
  driver and full GPU support. On par with other our devices now.
  Thanks to @kubntd for code and @barni2000 for testing !
* ath10k wlan no-msa-indication hack was dropped in favor of
  solution that was accepted upstream.
* Adreno 5xx preemption fixes were also included.

Jens Reidel authored 5 months ago and Pablo Correa Gomez committed 5 months ago

Signed-off-by: Jens Reidel <adrian@travitia.xyz>
[ci:skip-vercheck]

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

Jens Reidel authored 5 months ago and Pablo Correa Gomez committed 5 months ago

Signed-off-by: Jens Reidel <adrian@travitia.xyz>