slash sign is not indexed/searched properly

Bug #893070 reported by Wojciech Semik on 2011-11-21
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bzr search plugin

Bug Description

Slash sign '/' in bzr comments seems to be not properly indexed/searched.
bazaar version: 2.1.4
bzr-search version: 1.7.0~bzr77-1
os: Ubuntu 10.04

Replication path:
user@comp:~/temp/aabzr$ bzr init
Created a standalone tree (format: 2a)
user@comp:~/temp/aabzr$vim test.txt
"test.txt" [New] 1L, 67C written
user@comp:~/temp/aabzr$ bzr add test.txt
adding test.txt
user@comp:~/temp/aabzr$ bzr commit -m "Error ERR/313 resolved"
Committing to: /home/user/temp/aabzr/
added test.txt
Committed revision 1.
user@comp:~/temp/aabzr$ bzr log
revno: 1
committer: user <email address hidden>
branch nick: aabzr
timestamp: Mon 2011-11-21 12:40:00 +0100
  Error ERR/313 resolved
user@comp:~/temp/aabzr$ bzr index
user@comp:~/temp/aabzr$ bzr search "ERR/313"
bzr: ERROR: No matches were found for the search [u'ERR/313'].
user@comp:~/temp/aabzr$ bzr search "313"
Revision id '<email address hidden>'. Summary: 'Error ERR/313 resolved'

Jelmer Vernooij (jelmer) on 2012-03-22
Changed in bzr-search:
status: New → Confirmed

ERR/313 should be tokenised into (ERR, 313) and then those indexed
separately. The search for 313 working suggests that the index is ok.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers