You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Studio name: Balance Film GmbH
Zou version: 0.20.15
Zou installation type: self-hosted
Ubuntu Version 24.04.1 LTS
Describe the bug
While running bin/zou init-db while installing zou, it fails with a python error (Traceback attached) and does not initialize the zou database. As a result, the database remains empty.
Python3.12 is installed.
Expected behavior
init-db should initialise the zou database.
Additional context
I was following the instructions at https://zou.cg-wire.com/ for setting up zou. We previously had a much older version (0.16.x) running, but I completely removed zou and attempted a fresh install for the current version. This is when the bug happened.
The text was updated successfully, but these errors were encountered:
Hi @elias-schwarze,
This is mainly a python/ubuntu error. Have you just upgraded your ubuntu ?
If yes, have you removed all the files from your virtualenv ?
I think I will start by removing and recreating my virtualenv in this case.
Apologies, I did indeed upgrade to Ubuntu 24.04 recently and it seems that I have a dependency issue with python3.12-dev. I will try and fix that before attempting to install zou again.
Context
Studio name: Balance Film GmbH
Zou version: 0.20.15
Zou installation type: self-hosted
Ubuntu Version 24.04.1 LTS
Describe the bug
While running bin/zou init-db while installing zou, it fails with a python error (Traceback attached) and does not initialize the zou database. As a result, the database remains empty.
Python3.12 is installed.
traceback.txt
Expected behavior
init-db should initialise the zou database.
Additional context
I was following the instructions at https://zou.cg-wire.com/ for setting up zou. We previously had a much older version (0.16.x) running, but I completely removed zou and attempted a fresh install for the current version. This is when the bug happened.
The text was updated successfully, but these errors were encountered: