Problem bei Update von 2.0.1.3 auf 2.2.2.2

[Haidy]

Hallo LoxBerry-Experten,

hab heute mal wieder nach meinem LoxBerry gesehen und festgestellt, dass es ein Update gibt. Leider schlägt die Installation immer fehl und ich bin etwas planlos.
Die Tipps aus dem Forum mit sudo apt-get update --allow-releaseinfo-change hätte ich auch schon versucht, da bekomme ich immer Meldungen wie:

W: Target Packages (rpi/binary-armhf/Packages) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:6

hier noch ein Auszug aus dem Log des Updates ab dem ersten Warning:

[B]OK:[/B] Upgrading kernel and firmware successfully.
[B]WARNING:[/B] Update file /opt/loxberry/sbin/loxberryupdate/update_v2.0.2.pl requests a reboot of LoxBerry. Please reboot your LoxBerry after the installation has finished.
[B]OK:[/B] Update script /opt/loxberry/sbin/loxberryupdate/update_v2.0.2.pl finished.
11:04:03.922 [B]INFO:[/B] exec_perl_script /opt/loxberry/sbin/loxberryupdate/update_v2.0.2.pl release=v2.2.1.2 logfilename=/opt/loxberry/log/system/loxberryupdate/20211211_105101_454_update.log cron= updatedir=/tmp/loxberryupdate/mschlenstedt-Loxberry-d9db9fb with user - errcode 0
11:04:03.924 [B]INFO:[/B] Script version: v2.0.2.1
11:04:03.936 [B]INFO:[/B] Running update script for v2.0.2.1...
11:04:04.120 [B]INFO:[/B] Executing /opt/loxberry/sbin/loxberryupdate/update_v2.0.2.1.pl release=v2.2.1.2 logfilename=/opt/loxberry/log/system/loxberryupdate/20211211_105101_454_update.log cron= updatedir=/tmp/loxberryupdate/mschlenstedt-Loxberry-d9db9fb
[B]OK:[/B] Update script /opt/loxberry/sbin/loxberryupdate/update_v2.0.2.1.pl started.
[B]INFO:[/B] Updating yarn public key...
[B]CRITICAL:[/B] Error installing libhash-merge-perl - Error 100
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 243 not upgraded.
1 not fully installed or removed.
Need to get 0 B/14.3 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 82833 files and directories currently installed.)
Preparing to unpack .../libhash-merge-perl_0.300-1_all.deb ...
Unpacking libhash-merge-perl (0.300-1) over (0.300-1) ...
Setting up rpimonitor (2.13-beta6) ...
Configuration file '/etc/rpimonitor/template/version.conf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** version.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package rpimonitor (--configure):
end of file on stdin at conffile prompt
Setting up libhash-merge-perl (0.300-1) ...
Processing triggers for man-db (2.8.5-2) ...
Errors were encountered while processing:
rpimonitor
W: Target Packages (main/binary-armhf/Packages) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:6
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:6
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:6
W: Target Packages (contrib/binary-armhf/Packages) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:6
W: Target Packages (contrib/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:6
W: Target Translations (contrib/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:6
W: Target Packages (non-free/binary-armhf/Packages) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:6
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:6
W: Target Translations (non-free/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:6
W: Target Packages (rpi/binary-armhf/Packages) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:6
W: Target Packages (rpi/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:6
W: Target Translations (rpi/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:6
E: Sub-process /usr/bin/dpkg returned an error code (1)
[B]ERROR:[/B] Update script /opt/loxberry/sbin/loxberryupdate/update_v2.0.2.1.pl finished with errors.
11:08:02.837 [B]INFO:[/B] exec_perl_script /opt/loxberry/sbin/loxberryupdate/update_v2.0.2.1.pl release=v2.2.1.2 logfilename=/opt/loxberry/log/system/loxberryupdate/20211211_105101_454_update.log cron= updatedir=/tmp/loxberryupdate/mschlenstedt-Loxberry-d9db9fb with user - errcode 1
11:08:02.839 [B]ERROR:[/B] Update-Script update_v2.0.2.1 returned errorcode 1. Despite errors loxberryupdate.pl will continue.
11:08:02.840 [B]INFO:[/B] Setting update script update_v2.0.2.1 as failed in general configuration.
11:08:02.842 [B]INFO:[/B] Updating update script fail state in general configuration...
11:08:02.876 [B]WARNING:[/B] LoxBerry Update was SUCCESSFULL, but skipped at least 1 warnings or errors. Check the log.
11:08:02.878 [B]CRITICAL:[/B] LoxBerry Update exited or terminated with an error. Errorcode: 1

Kann da jemand helfen?
Danke im Voraus!

[Christian Fenzl]

Wie man sieht: rpimonitor bleibt hängen.
Das Plugin deinstallieren und
sudo apt-get purge rpimonitor

[Haidy]

Danke Christian, hat geklappt.
Auch wenn das apt-get purge nach der Deinstallation des Plugins nichts mehr gemacht hat, weil das Paket schon weg war. Nach dem Update vom LoxBerry hab ich das Plugin wieder installiert.