Das neueste apt-get update und apt-get upgrade führt Aufforderung autoremove. Hiernach funktioniert das Gerät Flightaware, Flightradar und Radabox nicht mehr.
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr ben▒tigt:
atmel-firmware beast-splitter dump1090-fa dump978-fa firmware-intelwimax
firmware-iwlwifi firmware-ti-connectivity firmware-zd1211 gunicorn itcl3
libbladerf2 libboost-filesystem1.74.0 libhackrf0 liblimesuite20.10-1 piaware
piaware-ble-connect piaware-configurator piaware-support piaware-web
piaware-wifi-scan python3-click python3-colorama python3-flask
python3-gunicorn python3-itsdangerous python3-jinja2 python3-markupsafe
python3-tohil python3-werkzeug skyaware978 socat tcl tcl-tls tcllib tclx8.4
whois
Verwenden Sie ▒apt autoremove▒, um sie zu entfernen.
Upgrading via sudo apt full-upgrade will errorneously remove the piaware-release package. Please avoid upgrading using this for now as this will be fixed in a minor release shortly.
Rpi 2:
Restarting piaware-configurator server
Failed to try-restart piaware-configurator.service: Unit piaware-configurator.service is masked.
dpkg: error processing package piaware-configurator (–configure):
installed piaware-configurator package post-installation script subprocess returned error exit status 1
Setting up libpangoft2-1.0-0:armhf (1.46.2-3) …
Setting up libpangocairo-1.0-0:armhf (1.46.2-3) …
Setting up plymouth-label (0.9.5-3+rpt2) …
dpkg: dependency problems prevent configuration of piaware-release:
piaware-release depends on piaware-configurator (= 8.2); however:
Package piaware-configurator is not configured yet.
dpkg: error processing package piaware-release (–configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of piaware-ble-connect:
piaware-ble-connect depends on piaware-configurator; however:
Package piaware-configurator is not configured yet.
dpkg: error processing package piaware-ble-connect (–configure):
dependency problems - leaving unconfigured
Setting up plymouth-themes (0.9.5-3+rpt2) …
update-initramfs: deferring update (trigger activated)
Processing triggers for rsyslog (8.2102.0-2+deb11u1) …
Processing triggers for man-db (2.9.4-2) …
Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u5) …
Processing triggers for initramfs-tools (0.140) …
Errors were encountered while processing:
piaware-configurator
piaware-release
piaware-ble-connect
E: Sub-process /usr/bin/dpkg returned an error code (1)
exit
RPi 3
apt upgrade piaware-release Paketlisten werden gelesen… Fertig
Abh▒ngigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
piaware-release ist schon die neueste Version (8.2).
Paketaktualisierung (Upgrade) wird berechnet… Fertig
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
3 nicht vollst▒ndig installiert oder entfernt.
Nach dieser Operation werden 0 B Plattenplatz zus▒tzlich benutzt.
M▒chten Sie fortfahren? [J/n] J
piaware-configurator (8.2) wird eingerichtet …
Restarting piaware-configurator server
Failed to try-restart piaware-configurator.service: Unit piaware-configurator.service is masked.
dpkg: Fehler beim Bearbeiten des Paketes piaware-configurator (–configure):
▒installiertes piaware-configurator-Skript des Paketes post-installation▒-Unterprozess gab den Fehlerwert 1 zur▒ck
dpkg: Abh▒ngigkeitsprobleme verhindern Konfiguration von piaware-release:
piaware-release h▒ngt ab von piaware-configurator (= 8.2); aber:
Paket piaware-configurator ist noch nicht konfiguriert.
dpkg: Fehler beim Bearbeiten des Paketes piaware-release (–configure):
Abh▒ngigkeitsprobleme - verbleibt unkonfiguriert
dpkg: Abh▒ngigkeitsprobleme verhindern Konfiguration von piaware-ble-connect:
piaware-ble-connect h▒ngt ab von piaware-configurator; aber:
Paket piaware-configurator ist noch nicht konfiguriert.
dpkg: Fehler beim Bearbeiten des Paketes piaware-ble-connect (–configure):
Abh▒ngigkeitsprobleme - verbleibt unkonfiguriert
Fehler traten auf beim Bearbeiten von:
piaware-configurator
piaware-release
piaware-ble-connect
E: Sub-process /usr/bin/dpkg returned an error code (1)
Since you are using the SD card image, the easiest way would be to redownload the new image and to reimage the card. Then you can add your own unique identifier again.
Everyone has different requirement/use of Pi, so prefers different way to update/upgrade. For some cases re-imaging may be very difficult, for example Pi at a remote site, or running some other important software.
In my case, I use my Pi only for ADS-B and AIS and all my Pis are in my apartment at arm’s reach. I therefore prefer to re-image the microSD card with latest Flightaware image on one of the Pis, and on other Pis RaspberryPiOS image + package install of piaware, dump1090-fa, dump978-fa.
I have written down in notepad on my PC, the commands for Package Install of feeders (Piaware, FR24, RB24, Planefinder, Adsbexchange etc and @wiedehopf 's graphs1090), so it is simply a matter of copy-pasting these commands in SSH terminal.
In total it takes less than half an hour to get one microSD card with everything latest.
I dont reimage existing running microSD card. I just slip it out and keep it as backup, and usse a spare microSD card to prepare the fresh install.
Sorry it did not work. There’s no difference after this installation. Is there any other possibility what I can do?
I reinstalled already one of the machines. But one machine is really too difficult to reinstall, though it produces all the data. But it’s not so nice that I cannot see the first page running in a good for you.
