summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* Revert "build: Avoid extra variable on compiler flag checking"Ondrej Holy2019-01-071-2/+4
| | | | This reverts commit a644c8763e1ed8a97fb1115046903d0c2583b8d5.
* Revert "build: Simplify man file building"Ondrej Holy2019-01-071-8/+22
| | | | This reverts commit 7aaada6e723122c705ac5a5dc638e18b8f8ddd36.
* Revert "build: Make use of dictionaries to gain readibility"Ondrej Holy2019-01-071-31/+72
| | | | This reverts commit a60d8c0987914213f2e69f760b15500a10c3adb4.
* build: Make use of dictionaries to gain readibilityIñigo Martínez2019-01-041-72/+31
| | | | | | | | | | | | | | | | The set of daemons is a large list of executables to be built. To ease its build an array of arrays was created, but this harms readibility. This has been improved by the use of the new dictionary types[0] and the possibility of using a dictionary as a parameter in target objects[1]. The individual dependencies have been moved directly to the new dictionary because it remains clear their meaning. [0] http://mesonbuild.com/Release-notes-for-0-47-0.html#new-builtin-object-type-dictionary [1] http://mesonbuild.com/Release-notes-for-0-49-0.html#can-specify-keyword-arguments-with-a-dictionary
* build: Simplify man file buildingIñigo Martínez2019-01-041-22/+8
| | | | | man file building has been simplified by taking advantage of meson arrays and generators placeholders.
* build: Avoid extra variable on compiler flag checkingIñigo Martínez2019-01-041-4/+2
| | | | | | The use of an extra variable can be avoided and still maintain readibility when checking compiler flags, so the build commands have been changed.
* build: Define meson information earlyIñigo Martínez2019-01-041-11/+11
| | | | | | | | | The used meson modules, default directories and includes have been moved to the start of the build file, just after project related information, so they are available early. The way `po` directory path is defined has also been changed to avoid the use of the `source_root` function.
* build: Do not use prefix on directory variablesIñigo Martínez2019-01-0413-32/+32
| | | | | | | | | Although usually directory variables are set by using the `prefix` directory, this might cause issues due to parameters that need relative directories. In order to ease the transition `prefix` directory has been stripped from directory variables and only has been appended when necessary.
* build: Remove gdbus codegen workaroundIñigo Martínez2019-01-044-54/+12
| | | | | | | | | | | When gvfs was ported to meson `gdbus-codegen` was not able to generate the source and header files independently, and this caused issues on highly parallelized build. To avoid this issue a workaround was placed by using an external script. However, recently glib and meson acquired support for generating source and header files independently, so the workaround has been removed.
* build: Use generators placeholdersIñigo Martínez2019-01-044-14/+10
| | | | | | | | | | Functions derived from generators as `configure_file`, `custom_target` and `i18n.merge_file` can use placeholders like `@BASENAME@` that removes the extension from the input filename string. The output string has been replaced by this placeholder that allows in some cases the use of less variables.
* build: Fix the parameter order in configure_fileIñigo Martínez2019-01-044-9/+9
| | | | | | | The `install` and `install_dir` parameters must be the last parameters in the `configure_file` function. The paremeters have been reordered to fix this issue.
* build: Fix the use of pkg-config file variablesIñigo Martínez2019-01-0411-40/+50
| | | | | | | | | The names of the variables in meson corresponding to the variables obtained from the pkg-config files has been fixed by using a pattern. The pattern uses the dependency name as the prefix and the obtained variable as the suffix.
* build: Use / instead of join_pathsIñigo Martínez2019-01-048-28/+28
| | | | | | | Since meson 0.49, the `/` character can be used to join paths[0], so all the instances of `join_paths` have been replaced. [0] http://mesonbuild.com/Release-notes-for-0-49-0.html#joining-paths-with-
* build: Always use dependency function for libgcryptIñigo Martínez2019-01-041-19/+2
| | | | | | | | | | meson 0.49 has gained support for `libgcrypt-config` when using the `dependency` function[0], so there is not need to call to it from build files. The minimum required meson version has also been bumped to 0.49. [0] http://mesonbuild.com/Release-notes-for-0-49-0.html#libgcrypt-dependency-now-supports-libgcryptconfig
* build: Add trailing commasIñigo Martínez2019-01-0415-155/+155
| | | | | | | Add missing trailing commas that avoids getting noise when another file/parameter is added and eases reviewing changes[0]. [0] https://gitlab.gnome.org/GNOME/dconf/merge_requests/11#note_291585
* build: Make monitors build commands commonIñigo Martínez2019-01-047-209/+62
| | | | | | | | | | | | | | All the available monitors install a set of files: volume monitor files, DBus service files, etc... These build commands are mostly common and only file names change, which are built using a given pattern. These build commands have been replaced by only one set of build commands that adapt to monitors needs by changing their name and simplifies the entire process. These changes also help installing `GOA` and `MTP` necessary test files.
* build: Remove unnecessary dir definesIñigo Martínez2019-01-041-2/+0
| | | | | `gvfs_bindir` and `gvfs_includedir` are not used in any meson's build files so they have been removed.
* keyring: Prefer the most recent itemOndrej Holy2019-01-041-0/+4
| | | | | | | | | | | | | | | | | | If keyring contains more entries for one host, the first one is always used. However, this is not always the best one. Imagine the situation that the username was changed on the server for some reason and the previous username is invalid. When user connects using the new username, a new entry is added to the keyring. However, next time the old username is automatically used when mounting using the hostname only, which leads to login failures and the user has to specify its password each time... Prefer the most recent item from keyring if they are equal in specificity in order to prevent such issues. It would be best to remove the invalid entry automatically from the keyring, but it is not safe to remove it just in case of login failure, because it might be just some network outage, or so... https://gitlab.gnome.org/GNOME/gvfs/issues/352
* afp: Try to find credentials even if user is not specifiedOndrej Holy2019-01-041-16/+16
| | | | | | | | | | | Currently, when you try to mount AFP share and don't specify username in the URI, the g_vfs_keyring_lookup_password() call is skipped and thus you have to specify the credentials manually even if "Remember Password Forever" was used last time. This is wrong and other backends in the same situation tries to use the stored credentials. This is especially annoying for locations which are propagated over DNS-SD. Let's change this. Closes: https://gitlab.gnome.org/GNOME/gvfs/issues/352
* dav: Try authenticate again even if 403 was returnedOndrej Holy2019-01-041-2/+29
| | | | | | | | | | | | Some servers e.g. davs://webdav.mc.gmx.net returns 403 status code instead of 401 in case of invalid credentials. This causes that libsoup fails immediately after the first login attempt, which is especially problem in case of the wrong credentials stored in the keyring. A user doesn't have any chance to manually specify correct credentials. Clear the credentials cache and force libsoup to call the authentication callback again... Closes: https://gitlab.gnome.org/GNOME/gvfs/issues/351
* Update Catalan translationJordi Mas2018-12-291-6/+6
|
* ci: Update docker imageOndrej Holy2018-12-182-2/+2
| | | | | This is needed to include the latest meson release, which is necessary for: https://gitlab.gnome.org/GNOME/gvfs/merge_requests/25.
* Replace Bugzilla by Gitlab URL in DOAP fileAndre Klapper2018-12-141-1/+1
|
* Post release version bumpOndrej Holy2018-12-101-1/+1
|
* Update NEWS for 1.39.3 release1.39.3Ondrej Holy2018-12-102-1/+10
|
* ci: Update docker imageOndrej Holy2018-12-073-6/+7
| | | | | New image is necessary because of new functionality. Add --no-cache option to force rebuilding the image.
* build: Use g_unix_mount_get_root_path conditionallyOndrej Holy2018-12-072-3/+17
| | | | | GLib hasn't been released with g_unix_mount_get_root_path support yet, so let's add macros to use this functionality only if available.
* udisks2: Improve handling of mounts which doesn't point into fs rootOndrej Holy2018-12-071-3/+14
| | | | | | | | | | | | | UDisks2 handling of mounts which doesn't point into fs root (created over bind operation, or btrfs subvolumes) is not optimal, see: https://github.com/storaged-project/udisks/issues/478 Also GIO API doesn't expect that one GVolume can have multiple mountpoints. Thus don't try to match UDisksBlock with mount which doesn't point into fs root and create standalone GVfsUDisks2Mount for it (or use GVfsUDisks2Volume corresponding with fstab entry). https://gitlab.gnome.org/GNOME/gvfs/issues/330
* udisks2: Do not ignore mounts without volumesOndrej Holy2018-12-071-6/+0
| | | | | | | | | | | | | | | gvfs_udisks2_mount_new returns NULL if volume is not specified and mount is considered as internal by g_unix_mount_is_system_internal. This prevents mount creation in certain cases even if x-gvfs-show is manually specified. Mounts are already filtered out by should_include_mounts, so I don't see much reason for additional check. It is true that should_include_mount doesn't use g_unix_mount_is_system_internal, but just g_unix_is_mount_path_system_internal, however, we can change this in future if needed. https://gitlab.gnome.org/GNOME/gvfs/issues/330
* udisks2: Restore support of comment=x-gvfs-* optionOndrej Holy2018-12-032-9/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Beginning the commit 959db3e0, mtab-based mount options are prioritized prior to the fstab options. However, "comment" option is not propagated to mtab and thus mounts with "comment=x-gvfs-show" can be ignored, but volumes can be still shown for them and vice versa. Consequently, mount operation fails with the following: "Mount is denied because the NTFS volume is already exclusively opened. The volume may be already mounted, or another software may use it which could be identified for example by the help of the 'fuser' command." Just a note, that "comment=x-gvfs-*" is wrong as per the docs and it should be "comment=gvfs-*" instead. However, it seems that the people started using this after commit 37d4bf32 as workaround on distributions with old util-linux versions, where plain "x-gvfs-*" option caused the following error: "Unrecognized mount option "x-gvfs-show" or missing value" The workaround using "comment=x-gvfs-*" option worked so far just only thanks to the "bug" in gvfs_udisks2_utils_lookup_fstab_options_value() function, which doesn't care about the prefix of the mount option. Let's prioritize fstab options before mtab-based mount options to fix this regression. It is maybe less reliable because the assignment of the corresponding fstab entry is arguable, but the rest of the volume monitor code relies on it anyway. Closes: https://gitlab.gnome.org/GNOME/gvfs/issues/348
* daemon: Prevent spawning new daemons if outgoing operation existsOndrej Holy2018-11-191-0/+26
| | | | | | | | | | | | | | | | A new daemon is always spawned if MountLocation method (or LookupMount for automounted) is called and the respective mount isn't registered yet. This is not usually an issue, because the redundant daemons are consequently terminated. However, this is a problem if mount operations hang for some reason. This may happen e.g. with trash backend due to stale NFS mounts. Consequently, new and new daemons are spawned which may lead to system failures due to lack of system resources. See the following downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1632960 Let's fix that behavior simply by preventing spawning of new daemons if respective outgoing mount operations exist. https://gitlab.gnome.org/GNOME/gvfs/merge_requests/19
* common: Prevent crashes on invalid autorun fileOndrej Holy2018-10-261-1/+1
| | | | | | | | GRegex expects valid UTF-8 input by default and libpcre may crash if it is not valid. GRegex is used to parse autorun file, which doesn't have to be always valid. Let's use G_REGEX_RAW to prevent the crashes. Closes: https://gitlab.gnome.org/GNOME/gvfs/issues/344
* Update Slovak translationDušan Kazik2018-10-241-531/+539
| | | | (cherry picked from commit b846e5389073fc8607ef41851bf525b29029d976)
* Post release version bumpOndrej Holy2018-10-081-1/+1
|
* Update NEWS for 1.39.1 release1.39.1Ondrej Holy2018-10-081-0/+11
|
* Update Serbian translationМарко Костић2018-09-291-527/+534
| | | | (cherry picked from commit fa11cb717155213847c9941ce8fbcc9f83f3a44e)
* gvfs-test: Don't specify the port if we are running in the sandboxIain Lane2018-09-251-2/+9
| | | | | In this case the smb config is set up using the default port by the sandbox itself - the config in the testsuite is not used.
* gphoto2: Fix mounting for devices with special chars in ID_SERIALOndrej Holy2018-09-241-4/+7
| | | | | | | ID_SERIAL string is not URI-escaped before use, but unfortunately, it may contain special characters (e.g. colons) and consequently it is not possible to mount affected devices over activation_root. Let's URI-escape the ID_SERIAL string before use as URI to fix that issue.
* mtp: Fix mounting for devices with special chars in ID_SERIALOndrej Holy2018-09-241-2/+4
| | | | | | | | | ID_SERIAL string is not URI-escaped before use, but unfortunately, it may contain special characters (e.g. colons) and consequently it is not possible to mount affected devices over activation_root. Let's URI-escape the ID_SERIAL string before use as URI to fix that issue. Closes: https://gitlab.gnome.org/GNOME/gvfs/issues/338
* google: Handle child of volatile also as volatileOndrej Holy2018-09-211-39/+19
| | | | | | Files in volatile folder should be also marked as volatile. Volatile handling is a bit simplified as a part of this patch also.
* google: Use cache for enumeration alsoOndrej Holy2018-09-211-16/+46
| | | | | | | The reworked cache hasn't been used for enumeration results and also for missing files checks, which always caused rebuilding cache. Let's save timestamps also for enumerations and use it to prevent redundant cache rebuilds.
* google: Rework cache for better performanceOndrej Holy2018-09-211-238/+166
| | | | | | | | | | | The backend is totally unusable if you have too many files on your Drive. This happens because the backend preloads the whole Drive's metadata. Let's build the cache incrementaly per folders. As a result, the backend works smoothly regardless of the total number of Drive files, because the total number of transmitted data is significantly reduced. On the other hand, more requests is done to Drive, but the Drive quotas seem big enough.
* google: Remove file just from concrete parentOndrej Holy2018-09-211-4/+33
| | | | | | Files with multiple parents are currently removed from all parents. This is unexpected and may cause data loss, because it is not obvious that it is one file. Let's remove the file just from requested folder.
* google: Add support for files with multiple parentsOndrej Holy2018-09-211-220/+168
| | | | | | | | | One entry can have multiple parents. You can create such entry on the web in a pretty simple way, e.g. Ctrl + Drag&Drop. Such entries are currently shown only on one place in the backend. Also the backend rely on get_parent_id() and get_entry_path() functions which are tottaly wrong. Let's introduce get_parent_ids() and resolve entry_path only from given filename.
* google: Ignore entries without parentsOndrej Holy2018-09-211-17/+1
| | | | | | Entries without parents are not shown on the web and there isn't any reason to list them here. Such entries belongs to some web services and we have no control over them.
* google: Remove also dir_collisions entriesOndrej Holy2018-09-211-0/+7
| | | | | dir_collisions are not properly invalidated if removed entry is on this list. Let's remove the entry also from this list.
* google: Move debug prints before releasing entryOndrej Holy2018-09-211-2/+2
| | | | | | Debug output contains mess because id and title are const gchar * and are released together with GDataEntry on previous line. Let's just swap the lines.
* smbbrowse: Force NT1 protocol version for workgroup supportOndrej Holy2018-09-212-0/+44
| | | | | | | | | | | | "Windows Network" doesn't work with recent samba versions, because "client max protocol" has been changed from NT1 to SMB3 recently. NT1 is mandatory for workgroup support. Let's force NT1 using the newly added smbc_setOptionProtocols API if available. But force this only when neither hostname, nor IP address is used. This among others prevents complete breakage if NT1 is disabled on server. Use GResolver to implement this heuristic. https://bugzilla.gnome.org/show_bug.cgi?id=780958
* Update Russian translationStas Solovey2018-09-061-525/+532
| | | | (cherry picked from commit 847058eb893cf8cf724ce3f61d4b4458bad40b9d)
* Update Belarusian translationYuras Shumovich2018-09-061-1628/+1577
| | | | (cherry picked from commit dcf47dbb1c4cfcdafb876b7bc5f79b7228d0a42e)
View Lorry Controller Status