Summary: | app-portage/esearch keywording | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Paul Varner (RETIRED) <fuzzyray> |
Component: | Third-Party Tools | Assignee: | Portage Tools Team <tools-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | Keywords: | KEYWORDREQ |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 253176, 253177 |
Description
Paul Varner (RETIRED)
2008-12-30 18:40:57 UTC
Few issues on amd64: -Every package shows: Size of downloaded files: [no/bad digest] -The -e flag is messed up: # esearch -e esearch Traceback (most recent call last): File "/usr/bin/esearch", line 322, in <module> searchEbuilds("%s/%s/" % (portdir, pkg[1]), True, searchdef, "") File "/usr/bin/esearch", line 88, in searchEbuilds pkgs[-1].append(path + file) AttributeError: 'tuple' object has no attribute 'append' -bug 231223 is not fixed with the -v flag # esearch -v esearch /usr/lib/portage/pym/output.py:39: DeprecationWarning: DEPRECATION NOTICE: The output module was replaced by portage.output I hate to be critical, but did this get any testing? It did get testing late at night against the bugs where patches were applied. I just caught the deprecation notice with -v as well. Can you please re-keyword 0.7.1 unstable, since I obviously need to do more work before we can get another version stable? 0.7.1 is broken much worse than this version and I would prefer not having a stable version to having a broken stable version. reverted 0.7.1 down to ~amd64 per request. After discussion on IRC, we decided to just package mask esearch-0.7.1. Users can either switch to the unstable version of esearch or convert over to app-portage/eix |