From 5b1f906372e1611ceb1177733d7ec395f3a09e46 Mon Sep 17 00:00:00 2001 From: Javier Tia Date: Thu, 19 Nov 2026 12:57:39 -0600 Subject: [PATCH] Fix the feed notes and the package url The README said the feed today is 2024/edge-next and that the 2026 feed publishes only jetson-agx-thor, and the Test workflow comment said 2024/next is where the targets are published today. None of that holds: the workflows pass 2024/next, the 2026 feed has qemux86-64 on both edge and next, and edge-next is stale. The avocado.yaml url also pointed at github.com/avocadolinux/avocado-os, a 404 because the organization is avocado-linux, and extensions and BSPs now live in their own repositories rather than in avocado-os. The url ships in every derived package. State the feed the workflows use and how to check whether a target exists in the 2026 feed, and point the url at this repository with a note to set it to the new one. The workflow change is a comment only. --- .github/workflows/test.yml | 8 +++++--- README.md | 7 ++++--- avocado.yaml | 3 ++- 3 files changed, 11 insertions(+), 7 deletions(-) diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml index fcd54ef..abc3273 100644 --- a/.github/workflows/test.yml +++ b/.github/workflows/test.yml @@ -3,9 +3,11 @@ name: Test # "Does it build" check on PRs. The matrix lives here (the caller owns it); each leg # calls the single-combo reusable helper. Add rows for more targets/feeds as needed. # -# Feed is 2024/next because that is where the targets are published today. Flip a leg to -# { distro-release: "2026", distro-channel: next } once your target exists in the 2026 -# feed. Note this only picks the feed + SDK image tag — the sdk.image string in +# Feed is 2024/next. Some targets are published in the 2026 feed too: flip a leg to +# { distro-release: "2026", distro-channel: next } once the packages your extension +# depends on exist there (check +# https://repo.avocadolinux.org/2026/next/target//repodata/repomd.xml). +# Note this only picks the feed + SDK image tag — the sdk.image string in # avocado.yaml stays release-scoped either way. on: pull_request: diff --git a/README.md b/README.md index 83f39af..9779a62 100644 --- a/README.md +++ b/README.md @@ -30,9 +30,10 @@ Release: tag the commit with the exact `avocado.yaml` version, e.g. `git tag 0.1 selects the *package feed*; the image tag is per-release only. - **CI comes from `avocado-linux/actions@v1`**, pinned. The matrix lives in the caller so each repo owns its own target/feed combinations. -- **Feed today is `2024`/`edge-next`.** `avocado-linux/actions@v1` *defaults* to - `2026`/`edge`, but the 2026 feed currently publishes only `jetson-agx-thor`, so the - workflows here pass 2024 explicitly. Move a target to 2026 as it lands there. +- **The workflows here use the `2024`/`next` feed.** `avocado-linux/actions@v1` *defaults* + to `2026`/`edge`, but the workflows pass `2024`/`next` explicitly. Add or move a row to + `2026` once the packages your extension depends on are published there. Check + `https://repo.avocadolinux.org/2026/next/target//repodata/repomd.xml`. ## Using this extension diff --git a/avocado.yaml b/avocado.yaml index dc5de79..b3e5c38 100644 --- a/avocado.yaml +++ b/avocado.yaml @@ -10,7 +10,8 @@ extensions: summary: One-line summary description: One-line description license: Apache-2.0 - url: https://github.com/avocadolinux/avocado-os + # Set this to your repository's URL. + url: https://github.com/avocado-linux/ext-template vendor: Avocado Linux # Runtime packages pulled from the target feed.