config/distributions: plucky -> eos, resolute -> supported#9657
config/distributions: plucky -> eos, resolute -> supported#9657igorpecovnik merged 1 commit intomainfrom
Conversation
Plucky (Ubuntu 25.04) is a 9-month interim that Canonical EOL'd on 2026-01-25, three months before today's build. Moving it to `eos` prevents the images from being produced against an archive that no longer receives security updates. Resolute (Ubuntu 26.04 LTS) just released and has been stable for our csc builds, so promote it to `supported` alongside noble and trixie.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughTwo distribution support marker files were updated with different values. The plucky distribution support marker changed from Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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. Comment |
plucky (Ubuntu 25.04) is eos as of 2026-01-25 — see armbian/build#9657 where we flipped its support flag. The audit script already excludes eos releases from the missing-releases report, but it does not auto-remove existing entries; those just sit as drift. questing (Ubuntu 25.10) is a 9-month interim release with about 3 months of life left (EOL ~2026-07). Rare on real boards and not worth the per-release maintenance overhead. Dropped: common.yaml - browser map: plucky, questing entries - tier_overrides.mid.releases: plucky, questing loupe blocks - tier_overrides.full.releases: plucky, questing thunderbird blocks (jammy still strips on armhf+riscv64; resolute keeps its strip) per-DE YAMLs (11 files): plucky and questing release blocks Bianbu was already noble+resolute only; nothing to drop there. Comments mentioning plucky/questing as historical context (e.g. "pavumeter dropped in plucky") are kept — those are reference, not active config. Verified DESKTOP_SUPPORTED="yes" still for every kept release/arch combo on xfce; "no" for plucky/questing as expected. Knock-on: armbian/os#444 will drop the questing aptly configs (chromium-aarch64-questing.conf, firefox-questing.conf, thunderbird-questing.conf) since this PR removes their consumer.
plucky (Ubuntu 25.04) is eos as of 2026-01-25 — see armbian/build#9657 where we flipped its support flag. The audit script already excludes eos releases from the missing-releases report, but it does not auto-remove existing entries; those just sit as drift. questing (Ubuntu 25.10) is a 9-month interim release with about 3 months of life left (EOL ~2026-07). Rare on real boards and not worth the per-release maintenance overhead. Dropped: common.yaml - browser map: plucky, questing entries - tier_overrides.mid.releases: plucky, questing loupe blocks - tier_overrides.full.releases: plucky, questing thunderbird blocks (jammy still strips on armhf+riscv64; resolute keeps its strip) per-DE YAMLs (11 files): plucky and questing release blocks Bianbu was already noble+resolute only; nothing to drop there. Comments mentioning plucky/questing as historical context (e.g. "pavumeter dropped in plucky") are kept — those are reference, not active config. Verified DESKTOP_SUPPORTED="yes" still for every kept release/arch combo on xfce; "no" for plucky/questing as expected. Knock-on: armbian/os#444 will drop the questing aptly configs (chromium-aarch64-questing.conf, firefox-questing.conf, thunderbird-questing.conf) since this PR removes their consumer.
…EN01) resolute (Ubuntu 26.04 LTS) just promoted to `supported` in armbian/build#9657, and apt.armbian.com#444 added apt.armbian.com coverage for the snap-shim workarounds + vendor desktop apps on resolute. Time to actually exercise the desktop install path on resolute in CI. Add `resolute` to RELEASE in every desktop test (10 of 11 had `bookworm:trixie:noble`; BUDG01 had only `trixie:noble`). Also drop `plucky` from KDEN01 — plucky is eos as of 2026-01-25, no point running tests against an eos release.
…EN01) resolute (Ubuntu 26.04 LTS) just promoted to `supported` in armbian/build#9657, and apt.armbian.com#444 added apt.armbian.com coverage for the snap-shim workarounds + vendor desktop apps on resolute. Time to actually exercise the desktop install path on resolute in CI. Add `resolute` to RELEASE in every desktop test (10 of 11 had `bookworm:trixie:noble`; BUDG01 had only `trixie:noble`). Also drop `plucky` from KDEN01 — plucky is eos as of 2026-01-25, no point running tests against an eos release.
…853) * tests: enable resolute on every desktop test (and drop plucky from KDEN01) resolute (Ubuntu 26.04 LTS) just promoted to `supported` in armbian/build#9657, and apt.armbian.com#444 added apt.armbian.com coverage for the snap-shim workarounds + vendor desktop apps on resolute. Time to actually exercise the desktop install path on resolute in CI. Add `resolute` to RELEASE in every desktop test (10 of 11 had `bookworm:trixie:noble`; BUDG01 had only `trixie:noble`). Also drop `plucky` from KDEN01 — plucky is eos as of 2026-01-25, no point running tests against an eos release. * desktops: drop libu2f-udev from resolute (no installation candidate) libu2f-udev was an Ubuntu/Debian transitional package that shipped udev rules for U2F security keys. The rules have since been absorbed into `udev` itself (and `libfido2-1` for newer FIDO2 flows), so resolute (Ubuntu 26.04 LTS) drops the transitional package from the archive entirely. Symptom on resolute desktop install: E: Package 'libu2f-udev' has no installation candidate Strip `- libu2f-udev` from each DE YAML's `resolute:` release block (8 files: cinnamon, enlightenment, gnome, i3-wm, kde-plasma, mate, xfce, xmonad). Other release blocks keep it — bookworm/trixie/ noble/jammy/forky/sid still ship the transitional package and the desktop install path on those releases continues to install it. Bianbu has a resolute block but never carried libu2f-udev, so no change there. * desktops: add libfido2-1 to resolute as the libu2f-udev replacement Restores U2F / FIDO2 security-key support (used by Chrome/Chromium and Firefox WebAuthn) on resolute. The previous commit dropped libu2f-udev because resolute no longer ships the transitional package; libfido2-1 is the modern stack that supersedes it and ships the same `/lib/udev/rules.d/70-u2f.rules` style rules needed for an unprivileged browser to talk to /dev/hidraw* of a plugged-in security key. Added to the resolute release block of the same 8 DE YAMLs touched in the previous commit (cinnamon, enlightenment, gnome, i3-wm, kde-plasma, mate, xfce, xmonad). Other releases keep libu2f-udev — those still ship the transitional package and the modern libfido2-1 isn't needed there. Bianbu untouched — it never carried libu2f-udev either.
Summary
Routine maintenance of
config/distributions/*/supportflags:cscstatus produces images against an archive that no longer receives security updates.cscfor at least one cycle. Promote alongsidenobleandtrixieso the desktop matrix audit and other consumers treat it as a first-class supported release.Current state before this PR:
Test plan
grep -l supported config/distributions/*/supportlists noble, trixie, resolutegrep -l eos config/distributions/*/supportlists bullseye, buster, focal, oracular, pluckyresoluteas a supported release on its next runSummary by CodeRabbit