Using the img raspbian-stretch_Picroft_2018-09-12.img on an RPi 3B+ with the AIY Voice Kit. In auto_run.sh, if AIY is selected, the script calls
sudo apt-get install aiy-python-wheels
This fails on the error
protobuf-3.6.1-cp35-cp35m-linux_armv6.1 is not a supported wheel on this platform
Is this a Google issue or a Mycroft one? Is there a workaround? I don’t think Mycroft requires protocol buffers!
I hassnt seen that issue on my installs. But I know that it isnt that well made the AIY part (i did that part)
What do work for me is using a script I made which installs everything that is needed.
Instaling the picroft strech image
ssh into picroft by ssh pi@picroft
Exit auto_run.sh by Ctrl+C and run these commands to install google AIY
Just saw same error
protobuf-3.6.1-cp35-cp35m-linux_armv6.1 is not a supported wheel on this platform
when i did do an sudo apt-get update and apt-get upgrade. There were a lot of google stuff beeing updatet.
It didnt break my installations, anf the AIY is still working, but it seems there is something going on with the google stuff.
Thanks andlo, your script is working. I’ve also raised this in the AIY projects raspbian group as issue 526. Their response so far is
Thanks for reporting this. Technically this wheel is compatible and should work on RPi 3B+ but looks like pip is not happy about its name. Please use our SD card image if possible, it should work on any Pi board.
I don’t have an AIY kit, so just ventilating some ideas here;
sudo apt-get -y install aiy-python-wheels
Isn’t this command perhaps change the /etc/pip.conf to add/remove/change the location of where to get wheels from? I believe the picroft image has added the piwheels repository
You can change / override certain things via /etc/pip.conf (https://pip.pypa.io/en/stable/user_guide/) perhaps a (quick) fix lies in changing the config file to grab that certain protobuf-3.6.1 package from piwheels instead (forcing it baqck if aiy-wheels had changed it)
quote from the pip manual; “Command line options have precedence over environment variables, which have precedence over the config file.”
Again, no AIY here, so just sucking some stuff out of my big thumb. To me it looks like the debian package; aiy-wheels install some preset wheels or wheel location overriding the one configured from piwheels in /et/pip/conf
Forcing it back, or somehow blacklist the protobuf again might fix it.
Hence, perhaps protobuf was not yet included within the aiy-wheels debian package before and they did now in the last update.
that sounds right. What I did were just not to install the aiy-python-wheels, and my AIY kit works fine whitout it.
And truly i dont know what the aiy-python-wheels or python-wheels does.
Can yo explain what it does and why it maybe is needed ?
I believe that question is for someone that installed the aiy-python-wheels package right? Not me, because I have no clue what the package does or installs