bitbake crashed with IndexError in base_get_scmbasepath()

[Michael Fritscher]

Binary package hint: bitbake

on bitbake world if BBFILES is not set

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/bitbake
InterpreterPath: /usr/bin/python2.5
Package: bitbake 1.8.10-3
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/bin/bitbake nano
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/arm/oe/bin:/usr/local/arm/oe/bin:/usr/local/arm/oe/bin:/usr/local/arm/oe/bin:/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
PythonArgs: ['/usr/bin/bitbake', 'nano']
SourcePackage: bitbake
Title: bitbake crashed with IndexError in base_get_scmbasepath()
Uname: Linux 2.6.27-6-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev pulse pulse-access pulse-rt sambashare scanner vboxusers video

[Loïc Minier (lool)]

I tried reproducing the problem from a clean install:

bitbake helloworld
ERROR: Please set the 'PERSISTENT_DIR' or 'CACHE' variable.

# git version
PATH="$PWD/bitbake/bin:$PATH" bitbake helloworld
The BBPATH variable is not set

PATH="$PWD/bitbake/bin:$PATH" BBPATH="$PWD/build:$PWD/openembedded" bitbake helloworld
ERROR: no recipe files to build, check your BBPATH and BBFILES?
ERROR: Openembedded's config sanity checker detected a potential misconfiguration.
        Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
        Following is the list of potential problems / advisories:

        Please set TARGET_ARCH directly, or choose a MACHINE or DISTRO that does so.
Please set TARGET_OS directly, or choose a MACHINE or DISTRO that does so.
DISTRO 'None' not found. Please set a valid DISTRO in your local.conf
Please install following missing utilities: help2man,texi2html,makeinfo,chrpath
Using dash as /bin/sh causes various subtle build problems, please use bash instead.

So it seems that the git version of bitbake is a bit more helpful; I guess we can close this bug when we update bitbake to some modern 1.10.x version.