external: add resolute (Ubuntu 26.04 LTS) to desktop package coverage#444
Merged
igorpecovnik merged 3 commits intomainfrom Apr 13, 2026
Merged
external: add resolute (Ubuntu 26.04 LTS) to desktop package coverage#444igorpecovnik merged 3 commits intomainfrom
igorpecovnik merged 3 commits intomainfrom
Conversation
Mirrors the existing noble desktop sources for the new LTS so the desktop YAML in configng (PR armbian/configng#848) can rely on apt.armbian.com for chromium/firefox/thunderbird/code/chrome/edge on resolute, not just on noble. New per-release files: chromium-aarch64-resolute.conf — xtradeb/apps PPA, arm64 firefox-resolute.conf — mozillateam PPA, all 4 arches thunderbird-resolute.conf — mozillateam PPA, all 4 arches Multi-release RELEASE lists gain `resolute`: code.conf, codium.conf (vscode + vscodium) discord.conf edge.conf google-chrome.conf zoom.conf Untouched (utils, separate concern — split off if needed): urbackup-server-noble.conf, zfs-noble.conf, rpi-libraspberrypi-bin-noble.conf, rpi-pi-bluetooth-ubuntu.conf, rpi-ubuntu-firmware-raspi.conf If any upstream PPA does not yet publish for resolute, the aptly build of that source will surface the gap on the next run.
PR armbian/configng#848 expects apt.armbian.com to host the snap- shim workarounds (chromium / firefox / thunderbird) and vendor desktop apps (chrome / code / codium / edge / discord / zoom) on every non-eos release armbian/build supports. The previous commit covered noble + resolute; this one fills in the rest. Added per-release noble-style files for snap-shim workarounds: chromium-aarch64-jammy.conf — re-enabled (was .disabled); uses liujianfeng1994/chromium PPA chromium-aarch64-questing.conf — xtradeb/apps PPA, arm64 firefox-jammy.conf — mozillateam PPA, all 4 arches firefox-questing.conf — mozillateam PPA, all 4 arches thunderbird-jammy.conf — mozillateam PPA, all 4 arches thunderbird-questing.conf — mozillateam PPA, all 4 arches Multi-release RELEASE lists gain `jammy` (Ubuntu LTS, csc) and `forky` (next Debian stable, csc): code.conf, codium.conf discord.conf edge.conf google-chrome.conf zoom.conf Releases skipped on purpose: plucky — eos as of 2026-01-25 (armbian/build PR #9657) sid — Debian unstable; rolling, vendor debs may break loong64 — separate arch story; not yet a desktop target If a particular upstream PPA (notably mozillateam, xtradeb, liujianfeng1994) doesn't actually publish for a given release, the aptly build of that source will fail loudly on next run and we drop that single config — better than silent gaps.
igorpecovnik
changed the title
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.
armbian/configng PR for `drop-plucky-questing` removes both plucky and questing from every DE YAML's release blocks. Without a desktop YAML reference, the questing-specific aptly snapshots ship nothing useful — drop them rather than maintain dead sources. plucky was never added (it's eos), so nothing to drop there. The jammy + resolute additions stay — those are LTS releases the desktop YAML still supports.
4 tasks
igorpecovnik
added a commit
to armbian/configng
that referenced
this pull request
Apr 13, 2026
Two real (release, arch) gaps for `code` (Microsoft VSCode) that the apt.armbian.com expansion (armbian/os#444) doesn't fill: - `riscv64` every release — Microsoft publishes no riscv64 build upstream, so apt.armbian.com cannot mirror one. Permanent arch-wide hole; uses the per-arch tier_overrides layer. - `sid` every arch — Debian unstable is intentionally not tracked in apt.armbian.com (vendor debs may break against rolling base). Per-release strip across all four arches. The other combos a code-review bot flagged (forky/jammy/resolute for `code`; jammy/resolute amd64+arm64 for `thunderbird`) are either covered by armbian/os#444 (apt.armbian.com expansion) or already removed in #849 (plucky/questing drop) — no further YAML changes needed for them. The BSP pin file at packages/bsp/common/etc/apt/preferences.d/armbian forces o=Armbian to priority 1001 over Ubuntu's 50, so the real apt. armbian.com .debs win on every release/arch where they exist.
igorpecovnik
changed the title
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
Two real (release, arch) gaps for `code` (Microsoft VSCode) that the apt.armbian.com expansion (armbian/os#444) doesn't fill: - `riscv64` every release — Microsoft publishes no riscv64 build upstream, so apt.armbian.com cannot mirror one. Permanent arch-wide hole; uses the per-arch tier_overrides layer. - `sid` every arch — Debian unstable is intentionally not tracked in apt.armbian.com (vendor debs may break against rolling base). Per-release strip across all four arches. The other combos a code-review bot flagged (forky/jammy/resolute for `code`; jammy/resolute amd64+arm64 for `thunderbird`) are either covered by armbian/os#444 (apt.armbian.com expansion) or already removed in #849 (plucky/questing drop) — no further YAML changes needed for them. The BSP pin file at packages/bsp/common/etc/apt/preferences.d/armbian forces o=Armbian to priority 1001 over Ubuntu's 50, so the real apt. armbian.com .debs win on every release/arch where they exist.
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
resolute just promoted to
supportedin armbian/build#9657. Mirror the existing noble desktop sources for the new LTS so the desktop YAML in armbian/configng#848 can rely on apt.armbian.com for chromium / firefox / thunderbird and the vendor apps on resolute.New per-release files
chromium-aarch64-resolute.conffirefox-resolute.confthunderbird-resolute.confRELEASElists extended to includeresolutecode.conf,codium.conf,discord.conf,edge.conf,google-chrome.conf,zoom.confReleases skipped on purpose
Out of scope
Utils packages with their own scope (
urbackup-server-*,zfs-*,harfbuzz-jammy.conf,libcec6-sid-to-jammy.conf,rpi-*) — extend in a follow-up if needed.Test plan
code/codium/discord/edge/google-chrome/zoomresolute snapshots build (Microsoft / Google / vendor sources should support resolute as the new LTS)