Display MoreI had exactly the same scenario.
"apt clean && apt install libapt-inst2.0" helped
This happened at least 3 times to me. At least it's one line clean up instead of many
Thx
Thanks, that helped for me as well on an installation that is less than a day old (had to reinstall).
But keeps coming back after every package update !
Again: This is due to mixing repositories of two different operating systems which are not meant to be mixed together. The Raspbian project takes the Debian packages and rebuilds them, leading to different hashsums. So this issue will re-appear again and again.
It seems that there have been efforts though to make the installation of a pristine Debian possible for Raspberry PIs. With a pristine Debian this issue will not appear.
Again: This is due to mixing repositories of two different operating systems which are not meant to be mixed together. The Raspbian project takes the Debian packages and rebuilds them, leading to different hashsums. So this issue will re-appear again and again.
It seems that there have been efforts though to make the installation of a pristine Debian possible for Raspberry PIs. With a pristine Debian this issue will not appear.
Why was not it happening before ?
Why was not it happening before ?
I cannot describe the exact circumstances. The issue probably involves some kind of sorting order difference in which apt determines the package to install and the package to download. This issue appeared often in the past when people used third party repositories which just rebuilt packages after changing some configuration options. That's why there are rules/recommendations to change the version number (add a local suffix or similar) when rebuilding a package to avoid these kind of clashes. Raspbian systems shouldn't mix in debian-security. Raspbian takes updates from debian-security and rebuilds them for their own repository. That's why mixing in debian-security IMHO is also superfluous. Also debian-backports is not really meant for Raspbian.
Also debian-backports is not really meant for Raspbian.
The only packages that an RPi should use from debian-backports are cockpit and borgbackup. I see no harm in using either.
I changed the install script and submitted a pull request to not add the security repo on RPis. Old installs will have to set environment variable. I guess I could have an update of omv-extras do it.
The only packages that an RPi should use from debian-backports are cockpit and borgbackup. I see no harm in using either.
I changed the install script and submitted a pull request to not add the security repo on RPis. Old installs will have to set environment variable. I guess I could have an update of omv-extras do it.
Please do as this only occurs (at least for me) on recent, new installs, I don't experience the problem on an older installation.
Please do as this only occurs (at least for me) on recent, new installs, I don't experience the problem on an older installation.
Did the link to the pull request not prove that I am doing this? Oddly enough, I still have not run into this issue. But maybe I keep using the 64bit image which does not use raspbian packages - it is pure Debian.
Did the link to the pull request not prove that I am doing this? Oddly enough, I still have not run into this issue. But maybe I keep using the 64bit image which does not use raspbian packages - it is pure Debian.
Apologies, I misunderstood. And I am only running into this issue on one of my two installations. Due to some corruption I had to reinstall one last Saturday and on that one the problem crops up. The problem does not show on the other installation, which was last reinstalled last September.
This is annoying, every day I get long list of updates. Any way to deal with this ?
And this ^ is half of it !
every day this is automatically installed.
how to get rid of this?
The following security packages have been installed automatically.
CRON-APT RUN [/etc/cron-apt/config]: Wed Apr 14 07:37:37 CEST 2021
CRON-APT SLEEP: 3031, Wed Apr 14 08:28:08 CEST 2021
CRON-APT ACTION: 5-openmediavault-security
CRON-APT LINE: /usr/bin/apt-get --option quiet=1 --option APT::Get::List-Cleanup=false --option Dir::Etc::SourceList=/etc/apt/sources.list.d/openmediavault-os-security.list --option Dir::Etc::SourceParts="/dev/null" --option DPkg::Options::=--force-confold dist-upgrade --yes --option APT::Get::Show-Upgraded=true
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
apt apt-utils bind9-host curl dnsutils git libapt-pkg5.0 libbind9-161
libcurl3-gnutls libcurl4 libdns-export1104 libdns1104 libexif12 libexpat1
libfreetype6 libfreetype6-dev libfribidi0 libgssapi-krb5-2 libicu63
armhf 2.1.27+dfsg-1+deb10u1 [96.8 kB]
Get:46 http://security.debian.org/debian-security buster/updates/main armhf libtiff5 armhf 4.1.0+git191117-2~deb10u2 [252 kB]
Get:47 http://security.debian.org/debian-security buster/updates/main armhf libvpx5 armhf 1.7.0-3+deb10u1 [460 kB]
Get:48 http://security.debian.org/debian-security buster/updates/main armhf libzmq5 armhf 4.3.1-4+deb10u2 [209 kB]
Get:49 http://security.debian.org/debian-security buster/updates/main armhf nginx-full armhf 1.14.2-2+deb10u3 [453 kB]
Get:50 http://security.debian.org/debian-security buster/updates/main armhf patch armhf 2.7.6-3+deb10u1 [123 kB]
Get:51 http://security.debian.org/debian-security buster/updates/main armhf php7.3-common armhf 7.3.27-1~deb10u1 [533 kB]
Get:52 http://security.debian.org/debian-security buster/updates/main armhf php7.3-bcmath armhf 7.3.27-1~deb10u1 [12.5 kB]
Get:53 http://security.debian.org/debian-security buster/updates/main armhf php7.3-json armhf 7.3.27-1~deb10u1 [16.3 kB]
Get:54 http://security.debian.org/debian-security buster/updates/main armhf php7.3-opcache armhf 7.3.27-1~deb10u1 [159 kB]
Get:55 http://security.debian.org/debian-security buster/updates/main armhf php7.3-readline armhf 7.3.27-1~deb10u1 [10.5 kB]
Get:56 http://security.debian.org/debian-security buster/updates/main armhf php7.3-cli armhf 7.3.27-1~deb10u1 [1172 kB]
Get:57 http://security.debian.org/debian-security buster/updates/main armhf php7.3-cgi armhf 7.3.27-1~deb10u1 [1138 kB]
Get:58 http://security.debian.org/debian-security buster/updates/main armhf php7.3-fpm armhf 7.3.27-1~deb10u1 [1185 kB]
Get:59 http://security.debian.org/debian-security buster/updates/main armhf php7.3-mbstring armhf 7.3.27-1~deb10u1 [473 kB]
Get:60 http://security.debian.org/debian-security buster/updates/main armhf php7.3-xml armhf 7.3.27-1~deb10u1 [87.8 kB]
Get:61 http://security.debian.org/debian-security buster/updates/main armhf python-ldb armhf 2:1.5.1+really1.4.6-3+deb10u1 [33.9 kB]
Get:62 http://security.debian.org/debian-security buster/updates/main armhf python3-apt armhf 1.8.4.3 [169 kB]
Get:63 http://security.debian.org/debian-security buster/updates/main armhf python3-lxml armhf 4.3.2-1+deb10u3 [1084 kB]
Get:64 http://security.debian.org/debian-security buster/updates/main armhf sudo armhf 1.8.27-1+deb10u3 [1210 kB]
apt-listchanges: Reading changelogs...
Fetched 34.6 MB in 3s (11.7 MB/s)
(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 ... 62197 files and directories currently installed.)
Preparing to unpack .../libapt-pkg5.0_1.8.2.2_armhf.deb ...
Unpacking libapt-pkg5.0:armhf (1.8.2.2) over (1.8.2.2) ...
Setting up libapt-pkg5.0:armhf (1.8.2.2) ...
(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 ... 62197 files and directories currently installed.)
Preparing to unpack .../archives/apt_1.8.2.2_armhf.deb ...
Unpacking apt (1.8.2.2) over (1.8.2.2) ...
Setting up apt (1.8.2.2) ...
(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 ... 62197 files and directories currently installed.)
Preparing to unpack .../libexif12_0.6.21-5.1+deb10u5_armhf.deb ...
Unpacking libexif12:armhf (0.6.21-5.1+deb10u5) over (0.6.21-5.1+deb10u5) ...
Preparing to unpack .../minidlna_1.2.1+dfsg-2+deb10u2_armhf.deb ...
Unpacking minidlna (1.2.1+dfsg-2+deb10u2) over (1.2.1+dfsg-2+deb10u2) ...
Preparing to unpack .../libp11-kit0_0.23.15-2+deb10u1_armhf.deb ...
Unpacking libp11-kit0:armhf (0.23.15-2+deb10u1) over (0.23.15-2+deb10u1) ...
Setting up libp11-kit0:armhf (0.23.15-2+deb10u1) ...
(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 ... 62197 files and directories currently installed.)
Preparing to unpack .../libsasl2-modules-db_2.1.27+dfsg-1+deb10u1_armhf.deb ...
Unpacking libsasl2-modules-db:armhf (2.1.27+dfsg-1+deb10u1) over (2.1.27+dfsg-1+deb10u1) ...
Setting up libsasl2-modules-db:armhf (2.1.27+dfsg-1+deb10u1) ...
(Reading database ...
(Reading database ... 5%
triggers for man-db (2.8.5-2) ...
Old installs will have to set environment variable.
I removed the source "openmediavault-os-security.list" (with a backup, of course.)
Seeing as your pull request hasn't been merged yet, what environment variable do I need to set, if any, before the next update of openmediavault?
Run:
echo "OMV_APT_USE_OS_SECURITY=0" | sudo tee -a /etc/default/openmediavault
sudo omv-salt stage run prepare
still on my raspberry the same cronjob activates. please how to stop it. the above command does not work.
still on my raspberry the same cronjob activates. please how to stop it. the above command does not work.
The following worked for me:
omv-env set OMV_CRONAPT_SECURITY_UPGRADES_ENABLED "NO"
monit restart omv-engined
omv-salt stage run prepare
omv-salt stage run deployomv-salt stage run deployno output given.
system hangs after 2 minutes
Codeomv-salt stage run deployno output given.
system hangs after 2 minutes
Not sure what happened in your case, but I followed the doc at https://openmediavault.readthe…n/5.x/various/advset.html to set the environmental variable.
still on my raspberry the same cronjob activates. please how to stop it. the above command does not work.
You need to deactivate the source "openmediavault-os-security.list" as per:
Display Moresudo mv /etc/apt/sources.list.d/openmediavault-os-security.list /etc/apt/sources.list.d/openmediavault-os-security.bak
sudo apt-get update
sudo rm /var/lib/dpkg/info/libapt-inst2.0:armhf.md5sums
sudo apt-get update
sudo apt-get clean
sudo apt-get --reinstall install libapt-inst2.0
sudo apt-get dist-upgrade
Then you can set the environment variable given in post #33, though it will only be taken into account after the next update of openmediavault, if I'm not mistaken.
Okay. Done all that. Let's see tomorrow
You are better to remove the security repo from /etc/apt/sources.list now. After the next update of OMV, it shouldn't matter though.
Don’t have an account yet? Register yourself now and be a part of our community!