summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Revert "build: Require Meson >= 0.50"wip/carlosg/downgrade-meson-versionCarlos Garnacho2019-05-011-1/+1
| | | | | | | This reverts commit 17777040c63b7bc8586fa77bfa1219c0d96a9dd9. This version is still too new for gnome-build-meta and flatpaks, let's try to do without it.
* build: Avoid install:true in configure_file()Carlos Garnacho2019-05-015-6/+0
| | | | | | | | | This is a meson 0.50 feature which we don't strictly need to rely on. According to meson docs: "When omitted it defaults to true when install_dir is set and not empty, false otherwise." In all places we use it we (obviously) define install_dir, so the files should be installed without it being specifically told so.
* g-ir-merge: Avoid recursive includesCarlos Garnacho2019-05-011-3/+3
| | | | | | | | | Ensure the namespace is not part of the includes. This is a kludge and shouldn't ever happen, except it does (in continuous, induced by vala). The next big thing that would happen here is a rewrite of libtracker-sparql vala bits so we don't need this merging anymore, so I won't put much thought on it.
* build: Use current build dir as includedirCarlos Garnacho2019-05-011-1/+1
| | | | | Ebassi points out it's actually what g-ir-compile expects, so let's cross fingers again...
* build: Modify how we define the enum headerSam Thursfield2019-05-012-2/+4
| | | | | | | This is another change needed for tracker-miners to use the GSettings schemas from this project when its build as a subproject. See: https://gitlab.gnome.org/GNOME/tracker-miners/merge_requests/61
* build: Specify include dir to g-ir-compiler custom targetCarlos Garnacho2019-05-011-1/+1
| | | | | | | | | Try to help it find the Tracker-2.0.gir target it depends upon. The command is given a relative path from the build root, so add it. Hopefully fixes: http://build.gnome.org/continuous/buildmaster/builds/2019/05/01/5/build/log-tracker.txt
* build: Modify how we define the GSettings schemasSam Thursfield2019-05-012-6/+10
| | | | | | | | These changes are needed so that the 'tracker-miners' project can make use of the 'tracker' settings schemas when build with the `tracker=subproject` option. There should be no change to funtionality. This is related to https://gitlab.gnome.org/GNOME/tracker/issues/24
* functional-tests: Fix use of meson.build_root()Sam Thursfield2019-05-011-1/+1
| | | | | | | | | | | We must avoid using meson.build_root() because the value changes if we are embedded as a subproject in another project. I discovered this issue while testing <https://gitlab.gnome.org/GNOME/tracker/merge_requests/74> where it caused GSettings schemas not to be found when Tracker wasn't installed into /usr . It didn't cause any problems before, because the test was able to fall back on the GSettings schemas from /usr.
* build: Require Meson >= 0.50Sam Thursfield2019-05-011-1/+1
| | | | | | | Meson helpfully warns us that this is needed: WARNING: Project specifies a minimum meson_version '>=0.47' but uses features which were added in newer versions: * 0.50.0: {'install arg in configure_file'}
* libtracker-data: Plug parser leak on errorCarlos Garnacho2019-04-171-0/+1
| | | | | | We would leak the parsing tree accumulated thus far on errors. Good news is that it's potentially unlikely, bad news is that it's potentially big.
* Merge branch 'fix-lp-1822629' into 'master'Sam Thursfield2019-04-011-3/+3
|\ | | | | | | | | | | | | tracker-miner: Fix cancellation of g_file_enumerator_next_files_async Closes #86 See merge request GNOME/tracker!86
| * tracker-miner: Fix cancellation of g_file_enumerator_next_files_asyncAndrea Azzarone2019-04-011-3/+3
|/ | | | | | | | The async op is not owner of the user data, so it may be actually gone in the GAsyncReadyCallback. Ensure we only use it on success or on other errors than cancelled. Closes: https://gitlab.gnome.org/GNOME/tracker/issues/86
* Merge branch 'wip/carlosg/handle-recursive-resources' into 'master'Sam Thursfield2019-04-012-14/+10
|\ | | | | | | | | libtracker-sparql: Handle correctly backreferences in TrackerResource tree See merge request GNOME/tracker!84
| * libtracker-sparql: Handle correctly backreferences in TrackerResource treeCarlos Garnacho2019-03-311-12/+9
| | | | | | | | | | | | | | | | | | | | | | We do keep a notion of already visited TrackerResources when generating the output. However that could go wrong if the TrackerResource references itself or a "parent" TrackerResource. Add the resources to the done list beforehand, so they are ensured not to be visited again if such backreferences exist. Related: https://gitlab.gnome.org/GNOME/tracker-miners/issues/60
| * build: Fix build with meson >= 0.50Carlos Garnacho2019-03-311-2/+1
|/ | | | | | | | | | Since I got meson 0.50, tracker fails to build with: undefined reference to `builtin_ontology_resource_data' when building libtracker-data.so. Do not use the compile_gresource values individually, this seems to make meson 0.50 happy and should work with older meson.
* Merge branch 'wip/tintou/tracker-sparql-doc' into 'master'Sam Thursfield2019-03-309-76/+141
|\ | | | | | | | | docs: Modernize the libtracker-sparql documentation See merge request GNOME/tracker!81
| * docs: Modernize the libtracker-sparql documentationCorentin Noël2019-03-289-76/+141
|/ | | | Still not fixed the Tracker 2.0 references here and there
* Merge branch 'sam/functional-tests-removal' into 'master'Sam Thursfield2019-03-2712-1392/+0
|\ | | | | | | | | tests: Remove some functional tests See merge request GNOME/tracker!72
| * tests: Remove some functional testsSam Thursfield2019-03-0412-1392/+0
| | | | | | | | | | | | These tests appear to be either basic smoke tests, or performance tests that are intended to be timed and executed manually. Some also dump huge amounts of text to the test log file.
* | Merge branch 'wip/tintou/tracker-miner-doc' into 'master'Sam Thursfield2019-03-2718-350/+167
|\ \ | | | | | | | | | | | | docs: Modernize the libtracker-miner documentation See merge request GNOME/tracker!78
| * | docs: Modernize the libtracker-miner documentationCorentin Noël2019-03-276-294/+114
| | |
| * | Prepare source files to documentationCorentin Noël2019-03-2712-56/+53
| | |
* | | Merge branch 'wip/carlosg/issue-84' into 'master'Carlos Garnacho2019-03-271-4/+4
|\ \ \ | |/ / |/| | | | | | | | | | | | | | Fix parsing of doubles with exponential part Closes #84 See merge request GNOME/tracker!77
| * | libtracker-data: Handle doubles before other numeric typesCarlos Garnacho2019-03-271-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | Otherwise there are greediness issues as the definition of DECIMAL fits within DOUBLE and wins over it, leaving the exponential part out of the match. Closes: https://gitlab.gnome.org/GNOME/tracker/issues/84
| * | libtracker-data: Fix infinite recursion on positive doublesCarlos Garnacho2019-03-271-1/+1
|/ / | | | | | | | | A c&p typo made the DOUBLE_POSITIVE terminal defined upon itself, it should be defined on top of DOUBLE.
* | Merge branch 'wip/tintou/tracker-control-doc' into 'master'Sam Thursfield2019-03-276-78/+83
|\ \ | | | | | | | | | | | | docs: Modernize the libtracker-control documentation See merge request GNOME/tracker!76
| * | docs: Modernize the libtracker-control documentationCorentin Noël2019-03-276-78/+83
|/ /
* | Merge branch 'wip/tintou/readme' into 'master'Sam Thursfield2019-03-262-231/+189
|\ \ | | | | | | | | | | | | Switch to README.md See merge request GNOME/tracker!75
| * | Switch to README.mdCorentin Noël2019-03-262-231/+189
|/ /
* | Update Croatian translationGoran Vidović2019-03-251-508/+530
| |
* | tracker-store: yield statements not allowed without async contextRico Tzschichholz2019-03-161-1/+0
| |
* | Release 2.2.12.2.1Carlos Garnacho2019-03-062-1/+16
| |
* | libtracker-data: Handle NULLs in update solutionsCarlos Garnacho2019-03-051-0/+2
| | | | | | | | | | | | This broke in commit bb88e1d39, since it is valid for the cursor to leave the GValue unset on NULLs in the requested column. We should just forward the NULL as we used to.
* | Merge branch 'wip/carlosg/fix-changes-done-hint-handling' into 'master'Sam Thursfield2019-03-042-3/+19
|\ \ | | | | | | | | | | | | | | | | | | Fix CHANGES_DONE_HINT handling on inotify Closes tracker-miners#36 See merge request GNOME/tracker!73
| * | libtracker-miner: Dispose cached events on MONITOR_EVENT_DELETEDCarlos Garnacho2019-03-041-0/+13
| | | | | | | | | | | | | | | | | | I don't know if this is possible, but in case that happens we should drop the event either way, and neutralize CREATED+DELETED events early on.
| * | libtracker-miner: Preserve first cached eventCarlos Garnacho2019-03-041-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | We cache both CREATED and CHANGED events here, if we get both while waiting for the CHANGES_DONE_HINT, it makes things more consistent to cache the first CREATED event. This did not result in bugs as the miner reacts the same either way.
| * | libtracker-miner: Fix thinko in conditionCarlos Garnacho2019-03-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | use_changed_event refers to FAM and the inability of the GIO monitor implementation to send CHANGES_DONE_HINT for it. This means we have to forward CREATED/CHANGED events immediately if we have to rely on FAM-backed monitors. However the condition handling this was inverted, which meant we sucked with file monitors that honored CHANGES_DONE_HINT, and completely broke updates on FAM monitors. Closes: https://gitlab.gnome.org/GNOME/tracker-miners/issues/36
| * | tests: Drop dubious assertCarlos Garnacho2019-03-041-2/+0
| | | | | | | | | | | | | | | | | | In the comment above the "may" verb is key. If the monitor does a good job at coalescing events that would not be the case, we should admit the flag being either set or unset here.
* | | Merge branch 'fix-issue-78' into 'master'Sam Thursfield2019-03-042-2/+4
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | meson: Enforce build order using generated headers directly Closes #78 See merge request GNOME/tracker!65
| * | | meson: Enforce build order using generated headers directlyAndrea Azzarone2019-02-282-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Both libtracker-fts and libtracker-data end up requiring includes from tracker-sparql.h, but we have to generate tracker-generated.h first. To solve this, commit a452173ed introduced a dependency to an intermediate target (tracker_sparql_intermediate_dep). Use directly the custom target tracker_sparql_generated_header to enforce build order. Closes: https://gitlab.gnome.org/GNOME/tracker/issues/78
* | | | Merge branch 'sam/ci-save-logs-on-failure' into 'master'Sam Thursfield2019-03-041-0/+5
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | ci: Upload test suite logs when tests fail See merge request GNOME/tracker!71
| * | | | ci: Upload test suite logs as a CI artifactSam Thursfield2019-03-041-0/+5
| | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We sometimes see unreproducible test failures in CI. These are often hard to debug because they don't occur all the time, and may even be triggered by something that only happens on a specific CI runner. As a step towards debugging these, we should upload the test log as a GitLab artifact. Meson only shows the last 100 lines of the test log on stdout, and there seems to be no way to cause it to emit more info, so this should help with debugging https://gitlab.gnome.org/GNOME/tracker/issues/79.
* | | | Merge branch 'sam/survive-missing-ontologies-gvdb' into 'master'Sam Thursfield2019-03-041-2/+7
|\ \ \ \ | |/ / / |/| | | | | | | | | | | Survive missing ontologies.gvdb file See merge request GNOME/tracker!68
| * | | Fix crash in read-only mode when ontologies.gdvb is missingSam Thursfield2019-03-041-2/+7
|/ / / | | | | | | | | | | | | We shouldn't unref the manager->ontologies object if loading the new ontologies failed. Fixes a crash in the fallback code path.
* | | Update Latvian translationRūdolfs Mazurs2019-03-031-517/+532
| |/ |/|
* | Merge branch 'wip/carlosg/trigger-filter-parent-on-monitor-events'Carlos Garnacho2019-03-032-90/+33
|\ \
| * | libtracker-miner: Drop TrackerMonitor API to get/set the indexing treewip/carlosg/trigger-filter-parent-on-monitor-eventsCarlos Garnacho2019-03-032-36/+0
| | | | | | | | | | | | This is unused now.
| * | libtracker-miner: Handle deletes of files triggering parent folder filtersCarlos Garnacho2019-03-031-13/+14
| | | | | | | | | | | | | | | Theoretically at least, since we don't have file monitors on the directory in that case. The code is now correct at least.
| * | libtracker-miner: Let non-indexable files trigger parent folder checksCarlos Garnacho2019-03-031-12/+19
| | | | | | | | | | | | | | | | | | | | | Files that are non-indexable by themselves may trigger is_parent_indexable() changes. Defer the early return after that. Closes: https://gitlab.gnome.org/GNOME/tracker/issues/47
| * | libtracker-miner: Do not check indexing tree on monitor eventsCarlos Garnacho2019-03-031-29/+0
|/ / | | | | | | | | | | | | Leave all checks on TrackerIndexingTree to the TrackerFileNotifier, and report all events to it. Those might trigger other actions (eg. policy changes through the TrackerIndexingTree) that shouldn't go ignored.
View Lorry Controller Status