NEWS
iobroker zeschossen
-
krisiun@Marek2:/root$ sudo apt update Get:1 https://dl.yarnpkg.com/debian stable InRelease [17.1 kB] Hit:2 https://deb.nodesource.com/node_18.x nodistro InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy InRelease Get:4 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB] Get:5 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB] Err:1 https://dl.yarnpkg.com/debian stable InRelease The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx> Get:6 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB] Err:2 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 355 kB in 4s (94.6 kB/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. N: Ignoring file 'nodesource.listy' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension 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. krisiun@Marek2:/root$ apt policy nodejs nodejs: Installed: 12.22.9~dfsg-1ubuntu3 Candidate: 18.18.0-1nodesource1 Version table: 18.18.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.15.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.13.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.12.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.11.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.10.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.8.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.7.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.6.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.5.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.4.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.3.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.2.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.1.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.0.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages *** 12.22.9~dfsg-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status N: Ignoring file 'nodesource.listy' in directory '/etc/apt/sources.list.d/' as it has an invali@krisiun sagte in iobroker zeschossen:
N: Ignoring file 'nodesource.listy' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
Kerl...
Du musst auch schon tun, was man dir einflüstert....Die Datei ist zu viel, lösch die.
sudo rm /etc/apt/sources.list./nodesource.listy
-
@krisiun sagte in iobroker zeschossen:
N: Ignoring file 'nodesource.listy' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
Kerl...
Du musst auch schon tun, was man dir einflüstert....Die Datei ist zu viel, lösch die.
sudo rm /etc/apt/sources.list./nodesource.listy
OK dann nochmal editor und dann den inhalt löschen?
-
@krisiun sagte in iobroker zeschossen:
N: Ignoring file 'nodesource.listy' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
Kerl...
Du musst auch schon tun, was man dir einflüstert....Die Datei ist zu viel, lösch die.
sudo rm /etc/apt/sources.list./nodesource.listy
@thomas-braun sagte in iobroker zeschossen:
sudo rm /etc/apt/sources.list./nodesource.listy
da fehlt noch ein "d" hinter list.
-
OK dann nochmal editor und dann den inhalt löschen?
@krisiun sagte in iobroker zeschossen:
OK dann nochmal editor und dann den inhalt löschen?
Bevor Thomas ganz verrückt wird:
Du sollte auf der Konsole !!! -> nicht im Editor dies eingeben:
sudo rm /etc/apt/sources.list.d/nodesource.listy
-
@krisiun sagte in iobroker zeschossen:
OK dann nochmal editor und dann den inhalt löschen?
Bevor Thomas ganz verrückt wird:
Du sollte auf der Konsole !!! -> nicht im Editor dies eingeben:
sudo rm /etc/apt/sources.list.d/nodesource.listy
-
@thomas-braun sagte in iobroker zeschossen:
sudo rm /etc/apt/sources.list./nodesource.listy
da fehlt noch ein "d" hinter list.
@bahnuhr sagte in iobroker zeschossen:
da fehlt noch ein "d" hinter list.
Stimmt.
sudo rm /etc/apt/sources.list.d/nodesource.listyalso.
-
-
@thomas-braun
Hab alles gemacht -
@thomas-braun
Hab alles gemacht@krisiun
Dann sollte beisudo apt updatenur noch der fehlende Schlüssel für nodesource angemeckert werden.
-
Kann aber trotzdem den iob nicht starten. Gleiche Fehler.
krisiun@Marek2:/root$ iobroker start /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted string -
Kann aber trotzdem den iob nicht starten. Gleiche Fehler.
krisiun@Marek2:/root$ iobroker start /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted string -
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. -
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 -
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.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 -
@thomas-braun
Dann sag mir bitte, bitte wie? Sorry aber das ist mir auch schon unangenehm dass ich das nicht schnalle@krisiun sagte in iobroker zeschossen:
Dann sag mir bitte, bitte wie?
Steht doch da.
sudo rm /etc/apt/sources.list.d/yar* -
@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
Ich bin dabei aber ich kanns nicht finden -
@thomas-braun
wo ich das löschen kann -
@thomas-braun
Ich bin dabei aber ich kanns nicht finden@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.