Bug 304313 – app-portage/esearch: traceback with invalid (regex) search pattern rather than pretty error message

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Florian CROUZAT (SuperFlo) 2010-02-10 13:01:03 UTC]

esearch (0.7.1) fails and prints out python when pattern is like '*<more_than_two_letters>*'

Reproducible: Always

Steps to Reproduce:
1. emerge app-portage/esearch-0.7.1-r7
2. run `esearch *foo*'

Actual Results:  
Traceback (most recent call last):
  File "/usr/bin/esearch", line 195, in <module>
    regexlist.append([re.compile(pattern, re.IGNORECASE), pattern, "", 0])
  File "/usr/lib/python2.6/re.py", line 190, in compile
    return _compile(pattern, flags)
  File "/usr/lib/python2.6/re.py", line 245, in _compile
    raise error, v # invalid expression
sre_constants.error: nothing to repeat

[Comment 1 Florian CROUZAT (SuperFlo) 2010-06-08 18:25:42 UTC]

Actually, esearch fails when you add a leading *, e.g: esearch '*foo' cause esearch to crash, when esearch 'foo*' works fine.

[Comment 2 Paul Varner (RETIRED) 2011-07-22 06:07:11 UTC]

This will be fixed in the next release.

[Comment 3 Paul Varner (RETIRED) 2011-07-22 19:03:06 UTC]

Released in esearch-0.7.2