installing libarcus3 4.13 over 4.8 considered a downgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libarcus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Description: Ubuntu 22.04 LTS
Release: 22.04
libarcus3:
Installed: 1:4.8.0~
Candidate: 1:4.8.0~
Version table:
*** 1:4.8.0~
100 /var/lib/
4.13.0-2build1 500
500 http://
Expected behavior: When installing software which depends libarcus3 >= 4.13, the dependency should be upgraded from prior packages
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~
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~
Candidate: 1:4.8.0~
Version table:
*** 1:4.8.0~
100 /var/lib/
4.13.0-2build1 500
500 http://
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.