iobroker zeschossen
-
krisiun@Marek2:/root$ sudo apt update Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:3 http://security.ubuntu.com/ubuntu jammy-security InRelease Get:4 https://dl.yarnpkg.com/debian stable InRelease [17.1 kB] Hit:5 http://archive.ubuntu.com/ubuntu jammy-backports InRelease Hit:6 https://deb.nodesource.com/node_18.x nodistro InRelease Err:4 https://dl.yarnpkg.com/debian stable InRelease The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx> Err:6 https://deb.nodesource.com/node_18.x nodistro InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4 Fetched 17.1 kB in 4s (4719 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done 1 package can be upgraded. Run 'apt list --upgradable' to see it. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx> W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://deb.nodesource.com/node_18.x nodistro InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4 W: Failed to fetch https://deb.nodesource.com/node_18.x/dists/nodistro/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4 W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx> W: Some index files failed to download. They have been ignored, or old ones used instead. -
-
@thomas-braun
Dann sag mir bitte, bitte wie? Sorry aber das ist mir auch schon unangenehm dass ich das nicht schnalle -
Dann
sudo rm `sudo find / -name nodesource.gpg` sudo rm `sudo find / -name nodesource.key` sudo apt install -y ca-certificates curl gnupg sudo mkdir -p /etc/apt/keyrings curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg sudo apt update -
@krisiun sagte in iobroker zeschossen:
Dann sag mir bitte, bitte wie?
Steht doch da.
sudo rm /etc/apt/sources.list.d/yar* -
@thomas-braun
Ich bin dabei aber ich kanns nicht finden -
-
@thomas-braun
wo ich das löschen kann -
@krisiun sagte in iobroker zeschossen:
Ich bin dabei aber ich kanns nicht finden
Du sollst da nichts finden.
Sondern dich per putty (oder was du auch immer nimmst) einloggen.
Und dann in der konsole den Befehl eingeben.Mehr nicht.
-
MIT DEM BEFEHL:
sudo rm /etc/apt/sources.list.d/yar*Klickst du da mit einem Filebrowser wild durch die Gegend? Lass das!
-
krisiun@Marek2:/root$ sudo rm /etc/apt/sources.list.d/yar* rm: cannot remove '/etc/apt/sources.list.d/yar*': No such file or directory krisiun@Marek2:/root$ -
@thomas-braun
Ist wohl wieder falsch? -
cd ls -lAh /etc/apt/sources.list.d/ -
krisiun@Marek2:/root$ ls -lAh /etc/apt/sources.list.d/ total 0 -rw-r--r-- 1 root root 100 Oct 8 21:12 nodesource.list -rw-r--r-- 1 root root 202 Nov 22 2022 nodesource.list.distUpgrade -rw-r--r-- 1 root root 109 Oct 8 21:11 nodesource.list.save -
cd sudo rm /etc/apt/sources.list.d/nodesource.list.* sudo apt update -
-
krisiun@Marek2:/root$ cd krisiun@Marek2:~$ sudo rm /etc/apt/sources.list.d/nodesource.list.* krisiun@Marek2:~$ sudo apt update Hit:1 https://deb.nodesource.com/node_18.x nodistro InRelease Hit:2 http://security.ubuntu.com/ubuntu jammy-security InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:4 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:5 http://archive.ubuntu.com/ubuntu jammy-backports InRelease Err:1 https://deb.nodesource.com/node_18.x nodistro InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4 Reading package lists... Done Building dependency tree... Done Reading state information... Done 1 package can be upgraded. Run 'apt list --upgradable' to see it. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://deb.nodesource.com/node_18.x nodistro InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4 W: Failed to fetch https://deb.nodesource.com/node_18.x/dists/nodistro/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4 W: Some index files failed to download. They have been ignored, or old ones used instead. -
Wir nähern uns langsam an...
sudo rm `sudo find / -name nodesource.gpg` sudo rm `sudo find / -name nodesource.key` sudo apt install -y ca-certificates curl gnupg sudo mkdir -p /etc/apt/keyrings curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg sudo apt update -
@thomas-braun sagte in iobroker zeschossen:
Wir nähern uns langsam an...
sudo rm `sudo find / -name nodesource.gpg` sudo rm `sudo find / -name nodesource.key` sudo apt install -y ca-certificates curl gnupg sudo mkdir -p /etc/apt/keyrings curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg sudo apt updateHeißt das jetzt ich soll die Befehle einzeln eingeben?
-
@krisiun sagte in iobroker zeschossen:
Heißt das jetzt ich soll die Befehle einzeln eingeben?
Zeilenweise am besten.
