2018-08-30  Carlos Garnacho  <carlosg@gnome.org>

	Release 2.1.3

	Revert "Add tracker_sparql_connection_get/set_dbus_connection()"
	This reverts commit eb24ea93bc550934d15223d002b490143e604921.

	This is an interesting feature, but not a good timing. Punt for
	2.2.x that will happen after 3.30.

	Merge branch 'wip/carlosg/insert-delete-triggers'

	libtracker-data: Avoid refcount leaks on ontology updates
	Make sure we add the new triggers after the "rename table, create
	replacement one, dump data" dance we do on ontology changes. This will
	avoid leaks as the last step there would increase refcount for all
	involved resources.

	There is only one situation where this does not work: Ontology changes
	that remove properties with rdfs:Resource range will result in those
	resources being leaked. This breaks differently but in similar ways for
	single-valued and multivalued properties, in the first we fail to delete
	elements from the old table, in the second we fail to delete the table
	altogether.

	This barely ever happens, so a FIXME has been added, we should cross this
	bridge before doing any such modification in the ontology.

	libtracker-data: Make insert/delete triggers modify all resource properties
	Refcount is not being increased if inserts happen with other values than
	the initial one, nor decreased when deletes happen on rows holding
	references to resources.

	In order to fix this, make the insert/delete triggers check all properties
	with rdfs:Resource range, this will ensure resources are properly
	refcounted in those cases.

	Closes: https://gitlab.gnome.org/GNOME/tracker/issues/32

	libtracker-data: Keep internal resources out of refcount checks
	Whatever it happens, we don't want to break the database that bad.

	libtracker-direct: Fix error fetching for single updates in update_array()
	The error location was being silently leaked.

	libtracker-direct: Use ';' as separator for multiple update statements
	Let's stick to SPARQL1.1 correct syntax.

	libtracker-miner: Use ';' as separator for multiple update statements
	Let's stick to SPARQL1.1 correct syntax.

	libtracker-sparql: Use ';' as separator for multiple update statements
	The separator being optional is a tracker-specific "feature". Seems better
	to use proper SPARQL1.1 here.

	libtracker-data: Correct SQL query for ontology checks
	The column does not exist in that table, should be fetched from the
	rdfs:Resource table. This results in the query returning the column
	name as a string (due to the quotes), and turning out as a 0
	nao:lastModified.

	Those dates are kinda thrown away for readwrite connections, so it
	didn't matter there. They stick around for readonly connections in
	the internal TrackerOntologies, but the modification date has no
	use or purpose on those.

	libtracker-data: Update nao:lastModified after creating new database
	It used to happen only right after ontology checks, which left branch new
	databases with an unset ontology modification date. This really didn't have
	ill effects, on the second run ontologies would be checked, but no real
	change would happen except the nao:lastModified change.

	Still better to do it at once, instead of waiting for the next run.

	tests: Run sparql blank tests on a temporary folder
	So it can't fail due to leftovers from previous runs.

	tests: Ignore previous events from monitor test setup
	Similar to commit ff1f66a4d46. The move..._after_file_update test has
	the same issue than the move..._after_file_create, so let's forget those
	first events.

	libtracker-miner: Fix tracker-store DBus name watch

2018-08-29  Fran Dieguez  <frandieguez@gnome.org>

	Update Galician translation

2018-08-29  Sam Thursfield  <sam@afuera.me.uk>

	Merge remote-tracking branch 'origin/wip/carlosg/legalese-cardinality'
	See https://gitlab.gnome.org/GNOME/tracker/merge_requests/19

2018-08-28  Seong-ho Cho  <shcho@gnome.org>

	Update Korean translation

2018-08-28  Carlos Garnacho  <carlosg@gnome.org>

	ontologies: Drop cardinality from legalese properties
	nie:copyright and nie:license were single valued and subproperties of the
	common single valued properties nie:legal and dc:rights. Drop cardinality
	restrictions on all of those, so we can have multiple values for each.

	This happens to be in line with the last ever version of NIE ontology.

	Closes: https://gitlab.gnome.org/GNOME/tracker/issues/33

2018-08-26  Kukuh Syafaat  <kukuhsyafaat@gnome.org>

	Update Indonesian translation

2018-08-16  Sam Thursfield  <sam@afuera.me.uk>

	Merge branch 'sam/domain-rules-outside-usr'
	See https://gitlab.gnome.org/GNOME/tracker/merge_requests/14

	Merge branch 'sam/tracker-sparql-connection-set-dbus-connection'
	See https://gitlab.gnome.org/GNOME/tracker/merge_requests/14