The dependency is a git dependency so I guess that’s why it fails to load the correct version.
This worked fine for previous releases I’m struggling to understand the state of the vendored dependencies inside of the build step, and this is one place where cargo error messages are not that good
I’m the maintainer of bodev. If the sources are generated wrong it’s the fault of flatpak-cargo-generator (cargo works just fine when online). I ran flatpak-cargo-generator (latest version) on the latest Cargo.lock, that corresponds to the commit used for the main repo.
Do you mean opening an issue on flatpak/flatpak-build-tools ? Yes good idea.
Looks like there’s some weird stuff in the Cargo.toml that even cargo vendor can’t handle. The issue is actually with libcosmic and/or cargo it appears. Though it’s a bit annoying that there is now way to work around it in flatpak.