twenger26,
I think I confirm this is a bug (a regression) with v5. If you get more clues,
please fill a bug report.
I think setting a state like 'not installed' (or the right key) in the
corresponding ir_module_module table + restarting will do it as a workaround.
Hope this helps.
Raphaël
I actually figured out what was wrong. I forgot to instantiate my model
classes so the rdbm wasn't creating the tables. I ended up removing the module
through the database manually. Then I re-installed it again and everything
worked fine.
After that I tested again to see if I could
