Blender is ready at D11060.

Hexchat is now tested and ready to be merged

@ReillyBrogan, thanks, appreciated :)

FYI: Don't bother with tensorflow, I need to update libicu to 69.1 for Firefox 91 and tensorflow is a libicu rebuild.

Do want to raise the question whether or not we should deprecate mycroft-core and its associated dependencies (that have no other revdeps). It isn't being maintained by @clivejo and as far as I know never properly worked to begin with. Seeing as it was last touched (by @livingsilver94) clear back in 2019, no maintainer or integration in the two years spanning its inclusion isn't good.

@JoshStrobl additionally I tried to build it against py 3.9 and it needs an update to build it

Yea so at this point, unless there is opposition by @clivejo or @livingsilver94 and some commitment to get it updated, should be deprecated instead. I just don't see anyone else coming to the table to get it packaged, just seems like there is little to no incentive for its inclusion (not sure what the usecase would've been in the first place either :P)

W.r.t mycroft deprecation: It's also worth a look through T4276 to see if any other dangling python modules can be deprecated along with it apart from mycroft itself, python-msm and python-msk.

Following packages should be only used by mycroft

• google-api-python-client
• python-uritemplate
• python-requests-futures
• python-vlc
• python-gtts
• python-gtts-token
• python-padatious
• python-xxhash
• python-speech-recognition
• pyalsaaudio
• python-adapt-parser
• python-fann2
• python-pyee
• python-adapt-parser
• python-msk
• python-msm
• python-padaos
• python-petact
• python-pocketsphinx
• python-precise-runner
• python-pulsectl
• python-xmlrunner

Green light from me for the deprecation of Mycroft. I haven't been using it for a long time by now.

I tried building py with the tests re-enabled, but the tests fail. There are a few newer versions available, but then our patches fail to apply, and trying it without the patch also fails immediately. Looking at this PR, they simply say that it's not compatible with newer versions of pytest. Soo, not sure where we want to go from here.

It's okay we can disable the tests for now. Should probably also update since we're looking at it.

In T9866#187290, @joebonrichie wrote:

It's okay we can disable the tests for now. Should probably also update since we're looking at it.

Sounds good. I'll get on it. :)

Also as a note, the work done for py is also resulting in doing python-tox, and maybe virtualenv.

In T9866#187218, @JoshStrobl wrote:

Yea so at this point, unless there is opposition by @clivejo or @livingsilver94 and some commitment to get it updated, should be deprecated instead. I just don't see anyone else coming to the table to get it packaged, just seems like there is little to no incentive for its inclusion (not sure what the usecase would've been in the first place either :P)

No objections here, I can't get it to work with tensorflow. I don't know if it just my specific hardware or tensorflow is broken.

Some poor bugger will need to rebuild graph-tool before Friday sync

Just mycroft stuff to be deprecated and anki to be updated now, thanks to everyone who helped resolve any issues in this task! :)

I want to inform you that gtts dont' seams to work properly, I use it with foliate (https://github.com/johnfactotum/foliate/wiki) with the following script :
#!/bin/bash
gtts-cli -l $FOLIATE_TTS_LANG_LOWER --file /dev/stdin | play -t mp3 - &
trap 'kill $!; exit 0' INT
wait

but the same script work if I install gtts from source with pi