2017-09-29  Carlos Garnacho  <carlosg@gnome.org>

	Release 1.12.4

2017-09-29  Sam Thursfield  <sam.thursfield@codethink.co.uk>

	libtracker-sparql: Introspection fix for tracker_notifier_new()
	The tracker_notifier_new() function allows NULL for 'classes'.

2017-09-29  Sam Thursfield  <sam@afuera.me.uk>

	libtracker-sparql: Fix introspection for Tracker.Notifier.new()
	The 'classes' parameter wasn't annotated correctly.

2017-09-29  Carlos Garnacho  <carlosg@gnome.org>

	applications: Ignore broken symlinks
	We still do need to query mtime from the symlink itself in order to keep
	filesystem accounting happy, so wait for ENOENT while doing
	g_key_file_load_from_file() in order to figure out we are dealing with
	a broken link (or a no longer existing file, which is also possible). This
	avoids spewing any warnings with those.

	https://bugzilla.gnome.org/show_bug.cgi?id=786132

	tracker-miner-fs: Explicitly ignore non-native mounts
	tracker-miner-fs does rely in a few places to index local content
	exclusively. Make it explicitly ignore non-native mounts, they won't
	be indexed anyway, but we can spare trying to create the tracker:Volume
	and mount root's nfo:FileDataObject for these.

	Fixes nie:url constraint errors and other warnings when trying to deal
	with those.

	https://bugzilla.gnome.org/show_bug.cgi?id=786132

	libtracker-miner: Always fallback to URN query when queueing file
	Tracker may end up with nfo:FileDataObject prior to handling monitor
	events. Be it leftover data from previous bugs, explicit "tracker index"
	calls, or data from some other application.

	As we can't be really sure of the data consistence, always fallback to
	a URN query so we don't break nie:url UNIQUE constraint (inverse functional
	property in SPARQL parlance).

	https://bugzilla.gnome.org/show_bug.cgi?id=786132

	libtracker-miner: Check directory updates before dropping mtime info
	file_notifier_traverse_tree() has the side effect of deleting mtime data,
	as it's presumably not needed anymore, except here. Check whether the
	directory was updated before notifying of the files inside, so we can
	thoroughly check for deleted content.

	https://bugzilla.gnome.org/show_bug.cgi?id=786132

	libtracker-miner: Use TrackerDecorator variable after checking cancellable
	It may be actually destroyed if the decorator was cancelled.

	https://bugzilla.gnome.org/show_bug.cgi?id=785701

	libtracker-miner: Set up cancellable for TrackerDecorator internal ops
	Those must be cancelled if the TrackerDecorator gets destroyed.

	libtracker-miner: Ensure sparql buffer keeps flushing
	The sparql buffer might get full again with new tasks before the
	update_array operation for the current batch returned. In this case
	nothing will kick the TrackerMinerFS again, nor the SPARQL buffer
	from flushing again. Fix this by just flushing again, the miner
	will follow as soon as the SPARQL buffer is below limits.

	libtracker-miner: Fix warnings if move ops happened during initial crawling
	The checks to notify about indexing having finished on TrackerIndexingTree
	roots were mistaking ItemMovedData* with GFile*, which lead to warnings.
	This should be harmless, the signal might be possibly emitted before the
	move op is dispatched, that's all.

	libtracker-miner: Shuffle refcount handling when queueing back a file
	The file might or might not be inserted to the queue, which meant that
	the extra ref created outside the call might never dropped if the file
	didn't end up inserted again. Fix this by doing the refcount increase
	when actually inserting the file back in the queue.

	Reported by Jose M. Arroyo <jose.m.arroyo.se@gmail.com>.

2017-09-27  Matej Urbančič  <mateju@svn.gnome.org>

	Slovenian update ...

2017-09-21  Debarshi Ray  <debarshir@gnome.org>

	tracker-extract: Fix insertion of white balance values
	https://bugzilla.gnome.org/show_bug.cgi?id=787774