Skip to content

external: enable code (VSCode) pull for jammy#457

Merged
igorpecovnik merged 1 commit intomainfrom
code-jammy
Apr 20, 2026
Merged

external: enable code (VSCode) pull for jammy#457
igorpecovnik merged 1 commit intomainfrom
code-jammy

Conversation

@igorpecovnik
Copy link
Copy Markdown
Member

Summary

Add `jammy` to the RELEASE allow-list in `external/code.conf` so the `code` (Microsoft VSCode) package gets mirrored into apt.armbian.com's `jammy-desktop` component alongside the other five releases it already covers.

Background

`packages.microsoft.com/repos/code` publishes a single `stable main main` suite that serves every Debian + Ubuntu release — the apt metadata isn't release-scoped, just arch-scoped (armhf / arm64 / amd64). So from the PPA side there's nothing jammy-specific to configure; the suite + arches stay identical.

On the armbian-config side, the full-tier desktop install on jammy was previously failing with `E: Unable to locate package code` because our mirror hadn't ingested it for that release. With this change the next `Infrastructure: APT repositories update` run ingests code for jammy and the full-tier install resolves cleanly.

File

`external/code.conf`:

```
URL=https://packages.microsoft.com/repos/code
KEY="stable main main"
RELEASE=jammy:noble:resolute:bookworm:trixie:forky ← added jammy
TARGET=desktop
METHOD=aptly
INSTALL=code
GLOB="Name (% code), $Version (>= 1.107.0)"
CHECKSUM=ignore
ARCH=armhf:arm64:amd64
REPOSITORY=BS
```

Test plan

  • Next `Infrastructure: APT repositories update` run picks this up and mirrors code for jammy armhf/arm64/amd64 into debs-beta/debs.
  • Post-sync: `apt-cache policy code` on a jammy/arm64 or jammy/amd64 Armbian install shows apt.armbian.com as a candidate with version ≥ 1.107.0.
  • `armbian-config --api module_desktops install de=xfce tier=full` on jammy no longer hits `E: Unable to locate package code`.

Microsoft publishes a single 'stable main main' suite at
packages.microsoft.com/repos/code that serves every Debian and
Ubuntu release we target — the apt metadata isn't release-specific,
just architecture-specific. Adding jammy to the RELEASE allow-list
starts mirroring the same code package (armhf/arm64/amd64) into
apt.armbian.com's jammy-desktop component that the other five
releases already get.

Keeps the Armbian apt repo consistent across releases: a jammy
desktop install via armbian-config module_desktops (full tier)
was previously failing with 'E: Unable to locate package code'
because the mirror hadn't ingested code for jammy. With this
change the next 'Infrastructure: APT repositories update' run
picks up the new config and the full-tier install resolves
cleanly on jammy.
@github-actions github-actions Bot added the Software package Executing build train label Apr 20, 2026
@igorpecovnik igorpecovnik merged commit c9ea1b1 into main Apr 20, 2026
3 checks passed
@igorpecovnik igorpecovnik deleted the code-jammy branch April 20, 2026 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Software package Executing build train

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant