Yes. Adobe LCP conversions require lensfun database version 2. The main schema changes are minor, but the converted Adobe profiles are meant for the newer lensfun format.

Darktable itself does not depend on a specific database version so much as on the lensfun library API it was built against. In your case, the non-git darktable package was trying to load liblensfun.so.1, while lensfun-git installed liblensfun.so.2, so the lens correction module could not load.

The reported working solution was:

• install lensfun-git
• create a symlink so darktable can find the expected library name:
  • cd /lib
  • sudo ln -s liblensfun.so.2 liblensfun.so.1
• then launch darktable

With that in place, darktable picked up the converted Adobe profiles correctly.

So the issue was not really darktable rejecting DB v2 data; it was a library version mismatch between darktable and lensfun. If you use distro packages, the cleaner long-term fix is matching darktable and lensfun builds from the same package set.