| 1 |
Is tatt usable for anyone? Both the 0.3 and 9999 versions seem to hang |
| 2 |
after printing the Bugnumber: |
| 3 |
|
| 4 |
# tatt -b 576112 |
| 5 |
Bugnumber: 576112 |
| 6 |
|
| 7 |
CTRL+C gives this traceback: |
| 8 |
|
| 9 |
^CTraceback (most recent call last): |
| 10 |
File "/usr/lib/python-exec/python3.4/tatt", line 135, in <module> |
| 11 |
bugraw = p1.communicate()[0].decode('utf-8') |
| 12 |
File "/usr/lib/python3.4/subprocess.py", line 947, in communicate |
| 13 |
stdout = _eintr_retry_call(self.stdout.read) |
| 14 |
File "/usr/lib/python3.4/subprocess.py", line 491, in _eintr_retry_call |
| 15 |
return func(*args) |
| 16 |
KeyboardInterrupt |
| 17 |
|
| 18 |
I've asked multiple times in #gentoo-dev, but the lack of responses |
| 19 |
indicates to me that no one actually uses it which would be a shame. |
| 20 |
If it is indeed broken, perhaps we should remove mentions of it from |
| 21 |
pages such as [1]. |
| 22 |
|
| 23 |
Does anyone successfully use tatt? Are there alternatives to scripting |
| 24 |
this boring keywording procedure? |
| 25 |
|
| 26 |
[1] https://wiki.gentoo.org/wiki/Arch_testing_guide#tatt |
Archives