Nautilus

nautilus:gnome-42

  1. Git
  2. lp:nautilus
  3. gnome-42
Last commit made on 2023-02-07
Get this branch:
git clone -b gnome-42 https://git.launchpad.net/nautilus

Branch merges

Branch information

Name:
gnome-42
Repository:
lp:nautilus

Recent commits

8cd9503... by Ondrej Holy

view-icon-item-ui: Fix style for updated version of uncrustify

The updated version of uncrustify doesn't like this style.

7205071... by Corey Berla

general: Fix style for updated version of uncrustify

The updated version of uncrustify didn't like this style,
the new style doesn't look great either.

f603186... by =?utf-8?q?Ant=C3=B3nio_Fernandes?= <email address hidden>

ci: Prefer the json manifest

This is what Builder uses.

60d44ce... by =?utf-8?q?Ant=C3=B3nio_Fernandes?= <email address hidden>

flatpak: Remove YAML manifest

It's been added expecting Builder would support it, such that we could
drop the JSON manifest. 3b8f238624837a8a45cc675a954233cc46b30700

But it didn't happen so far https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/520

Since then we have been maintaining both files in sync, which is a waste
of effort at best, and a risk of the product of each manifest becoming
different, at worst.

Now that the CI uses the JSON manifest, we can just drop the YAML one.

1c07c97... by Ondrej Holy

flatpak: Use -Dbattery_detection=none for tracker-miners

The flatpak jobs are broken currently, because the tracker-miners project
fails to build due to missing upower-glib depenedency. It is used to tweak
the behavior when running on battery. It used to be automatically disabled
until the following MR:
https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/1121. I suppose
it is safe to disable this functionality as our flatpak isn't meant for
production. Let's explicitely disable that to fix our pipeline.

(cherry picked from commit 1569af12df5694af3eb1e83c8e64b6f360f35520)

30203bb... by Ondrej Holy

file-operations: Fix inverted g_assert condition

The commit e2969a9c29d0d171038fcb35d8baa5a7df372191 introduced an assertion
statement to ensure that the `g_file_get_basename` returned non-NULL string.
Unfortunately, the assertion has an inverted condition. This leads to crashes
in the `get_unique_target_file` function for files that don't have the
`edit-name` attribute set (i.e just a few GVfs backends). Let's fix the
inverted condition.

Fixes: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2825

(cherry picked from commit fcf8f9de8336549f6395c440a9be983849254b31)

394ca74... by Nart Tlisha

Add Abkhazian translation

ddd1e90... by =?utf-8?q?Ant=C3=B3nio_Fernandes?= <email address hidden>

Release version 42.6

a8a4610... by =?utf-8?q?Ant=C3=B3nio_Fernandes?= <email address hidden>

flatpak: Pin libportal dependency

Fixes CI pipeline failing in stable branch due to meson build options
changes in bleeding edge libportal.

bec137c... by Corey Berla

dbus-manager: Fix another crash from invalid dbus innvocation

Passing an invalid uri to create-folder also crashes nautilus.
If the parent_file is NULL, return an error instead of crashes.

(cherry picked from commit 8f989fa39fd53932597efdf9e728a88b4337fef9)