Hi,

On 26/05/16 02:12, Matt Turner wrote:
> 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

Sorry, maintenance of tatt has more or less stalled since I'm not
doing any archtesting myself anymore.  I'll investigate, but as
I've expressed before, I'd be very happy if somebody else would
want to take over maintenance.

> 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].

I'm not following IRC, please use bugzilla or the issue tracker
here https://github.com/tom111/tatt to report bugs.

Cheers,
Thomas

> Does anyone successfully use tatt? Are there alternatives to scripting
> this boring keywording procedure?
> 
> [1] https://wiki.gentoo.org/wiki/Arch_testing_guide#tatt
> 

-- 
Thomas Kahle
http://dev.gentoo.org/~tomka/