Repository navigation
build: mirror ntfs-3g through the Fedora lookaside - #187
Merged
Merged
Conversation
download.tuxera.com returned 403 to GitHub's runners on two experimental release runs (2026-10-01, 14:43 and 15:11 UTC), and sources.buildroot.net has no copy of ntfs-3g 2026.2.25. Every FOS release failed in download_filesystem_packages. The same URL serves other hosts. seedFragileSources() now takes a Buildroot package as well as FOG's own. FOG ships only the package's .hash, with a sha512 added; build.sh's rsync lays it over Buildroot's copy. The .mk is read from Buildroot's tree, so the version still follows BUILDROOT_VERSION. readPackageVars() maps '-' to '_' (ntfs-3g -> NTFS_3G_*). bump-package.sh refuses to bump such a package and --check reads its .mk from a fssource*/ tree. Fedora's lookaside copy is byte-identical to tuxera's (sha256 7754f3b3...). Verified locally with tuxera blocked: the seed fell through to Fedora, and "make ntfs-3g-source" accepted the file with no network fetch. bump-package.sh --check passes for all six packages. The new harness cases fail when the .mk fallback or the '-' mapping is reverted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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
Every FOS release now fails in
download_filesystem_packages.download.tuxera.comreturns 403 to GitHub's runners forntfs-3g_ntfsprogs-2026.2.25.tgz, on run 36878008658 and on its re-run.sources.buildroot.nethas no copy. The same URL serves other hosts.Fix
seedFragileSources()takes a Buildroot package as well as FOG's own five. FOG ships only its.hash, with a sha512 added, underBuildroot/package/ntfs-3g/.build.sh's rsync lays that file over Buildroot's copy. The.mkstays Buildroot's, so the version followsBUILDROOT_VERSION.readPackageVars()maps-to_, sontfs-3gresolvesNTFS_3G_*.bump-package.shrefuses to bump a hash-only package.--checkreads its.mkfrom afssource*/tree when one exists.7754f3b3…, the same value as Buildroot's hash).Verification
src.fedoraproject.org.make ntfs-3g-sourceaccepted it with sha256 and sha512 OK and no fetch../bump-package.sh --check: all six packages OK.tests/checks/package-mirrors.sh: new cases 10 and 11, plus the shipped-file checks for ntfs-3g. They fail when I revert the.mkfallback or the-mapping.When the Buildroot pin moves ntfs-3g, update
Buildroot/package/ntfs-3g/ntfs-3g.hashby hand. Buildroot stops with "No hash found" if that is skipped.🤖 Generated with Claude Code