Quoting David Bremner (2021-05-29 14:32:09) > 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,
Oh, wauw - then apparently I did something hard without even knowing it: I grabbed and applied the patch and it seems to work just fine: https://source.puri.sm/pureos/packages/darktable/-/commit/19eb57c7bffdca0575f1d526656ca4614f05a33c Where do upstream say that? Perhaps they mean backporting further back than nearest point release, 3.4.1? > 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). The application megapixels targeted Debian bullseye outputs DNG. I think it would be helpful that darktable in bullseye could either process such DNG files or if not then at least _not_ process them - not crash and continue crashing thereafter because the crashing files would "pollute" cashed data of darktable. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
