Skip to content

Fix the feed notes and the package url - #4

Merged
mobileoverlord merged 1 commit into
mainfrom
misc-1112/fix-feed-and-url
Nov 19, 2026
Merged

mobileoverlord merged 1 commit into
mainfrom
misc-1112/fix-feed-and-url

Conversation

@jetm

@jetm jetm commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Problem

Three notes in the template are wrong. The README says the feed today is 2024/edge-next and that the 2026 feed publishes only jetson-agx-thor. The Test workflow comment says 2024/next is where the targets are published today. And the url: in avocado.yaml points at github.com/avocadolinux/avocado-os, which returns 404 because the organization is avocado-linux,. That url ships in every package built from a derived repo.

Solution

State the feed the workflows actually use, and how to check whether a target exists in the 2026 feed. Point the url at this repository, with a note to set it to the new one.

Key changes

  • README.md: the feed bullet now says the workflows use 2024/next, actions@v1 defaults to 2026/edge, and gives the repomd.xml path to check.
  • .github/workflows/test.yml: comment only, same correction.
  • avocado.yaml: url becomes https://github.com/avocado-linux/ext-template, with a comment to replace it.

Reviewer notes

I checked the feed with status codes: qemux86-64 returns 200 for 2024/next, 2026/next and 2026/edge, and jetson-agx-thor returns 200 for 2026/next. github.com/avocado-linux/avocado-os returns 200. I parsed the two edited YAML files; no workflow logic changed. github.com/avocado-linux/ext-template returns 200. bsp-raspberrypi5/avocado.yaml had the same wrong url and is fixed in avocado-linux/bsp-raspberrypi5#4.

@jetm
jetm force-pushed the misc-1112/fix-feed-and-url branch from c2a4450 to 0a0d738 Compare November 19, 2026 19:08
@jetm jetm changed the title Fix the feed notes and the avocado-os URL Fix the feed notes and the package url Nov 19, 2026
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.

@mobileoverlord mobileoverlord left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved. The feed notes match what the workflows pass, the repomd.xml check URL resolves (200), and the corrected avocado-linux/avocado-os URL resolves too. #5 adds the 2026 legs on top of this; I'll rebase it after this merges.

@mobileoverlord
mobileoverlord merged commit d2d524d into main Nov 19, 2026
1 check passed
@mobileoverlord
mobileoverlord deleted the misc-1112/fix-feed-and-url branch November 19, 2026 19:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants