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?!

Today:

Fetching project fake-qemu-kernel
error: Cannot fetch fake-qemu-kernel (GitError: --force-sync not enabled; 
cannot overwrite a local work tree. If you're comfortable with the possibility 
of losing the work tree's git metadata, use `repo sync --force-sync 
prebuilts/qemu-kernel` to proceed.)
Fetching project platform/external/jack
Exception in thread Thread-22:
Traceback (most recent call last):
  File 
"/usr/local/Cellar/python/2.7.9/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py",
 line 810, in __bootstrap_inner
    self.run()
  File 
"/usr/local/Cellar/python/2.7.9/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py",
 line 763, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/Volumes/repos/b2g/.repo/repo/subcmds/sync.py", line 265, in 
_FetchProjectList
    success = self._FetchHelper(opt, project, *args, **kwargs)
  File "/Volumes/repos/b2g/.repo/repo/subcmds/sync.py", line 308, in 
_FetchHelper
    optimized_fetch=opt.optimized_fetch)
  File "/Volumes/repos/b2g/.repo/repo/project.py", line 1147, in 
Sync_NetworkHalf
    self._InitGitDir(force_sync=force_sync)
  File "/Volumes/repos/b2g/.repo/repo/project.py", line 2171, in _InitGitDir
    raise e
GitError: --force-sync not enabled; cannot overwrite a local work tree. If 
you're comfortable with the possibility of losing the work tree's git metadata, 
use `repo sync --force-sync prebuilts/qemu-kernel` to proceed.

Fetching projects:  15% (21/139)
error: Exited sync due to fetch errors
Repo sync failed

... I NEVER EVER touched fake-qemu-kernel ...

Sooooo let's run the suggested: repo sync --force-sync prebuilts/qemu-kernel

-bash: repo: command not found

OK. So where the f* is fake-qemu-kernel located... I'd guess in 
prebuilts/qemu-kernel as that's what repo sync suggests.

Jans-MacBook-Pro-2:b2g janjongboom$ cd prebuilts/qemu-kernel
Jans-MacBook-Pro-2:qemu-kernel janjongboom$ git status
Not currently on any branch.
nothing to commit, working directory clean

OK. So I'm not even on a branch so why the f* is it complaining?!

Ah well, I know that we have a repo bundled with the b2g repo so I can then use 
that to remove it, but seriously. I want to run ./config.sh flame-kk on a clean 
directory and that it would just like, urm, work?

P.S. I'm also pretty sure that similar errors can show up that just report the 
name and not where they're located on filesystem (bluetooth library does this I 
think if you have a dirty version of that) which will leave you clueless 
because there's no direct mapping between name and fs location.

P.S.2. It also happens that config just exists with 'Cannot fetch repository'. 
Sooo... which one? Why? Why didn't it retry?

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.
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos

Reply via email to