Repository navigation
Upstream watch: read L4T versions from NVIDIA's package index - #14
Merged
SpectrumFRC3847 merged 1 commit intoOct 15, 2026
Merged
Conversation
Member
Author
|
@allengregoryiv new one, ready for a review. The weekly upstream watch's L4T check has been skipping since NVIDIA removed the directory listing it read. Details are in the description. |
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.
What this changes
The weekly upstream watch's L4T check has not run for at least this month. NVIDIA removed the directory listing at
https://repo.download.nvidia.com/jetson/common/dists/, so it returns 404. The script printed "couldn't reach NVIDIA's apt repo (HTTP Error 404: Not Found): L4T not checked this run" and passed. The Oct 12 run (38258673077) shows it.https://repo.download.nvidia.com/jetson/, which lists every package file, and takes the L4T versions from the t234nvidia-l4t-corepackages (nvidia-l4t-core_36.5.2-...deb).L4T_VERSION=36.5.2, so a point release like 36.5.3 is reported. Before, it compared only36.5.nvidia-l4t-coreentries now fails the run, since both mean the URL or format changed again. Timeouts and other network errors still skip the check for that run.Checks
report_l4t()against the live index: it reports nothing new for 36.5.2. With the pin set to 36.4.7 it reportsr36.5.0,r36.5.1,r36.5.2.scripts/ci/lint.shis clean.Noticed, not fixed