Fixes podman issue
Error: Error reading blob sha256:4bb4a44c73af78e20e3d4c36bc1ce95b4b77a546f11a65babf752f869f1ca655:
open /var/lib/containers/storage/vfs/dir/9b8cfd27e86ef18db67fbda7d61d72046f3f5d8ad312655713d4cd8b065c80cd/usr/bin/staprun: permission denied
Related to https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/1247
We were facing this CI build failure error
[573/879] Linking target panels/online-accounts/gnome-control-center-goa-helper
FAILED: panels/online-accounts/gnome-control-center-goa-helper
cc -o panels/online-accounts/gnome-control-center-goa-helper panels/online-accounts/gnome-control-center-goa-helper.p/gnome-control-center-goa-helper.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,--start-group /usr/lib64/libgoa-backend-1.0.so /usr/lib64/libgoa-1.0.so /usr/lib64/libgtk-3.so /usr/lib64/libgdk-3.so /usr/lib64/libz.so /usr/lib64/libatk-1.0.so /usr/lib64/libpangocairo-1.0.so /usr/lib64/libharfbuzz.so /usr/lib64/libgio-2.0.so /usr/lib64/libgdk_pixbuf-2.0.so /usr/lib64/libcairo-gobject.so /usr/lib64/libpango-1.0.so /usr/lib64/libcairo.so /usr/lib64/libglib-2.0.so /usr/lib64/libgobject-2.0.so -Wl,--end-group
/usr/bin/ld: /usr/lib64/libtracker-sparql-3.0.so.0: undefined reference to `g_assertion_message_cmpint'
collect2: error: ld returned 1 exit status
g_assertion_message_cmpint is available in newer glib than what's in
our container image.
Since "builddep" is part of dnf5-plugins in DNF5.
See https://gitlab.gnome.org/GNOME/gnome-control-center/-/jobs/2933787
Unknown argument "builddep" for command "dnf5". Add "--help" for more information about the arguments.
$ echo "== Installing =="
== Installing ==
$ ninja -C _build install
ninja: Entering directory `_build'
ninja: fatal: chdir to '_build' - No such file or directory
Cleaning up project directory and file based variables 00:02
ERROR: Job failed: exit code 1
libadwaita 1.4 depends on appstream, and builds have
been failing because the subproject fails to build.
This commit adds appstream as a dependency so that
the libadwaita subproject can build without issues.
We also bump FDO_DISTRIBUTION_TAG to rebuild the image.
So that the "Finalizing foo, but it still has children left" message is
not truncated. This commit will be reverted when GTK is new enough in
our image.
Bump the version of the CI image to force a rebuild. This should bring
us a newer version of Mesa that would fix problems running GTK4 with
Xvfb as a display server:
libEGL fatal: did not find extension DRI_Mesa version 1
Closes: #2397
This was missing out the `polkit-autogen` file, so the flatpak build was
failing because of that. Fix this by removing the copying phase and use
the correct manifest path directly instead.
The gnome-runtime-images have been recently migrated to Quay. This is already reflected in the template.
Please note this MR has been created semi-automatically. If it doesn't make sense, feel free to close it.
The panel supports 2G/3G/4G GSM/LTE modems. CDMA2000 Modems are not supported.
If a supported modem is present, the panel will be shown and the modem will be
handled, else, network-panel shall manage the modem as it did in the past.
If more than one modem with data enabled is present, the user is allowed to set
priority of one SIM over the other (the priority is for SIM, not modem).
Fixes https://gitlab.gnome.org/GNOME/gnome-control-center/issues/132
Instead of building the image on a schedule, use a user-incrementable
tag and try to build the image on each pipeline.
If the image tag does not exist, a new one is built and pushed.
If its already built the job is a no-op and the existing image
is used.
The code that uses Grilo to fetch the user's Flickr photos isn't
actually used by the Background panel, to the extent that the final
binary doesn't even link against Grilo. Getting rid of this unused code
will ensure that distributors aren't needlessly pulling in this
dependency.
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1345
This effectively means we do not build on non-x86_64. But the template
gives us a well maintained base.
Also added into the image is gsettings-desktop-schemas from git, so that
the scheduled job only needs to be manually run when an update is
needed.
ASAN hasn't been useful so far; we don't really see
meaningful results from it, it takes a long time to
run since it builds Settings twice, etc.
Move it to manual.
Building the docker images has been failing for a while now. The root
cause appears to be a docker upgrade causing issues with TLS. See
https://about.gitlab.com/blog/2019/07/31/docker-in-docker-with-docker-19-dot-03/
Update the configuration so that the images can be built again.
Thanks to Bartłomiej Piotrowski for debugging the issue and solving it
for gnome-settings-daemon!
For the "development" profile, lets use the Nightly variant, to
visually indicate to users that they are running an unstable
version of the application.
