[gentoo-dev] app-portage/tatt: completely broken?

[Matt Turner <mattst88@gentoo.org>]

Is tatt usable for anyone? Both the 0.3 and 9999 versions seem to hang
after printing the Bugnumber:

# tatt -b 576112
Bugnumber:  576112

CTRL+C gives this traceback:

        ^CTraceback (most recent call last):
  File "/usr/lib/python-exec/python3.4/tatt", line 135, in <module>
    bugraw = p1.communicate()[0].decode('utf-8')
  File "/usr/lib/python3.4/subprocess.py", line 947, in communicate
    stdout = _eintr_retry_call(self.stdout.read)
  File "/usr/lib/python3.4/subprocess.py", line 491, in _eintr_retry_call
    return func(*args)
KeyboardInterrupt

I've asked multiple times in #gentoo-dev, but the lack of responses
indicates to me that no one actually uses it which would be a shame.
If it is indeed broken, perhaps we should remove mentions of it from
pages such as [1].

Does anyone successfully use tatt? Are there alternatives to scripting
this boring keywording procedure?

[1] https://wiki.gentoo.org/wiki/Arch_testing_guide#tatt