Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 737408

Summary: app-portage/esearch-1.3-r2 - single quote character transformed incorrectly to esearchdb.py
Product: Gentoo Linux Reporter: Daniel Rozsnyo <daniel>
Component: Current packagesAssignee: Portage Tools Team <tools-portage>
Status: RESOLVED DUPLICATE    
Severity: normal CC: daniel
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Daniel Rozsnyo 2020-08-16 10:06:42 UTC
One package in portage tree causes the /var/cache/edb/esearchdb.py corruption. This applies both for lookups using esearch TEXT, and to eupdatedb. Likely an eupdtedb bug, when the meta information is transformed to esearchdb.py file and the double backslashes are generated for some reason before a single quote.

Traceback (most recent call last):
  File "/usr/lib/python-exec/python3.7/eupdatedb", line 5, in <module>
    main()
  File "/usr/lib/python3.7/site-packages/esearch/update.py", line 268, in main
    success = updatedb(config)
  File "/usr/lib/python3.7/site-packages/esearch/update.py", line 242, in updatedb
    import esearchdb # import the file, to generate pyc
  File "/var/cache/edb/esearchdb.py", line 4457
    ('time-compat', 'dev-haskell/time-compat', True, '1.9.3', False, '48 kB', 'https://github.com/phadej/time-compat', 'This packages tries to compat as much of \\'time\\' features as possible', 'BSD'),
                                                                                                                                                                       ^
SyntaxError: invalid syntax


Fixing the esearchdb.py file and changing \\' to \' manually on the two locations fixes the issue.
Comment 1 Zac Medico gentoo-dev 2020-08-16 18:29:48 UTC
Planning to remove app-portage/esearch with emerge --search as replacement. See bug 735622.
Comment 2 Zac Medico gentoo-dev 2020-08-16 20:39:42 UTC

*** This bug has been marked as a duplicate of bug 670224 ***