evmos: unable to parse genesis.json

[blacklodge-admin]

Bug description

I'm just trying to get bdjuno up and running targeting a fresh postgres (v14) instance using the current tip of thechains/evmos/mainnet branch and am encountering several issues. Debug logs suggest the module order specified in config.yaml may not be respected. I'm happy to fix this myself and submit a PR but would love a hair of guidance so I don't have to descend the rabbit hole with complete ignorance.

Is this even what I should be doing if my final goal is to run bdjuno against newer chains that are recent evmos forks?

Thank you in advance!

Steps to reproduce

~ sha256sum /genesis.json
4aa13da5eb4b9705ae8a7c3e09d1c36b92d08247dad2a6ed1844d031fcfe296c  /genesis.json31fcfe296c  /genesis.json
~ bdjuno version
version: 3.2.0-17-g9a96f7e
commit: 9a96f7e29cd49817c7ed436a049528401527aefa
go: go1.18.9 linux/amd64
~ # first attempt
~ yq '.chain.modules' config.yaml
- modules
- messages
- auth
- bank
- consensus
- feegrant
- gov
- inflation
- mint
- pricefeed
- slashing
- staking
- distribution
- actions
~ bdjuno parse genesis-file --genesis-file-path /genesis.json
12:21AM DBG parsing genesis module=auth
12:23AM DBG parsing genesis module=consensus
12:23AM DBG parsing genesis module=gov
ERROR: error while storing genesis governance proposals: error while storing deposits: pq: insert or update on table "proposal_deposit" violates foreign key constraint "proposal_deposit_height_fkey"
~ # remove gov module and try again...
~ sed -i '/- gov/d' config.yaml
~ bdjuno parse genesis-file --genesis-file-path /genesis.json # retry
12:36AM DBG parsing genesis module=auth
12:39AM DBG parsing genesis module=consensus
12:39AM DBG parsing genesis module=inflation
12:39AM DBG parsing genesis module=mint
ERROR: error while reading mint genesis data: EOF
~ # remove mint module and try again
~ sed -i '/- mint/d' config.yaml
~ bdjuno parse genesis-file --genesis-file-path /genesis.json
12:41AM DBG parsing genesis module=auth
12:44AM DBG parsing genesis module=consensus
12:44AM DBG parsing genesis module=inflation
12:44AM DBG parsing genesis module=slashing
12:44AM DBG parsing genesis module=staking
12:44AM DBG parsing genesis module=distribution
~ # success, I think?  not ideal.

HEAD^ (see below) produces the same results. I'll see if I can git bisect my way to a version that works, but any insight enabling me to move forward is appreciated (including informing me that this is a waste of my time for what I'm trying to accomplish, if that's the case 😛).

~ bdjuno version
version: 3.1.0-15-gd705817
commit: d705817c1c0e8094a88d9c4037d84e3beb14f29a
go: go1.18.9 linux/amd64

Expected behavior

We should be able to parse genesis.json with all the corresponding modules that have been checked in enabled, following the guidance in the docs.