Today I’ve tried to install mopidy on an Odroid Hc4, running latest image version with kernel 4.9.x, and it give me an error.
I sent a bugreport, but I forgot to copy the id.
It was something related with the apt urls signature I think.
Thank you!
Maybe you can try again and copy the error message from SSH terminal.
This is the error:
APT update │
│ - Command: apt-get -q update │
│ - Exit code: 100 │
│ - DietPi version: v8.2.2 (MichaIng/master) | HW_MODEL: 16 | HW_ARCH: 3 | DISTRO: 6 │
│ - Image creator: DietPi Core Team │
│ - Pre-image: Meveric │
│ - Error log: │
│ Hit:1 https://dietpi.com/meveric bullseye InRelease │
│ Hit:2 https://dietpi.com/meveric all InRelease │
│ Hit:3 https://deb.debian.org/debian bullseye InRelease │
│ Hit:4 https://deb.debian.org/debian bullseye-updates InRelease │
│ Hit:5 https://downloads.plex.tv/repo/deb public InRelease │
│ Hit:6 https://deb.debian.org/debian-security bullseye-security InRelease │
│ Hit:7 https://deb.debian.org/debian bullseye-backports InRelease │
│ Get:8 https://apt.mopidy.com buster InRelease [14.1 kB] │
│ Err:8 https://apt.mopidy.com buster InRelease │
│ The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 78FD980E271D2943 │
│ Ign:9 https://download.webmin.com/download/repository sarge InRelease │
│ Hit:10 https://download.webmin.com/download/repository sarge Release │
│ Reading package lists... │
│ W: GPG error: https://apt.mopidy.com buster InRelease: The following signatures couldn't be verified because the │
│ public key is not available: NO_PUBKEY 78FD980E271D2943
pls try following as quick fix before trying again
G_EXEC eval "echo 'deb https://apt.mopidy.com/ ${G_DISTRO_NAME/bullseye/buster} main contrib non-free' > /etc/apt/sources.list.d/mopidy.list"
I am getting the error to.
When i put that, this is the answer:
G_EXEC eval "echo 'deb https://apt.mopidy.com/ ${G_DISTRO_NAME/bullseye/buster} main contrib non-free' > /etc/apt/sources.list.d/mopidy.list"
And the error I think s the same:
│ APT update │
│ - Command: apt-get -q update │
│ - Exit code: 100 │
│ - DietPi version: v8.2.2 (MichaIng/master) | HW_MODEL: 16 | HW_ARCH: 3 | DISTRO: 6 │
│ - Image creator: DietPi Core Team │
│ - Pre-image: Meveric │
│ - Error log: │
│ Ign:1 https://download.webmin.com/download/repository sarge InRelease │
│ Hit:2 https://download.webmin.com/download/repository sarge Release │
│ Hit:4 https://downloads.plex.tv/repo/deb public InRelease │
│ Hit:5 https://dietpi.com/meveric bullseye InRelease │
│ Hit:6 https://dietpi.com/meveric all InRelease │
│ Hit:7 https://deb.debian.org/debian bullseye InRelease │
│ Hit:8 https://deb.debian.org/debian bullseye-updates InRelease │
│ Hit:9 https://deb.debian.org/debian-security bullseye-security InRelease │
│ Hit:10 https://deb.debian.org/debian bullseye-backports InRelease │
│ Get:11 https://apt.mopidy.com buster InRelease [14.1 kB] │
│ Err:11 https://apt.mopidy.com buster InRelease │
│ The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 78FD980E271D2943 │
│ Reading package lists... │
│ W: GPG error: https://apt.mopidy.com buster InRelease: The following signatures couldn't be verified because the │
│ public key is not available: NO_PUBKEY 78FD980E271D2943 │
│ E: The repository 'https://apt.mopidy.com buster InRelease' is not signed.
Are you sure that you get the same message back as you put in?
G_EXEC eval “echo ‘deb https://apt.mopidy.com/ ${G_DISTRO_NAME/bullseye/buster} main contrib non-free’ > /etc/apt/sources.list.d/mopidy.list”
Can you do the following:
cat /etc/apt/sources.list.d/mopidy.list
And Mopidy suggest in their documentation to add the key like this:
wget -q -O - https://apt.mopidy.com/mopidy.gpg | sudo apt-key add -
This is only a temporary solution bc I guess there is another reason why the key is missing in DietPi ootb?!
The key is not missing. But Mopidy changed the source file configuration and is expecting the key being available within a specific place. This is what we need to adjust on next release. For now, the workaround would be to change source file in a way it will work with current key setup.
amibumpin
once you hit by the error, you should see some options on the bottom of the screen. There you can open an additional command shell. Just do this and execute following
G_EXEC eval "echo 'deb https://apt.mopidy.com/ ${G_DISTRO_NAME/bullseye/buster} main contrib non-free' > /etc/apt/sources.list.d/mopidy.list"
This should overwrite the source file and create the one we use as workaround. Once done, exit the sub shell and retry on the error screen.
The key is not missing. But Mopidy changed the source file configuration and is expecting the key being available within a specific place. This is what we need to adjust on next release. For now, the workaround would be to change source file in a way it will work with current key setup.
@amibumpin
once you hit by the error, you should see some options on the bottom of the screen. There you can open an additional command shell. Just do this and execute following
G_EXEC eval "echo 'deb https://apt.mopidy.com/ ${G_DISTRO_NAME/bullseye/buster} main contrib non-free' > /etc/apt/sources.list.d/mopidy.list"
This should overwrite the source file and create the one we use as workaround. Once done, exit the sub shell and retry on the error screen.
Ok will try later that last option.
Thank you Joulinar, and glad to find something that can be fixed!
Thank you DietPi
the fix might be provided with upcoming release and this will take additional 2 weeks (at least)
Usually it should have been working this way as I tested it on my demo system without issue. Can you try to install Mopidy again and share the entire output (full log)
the fix might be provided with upcoming release and this will take additional 2 weeks (at least)
Usually it should have been working this way as I tested it on my demo system without issue. Can you try to install Mopidy again and share the entire output (full log)
Joulinar, I test it today, and it worked.
Thank you!
ok perfect. thx for sharing the good feedback.