Jammy-backports is missing the version 321 for ARM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cockpit (Ubuntu) |
Fix Released
|
Undecided
|
Build Daemon Maintainers |
Bug Description
1) Release of Ubuntu: Ubuntu 22.04.4 LTS
2) Version of the package: 316
3) Expected to happen: Cockpit-bridge and Cockpit-ws should be at version 321, so the main package (which already is at 321) can be installed.
4) What happened instead: Both packages are still at 316 for the jammy-backports for aarch64 processors, while the others are upgraded to 321.
Since cockpit version 321 depends on those two packages, the installation can't start, as they haven't been updated for the jammy-backports repository.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cockpit-bridge (not installed)
ProcVersionSign
Uname: Linux 6.5.0-1026-oracle aarch64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: arm64
CasperMD5CheckR
CloudArchitecture: aarch64
CloudID: oracle
CloudName: oracle
CloudPlatform: oracle
CloudSubPlatform: metadata (http://
Date: Mon Jul 22 14:54:55 2024
SourcePackage: cockpit
UpgradeStatus: No upgrade log present (probably fresh install)
That's because the two ARM architectures still didn't pick up the build: https:/ /launchpad. net/ubuntu/ +source/ cockpit/ 321-1~bpo24. 04.1
This must be a bug in the buildd configuration -- https:/ /launchpad. net/ubuntu/ noble/arm64/ +builds is empty, and even https:/ /launchpad. net/ubuntu/ oracular/ arm64/+ builds just has 6 builds (right now), so it doesn't like simply an overcrowded queue.