release-targets: switch fast-HDMI KDE matrix from kde-neon to kde-plasma#303
Conversation
Both KDE matrix blocks (standard-support `desktop-stable-ubuntu-kde-neon`
and community `community-noble-kde-neon`) emitted with `RELEASE: UBUNTU`,
which substitutes to whatever per-scope codename the workflow runs with.
After the noble→resolute promotion of `--ubuntu-standard` and
`--ubuntu-community`, both blocks now resolve to `RELEASE: resolute` —
and KDE Neon is pinned to a specific Ubuntu LTS (currently noble) with
no resolute build available, so any image build for these slots fails
to find the required packages.
Switch both blocks to `kde-plasma`. configng's kde-plasma.yaml advertises
arm64 + amd64 from bookworm through resolute, so the matrix entries
build cleanly across the whole release range without needing a
release-specific carve-out.
Changes:
* `desktop-stable-ubuntu-kde-neon` → `desktop-stable-ubuntu-kde-plasma`
(block name, comment header, DESKTOP_ENVIRONMENT value)
* `community-noble-kde-neon` → `community-noble-kde-plasma` (same
three rename points)
* scripts/generate-rpi-imager-json.py: add a `kde-plasma` →
"KDE Plasma Desktop" display-name mapping. The `kde-neon` mapping
stays — any kde-neon images still on the mirror keep their pretty
label until they age out of the published set.
Inline comments in both emit blocks record why kde-neon was retired
so the next maintainer reading the function doesn't add it back
without checking that kde-neon has caught up to the current
ubuntu-<scope> default.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
Disabled knowledge base sources:
WalkthroughTwo scripts were updated to transition from the Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Review rate limit: 0/1 reviews remaining, refill in 60 minutes.Comment |
Two additions to the manual targets list:
* Plain cloud kernel entries (no `ENABLE_EXTENSIONS`) for both
`uefi-arm64` and `uefi-x86`, alongside the existing
image-output-qcow2 / image-output-vhdx variants. Produces a
standard `.img.xz` cloud image with no extra output format
handling.
* Four new Ubuntu UEFI desktop targets to cover every `supported`
DE in configng's yaml/ that ships for amd64+arm64 and wasn't
already in the file: kde-plasma, mate, xfce, i3-wm. Branch
`current`, same v4l2loopback-dkms (+ nvidia on x86) extensions
pattern as the existing gnome/cinnamon blocks. UEFI items only
— board-specific items (thinkpad-x13s, radxa-dragon-q6a,
radxa-nio-12l) stay scoped to gnome/cinnamon since those were
the originally-curated desktops for those boards.
Skipped: kde-neon (retired with the resolute promotion, see
PR #303), bianbu (riscv64-only, lives in the auto-emitted
generator output for legacy/noble), and `community`-status DEs
(budgie, deepin, enlightenment) which belong in
targets-release-community-maintained.manual.
Symptom
Both KDE matrix blocks emit with
RELEASE: UBUNTU, which substitutes to whatever--ubuntu-<scope>codename is active. After the noble→resolute promotion of--ubuntu-standardand--ubuntu-community, both KDE Neon blocks resolve toRELEASE: resolute— and KDE Neon is pinned to a specific Ubuntu LTS (currently noble), with no resolute build. The image build can't find KDE Neon packages and fails.Fix
Switch both blocks to
kde-plasma. configng'skde-plasma.yamladvertisesarm64 + amd64from bookworm through resolute, so the same emit covers every codename in the fleet without needing per-release carve-outs.desktop-stable-ubuntu-kde-neondesktop-stable-ubuntu-kde-plasmacommunity-noble-kde-neoncommunity-noble-kde-plasmaDESKTOP_ENVIRONMENT: "kde-neon"(×2)DESKTOP_ENVIRONMENT: "kde-plasma"(×2)rpi-imager mapping
Added
"kde-plasma": "KDE Plasma Desktop"togenerate-rpi-imager-json.py's display-name dict. Kept thekde-neonrow — any straggler kde-neon images still on the mirror keep their pretty label until they age out of the published set.Inline comments
Both emit blocks now carry a short note explaining why kde-neon was retired (release-pin issue) so the next maintainer doesn't add it back without first checking whether kde-neon has caught up to the current
ubuntu-<scope>default.Test plan
release-targets/targets-release-*.yamland confirmkde-neonis gone from the matrix output (onlykde-plasmablocks remain).armbian/osbuild ofdesktop-stable-ubuntu-kde-plasmaagainst a fast-HDMI board and confirm the rootfs assembles + image builds._kde-plasma_.