GitLab

Update URLs to reflect where the packaging repo is being maintained.

This makes sure we follow the practices documented under
https://tracker.pureos.net/w/development/packaging_overview/

libhandy-1 Debian release 1.5.0-1

Update to upstream version '1.5.0'
with Debian dir 586417ac4d2bd78baca25514cdc2e721fe37ccc6

Fixes https://gitlab.gnome.org/GNOME/libadwaita/-/issues/294

Backported from https://gitlab.gnome.org/GNOME/libadwaita/-/commit/4e2ef2f5fd048afdb9f8a8866b55f389655db773

Backport parts of https://gitlab.gnome.org/GNOME/libadwaita/-/commit/466509f6120866005ea2e8c2cdb2ddb83a39cc40

Yikes, so because it contains a leaflet that's always leaked we had an
extra gtk_widget_destroy() here to compensate. Kill it with fire.

Fix a refcycle between the widget and the swipe tracker.

Backported from https://gitlab.gnome.org/GNOME/libadwaita/-/commit/2821a1063e332d00b9b2fc00ba28e5d1c754645f

This is a private object, no need to bother with with weak refs. Just avoid
a refcycle.

Backported from https://gitlab.gnome.org/GNOME/libadwaita/-/commit/d1da4bd8e5791cc6831cb1579843156b24a988cd

Philip Withnall authored Oct 05, 2021 and Alexander Mikhaylenko committed Nov 12, 2021

`g_settings_schema_source_lookup()` returns a new reference.
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>

Backported from https://gitlab.gnome.org/GNOME/libadwaita/-/commit/18a1d426e7a7dc1034c0012a14ca31e73fe266a0

These adaptive margins interfere with measuring the
default sizes, as the margins change the size. This
causes weird things like content being inaccessible
or content animating as soon as you open a PreferencesPage.

For now, we should drop the adaptive margins. In the future
we can implement this in the layout code.

(cherry picked from commit f2115b5a5d17639b1838c92ecd0a75001f5f4ef0)

One case we didn't guard against was if xdg-desktop-portal exists, but
doesn't provide a settings portal interface.

See https://gitlab.gnome.org/GNOME/libadwaita/-/merge_requests/269

Avoid falling back to Adwaita with no way to set dark variant.

The check is not perfect and will fail if libhandy and GTK prefixes differ.
Nothing we can do about that though.

Also it will stop picking up changes until restart if theme has been
invalid even once. This is unfixable too, since we can't track changes
on GdkScreen settings directly, and as soon as we set gtk-theme-name is set
it can't be used to track changes anymore.

Still better than nothing.

Only show it if the system doesn't support color schemes.