| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
Don't ignore the result_uncertain flag from g_content_type_guess() as it
might cause nautilus to incorrectly think that a particular file is of a
certain type, and never check its magic.
|
| |
|
|
|
|
| |
Don't ignore the result_uncertain flag from g_content_type_guess() as it
might cause nautilus to incorrectly think that a particular file is of a
certain type, and never check its magic.
|
| |
|
|
|
|
| |
Don't ignore the result_uncertain flag from g_content_type_guess() as it
might cause nautilus to incorrectly think that a particular file is of a
certain type, and never check its magic.
|
| |
|
|
|
|
| |
Don't ignore the result_uncertain flag from g_content_type_guess() as it
might cause nautilus to incorrectly think that a particular file is of a
certain type, and never check its magic.
|
| |
|
|
|
|
| |
Don't ignore the result_uncertain flag from g_content_type_guess() as it
might cause nautilus to incorrectly think that a particular file is of a
certain type, and never check its magic.
|
| |
|
|
|
|
| |
Don't ignore the result_uncertain flag from g_content_type_guess() as it
might cause nautilus to incorrectly think that a particular file is of a
certain type, and never check its magic.
|
| |
|
|
|
|
| |
Don't ignore the result_uncertain flag from g_content_type_guess() as it
might cause nautilus to incorrectly think that a particular file is of a
certain type, and never check its magic.
|
| |
|
|
|
|
| |
Don't ignore the result_uncertain flag from g_content_type_guess() as it
might cause nautilus to incorrectly think that a particular file is of a
certain type, and never check its magic.
|
| |
|
|
|
|
| |
Don't ignore the result_uncertain flag from g_content_type_guess() as it
might cause nautilus to incorrectly think that a particular file is of a
certain type, and never check its magic.
|
| |
|
|
|
| |
content_type was only used and initialised inside this block, so move it
there.
|
| |
|
|
|
|
|
|
|
|
| |
The mount operation currently fails with "Invalid argument" error if
GVfsDnsSdResolver returns link-local IPv6 address. This can quite easily
happen also when using File Share functionality provided by GNOME. It
fails because the link-local addresses requires interface to be specified.
Let's append the interface in them to fix this issue.
Fixes: https://gitlab.gnome.org/GNOME/gvfs/issues/423
|
| |
|
|
|
|
| |
GVfsDnsSdResolver doesn't store interface for the resolved service,
however, we need this for link-local address support. Let's add the
missing bits for it.
|
| |
|
|
|
|
| |
This is follow up of commit d8556a0, which removes brackets when mounting
over dav/davs schemes, however, the same fix is also needed when mounting
over dav+sd/davs+sd schemes in order to prevent "Invalid URI" error.
|
| | |
|
| |
|
|
| |
This reverts commit 1a38caf8bcb4e02b68f8062319ef7736796a7e64.
|
| |
|
|
| |
This reverts commit db26e29930084ad48711c076d611b0227dd97a65.
|
| |
|
|
|
| |
GTimeVal is deprecated. Let's replace it by GDateTime in order to
prevent the deprecation warnings.
|
| |
|
|
|
| |
GTimeVal is deprecated. Let's replace it by GDateTime in order to
prevent the deprecation warnings.
|
| |
|
|
|
| |
GTimeVal is deprecated. Let's remove it in order to prevent the
deprecation warnings.
|
| |
|
|
|
| |
GTimeVal is deprecated. Let's remove it in order to prevent the
deprecation warnings.
|
| |
|
|
|
| |
GTimeVal is deprecated. Let's remove it in order to prevent the
deprecation warnings.
|
| |
|
|
|
| |
GTimeVal is deprecated. Let's remove it in order to prevent the
deprecation warnings.
|
| |
|
|
|
| |
GTimeVal is deprecated. Let's remove it in order to prevent the
deprecation warnings.
|
| |
|
|
|
| |
GTimeVal is deprecated. Let's replace it by GDateTime in order to
prevent the deprecation warnings.
|
| |
|
|
|
| |
GTimeVal is deprecated. Let's remove it in order to prevent the
deprecation warnings.
|
| | |
|
| |
|
|
|
| |
The devel_utils and man meson options are by default false. Let's set
them to true to verify that everything is fine.
|
| |
|
|
|
| |
GitLab CI fails with GLib master currently because of new deprecated symbols.
Let's do not treat deprecated-declarations as error to fix CI for now.
|
| |
|
|
|
|
| |
Docker uses TLS by default now which breaks the runner. Let's disable TLS
for now to fix the update-image job. See the GitLab issue for more info:
https://gitlab.com/gitlab-org/gitlab-runner/issues/4501
|
| |
|
|
|
|
| |
The update-image job doesn't work as expected on forks, because the
$CI_REGISTRY_ variables are not properly set. Let's limit this only
to GNOME namespace to make it obvious.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The recent commit e9653aa9, which allows mounting when 403 is returned
instead of 401, broke the backend for the case when authentication
succeeded for subdirectory and 403 is returned for the parent folder.
The backend doesn't work properly, even though it doesn't return any
error from the mount operation. Nautilus just shows "File is of unknown
type" and the backend prints errors like "soup_auth_authenticate:
assertion 'password != NULL' failed". Let's prevent usage of the
workaround from commit e9653aa9 after the first successful auth to fix
this issue.
Fixes: https://gitlab.gnome.org/GNOME/gvfs/issues/417
|
| | |
|
| |
|
|
|
| |
Reflect the changes made in GNOME/gnome-build-meta!363 to make the job
work again.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
