1 |
Hey Matt, |
2 |
|
3 |
|
4 |
|
5 |
On Thu, May 26, 2016 at 1:12 AM, Matt Turner <mattst88@g.o> wrote: |
6 |
> Is tatt usable for anyone? Both the 0.3 and 9999 versions seem to hang |
7 |
> after printing the Bugnumber: |
8 |
|
9 |
I was using it successfully a few months ago, when I was actively |
10 |
doing arch testing. So something recently may have broken it. |
11 |
|
12 |
> # tatt -b 576112 |
13 |
> Bugnumber: 576112 |
14 |
> |
15 |
> CTRL+C gives this traceback: |
16 |
> |
17 |
> ^CTraceback (most recent call last): |
18 |
> File "/usr/lib/python-exec/python3.4/tatt", line 135, in <module> |
19 |
> bugraw = p1.communicate()[0].decode('utf-8') |
20 |
> File "/usr/lib/python3.4/subprocess.py", line 947, in communicate |
21 |
> stdout = _eintr_retry_call(self.stdout.read) |
22 |
> File "/usr/lib/python3.4/subprocess.py", line 491, in _eintr_retry_call |
23 |
> return func(*args) |
24 |
> KeyboardInterrupt |
25 |
> |
26 |
> I've asked multiple times in #gentoo-dev, but the lack of responses |
27 |
> indicates to me that no one actually uses it which would be a shame. |
28 |
> If it is indeed broken, perhaps we should remove mentions of it from |
29 |
> pages such as [1]. |
30 |
> |
31 |
> Does anyone successfully use tatt? Are there alternatives to scripting |
32 |
> this boring keywording procedure? |
33 |
|
34 |
I dont know of any other alternatives, but I will set tatt up on my |
35 |
new machine and let you know if I run into the same issues. |
36 |
|
37 |
> [1] https://wiki.gentoo.org/wiki/Arch_testing_guide#tatt |
38 |
> |