app-portage/esearch is no longer being maintained upstream and parts of the current stable, esearch-0.7.1 are broken with portage 2.1.6. Even though it is no longer maintained, I am keeping it around since it still functions fine (with some patches) and is a usable utility. I added esearch-0.7.1-r5 which fixes the known problems with portage 2.1 and 2.2 last night to the tree. Arch teams, would you please either mark esearch-0.7.1-r5 stable or re-keyword esearch-0.7.1 to unstable so that I can get it removed from the tree.
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
