To replicate: mkdir ~/cow; cd ~/cow; . ~/poky/oe-init-build-env .; . toaster start; # . toaster start will fail: sqlite3.OperationalError: unable to open database file │································· ++++++++++++ a proposal: Currently, we reach "above" the build dir and put toaster directory's e.g. build_toaster_xx and _toaster_clones_ there. Unfortunately, we can't even guarantee that the running user has permissions to access the directory above the builddir. For example, if I do cd ~;. ~/poky/oe-init-build-env .; I don't have permission for /home. So, I'd be ok with a standard start being build/ build/conf build/toaster_build_XX build/_toaster_clones_ That way cd ~;. ~/poky/oe-init-build-env .;. toaster start; would work.
hint this currently set in: toastermain/settings.py TOASTER_SQLITE_DEFAULT_DIR = os.path.join(os.environ.get('TOASTER_DIR', ''), 'build') DATABASES = { 'default': { # Add 'postgresql_psycopg2', 'mysql', 'sqlite3' or 'oracle'. 'ENGINE': 'django.db.backends.sqlite3', # DB name or full path to database file if using sqlite3. 'NAME': "%s/toaster.sqlite" % TOASTER_SQLITE_DEFAULT_DIR, 'USER': '', (We should really ecourage people to write their own config files such as we have for the test db toastermain/settings_test.py)
*** Bug 10524 has been marked as a duplicate of this bug. ***
sent to toaster ml: https://patchwork.openembedded.org/series/5104/
f43d97af9466580c3a10d766791836b42c674497