apt.kitware.com arm32 cmake package dependency error

First, sorry for posting here by default, feel free to redirect me if this is not the optimal place.

I’ve been enjoying using .deb cmake packages from https://apt.kitware.com for a while to get up to date versions of cmake.

For a couple of months I have encountered what seems to be a dependency error in the arm32 cmake package. Here is how I reproduce it :
On fresh install of ubuntu 20.04.03 32 bits on a raspberry pi 4 I do the following :

wget -O - https://apt.kitware.com/keys/kitware-archive-latest.asc | gpg --dearmor - | sudo tee /usr/share/keyrings/kitware-archive-keyring.gpg
echo 'deb [signed-by=/usr/share/keyrings/kitware-archive-keyring.gpg] https://apt.kitware.com/ubuntu/ focal main' | sudo tee /etc/apt/sources.list.d/kitware.list
sudo apt update
sudo apt install cmake

And the final result is :

Reading package lists... Done
Building dependency tree       
Reading state information... Done

Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
cmake : Depends: cmake-data (= 3.20.5-0kitware1ubuntu20.04.1) but 3.22.0-0kitware1ubuntu20.04.1 is to be installed
         Recommends: gcc but it is not going to be installed
         Recommends: make
E: Unable to correct problems, you have held broken packages

Note that this doesn’t happen on a 64 bits arm setup.

The workaround for me is to stick to the last version that this problem was not affecting :

sudo apt install cmake=3.20.5-0kitware1ubuntu20.04.1 cmake-data=3.20.5-0kitware1ubuntu20.04.1

Thanks for your attention.

Cc: @kyle.edwards

1 Like

See https://gitlab.kitware.com/cmake/cmake/-/issues/22683#note_1076888 for an explanation.

Thanks for the information @kyle.edwards
Can you provide a link to the mailing list where you reported the problem to OBS ?
I could maybe report users are affected, hoping to increase the odds of this issue being better prioritized.