Closed Bug 872817 Opened 13 years ago Closed 13 years ago

b2g peak build fails with missing peak.xml manifest

Categories

(Firefox OS Graveyard :: GonkIntegration, defect)

x86
All
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: cr, Unassigned)

Details

Steps to reproduce: $ git clone git://github.com/mozilla-b2g/B2G.git $ cd B2G $ ./config.sh peak Get git://github.com/mozilla-b2g/b2g-manifest remote: Counting objects: 620, done. remote: Compressing objects: 100% (326/326), done. remote: Total 620 (delta 398), reused 483 (delta 276) Receiving objects: 100% (620/620), 128.81 KiB, done. Resolving deltas: 100% (398/398), done. From git://github.com/mozilla-b2g/b2g-manifest * [new branch] master -> origin/master * [new branch] v1-train -> origin/v1-train * [new branch] v1.0.0 -> origin/v1.0.0 * [new branch] v1.0.1 -> origin/v1.0.1 * [new tag] B2G_1_0_1_20130213094222 -> B2G_1_0_1_20130213094222 * [new tag] closing-nightly -> closing-nightly fatal: manifest 'peak.xml' not available fatal: manifest peak.xml not found Repo sync failed Problem: config.sh checks out the default branch of git://github.com/mozilla-b2g/b2g-manifest, but peak.xml is only available in master. $ cd .repo/manifests/ $ git branch * default $ ls -l peak.xml ls: peak.xml: No such file or directory $ git checkout master Branch master set up to track remote branch master from origin. Switched to a new branch 'master' $ ls -l peak.xml -rw-r--r-- 1 cruetten staff 11083 16 May 00:48 peak.xml Workaround: $ BRANCH=master ./config.sh peak Fix: Update default branch of b2g-manifest Then again, why is the default branch being checked out when default parameter substitution BRANCH=${BRANCH:-v1-train} in config.sh suggests that v1-train should be used? Either way, it is missing peak.xml, too.
The v1-train branch is not reasonable for the peak since it doesn't support HDPI. Not having a peak manifest was intentional.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.