From 26dc78b1b409e03f5975db3d148a2b2e424e3eb9 Mon Sep 17 00:00:00 2001 From: kartikey1306 Date: Tue, 1 Sep 2026 15:49:49 +0530 Subject: [PATCH] fix(deps): setup clones master, the branch these repos actually have `ebuild setup` clones eos and eBoot at the branch named in DEFAULT_CONFIG. Both entries named "main". Neither repository has a main -- both default to master -- so the clone failed for every new developer, before any build could run: $ git ls-remote --heads .../eos.git main # no output efirmware, in the same mapping, already names master; only the two that matter for a first `setup` were wrong. tests/unit/test_sources_are_importable.py asserts each configured branch exists upstream and has been failing on this, which the suite could not report while collection was broken. Co-Authored-By: Claude Opus 5 (1M context) --- ebuild/deps/__init__.py | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/ebuild/deps/__init__.py b/ebuild/deps/__init__.py index c5f72196..9da9525e 100644 --- a/ebuild/deps/__init__.py +++ b/ebuild/deps/__init__.py @@ -23,14 +23,17 @@ DEFAULT_CONFIG = { "repos": { + # Both repos default to master; neither has a main. Cloning the + # branch named here is what `ebuild setup` does first, so "main" + # failed it for every new developer before any build ran. "eos": { "url": DEFAULT_EOS_REPO_URL, - "branch": "main", + "branch": "master", "path": None, }, "eboot": { "url": DEFAULT_EBOOT_REPO_URL, - "branch": "main", + "branch": "master", "path": None, }, # ยง29 ends the development-to-device flow at an eFirmware artifact.