lp:tracker

Created by Jelmer Vernooij on 2010-01-26 and last modified on 2015-02-05
Get this branch:
bzr branch lp:tracker

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
VCS imports
Project:
Tracker
Status:
Development

Import details

Import Status: Failed

This branch is an import of the HEAD branch of the Git repository at git://git.gnome.org/tracker.

The import has been suspended because it failed 5 or more times in succession.

Last successful import was on 2015-02-07.

Import started on 2015-02-11 on pear and finished on 2015-02-11 taking 25 seconds — see the log
Import started on 2015-02-09 on pear and finished on 2015-02-09 taking 20 seconds — see the log
Import started on 2015-02-08 on pear and finished on 2015-02-08 taking 15 seconds — see the log
Import started on 2015-02-08 on pear and finished on 2015-02-08 taking 15 seconds — see the log

Recent revisions

9131. By Martyn Russell on 2015-02-05

Release 1.3.3

9130. By Martyn Russell on 2015-02-05

Merge tag 'fix-discno' of git://git.meterriblecrew.net/spacefrogg/tracker

Fixed parsing disc number in vorbis comments.

This fixes:
https://bugzilla.gnome.org/show_bug.cgi?id=681698

* tag 'fix-discno' of git://git.meterriblecrew.net/spacefrogg/tracker:
  Fixed parsing disc number in Vorbis comments.

9129. By Mingxiang Lin <paralmx@163.com> on 2015-02-05

tracker-extract: Add width and height information to BMP extractor

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

9128. By Yanko Kaneti on 2015-01-26

Mechanically adjust for libmediaart-2.0

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

9127. By Dimitris Spingos on 2015-01-17

Updated Greek translation

9126. By Debarshi Ray <email address hidden> on 2015-01-13

libtracker-miner: Restrict the amount of data that is logged for errors

SPARQL update strings can be very long if the entire text of a document
is being stored. Dumping these huge strings to the log eats up disk
space and makes them harder to follow.

However, often, the occurence of such an error indicates a broken
extractor. In those cases, knowing part of the SPARQL can help in
identifying the file that triggered the error.

Usually the "nie:plainTextContent" property is the last one in the
string, so we truncate the error messages at the first occurance of
this property to achieve the best of both worlds.

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

9125. By Fran Diéguez on 2015-01-12

Updated Galician translations

9124. By Iñaki Larrañaga Murgoitio on 2015-01-08

Updated Basque language

9123. By Debarshi Ray <email address hidden> on 2015-01-05

miners: Detect locale changes only when the miner could be constructed

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

9122. By Sam Thursfield on 2014-12-31

miner-fs: Give clearer warning when XDG user dirs are unconfigured

If Tracker can't resolve special dirs like &DOCUMENTS to real path
names, it now gives a warning like this:

    (tracker-miner-fs:7207): Tracker-WARNING **: Unable to get XDG user
    directory path for special directory &DOCUMENTS. Ignoring this
    location.

Previously (since commit 5f06c134f4f6da02027c813322e13c220b51cd0a) the
user would see this rather more scary output:

    (tracker-miner-fs:6046): GLib-GIO-CRITICAL **: g_file_new_for_path:
    assertion 'path != NULL' failed

    (tracker-miner-fs:6046): GLib-GIO-CRITICAL **: g_file_equal: assertion
    'G_IS_FILE (file1)' failed

    (tracker-miner-fs:6046): GLib-GObject-CRITICAL **: g_object_unref:
    assertion 'G_IS_OBJECT (object)' failed

This situation is rare (you need to manually change or break
XDG_CONFIG_HOME to really see it) but it's always nice to avoid showing
critical errors!

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.

Subscribers