APT repo not working for Ubuntu 22.04/24/04 anymore (package kitware-archive-keyring)

Community
1

Hi, internally we’re using a different script, but I reproduced the exact same behavior with kitware-archive.sh.

The error is quite clear:

Get:1 https://apt.kitware.com/ubuntu jammy/main amd64 kitware-archive-keyring all 2025.06.23 [28.2 kB]
Err:1 https://apt.kitware.com/ubuntu jammy/main amd64 kitware-archive-keyring all 2025.06.23
  File has unexpected size (28052 != 28184). Mirror sync in progress? [IP: 66.194.253.25 443]
  Hashes of expected file:
   - SHA512:46cf00f34d64d17b34b0bdf683ce1dca0c65c95fd4227a7b4b79feba2e23ac49d5863e5d7e7c39773882d1c029a4c52ed51a831b3aa16c86641b762dd30d7634
   - SHA256:576bb5fdecb03ed13379bdecc79cab825849c339032bdc5c3753925efe3b36b5
   - SHA1:492aeb62fd7e1484e50fb491181eda89a13e8643 [weak]
   - MD5Sum:3a887eb7114a7e07a118b80aae438e95 [weak]
   - Filesize:28184 [weak]
E: Failed to fetch https://apt.kitware.com/ubuntu/pool/main/k/kitware-archive-keyring/kitware-archive-keyring_2025.06.23_all.deb  File has unexpected size (28052 != 28184). Mirror sync in progress? [IP: 66.194.253.25 443]
   Hashes of expected file:
    - SHA512:46cf00f34d64d17b34b0bdf683ce1dca0c65c95fd4227a7b4b79feba2e23ac49d5863e5d7e7c39773882d1c029a4c52ed51a831b3aa16c86641b762dd30d7634
    - SHA256:576bb5fdecb03ed13379bdecc79cab825849c339032bdc5c3753925efe3b36b5
    - SHA1:492aeb62fd7e1484e50fb491181eda89a13e8643 [weak]
    - MD5Sum:3a887eb7114a7e07a118b80aae438e95 [weak]
    - Filesize:28184 [weak]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Nothing similar happens for Ubuntu 24.04.

Correction: for kitware-archive-keyring_2025.06.23_all.deb this happens all the same on Ubuntu 24.04.

2 
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 24.04.4 LTS
Release:        24.04
Codename:       noble
$ sudo apt install kitware-archive-keyring
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  kitware-archive-keyring
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 28.2 kB of archives.
After this operation, 46.1 kB of additional disk space will be used.
Get:1 https://apt.kitware.com/ubuntu noble/main amd64 kitware-archive-keyring all 2025.06.23 [28.2 kB]
Err:1 https://apt.kitware.com/ubuntu noble/main amd64 kitware-archive-keyring all 2025.06.23
  File has unexpected size (28052 != 28184). Mirror sync in progress? [IP: 66.194.253.25 443]
  Hashes of expected file:
   - SHA512:46cf00f34d64d17b34b0bdf683ce1dca0c65c95fd4227a7b4b79feba2e23ac49d5863e5d7e7c39773882d1c029a4c52ed51a831b3aa16c86641b762dd30d7634
   - SHA256:576bb5fdecb03ed13379bdecc79cab825849c339032bdc5c3753925efe3b36b5
   - SHA1:492aeb62fd7e1484e50fb491181eda89a13e8643 [weak]
   - MD5Sum:3a887eb7114a7e07a118b80aae438e95 [weak]
   - Filesize:28184 [weak]
E: Failed to fetch https://apt.kitware.com/ubuntu/pool/main/k/kitware-archive-keyring/kitware-archive-keyring_2025.06.23_all.deb  File has unexpected size (28052 != 28184). Mirror sync in progress? [IP: 66.194.253.25 443]
   Hashes of expected file:
    - SHA512:46cf00f34d64d17b34b0bdf683ce1dca0c65c95fd4227a7b4b79feba2e23ac49d5863e5d7e7c39773882d1c029a4c52ed51a831b3aa16c86641b762dd30d7634
    - SHA256:576bb5fdecb03ed13379bdecc79cab825849c339032bdc5c3753925efe3b36b5
    - SHA1:492aeb62fd7e1484e50fb491181eda89a13e8643 [weak]
    - MD5Sum:3a887eb7114a7e07a118b80aae438e95 [weak]
    - Filesize:28184 [weak]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
3

Yep, started breaking our CI without any other moving parts. So I guess I am not dreaming that up.

4

Seems to be fixed now as per https://gitlab.kitware.com/cmake/cmake/-/work_items/27852

5

FWIW, we do not recommend using apt.kitware.com to install packages in CI jobs. The GitHub-hosted release binary tarballs can be easily extracted, are relocatable, and are hosted with a CDN.

1 Like
6

Hi Brad, thanks for the clarification. I really dislike using unpackaged software in a package-managed environment, so I’d gladly use the APT repo anytime. But since you stated it this way, I think I’ll have a look at how I can integrate it in the script parts (which I maintain) that will make CMake and other stuff available.

But the joke’s still on us regarding the broken CI, because technically the colleagues who run the CI processes should IMO use an APT caching proxy of sorts. There are enough ways to decouple from external resources while also keeping an eye on the use of said external resources. My remark was more meant as confirmation, because I reported another “issue” in January which turned out to be PEBKAC.

Also noticed the apt.kitware.com page changed ever so slightly overnight :grin: (and yeah I confirmed this hadn’t been mentioned before):

This repository is intended for developers to install packages on their own machines. Please do not use this apt repository in CI jobs. Our official release binaries are hosted by GitHub’s CDN.

Side-note: the script which does use the APT repo is in fact geared to developers. In fact to manual preparation of a developer machine. It was co-opted by our CI folks into their process, because it’s so convenient.

7

Certainly the binary tarballs shouldn’t be extracted to a distro-managed prefix like /usr.

In CMake’s own CI we extract to a path inside the job’s work tree and add it to the PATH.

8

Yep, that’s what I thought. The GitHub API/download throttling is the only thing I need to keep in mind.

Do you follow rules for the naming of the assets and if so, where are they documented?

Thanks.

9

The release assets are generated automatically by a CI pipeline. One can see the artifact patterns after an “Any packages made” comment.

FWIW, CMake’s own CI jobs never look for future versions of anything. We always download fixed versions with known asset names and hashes. We update to new versions by changing those specs.