Repository navigation
Fix the feed notes and the package url - #4
Merged
Merged
Conversation
jetm
force-pushed
the
misc-1112/fix-feed-and-url
branch
from
November 19, 2026 19:08
c2a4450 to
0a0d738
Compare
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.
jetm
force-pushed
the
misc-1112/fix-feed-and-url
branch
from
November 19, 2026 19:12
0a0d738 to
5b1f906
Compare
mobileoverlord
approved these changes
Nov 19, 2026
mobileoverlord
left a comment
Contributor
There was a problem hiding this comment.
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.
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
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.
Problem
Three notes in the template are wrong. The README says the feed today is
2024/edge-nextand that the 2026 feed publishes onlyjetson-agx-thor. The Test workflow comment says2024/nextis where the targets are published today. And theurl:inavocado.yamlpoints atgithub.com/avocadolinux/avocado-os, which returns 404 because the organization isavocado-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 use2024/next,actions@v1defaults to2026/edge, and gives therepomd.xmlpath to check..github/workflows/test.yml: comment only, same correction.avocado.yaml:urlbecomeshttps://github.com/avocado-linux/ext-template, with a comment to replace it.Reviewer notes
I checked the feed with status codes:
qemux86-64returns 200 for2024/next,2026/nextand2026/edge, andjetson-agx-thorreturns 200 for2026/next.github.com/avocado-linux/avocado-osreturns 200. I parsed the two edited YAML files; no workflow logic changed.github.com/avocado-linux/ext-templatereturns 200.bsp-raspberrypi5/avocado.yamlhad the same wrong url and is fixed in avocado-linux/bsp-raspberrypi5#4.