Jonas Smedegaard <d...@jones.dk> writes: > > Upstream tracked and has solved this issue at > https://github.com/darktable-org/darktable/issues/8951 > > At upstream issue tracking is mentioned that the file they used as proof > was arguably broken. >
Upstream suggests that fix is not easily backportable, so the fix likely have to wait until the release of darktable 3.6. If you think its a big issue in practice (I can't judge, I don't use DNG), maybe the release team would consider 3.6 for a bullseye point release (likely to a huge diff).
