Comment 0 for bug 1981860

Description: Ubuntu 22.04 LTS
Release: 22.04
libarcus3:
  Installed: 1:4.8.0~202107291208~rev185~pkg375~ubuntu21.04.1
  Candidate: 1:4.8.0~202107291208~rev185~pkg375~ubuntu21.04.1
  Version table:
 *** 1:4.8.0~202107291208~rev185~pkg375~ubuntu21.04.1 100
        100 /var/lib/dpkg/status
     4.13.0-2build1 500
        500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages

Expected behavior: When installing software which depends libarcus3 >= 4.13, the package should be Actual behavior: Apt reports an unsatisfiable dependency and considers 4.13 a downgrade from 4.8 which must be fixed manually

Extended description:

Following an upgrade to Jammy from Impish, I attempted to install the cura package from the Jammy repos. Apt reported a dependency conflict:
python3-arcus : Depends: libarcus3 (= 4.13.0-2build1) but 1:4.8.0~202107291208~rev185~pkg375~ubuntu21.04.1 is to be installed

For reference, this is the dependency chain from cura to libarcus3: cura <- python3-uranium <- python3-arcus <- libarcus3

apt-cache policy libarcus3 showed two potential versions:
libarcus3:
  Installed: 1:4.8.0~202107291208~rev185~pkg375~ubuntu21.04.1
  Candidate: 1:4.8.0~202107291208~rev185~pkg375~ubuntu21.04.1
  Version table:
 *** 1:4.8.0~202107291208~rev185~pkg375~ubuntu21.04.1 100
        100 /var/lib/dpkg/status
     4.13.0-2build1 500
        500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages

Telling apt to install the 4.13 version over the 4.8 version results in a reported DOWNGRADE:
The following packages will be DOWNGRADED:
  libarcus3
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded.

The installation of 4.13 succeeded, and cura installed successfully afterwards.

Having the move from 4.8 to 4.13 be reported as a downgrade is unintuitive and leads to incorrect behavior when attempting to install software from the repositories.