Noob question about updates

Quote from agusie

First, for few days now, I have package "cmake-data" showing as being updatable in the OMV WebUI but it is still here after I update it. If I run "apt update", the output is "All packages are up to date". And if I run "apt upgrade" it shows:

Code

The following packages will be DOWNGRADED:
  cmake-data

If I type in "Y" to go ahead with the upgrade I can see the package "cmake-data 3.16.3-3~bpo10+1" being downgraded to package "cmake-data 3.16.3-3~bpo10+1" (yes, the exact same package). And once done the package is still listed as being available for update in the OMV WebUI and "apt upgrade" still shows:

Code

The following packages will be DOWNGRADED:
  cmake-data

Why is that?

That usually happens when there are two repositories with the same package in the same version but with different hashsums. And that usually happens when one mixes repositories for different operating systems. In your case I assume that you are mixing Raspbian with Debian.

apt-cache policy cmake-data

Quote from agusie

Regarding my second question (why is apt update showing me "testing" packages available for update?), there are now even more packages and all but one are marked as "testing". I have checked the sources (/etc/apt/sources.list.d) but there is nothing about "testing" repositories in there. So why are they showing up? Are they safe to install? Here is the list of packages:

Code

$ apt list --upgradable
Listing... Done
alsa-utils/testing 1.1.8-2+rpt1 armhf [upgradable from: 1.1.8-2]
libssl-dev/testing 1.1.1d-0+deb10u5+rpt2 armhf [upgradable from: 1.1.1d-0+deb10u5+rpt1]
libssl1.1/testing 1.1.1d-0+deb10u5+rpt2 armhf [upgradable from: 1.1.1d-0+deb10u5+rpt1]
linux-libc-dev/buster-backports 5.10.19-1~bpo10+1 armhf [upgradable from: 4.19.171-2]
openssh-client/testing 1:7.9p1-10+deb10u2+rpt1 armhf [upgradable from: 1:7.9p1-10+deb10u2]
openssh-server/testing 1:7.9p1-10+deb10u2+rpt1 armhf [upgradable from: 1:7.9p1-10+deb10u2]
openssh-sftp-server/testing 1:7.9p1-10+deb10u2+rpt1 armhf [upgradable from: 1:7.9p1-10+deb10u2]
openssl/testing 1.1.1d-0+deb10u5+rpt2 armhf [upgradable from: 1.1.1d-0+deb10u5+rpt1]
rpi-eeprom/testing 11.12-1 armhf [upgradable from: 11.10-1]
ssh/testing 1:7.9p1-10+deb10u2+rpt1 all [upgradable from: 1:7.9p1-10+deb10u2]

Display More

You probably have a testing repository enabled: apt-cache policy

And if there is no pinning done, all repositories have the same pin priority (500) and are equal. Just remove the repository for testing. If you haven't enabled it, you should find out who or which software has.

Quote from agusie

I guess you are right. The output of apt-cache policy cmake-data is:

Code

cmake-data:
  Installed: 3.16.3-3~bpo10+1
  Candidate: 3.16.3-3~bpo10+1
  Version table:
 *** 3.16.3-3~bpo10+1 100
        100 http://httpredir.debian.org/debian buster-backports/main armhf Packages
        100 /var/lib/dpkg/status
     3.16.3-3~bpo10+1 500
        500 http://archive.raspberrypi.org/debian buster/main armhf Packages
     3.13.4-1 500
        500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages

Display More

Is it an issue? And if yes, how do I fix it?

Well, it results in this symptom. Raspbian is not supposed to use Debian repositories. That's why they rebuild Debian packages without changing the version. And this results in exactly this issue.

It has come up before, but I cannot find the thread. It is basically caused by enabling backports for Raspbian systems via OMV extras, if I'm not mistaken. Therefor CCing ryecoaaron. You'll have to reinstall the package by using the -t switch of APT and then you might be able to workaround it. But it can happen again and again. Raspbian != Debian.

Quote from ryecoaaron

And once again, omv-extras does not enable backports. backports is enabled by default.

Cut me some slack, yes? This:

Quote from dleidert

It has come up before, but I cannot find the thread. [..] if I'm not mistaken.

... clearly indicates that I'm not trying to blame you despite better knowledge. I tried to find the thread. Thanks.

The problem still is that Debian and Raspbian are not the same operating system and that Raspbian pulls in Debian packages and rebuilds them.

Quote from ryecoaaron

backports is enabled by default. omv-extras gives users access to toggle the switch that OMV uses to enable the backports repo. And when backports are enabled, only a few packages are pinned. The kernel is pinned by omv omv-extras pins this short list (mostly zfs and qemu). And this only affects raspbian32.

This conversation triggered my interest because it could help to identify a repeating root cause for errors.

To improve usability we should always try to eliminate identified root causes as this will have several benefits in the long run.

Can we define the uses case(s) when the current OMV setup causes errors?

Hello, fine humans! I come bearing no ill will. Now, as mi-hol said, this is an ongoing issue and is frankly a PITA, in terms of user experience. What exactly does one need to enable, disable, add, remove, delete, insert, make a rain dance, so that the end user (me) doesn't have to worry about it popping up again and again? Once again, this post isn't meant to denigrate, belittle or insult anyone at all. Simply want peace of mind and total zen

compulen, this is an old & lang resolved thread.

Quote from mi-hol

compulen, this is an old & lang resolved thread.

Thanks mi-hol. If you don't mind, can you please point me in the direction of the solution? I've been banging my head searching for a definitive remedy to this for the last couple of days.

the top 4 pinned posts in forum section for updates Updates/Upgrades

Quote from mi-hol

the top 4 pinned posts in forum section for updates Updates/Upgrades

Is there a specific post in there, which points to a solution?