-
Notifications
You must be signed in to change notification settings - Fork 290
makernotes: workaround for Olympus header corruption #2567
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2567 +/- ##
==========================================
- Coverage 63.90% 63.89% -0.02%
==========================================
Files 103 103
Lines 22393 22397 +4
Branches 10824 10826 +2
==========================================
Hits 14310 14310
- Misses 5864 5867 +3
- Partials 2219 2220 +1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Is there an appetite to backport for a 0.27.7 hotfix (w/ maybe a few more select cherry-picks)? @nehaljwani @kevinbackhouse @piponazo @postscript-dev @hassec |
Yes, that makes sense. My understanding from quickly reading #2542 is that this was a regression from 0.27.5 to 0.27.6. |
Not a regression per se, as the feature responsible for the bug wasn't there in 0.27.5 at all. |
Feel free to open a pull request for the 0.27-maintenance branch and I'll cut a release after it is merged. |
Great, can you please create a 0.27.7 milestone then as well? Any other changes we might want to backport? @kevinbackhouse @piponazo @postscript-dev @hassec |
makernotes: workaround for Olympus header corruption (backport #2567)
Add test case (complements #2567)
@kmilos Is now a good time to cut a release with the backports? |
@nehaljwani Sure, thanks! |
Exiv2 v0.27.7 2023-05-14
Exiv2 v0.27.7 Acknowledgements According to
Exiv2 v0.27.7 Release Notes
If I've failed to acknowledge anyone's contribution, I apologize. Please let me know and I'll update this comment. |
Release notes: - [0.27.7](Exiv2/exiv2#2567 (comment)) - [0.27.6](Exiv2/exiv2#2406 (comment)) Signed-off-by: Reilly Brogan <reilly@reillybrogan.com>
Addresses #2542 as a workaround rather than a proper solution.
Should be able to parse the data back, but still leaves a "corrupted" file that other apps might have trouble with...
@tenzap I think this should also apply to 0.27 branch (w/ maybe some minimal tweaks), so please feel free to test.