Le 19/10/2015 13:50, [email protected] a écrit : > Every now and then I still build b2g to test something out. So far *every > single time* |git pull && ./config.sh flame-kk| breaks on some repository > which is apparently changed but that I never touched. How is this user > friendly?!
Do you change the target device frequently ? For me I found this was the reason (and I use --force-sync to overcome this). > > Sooooo let's run the suggested: repo sync --force-sync prebuilts/qemu-kernel > > -bash: repo: command not found It should be "./repo" but we don't have control over repo's error messages. That said it's not possible to use repo before config.sh successfully ran... that's why I made it easier to pass "--force-sync" to "config.sh" in bug 1211869 <https://bugzilla.mozilla.org/show_bug.cgi?id=1211869>. > P.S.3. I have my own gecko configured in .userconfig, so if I see: `gecko/: > discarding 2 commits` after config'ing, I'm quite worried. Config should not > touch my gecko. Repo still downloads a copy of gecko. .userconfig is used only when building AFAIK. -- Julien
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
