Closed
Bug 1266723
Opened 8 years ago
Closed 8 years ago
Wrong gaia branch in latest build.
Categories
(Firefox OS Graveyard :: Gaia, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jkt, Unassigned)
References
Details
Attachments
(1 file)
20.45 KB,
patch
|
gerard-majax
:
review+
|
Details | Diff | Splinter Review |
Latest build https://tools.taskcluster.net/task-inspector/#MSx4qIL9T12ToZDSFWXdag/0 uses master branch of gaia. Currently getting the wrong 'webapps' vs 'apps' dir in this build. Should be using kanikani as per: https://wiki.mozilla.org/B2G/Transition_Project
Comment 1•8 years ago
|
||
Yes, I cannot tell why but sources.xml points to a954bd2954c422b7d24d92cfd73000cb455dce44 which looks to be a commit from the master branch: https://github.com/mozilla-b2g/gaia/tree/a954bd2954c422b7d24d92cfd73000cb455dce44 I am pretty sure :aus did a change to have a commit from kanikani, so I don't know what happened here.
Flags: needinfo?(aus)
Comment 2•8 years ago
|
||
Attachment #8744330 -
Flags: review+
Comment 4•8 years ago
|
||
I pushed this to unblock anyone needed working builds, but I would prefer we close this once we know why aus' changes got lost ...
Comment 5•8 years ago
|
||
This happened during the merge. Bumper bot unfortunately doesn't work on project branches and ultimately will be retired (soon). We're forced to bump the versions manually. Usually what's in gaia.json is what's used, if you're building gecko + gaia via mach. If you're building the full stack (./build.sh from a B2G repo) I believe it would also be using what's in gaia.json but with your patch seems to indicate that from building there it will use sources.xml first? I looked at the history of those and we never updated them until you did. :) We'll be talking about how to deal with this kind of stuff during the b2g transition infra/build meeting on thursday. I'm going to close this for now, I'll just remember to update sources.xml for the time being.
Flags: needinfo?(aus)
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•