GitLab

The IPv6 addresses with zone identifiers are refused by GVfs currently.
THis is because of g_uri_unescape_segment failure as RFC 4007 allows bare
% sign to be used as separator. Although, RFC 6874 tries to fix that by
the %25 separator, however, at the same time, it suggests that the bare %
sign should still be accepted in user interfaces. But this would make this
too complex and lead to various problems (e.g. it would not be clear what
separator should be used for g_file_get_uri function). So I intentionally
don't plan to support what is suggested by RFC 6874 for now, which
effectively means that zone identifiers with non-ASCII chars won't be
supported. Let's skip the g_uri_unescape_segment function for IPv6 address
and also fix the gvfs_is_ipv6 function in order to accept the zone
identifiers...

Fixes: #483

(cherry picked from commit 226f0dd4)

mmap returns MAP_FAILED if, well, it failed. Thus, checking for
NULL does not catch errors.

Which changed name from libplist to libplist-2.0 to embed its API
version number in the library name.

When a program (like Nautilus) modifies the metadata in a file
(like metadata::custom-icon) there is no way of detecting that
change from other programs: neither inotify generates an event
in the file or the directory holding it, nor is possible to use
it in the files at, or the folder itself,
~/.local/share/gvfs-metadata, because writting in them is delayed
for nearly a minute.

Unfortunately, there are cases where it is needed to be able
to detect that. An example (and the reason for this patch) is
when Nautilus (or another file manager) modifies the custom
icon in a file from the desktop, and the desktop is managed
by a different program (in this case, Desktop Icons NG), because
the later can't detect the change made by the former and, thus,
the file will keep the old icon until the whole desktop is
refreshed.

To fix this, this patch proposes to add a signal to the
org.gtk.vfs.Metadata DBus interface, which will be triggered
whenever a key is modified. To avoid saturating the system in
case of modifying a lot of keys, it is triggered up to once
per second.

Copy and move operations preserve file attributes (such as modification
time) in most of existing scenarios: local copy/move, remote copy/move,
file_copy_fallback in glib. However, one case remains special: copy/move
between local and remote (gvfs) locations. It's implemented by push and
pull operations in backends, which don't attempt to preserve the usual
attributes (e.g., mtime and atime).

This commit implements the missing piece of functionality in sftp
backend. Modification time is preserved on copy and move, and access
time is preserved on move only, complying to the settable attributes
list of sftp backend.
Signed-off-by: Maxim Mikityanskiy <maxtram95@gmail.com>

Currently, only Basic and Digest authentication is possible for	webdav
backend. Let's add support for NTLM also.

#342

Currently, only Basic and Digest authentication is possible for webdav
backend. Let's add support for Negotiate also.

#342

Drive icons/description are leaked currently when also media
icon/description is available. Let's add missing `g_clear_object`
resp. `g_free` calls to fix those leaks.

GNOME/gvfs#452

`g_list_remove_link` is used when filtering out mountpoints, but the
GList element is not consequently freed. Let's use `g_list_delete_link`
to not leak that element.

#452

This job was added to check merge requests in order to prevent
gnome-build-meta breakages for example when our dependencies are changed.
However, this job needs a lot of maintenance to keep it working. Also,
the job was changed to be manual in order to not waste the capacity of
runners. Let's remove this job as it is easier to run this locally if
needed.

Update docker image and also add the privileged tag as it fails otherwise
with "fuse: device not found, try 'modprobe fuse' first" error.

Runners are now unprivileged. I tried to use podman, but I was not able
to make it work. Let's add the privileged tag to workaround this for now.