中文 
o***[email protected]
deepin
2018-03-29 12:58 deepin As a little solution
I have delete the Apt of Spotify
I have delete the Apt of Spotify
Reply Like 0 View the author
All Replies
#1
deepak_hatkar
deepin
2018-03-29 20:07 deepin I too have deleted the Spotify Apt Repository.
Go to Deepin Files -> System Disk -> etc -> apt -> sources.list.d -> delete the Spotify apt.
Go to terminal and update again. You shouldn't see the error.
Go to Deepin Files -> System Disk -> etc -> apt -> sources.list.d -> delete the Spotify apt.
Go to terminal and update again. You shouldn't see the error.
Reply Like 0 View the author
s***[email protected]
deepin
2018-08-22 03:53 deepin https://bbs.deepin.org/post/154754
I too have deleted the Spotify Apt Repository.
Go to Deepin Files -> System Disk -> etc -> apt -> so ...
You Are Right
Reply Like 0 View the author
Please sign in first
Rankings
- 7 days
- 30 days
- 90 days
Popular Events
More
I type in terminal:
sudo apt-get update
[sudo] Mot de passe de Xeon :
Atteint:1 https://deepin-fr.org/mirror panda InRelease
Réception de:2 http://repository.spotify.com stable InRelease [3 302 B]
Ign:2 http://repository.spotify.com stable InRelease
3 302 o réceptionnés en 2s (1 218 o/s)
Lecture des listes de paquets... Fait
W: Erreur de GPG : http://repository.spotify.com stable InRelease : Les signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY EFDC8610341D9410
W: The repository 'http://repository.spotify.com stable InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.