Flatpak pipelines fail ramdomly on v2025dev3

Background

The flatpak pipelines for v2025dev3 tend to fail randomly with something like

2024/08/12 01:14:54 ==== Recipe done ====
INFO:flatdeb:Committing org.apertis.hmi.Sdk-armhf-v2025dev3-debug.tar.gz to OSTree
fb90435d7e08e6e9514c01df8bb213d1cad989e9c8e6afedc1a59afa20b90953
21.58user 1.87system 0:23.90elapsed 98%CPU (0avgtext+0avgdata 15704maxresident)k
29280inputs+767160outputs (181major+26538minor)pagefaults 0swaps
INFO:flatdeb:Committing org.apertis.hmi.Sdk-armhf-v2025dev3-sources.tar.gz to OSTree

(ostree commit:208): GLib-WARNING **: 01:15:40.622: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: gzip decompression failed

(ostree commit:208): GLib-WARNING **: 01:15:40.623: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: gzip decompression failed

https://gitlab.apertis.org/infrastructure/apertis-flatpak-runtime/-/jobs/3355006

Reproducibility

How often the issue is hit when repeating the steps to reproduce and changing nothing?

Put the ✅ in the most appropriate entry:

1. always
2. ✅ often, but not always
3. rarely

Impact of bug

How severe is the bug? Does it render an image unbootable? Is it a security issue? Does it prevent specific applications from working? What is the impact? Does this bug affect a critical component? Does it cause something else to not work? How often is the bug likely to be found by a user? For example, every boot or once per year?

Outcomes

TBD

Management data

This section is for management only, it should be the last one in the description.

/cc @andrunko @em @Balasubramanian @sudarshan @wlozano

Phabricator link: https://phabricator.apertis.org/T10644