Skip to content

config/distributions: plucky -> eos, resolute -> supported#9657

Merged
igorpecovnik merged 1 commit intomainfrom
distributions-status-update
Apr 12, 2026
Merged

config/distributions: plucky -> eos, resolute -> supported#9657
igorpecovnik merged 1 commit intomainfrom
distributions-status-update

Conversation

@igorpecovnik
Copy link
Copy Markdown
Member

@igorpecovnik igorpecovnik commented Apr 12, 2026

Summary

Routine maintenance of config/distributions/*/support flags:

  • plucky → eos — Ubuntu 25.04 is a 9-month interim release that Canonical EOL'd on 2026-01-25 (three months ago). Keeping csc status produces images against an archive that no longer receives security updates.
  • resolute → supported — Ubuntu 26.04 LTS just released and has been running as csc for at least one cycle. Promote alongside noble and trixie so the desktop matrix audit and other consumers treat it as a first-class supported release.

Current state before this PR:

release support
noble supported
trixie supported
resolute csc → supported
plucky csc → eos

Test plan

  • grep -l supported config/distributions/*/support lists noble, trixie, resolute
  • grep -l eos config/distributions/*/support lists bullseye, buster, focal, oracular, plucky
  • configng's desktop matrix audit picks up resolute as a supported release on its next run

Summary by CodeRabbit

  • Chores
    • Updated support status configuration for Plucky and Resolute distributions.

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.
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 12, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 1b20edaf-03da-4560-bdbe-5045e88cf9fb

📥 Commits

Reviewing files that changed from the base of the PR and between fdef407 and dc27911.

📒 Files selected for processing (2)
  • config/distributions/plucky/support
  • config/distributions/resolute/support

📝 Walkthrough

Walkthrough

Two distribution support marker files were updated with different values. The plucky distribution support marker changed from csc to eos, and the resolute distribution support marker changed from csc to supported.

Changes

Cohort / File(s) Summary
Distribution Support Markers
config/distributions/plucky/support, config/distributions/resolute/support
Updated support status values in configuration files. Plucky support changed to eos, resolute support changed to supported.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Hop, hop, the markers now declare,
Plucky's eos flows through the air,
Resolute stands supported and true,
Distribution paths, freshly renewed! 🎉

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely summarizes the main changes: updating distribution support markers for plucky (csc→eos) and resolute (csc→supported), directly matching the file modifications.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch distributions-status-update

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions Bot added size/small PR with less then 50 lines 05 Milestone: Second quarter release Needs review Seeking for review labels Apr 12, 2026
@igorpecovnik igorpecovnik merged commit 1008b72 into main Apr 12, 2026
12 checks passed
@igorpecovnik igorpecovnik deleted the distributions-status-update branch April 12, 2026 22:17
igorpecovnik added a commit to armbian/configng that referenced this pull request Apr 13, 2026
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.
igorpecovnik added a commit to armbian/configng that referenced this pull request Apr 13, 2026
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.
igorpecovnik added a commit to armbian/configng that referenced this pull request Apr 13, 2026
…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.
igorpecovnik added a commit to armbian/configng that referenced this pull request Apr 14, 2026
…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.
igorpecovnik added a commit to armbian/configng that referenced this pull request Apr 14, 2026
…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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

05 Milestone: Second quarter release Needs review Seeking for review size/small PR with less then 50 lines

Development

Successfully merging this pull request may close these issues.

1 participant