Iām happy to help you. I not sure I have understood what is being discussed. When I search the log, I donāt see anything that I recognise or understand.
There could be an API change concerning errors, however I honestly donāt remember.
There are changes to some APIs in Exiv2 v0.27. I donāt believe we have a list of these changes. The change log documents the issues and code changes and does not focus on the API.
When you build/link darktable with the exiv2 v0.27 header files, I would expect darktable to build/link/execute without issue.
We are planning a series of ādotā releases to Exiv2 v0.27 for the next couple of years. Exiv2 v0.27.1 is scheduled for release on 31 March 2019. If you have a āshow-stopperā issue with the Exiv2 v0.27 API, I will investigate restoring anything missing. I expect the Release Candidate of Exiv2 v0.27.1 to available in early March for testing.
We believe itās fixed in āmasterā, however weāll do more investigation to understand both the issue and the fix.
The fix will be in Exiv2 0.27.1 on 2019-03-31 I intend to publish Exiv2 0.27.1 RC1 in early March. Feedback concerning this (and any other matter) is always welcome.
I might be āon the same pageā now. I see an error:
/home/abuild/rpmbuild/BUILD/darktable-2.4.4/src/common/exif.cc:2658:71: error: no matching function for call to 'Exiv2::BasicError<char>::BasicError(int, const char [41])'
throw Exiv2::Error(1, "[xmp_write] failed to serialize xmp data");
The fix is only āproposedā at the moment. We hope to resolved this in the next few days.
Iām rather lost here. For sure I looked in the wrong log last week. Although youāre discussing patches, I donāt know to which patches you are referring and you appear to be dealing with RC1 and RC2 which were release candidates.