Automatic Installation doesn't work.

[sdetweil]

@doyoun0913 yes, the official.installer has a bug, use the development version

see

https://forum.magicmirror.builders/topic/10171/updated-installer-script-available-for-testing

[doyoun0913]

@sdetweil Oh really? Since when did it had a bug?

[sdetweil]

@doyoun0913 from the 1st moment… it hangs at the apt-get upgade on some systems
(because the darned thing prompts, but I have saved stdin and stdout, so u never see the prompt)

the updater also has a bug… so much fun

[doyoun0913]

@sdetweil So I ran the command that you had for the developer version and realized that I still have the old, dangling installation I did previously (the official installer that I had to force-stop). So I got this error message as expected:
Now, can I just remove the lock which is traditionally not recommended with sudo rm /var/lib/apt/lists/lock?

[doyoun0913]

@doyoun0913 Actually, nevermind. I did type these: sudo rm /var/cache/apt/archives/lock, sudo rm /var/lib/dpkg/lock, followed by sudo dpkg --configure -a and sudo apt install -f.
The thing is after I launched your script, I get struck by another error message looks like this:

What is the problem?

[sdetweil]

@doyoun0913 the dpkg stuff got left in a mess.

See here
https://unix.stackexchange.com/questions/78004/error-while-using-apt-get-install-for-any-package

I think it’s dpkg --configure - a

[doyoun0913]

@sdetweil This leads to another problem…

I already have searched this issue in the past; I think something is wrong with Google itself possibly. This is the source: Setting up aiy-python-wheels: protobuf not supported on armv6.1 #526

[sdetweil]

@doyoun0913 sorry. I have no idea

[doyoun0913]

@sdetweil All good! I forgot to post that I figured it out. Thank you for your help :)

[sdetweil]

@doyoun0913 what did u end up doing? and then did u redo the script install?