[tracker/tracker-0.10] libtracker-miner: Do not ignore DELETED event for IgnoreNextUpdate

[Martyn James Russell <mr src gnome org>]

commit 5ea14ff9c8e30884ebddc8e231abb62a2f2f8f71
Author: Jürg Billeter <j bitron ch>
Date:   Wed Apr 6 12:40:47 2011 +0200

    libtracker-miner: Do not ignore DELETED event for IgnoreNextUpdate
    
    We should never see DELETED on update (atomic rename or in-place
    update) but we may see DELETED due to actual file deletion right
    after update.
    
    Fixes NB#229461.

 src/libtracker-miner/tracker-miner-fs.c |   18 ++++--------------
 1 files changed, 4 insertions(+), 14 deletions(-)
---
diff --git a/src/libtracker-miner/tracker-miner-fs.c b/src/libtracker-miner/tracker-miner-fs.c
index 33453df..bcbf9f8 100644
--- a/src/libtracker-miner/tracker-miner-fs.c
+++ b/src/libtracker-miner/tracker-miner-fs.c
@@ -2370,20 +2370,10 @@ item_queue_get_next_file (TrackerMinerFS  *fs,
 
 		trace_eq_pop_head ("DELETED", queue_file);
 
-		/* TODO: Really check whether this makes sense... do
-		 * we really need to fully ignore the Delete event
-		 * and treat it as a IgnoreNextUpdate? */
-		if (check_ignore_next_update (fs, queue_file)) {
-			gchar *uri;
-
-			uri = g_file_get_uri (queue_file);
-			g_debug ("DELETED event ignored on file '%s', "
-			         " processing as IgnoreNextUpdate...",
-			         uri);
-			g_free (uri);
-
-			return QUEUE_IGNORE_NEXT_UPDATE;
-		}
+		/* Do not ignore DELETED event even if file is marked as
+		   IgnoreNextUpdate. We should never see DELETED on update
+		   (atomic rename or in-place update) but we may see DELETED
+		   due to actual file deletion right after update. */
 
 		/* If the same item OR its first parent is currently being processed,
 		 * we need to wait for this event */