2014-10-16 Martyn Russell <martyn@lanedo.com> all: Switch out GSettings "schema" property for "schema-id" Was causing unit tests to fail and made distcheck impossible 2014-10-16 Aleksander Morgado <aleksander@lanedo.com> tests,libtracker-fts: use a more generic test string for chinese parser tests Instead of a made up string, which doesn't have any true meaning, and which makes libicu and libunistring differ on the number of words found, use a simpler sentence... https://bugzilla.gnome.org/show_bug.cgi?id=699412 2014-10-16 Martyn Russell <martyn@lanedo.com> libtracker-miner: Don't fail unit tests with newer GLib on GSource API GLib complains now if you try to remove a GSource ID that doesn't exist. The critical means that tests can fail where before they wouldn't have. This fixes distcheck. 2014-10-15 Martyn Russell <martyn@lanedo.com> tracker-extract: Remove the need for fork() and sub-processes with PDF extraction This fuctionality we're removing has been around since be58d8da6da5a8f16ca83f78a9427ca4de723151 where Philip added code to kill a forked process after n seconds for really complex PDFs (or PDFs that take longer to process on embedded devices). This was covered under NB#290406. Later I improved the code to use select() instead of signal handlers due to IO blocking in some situations in commit 9c4e166ec101c79bdeac30696371ffe0abd4e046 and as part of GB#680897. However, the extra complexity is no longer needed as far as I can tell. There was a good reason for the IO blocking in the past and I believe it has been fixed by Carlos in one commit or another and with the new GTask and _run_in_thread() APIs we have now, it's unnecessary to use this approach. IF anything, we should add some timeout or cancellation in the task issuing (main?) thread instead of implementing this for each extractor. Currently we don't do this though. As an additional note, this may fix GB#726421. I've tested this patch with files attached to previous bug reports related, including GB#680897 and GB#685378. 2014-10-14 Debarshi Ray <debarshir@gnome.org> libtracker-data: Guard against failure to create a FTS update statement https://bugzilla.gnome.org/show_bug.cgi?id=738522 2014-10-13 Debarshi Ray <debarshir@gnome.org> libtracker-data: Be more explicit in the error message Add the sqlite3_errstr() to the error that is propagated from sqlite3_open_v2 so that we have a clearer picture of the failure. https://bugzilla.gnome.org/show_bug.cgi?id=738450 libtracker-data: Guard against invalid statements in public API https://bugzilla.gnome.org/show_bug.cgi?id=738450 libtracker-data: Guard against failure to open the database An error from sqlite3_open_v2 will lead to a failure to create a TrackerDBInterface. This means that DBManager.get_db_interface will fail. https://bugzilla.gnome.org/show_bug.cgi?id=738450 2014-10-02 Debarshi Ray <debarshir@gnome.org> libtracker-miner: Keep the crawler alive across async calls The EnumeratorData held a reference to TrackerCrawler while enumerating. Just before closing the enumerator we destroy the EnumeratorData and drop the reference. This can lead to TrackerCrawler getting destroyed. To prevent this, grab a new reference before dropping the older one and keep it till the asynchronous call is alive. https://bugzilla.gnome.org/show_bug.cgi?id=737769 libtracker-miner: Ensure that the async function uses owned data ... and simplify parent directory tracking. The GFileEnumerator keeps a reference to the directory that is being traversed, so we don't need to keep track of it ourselves. https://bugzilla.gnome.org/show_bug.cgi?id=737768 2014-05-28 Tim Lunn <tim@feathertop.org> tracker-miner-manager: don't run main_loop if fail to find datadir https://bugzilla.gnome.org/show_bug.cgi?id=729449 2014-03-15 Claude Paroz <claude@2xlibre.net> Updated French translation 2014-02-22 Gil Forcada <gforcada@gnome.org> [l10n] Update Catalan translation 2014-01-05 Wylmer Wang <wantinghard@gmail.com> Update Chinese simplified translation 2014-01-04 Marek Černocký <marek@manet.cz> Updated Czech translation 2014-01-03 Dimitris Spingos <dmtrs32@gmail.com> Updated Greek translation 2014-01-02 Christian Kirbach <christian.kirbach@gmail.com> Updated German translation 2013-12-03 Carlos Garnacho <carlosg@gnome.org> fts: Strengthen against sqlite failures in FTS functions function_weights() and function_property_names() (used respectively by SPARQL fts:rank and fts:offsets functions), initialize all data at first from the database, so it's available in memory for posterior runs, although currently those are being quite optimistic about the database return values in several ways, so: - Ensure no infinite loops happen on sqlite3_step() if the stmt trips into some unexpected state. SQLITE_BUSY still does keep looping though. - As initialization here is a failable task, stop using g_once_init_* and use an static GMutex so initialization can be tried later again if it failed previously. - For the cases where initialization failed, propagate the error code on the sqlite3_context. Based on work by Tim Waugh and Michael Catanzaro. https://bugzilla.redhat.com/show_bug.cgi?id=1026283 2013-11-28 Fran Diéguez <fran.dieguez@mabishu.com> Updated Galician translations 2013-11-28 Sam Thursfield <sam.thursfield@codethink.co.uk> build: Add SQLite 3.8.1 to list of bad SQLite versions There is a bug in SQLite version 3.8.1 which causes incorrect query results. See the following links for more details: https://mail.gnome.org/archives/tracker-list/2013-November/msg00021.html https://bugzilla.redhat.com/show_bug.cgi?id=1034714 The bug is fixed in SQLite master already so version 3.8.2 should be fine to use. 2013-11-23 Carlos Garnacho <carlosg@gnome.org> miner-fs: initialize timers as stopped This way timers are in agreement with their boolean guards, and will get continued when processing actually starts.