Kein Update mehr möglich mit Node.js 16
-
Knall mal den npm cache weg:
sudo -H -u iobroker npm cache clean --force iobroker update -
@thomas-braun sagte in Kein Update mehr möglich mit Node.js 16:
Knall mal den npm cache weg:
sudo -H -u iobroker npm cache clean --force iobroker updatepi@raspberrypi:~ $ sudo -H -u iobroker npm cache clean --force npm WARN using --force Recommended protections disabled. pi@raspberrypi:~ $ iobroker update Used repository: stable Adapter "admin" : 5.3.8 , installed 5.3.8 Adapter "alarm" : 3.1.0 , installed 3.1.0 Adapter "alexa2" : 3.11.2 , installed 3.12.0 Adapter "backitup" : 2.4.9 , installed 2.4.9 Adapter "birthdays" : 2.0.0 , installed 2.0.0 Adapter "bluelink" : 2.1.2 , installed 2.1.2 Adapter "bshb" : 0.1.20 , installed 0.1.20 Adapter "cloud" : 4.1.1 , installed 4.1.1 Adapter "coronavirus-statistics": 0.8.7, installed 0.8.7 Adapter "device-reminder": 1.2.9 , installed 1.2.9 Adapter "discovery" : 3.0.3 , installed 3.0.3 Adapter "dwd" : 2.8.3 , installed 2.8.3 Adapter "email" : 1.0.10 , installed 1.0.10 Adapter "fb-checkpresence": 1.1.14, installed 1.1.15 Adapter "flot" : 1.10.7 , installed 1.10.7 Adapter "fritzbox" : 0.2.1 , installed 0.2.1 Adapter "fritzdect" : 2.2.3 , installed 2.2.6 Adapter "fullybrowser" : 2.1.2 , installed 2.1.2 Adapter "habpanel" : 0.5.0 , installed 0.5.0 Adapter "history" : 1.11.1 , installed 1.11.1 Adapter "hue-extended" : 2.0.0 , installed 2.0.1 Adapter "ical" : 1.12.1 , installed 1.12.1 Adapter "icons-material-png": 0.1.0, installed 0.1.0 Adapter "icons-mfd-png": 1.1.0 , installed 1.1.0 Adapter "icons-open-icon-library-png": 0.1.2, installed 0.1.2 Adapter "icons-ultimate-png": 1.0.1, installed 1.0.1 Adapter "info" : 1.9.19 , installed 1.9.19 Adapter "iot" : 1.11.4 , installed 1.11.4 Adapter "javascript" : 5.7.0 , installed 5.7.0 Controller "js-controller": 4.0.23 , installed 4.0.23 Adapter "luftdaten" : 2.2.4 , installed 2.2.4 Adapter "midea" : 0.0.7 , installed 0.0.7 Adapter "netatmo-crawler": 0.8.1 , installed 0.8.1 Adapter "nina" : 0.0.25 , installed 0.0.25 Adapter "nuki-extended": 2.3.1 , installed 2.6.1 Adapter "octoprint" : 4.0.0 , installed 4.0.0 Adapter "parcel" : 0.0.15 , installed 0.0.15 Adapter "parser" : 1.1.5 , installed 1.1.5 Adapter "pi-hole" : 1.3.4 , installed 1.3.4 Adapter "pushover" : 2.1.0 , installed 2.1.0 Adapter "radar2" : 2.0.3 , installed 2.0.3 Adapter "rssfeed" : 1.0.0 , installed 1.0.0 Adapter "samsung" : 0.5.8 , installed 0.5.8 Adapter "scenes" : 2.3.9 , installed 2.3.9 Adapter "simple-api" : 2.6.5 , installed 2.6.5 Adapter "snmp" : 1.0.0 , installed 1.0.0 Adapter "socketio" : 4.2.0 , installed 4.2.0 Adapter "sonoff" : 2.5.1 , installed 2.5.1 Adapter "telegram" : 1.12.6 , installed 1.12.6 Adapter "tr-064" : 4.2.16 , installed 4.2.16 Adapter "tradfri" : 3.1.3 , installed 3.1.3 Adapter "trashschedule": 2.0.2 , installed 2.0.2 Adapter "tvprogram" : 1.1.2 , installed 1.1.2 Adapter "vis" : 1.4.15 , installed 1.4.15 Adapter "vis-hqwidgets": 1.2.0 , installed 1.2.0 Adapter "vis-icontwo" : 0.87.0 , installed 0.87.0 Adapter "vis-inventwo" : 3.3.1 , installed 3.3.1 Adapter "vis-metro" : 1.2.0 , installed 1.2.0 Adapter "vis-players" : 0.1.6 , installed 0.1.6 Adapter "vis-timeandweather": 1.1.7, installed 1.1.7 Adapter "web" : 4.3.0 , installed 4.3.0 Adapter "ws" : 1.3.0 , installed 1.3.0 Adapter "zigbee" : 1.7.5 , installed 1.7.5kein erfolg
-
-
@thomas-braun sagte in Kein Update mehr möglich mit Node.js 16:
Interesting...
npm view iobroker.js-controllerund
npm view iobroker.alexa2pi@raspberrypi:~ $ npm view iobroker.js-controller iobroker.js-controller@4.0.23 | MIT | deps: 38 | versions: 326 Updated by reinstall.js on 2018-06-11T15:19:56.688Z https://www.iobroker.com keywords: ioBroker, Smarthome, Home Automation, Smart Metering, Homematic, Hue, KNX, Z-Wave, ZigBee, Bidcos, TV, Sonos, AV Receiver bin: iobroker dist .tarball: https://registry.npmjs.org/iobroker.js-controller/-/iobroker.js-controller-4.0.23.tgz .shasum: 345fe7c6c17fec431ed97b98a1d53c31470fdd07 .integrity: sha512-jm2u6TOpVohEBIhPN2YgCQ6tf0idbvaXZTAI6SwPPKwjny7pE34CfGP2GgpY02S9NRTOtPb07BR2GILh86DxbA== .unpackedSize: 1.0 MB dependencies: @alcalzone/esbuild-register: ^2.5.1-1 @iobroker/plugin-sentry: ~1.2.0 @iobroker/db-objects-file: 4.0.23 axios: ^0.24.0 @iobroker/db-objects-jsonl: 4.0.23 daemonize2: ^0.4.2 @iobroker/db-objects-redis: 4.0.23 debug: ^4.3.3 @iobroker/db-states-file: 4.0.23 decache: ^4.6.1 @iobroker/db-states-jsonl: 4.0.23 deep-clone: ^3.0.3 @iobroker/db-states-redis: 4.0.23 fs-extra: ^10.0.0 @iobroker/js-controller-adapter: 4.0.23 jsonwebtoken: ^8.5.1 @iobroker/js-controller-cli: 4.0.23 jszip: ^3.7.0 @iobroker/js-controller-common-db: 4.0.23 loadavg-windows: ^1.1.1 @iobroker/js-controller-common: 4.0.23 mime: ^3.0.0 @iobroker/plugin-base: ~1.2.1 node-schedule: ^2.1.0 (...and 14 more.) maintainers: - foxriver76 <moritz.heusinger@gmail.com> - iobluefox <info@iobroker.net> - bluefox <dogafox@gmail.com> - apollon77 <github@fischer-ka.de> - ldittmar <iobroker@lmdsoft.de> - alcalzone <d.griesel@gmx.net> dist-tags: dev: 4.1.0-alpha.37-20220622-43cd5e40 next: 4.0.15 latest: 4.0.23 stable: 4.0.23 published 2 months ago by bluefox <dogafox@gmail.com> pi@raspberrypi:~ $ npm view iobroker.alexa2 iobroker.alexa2@3.12.0 | MIT | deps: 7 | versions: 73 Remote control for Alexa (Amazon Echo) https://github.com/Apollon77/ioBroker.alexa2 keywords: sync, iobroker file, JetBrains, webstorm, file, debug, editor, ide dist .tarball: https://registry.npmjs.org/iobroker.alexa2/-/iobroker.alexa2-3.12.0.tgz .shasum: ab73252c31ef31ed72363019166a2b416b08db94 .integrity: sha512-ize4XTUROiaU45UJexBddGoqRDIohV60g3qAtbnBGGQVXJ6vBCl41elIPuAJikNYYD45UqpN7Ocm21KW9+N/eg== .unpackedSize: 1.4 MB dependencies: @iobroker/adapter-core: ^2.5.1 alexa-remote2: ^4.1.0 source-map-support: ^0.5.20 @sentry/integrations: ^6.13.3 https: ^1.0.0 @sentry/node: ^6.13.3 nearest-color: ^0.4.4 maintainers: - bluefox <dogafox@gmail.com> - apollon77 <github@fischer-ka.de> dist-tags: latest: 3.12.0 published 7 months ago by apollon77 <github@fischer-ka.de> npm notice npm notice New minor version of npm available! 8.11.0 -> 8.12.2 npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.12.2 npm notice Run npm install -g npm@8.12.2 to update! npm notice pi@raspberrypi:~ $ -
iob repo list -
@thomas-braun sagte in Kein Update mehr möglich mit Node.js 16:
iob repo listpi@raspberrypi:~ $ iob repo list stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable pi@raspberrypi:~ $ -
Mich würde ja interessieren, was passiert, wenn man beta wieder anknipst.
-
@thomas-braun sagte in Kein Update mehr möglich mit Node.js 16:
Mich würde ja interessieren, was passiert, wenn man beta wieder anknipst.
ausprobieren, aktuell geht eh nicht viel
-
Hallo @thomas-braun
Ich hänge mich mal hier mit dran.
Seit gestern hab ich mit folgender Kombi auch Probleme mit Updates.
Node.js: v16.15.1
NPM: 8.11.0
Admin: 5.4.9
JS-Controller: 4.0.23Fehlermeldung:
$ iobroker upgrade cloud@4.1.2 Update cloud from @4.1.1 to @4.1.2 NPM version: 8.11.0 Installing iobroker.cloud@4.1.2... (System call) host.ioBroker Cannot install iobroker.cloud@4.1.2: 217 ERROR: Process exited with code 25nega@ioBroker:~$ npm ls | grep ERR nega@ioBroker:~$Auf NPM 8.11.0 bin ich schon länger und es funktionierten immer alle Updates.
Ich hab mir einige der letzten Threads durchgelesen. Da gehts aber immer um Admin 6.Wo kann ich noch nachschaun, bzw. was kann ich noch machen?
-
@negalein sagte in Kein Update mehr möglich mit Node.js 16:
was kann ich noch machen?
Ausgabe mit debug , dann sieht man mehr
iobroker upgrade cloud@4.1.2 --debug -
@glasfaser sagte in Kein Update mehr möglich mit Node.js 16:
iobroker upgrade cloud@4.1.2 --debug
nega@ioBroker:~$ iobroker upgrade cloud@4.1.2 --debug This upgrade of "cloud" will introduce the following changes: ========================================================================== -> 4.1.2: Added preparations for Admin 6 Added better error reporting Removed outdated `request` library Used common sockets (could be buggy) ========================================================================== Would you like to upgrade cloud from @4.1.1 to @4.1.2 now? [(y)es, (n)o]: y Update cloud from @4.1.1 to @4.1.2 NPM version: 8.11.0 Installing iobroker.cloud@4.1.2... (System call) npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm, npm WARN old lockfile so supplemental metadata must be fetched from the registry. npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient... npm WARN old lockfile npm WARN tarball tarball data for iobroker.icons-open-icon-library-png@https://github.com/ioBroker/ioBroker.icons-open-icon-library-png/tarball/master (sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w==) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.icons-open-icon-library-png@https://github.com/ioBroker/ioBroker.icons-open-icon-library-png/tarball/master (sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w==) seems to be corrupted. Trying again. npm WARN old lockfile Error: sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w== integrity checksum failed when using sha512: wanted sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w== but got sha512-ZH4lj95sM6IpZEL2H1HR0hXTo6GMqbUBPbQyylgdRd6TDEdU+fgohUVGW4gPI0UnrAzqM/kx5+mozLqCVh2DCg==. (64751136 bytes) npm WARN old lockfile at IntegrityStream.[_onEnd] (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:118:19) npm WARN old lockfile at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:88:19) npm WARN old lockfile at IntegrityStream.[maybeEmitEnd] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:370:12) npm WARN old lockfile at IntegrityStream.end (/usr/lib/node_modules/npm/node_modules/minipass/index.js:248:27) npm WARN old lockfile at Yallist.<anonymous> (/usr/lib/node_modules/npm/node_modules/minipass/index.js:409:18) npm WARN old lockfile at Yallist.forEach (/usr/lib/node_modules/npm/node_modules/yallist/yallist.js:156:8) npm WARN old lockfile at Minipass.emit (/usr/lib/node_modules/npm/node_modules/minipass/index.js:406:18) npm WARN old lockfile at Minipass.[maybeEmitEnd] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:370:12) npm WARN old lockfile at Minipass.emit (/usr/lib/node_modules/npm/node_modules/minipass/index.js:434:29) npm WARN old lockfile at Minipass.[resume] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:259:10) npm WARN old lockfile Could not fetch metadata for iobroker.icons-open-icon-library-png@https://github.com/ioBroker/ioBroker.icons-open-icon-library-png/tarball/master Error: sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w== integrity checksum failed when using sha512: wanted sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w== but got sha512-ZH4lj95sM6IpZEL2H1HR0hXTo6GMqbUBPbQyylgdRd6TDEdU+fgohUVGW4gPI0UnrAzqM/kx5+mozLqCVh2DCg==. (64751136 bytes) npm WARN old lockfile at IntegrityStream.[_onEnd] (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:118:19) npm WARN old lockfile at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:88:19) npm WARN old lockfile at IntegrityStream.[maybeEmitEnd] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:370:12) npm WARN old lockfile at IntegrityStream.end (/usr/lib/node_modules/npm/node_modules/minipass/index.js:248:27) npm WARN old lockfile at Yallist.<anonymous> (/usr/lib/node_modules/npm/node_modules/minipass/index.js:409:18) npm WARN old lockfile at Yallist.forEach (/usr/lib/node_modules/npm/node_modules/yallist/yallist.js:156:8) npm WARN old lockfile at Minipass.emit (/usr/lib/node_modules/npm/node_modules/minipass/index.js:406:18) npm WARN old lockfile at Minipass.[maybeEmitEnd] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:370:12) npm WARN old lockfile at Minipass.emit (/usr/lib/node_modules/npm/node_modules/minipass/index.js:434:29) npm WARN old lockfile at Minipass.[resume] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:259:10) { npm WARN old lockfile code: 'EINTEGRITY', npm WARN old lockfile found: Integrity { sha512: [ [Hash] ] }, npm WARN old lockfile expected: [ npm WARN old lockfile Hash { npm WARN old lockfile source: 'sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w==', npm WARN old lockfile digest: 'qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w==', npm WARN old lockfile algorithm: 'sha512', npm WARN old lockfile options: [] npm WARN old lockfile } npm WARN old lockfile ], npm WARN old lockfile algorithm: 'sha512', npm WARN old lockfile sri: Integrity { sha512: [ [Hash] ] } npm WARN old lockfile } npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /opt/iobroker/node_modules/follow-redirects npm ERR! dest /opt/iobroker/node_modules/.follow-redirects-vRGWWNjd npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/follow-redirects' -> '/opt/iobroker/node_modules/.follow-redirects-vRGWWNjd' npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-06-28T09_01_36_002Z-debug-0.log host.ioBroker Cannot install iobroker.cloud@4.1.2: 217 -
@negalein sagte in Kein Update mehr möglich mit Node.js 16:
nega@ioBroker:~$ npm ls | grep ERR
Du stehst im falschen Verzeichnis.
cd /opt/iobroker npm ls | grep -E 'ERR|github'Adapter aus dem github auf eine Version aus einem Repo drücken, wenn möglich.
-
@thomas-braun sagte in Kein Update mehr möglich mit Node.js 16:
npm ls | grep -E 'ERR|github'
+-- iobroker.enigma2@1.3.3 (git+ssh://git@github.com/Matten-Matten/ioBroker.enigma2.git#975e828ab4595b81333bcca5b32af3cbf3c287bc) +-- iobroker.fronius-solarweb@0.0.1 (git+ssh://git@github.com/TA2k/ioBroker.fronius-solarweb.git#bf873fc05ce1eecdff2aff880793b3e9f0a6c417) +-- iobroker.fronius@1.1.6 (git+ssh://git@github.com/iobroker-community-adapters/ioBroker.fronius.git#04dcfa98e3ca0e5d888dc8182a314717f65b390c) +-- iobroker.hs100@2.1.2 (git+ssh://git@github.com/arteck/ioBroker.hs100.git#9a5ada63aa2a381f934e2152a8d5155ebad8f16f) +-- iobroker.jarvis@3.0.12-beta.3 (git+ssh://git@github.com/Zefau/ioBroker.jarvis.git#bacd7221d9990610ee6c684e0ec6fddd397cde79) +-- iobroker.logparser@1.1.0 (git+ssh://git@github.com/Mic-M/ioBroker.logparser.git#f767910b12124a39c65132d4f835f71e9c9a03a8) +-- iobroker.octoprint@4.0.0 (git+ssh://git@github.com/klein0r/ioBroker.octoprint.git#d08a293e8f63fd36d6221ce9da014a2d67d5c9ec) +-- iobroker.pegelalarm@1.2.7 (git+ssh://git@github.com/simatec/ioBroker.pegelalarm.git#d5515a48667d9ced7f8c29fc187d967b557f495e) +-- iobroker.vis-knob@0.0.1 (git+ssh://git@github.com/ioBroker/ioBroker.vis-knob.git#a1dc9e3758987a921c893c0d63497e742d5c3526) +-- iobroker.web-speedy@0.2.0 (git+ssh://git@github.com/iobroker-community-adapters/ioBroker.web-speedy.git#294107d34a0e873959795bbc00c09e9def6e3a42) npm ERR! code ELSPROBLEMS npm ERR! invalid: iobroker.ical@1.13.1 /opt/iobroker/node_modules/iobroker.ical npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-06-28T09_10_03_705Z-debug-0.logAdapter aus dem github auf eine Version aus einem Repo drücken, wenn möglich.
wie meinst du das?
-
@negalein sagte in Kein Update mehr möglich mit Node.js 16:
wie meinst du das?
Damit meine ich, diese Adapter aus einem Repo zu installieren, falls es den denn in stable oder beta-Versionen gibt.
-
@thomas-braun sagte in Kein Update mehr möglich mit Node.js 16:
Damit meine ich, diese Adapter aus einem Repo zu installieren, falls es den denn in stable oder beta-Versionen gibt.
diese
+-- iobroker.enigma2@1.3.3 (git+ssh://git@github.com/Matten-Matten/ioBroker.enigma2.git#975e828ab4595b81333bcca5b32af3cbf3c287bc) +-- iobroker.fronius-solarweb@0.0.1 (git+ssh://git@github.com/TA2k/ioBroker.fronius-solarweb.git#bf873fc05ce1eecdff2aff880793b3e9f0a6c417) +-- iobroker.fronius@1.1.6 (git+ssh://git@github.com/iobroker-community-adapters/ioBroker.fronius.git#04dcfa98e3ca0e5d888dc8182a314717f65b390c) +-- iobroker.hs100@2.1.2 (git+ssh://git@github.com/arteck/ioBroker.hs100.git#9a5ada63aa2a381f934e2152a8d5155ebad8f16f) +-- iobroker.jarvis@3.0.12-beta.3 (git+ssh://git@github.com/Zefau/ioBroker.jarvis.git#bacd7221d9990610ee6c684e0ec6fddd397cde79) +-- iobroker.logparser@1.1.0 (git+ssh://git@github.com/Mic-M/ioBroker.logparser.git#f767910b12124a39c65132d4f835f71e9c9a03a8) +-- iobroker.octoprint@4.0.0 (git+ssh://git@github.com/klein0r/ioBroker.octoprint.git#d08a293e8f63fd36d6221ce9da014a2d67d5c9ec) +-- iobroker.pegelalarm@1.2.7 (git+ssh://git@github.com/simatec/ioBroker.pegelalarm.git#d5515a48667d9ced7f8c29fc187d967b557f495e) +-- iobroker.vis-knob@0.0.1 (git+ssh://git@github.com/ioBroker/ioBroker.vis-knob.git#a1dc9e3758987a921c893c0d63497e742d5c3526) +-- iobroker.web-speedy@0.2.0 (git+ssh://git@github.com/iobroker-community-adapters/ioBroker.web-speedy.git#294107d34a0e873959795bbc00c09e9def6e3a42)oder alle die aktuell nicht zu installieren sind?
-
PS: installiere ich von Git, kommt auch der Error 25
$ iobroker url simatec/ioBroker.pegelalarm --host ioBroker install simatec/ioBroker.pegelalarm NPM version: 8.11.0 Installing simatec/ioBroker.pegelalarm... (System call) host.ioBroker Cannot install simatec/ioBroker.pegelalarm: 217 ERROR: Process exited with code 25 -
So viele wie möglich aus github rausheben.
-
@thomas-braun sagte in Kein Update mehr möglich mit Node.js 16:
So viele wie möglich aus github rausheben.
Ah, du meinst "weg von Github"?
Hmm, das ist doof.
Ich hab die 10 upzudatenden Adapter alle im Beta.
Dann muss ich abwarten bis das gefixt ist, oder doch jetzt schon auf Admin 6 updaten. -
Alle Adapter mit
git+ssh://git@github.comsind derzeitig über github installiert, nicht aus den Repos. -
@thomas-braun sagte in Kein Update mehr möglich mit Node.js 16:
Alle Adapter mit git+ssh://git@github.com sind derzeitig über github installiert, nicht aus den Repos.
stimmt. Die benötige ich mit dieser Version.
Aber
CloudundIOTsind nicht aus Github. Zumindest stehen sie nicht in obiger Liste.
Bringen aber auch der Error 25.Ist das akzuell ein generelles Problem von Git, oder von meinem System?
