Problem bei "sudo apt update"
-
Hallo,
heute wollte ich mein Raspi4 updaten und nach dem Befehl "sudo apt update" kam ungewöhnliche Meldungen:
"Repository 'xxxxx' changed its 'Label,Version,Suite,Codename' to 'xxxxxxx'
This must be accepted .....
und dann die Frage: Do you want to accept these changes und continue upadting?
Also habe ich bestätigt mit YES. Dann am Ende wieder ein Error ... siehe den Verlauf:pi@iobroker:~ $ iob stop pi@iobroker:~ $ sudo apt update Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB] Get:2 http://security.debian.org/debian-security bullseye-security InRelease [27.2 kB] Ign:3 http://archive.raspberrypi.org/debian bullseye InRelease Ign:4 http://deb.debian.org/debian bullseye-updates InRelease Err:2 http://security.debian.org/debian-security bullseye-security InRelease Splitting up /var/lib/apt/lists/partial/security.debian.org_debian-security_dists_bullseye-security_InRelease into data and signature failed Get:5 http://deb.debian.org/debian bullseye-updates Release [42.4 kB] Get:6 http://archive.raspberrypi.org/debian bullseye Release [38.4 kB] Get:7 http://deb.debian.org/debian bullseye-updates Release.gpg [1,601 B] Get:8 http://archive.raspberrypi.org/debian bullseye Release.gpg [488 B] Hit:9 https://deb.nodesource.com/node_20.x nodistro InRelease E: Repository 'http://deb.debian.org/debian bullseye-updates Release' changed its 'Label' value from 'Debian-Security' to 'Debian' N: Repository 'http://deb.debian.org/debian bullseye-updates Release' changed its 'Version' value from '11' to '11-updates' N: Repository 'http://deb.debian.org/debian bullseye-updates Release' changed its 'Suite' value from 'oldstable-security' to 'oldstable-updates' E: Repository 'http://deb.debian.org/debian bullseye-updates Release' changed its 'Codename' value from 'bullseye-security' to 'bullseye-updates' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. Do you want to accept these changes and continue updating from this repository? [y/N] y Get:10 http://deb.debian.org/debian bullseye-updates/main arm64 Packages [16.3 kB] Get:11 http://deb.debian.org/debian bullseye-updates/main armhf Packages [16.3 kB] Get:12 http://deb.debian.org/debian bullseye-updates/main Translation-en [10.9 kB] Get:13 http://archive.raspberrypi.org/debian bullseye/main arm64 Packages [322 kB] Get:14 http://archive.raspberrypi.org/debian bullseye/main armhf Packages [329 kB] Fetched 921 kB in 5min 23s (2,852 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://security.debian.org/debian-security bullseye-security InRelease: Splitting up /var/lib/apt/lists/partial/security.debian.org_debian-security_dists_bullseye-security_InRelease into data and signature failed W: Failed to fetch http://security.debian.org/debian-security/dists/bullseye-security/InRelease Splitting up /var/lib/apt/lists/partial/security.debian.org_debian-security_dists_bullseye-security_InRelease into data and signature failed W: Some index files failed to download. They have been ignored, or old ones used instead.Dann habe ich sicherheitshalber den "iob fix" ausgeführt, wo auch diese komische Meldungen vorkommen:
pi@iobroker:~ $ iob fix library: loaded Library version=2024-10-22 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2024-10-22 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/5) ========================================================================== Get:1 http://security.debian.org/debian-security bullseye-security InRelease [27.2 kB] Hit:2 http://deb.debian.org/debian bullseye InRelease Get:3 http://archive.raspberrypi.org/debian bullseye InRelease [39.0 kB] Ign:4 http://deb.debian.org/debian bullseye-updates InRelease Hit:5 http://deb.debian.org/debian bullseye-updates Release Hit:6 https://deb.nodesource.com/node_20.x nodistro InRelease Reading package lists... Done W: Conflicting distribution: http://security.debian.org/debian-security bullseye-security InRelease (expected bullseye-security but got bullseye) E: Repository 'http://security.debian.org/debian-security bullseye-security InRelease' changed its 'Origin' value from 'Debian' to 'Raspberry Pi Foundation' E: Repository 'http://security.debian.org/debian-security bullseye-security InRelease' changed its 'Label' value from 'Debian-Security' to 'Raspberry Pi Foundation' N: Repository 'http://security.debian.org/debian-security bullseye-security InRelease' changed its 'Version' value from '11' to '' N: Repository 'http://security.debian.org/debian-security bullseye-security InRelease' changed its 'Suite' value from 'oldstable-security' to 'oldstable' E: Repository 'http://security.debian.org/debian-security bullseye-security InRelease' changed its 'Codename' value from 'bullseye-security' to 'bullseye' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. E: Failed to fetch http://security.debian.org/debian-security/dists/bullseye-security/InRelease Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?) E: The repository 'http://security.debian.org/debian-security bullseye-security InRelease' is no longer signed. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.raspberrypi.org/debian bullseye InRelease: Splitting up /var/lib/apt/lists/archive.raspberrypi.org_debian_dists_bullseye_InRelease into data and signature failed Installed polkitd ========================================================================== Checking ioBroker user and directory permissions (2/5) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... ========================================================================== Check and cleanup npm temporary directories (3/5) ========================================================================== Done. ========================================================================== Database maintenance (4/5) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! Compressing /opt/iobroker/iobroker-data/states.jsonl Compressing /opt/iobroker/iobroker-data/objects.jsonl Compressed 2 JSONL files. Done ========================================================================== Checking autostart (5/5) ========================================================================== ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Authentication is required to stop 'iobroker.service'. Authenticating as: ,,, (pi) Password: ==== AUTHENTICATION COMPLETE === Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ==========================================================================danach habe ich rebootet "sudo reboot", IoBroker startet und funktioniert normal, Gott sei dank.
Und dann nochmal update versucht "sudo apt update", wo wieder komische Meldungen sind:pi@iobroker:~ $ iob stop pi@iobroker:~ $ sudo apt update Get:1 http://security.debian.org/debian-security bullseye-security InRelease [27.2 kB] Hit:2 http://deb.debian.org/debian bullseye InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease Get:6 http://security.debian.org/debian-security bullseye-security/main armhf Packages [332 kB] Get:7 http://security.debian.org/debian-security bullseye-security/main arm64 Packages [335 kB] Get:8 http://security.debian.org/debian-security bullseye-security/main Translation-en [221 kB] Ign:9 http://archive.raspberrypi.org/debian bullseye/main Translation-en Ign:9 http://archive.raspberrypi.org/debian bullseye/main Translation-en Ign:9 http://archive.raspberrypi.org/debian bullseye/main Translation-en Err:9 http://archive.raspberrypi.org/debian bullseye/main Translation-en 404 Not Found [IP: 2a00:1098:80:56::2:1 80] Fetched 915 kB in 2s (573 kB/s) Reading package lists... Done W: Conflicting distribution: http://archive.raspberrypi.org/debian bullseye InRelease (expected bullseye but got bullseye-updates) E: Failed to fetch http://archive.raspberrypi.org/debian/dists/bullseye/main/i18n/Translation-en 404 Not Found [IP: 2a00:1098:80:56::2:1 80] E: Some index files failed to download. They have been ignored, or old ones used instead. pi@iobroker:~ $Jetzt brauche ich von euch hilfe, was ich machen soll.
Befehl "sudo apt full-upgrade" traue ich mich jetzt nicht ausführen
Vielen Dank im Voraus.
-
@pali-0 sagte in Problem bei "sudo apt update":
kam ungewöhnliche Meldungen:
"Repository 'xxxxx' changed its 'Label,Version,Suite,Codename' to 'xxxxxxx'
This must be accepted .....weil das Betriebssxstem EndOfLife ist, sollst du bestätigen, dass dir das gesagt eurde und du zrotzdem damit weitermachen willst.
EDIT:
Hab jetzt erst im log die nicht gexxxxten Stellen gesehen.Da wäre es schön, wenn @thomas-braun kurz etwas dazu sagen könnte.
-
also kann ich ruhig noch auch "sudo apt full-upgrade" ausführen?
-
@pali-0 sagte in Problem bei "sudo apt update":
also kann ich ruhig noch auch "sudo apt full-upgrade" ausführen?
siehe edit
-
ok, danke, ich warte ab.
-
Das hängt damit zusammen, das 'Bullseye' auf dem Abstellgleis steht.
Installier da NEU Raspberry 12 'Bookworm'. -
ok, danke dir. Mache ich ...
EDIT: habe ich erledigt. Bookworm installiert, mit BackItup die Sicherungen hergestellt und alles läuft wieder ohne Warnungen oder sonstigen Error-Meldungen. Danke.
-
Das sind genau die Errosions-Erscheinungen, die halt bei abgekündigten Releases auftauchen können.
