python stack trace when manifest project branch is broken

Reported by Shawn Pearce <sop@google.com> on Tue Apr 14 18:06:31 PDT 2009
Source: JIRA REPO-24
Affected Version: 1.6.5

If the manifest project is not on a "proper" branch, we get a stack trace from
just about every command:

$ repo start gl
frameworks/base hardware/libhardware system/core vendor/htc/dream
vendor/htc/sapphire vendor/qcom/proprietary
Traceback (most recent call last):
 File "/Volumes/sources/git/android/master/.repo/repo/main.py", line 230, in ?
   _Main(sys.argv[1:])
 File "/Volumes/sources/git/android/master/.repo/repo/main.py", line
214, in _Main
   repo._Run(argv)
 File "/Volumes/sources/git/android/master/.repo/repo/main.py", line
121, in _Run
   cmd.Execute(copts, cargs)
 File "/Volumes/sources/git/android/master/.repo/repo/subcmds/start.py",
line 51, in Execute
   for project in self.GetProjects(args[1:]):
 File "/Volumes/sources/git/android/master/.repo/repo/command.py",
line 60, in GetProjects
   all = self.manifest.projects
 File "/Volumes/sources/git/android/master/.repo/repo/manifest.py",
line 148, in projects
   self._Load()
 File "/Volumes/sources/git/android/master/.repo/repo/manifest.py",
line 176, in _Load
   if b.startswith(R_HEADS):
AttributeError: 'NoneType' object has no attribute 'startswith'

Original issue reported on code.google.com by code-rev...@gtempaccount.com on 24 Sep 2009 at 9:10

azzurris / git-repo

python stack trace when manifest project branch is broken #24