Description of problem: Darktable 3.8.1 is now released with many bug fixes. Since 3.8.0, cr3 Canon files are handled by Darktable, assuming exiv2 >= 0.27.4 and ISOBMFF support activated in both exiv2 and Darktable. exiv2 recent release has also introduced many bug and CVE fixes. Hence, the proposal is to update both together. Here attached are the spec files proposed. I have done that to support some Darktable users on the French forum. The packages have been tested for a week or so by them, without any issue reported. I have also added tools-noise and tools-basecurve, which are not part yet of the official Mageia package. I am a packager mentee, mentored by Nicolas L. I can provide him with the src.rpm, if handy.
Created attachment 13132 [details] exiv2 0.27.5 spec file Straightforward backport from Cauldron
Created attachment 13133 [details] darktable 3.8.1 spec file
Created attachment 13134 [details] darktable compiler patch pull request submitted and merged, as well https://github.com/darktable-org/rawspeed/pull/345
CC: (none) => mageia
Please take in mind that you have to use the internal lua version (from darktable) for building of darktable. Or it will break again the functionality of Gimp to load raw image files. See Bug #30002
After looking at your spec, it will break again Gimp functionality :(
Hi, I have tried build exiv2 from spec file. Apppears this bug: [jose@Mageia SPECS]$ rpmbuild -ba exiv2.spec Ejecutando(%prep): /bin/sh -e /var/tmp/rpm-tmp.s2fqgR + umask 022 + cd /home/jose/rpmbuild/BUILD + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + cd /home/jose/rpmbuild/BUILD + rm -rf exiv2-0.27.5-Source + /usr/bin/gzip -dc /home/jose/rpmbuild/SOURCES/exiv2-0.27.5-Source.tar.gz + /usr/bin/tar -xof - + STATUS=0 + '[' 0 -ne 0 ']' + cd exiv2-0.27.5-Source + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + echo 'Cannot read /home/jose/rpmbuild/SOURCES/exiv2-0.27.4-fix-pkgconfig-file.patch' Cannot read /home/jose/rpmbuild/SOURCES/exiv2-0.27.4-fix-pkgconfig-file.patch + exit 1 error: Estado de salida erróneo de /var/tmp/rpm-tmp.s2fqgR (%prep) Errores de construcción RPM: Estado de salida erróneo de /var/tmp/rpm-tmp.s2fqgR (%prep) [jose@Mageia SPECS]$ It is looking for a file patch that I haven't.
CC: (none) => joselp
@sturmvogel: lua is indeed bundled. Already the case since 3.8.0 @Jose Manuel: I posted only the exiv2.spec as the patches have not changed compared to what is in the repo. You need the 3 patches used to build on Cauldron. I will add them here to ease your life.
Created attachment 13135 [details] exiv2- patch1
Created attachment 13136 [details] exiv2- patch2
Created attachment 13137 [details] exiv2- patch3
(In reply to sturmvogel from comment #5) > After looking at your spec, it will break again Gimp functionality :( Could you elaborate? It is the lua version of darktable which is used.
For me it looked like you are using the system lua 5.2 from Mageia. But this will not work as darktable 3.8 requires lua 5.4 for proper building.
I have bugs still, after download and rename the patches like into spec file. [jose@Mageia SPECS]$ rpmbuild -ba exiv2.spec Ejecutando(%prep): /bin/sh -e /var/tmp/rpm-tmp.n6APuC + umask 022 + cd /home/jose/rpmbuild/BUILD + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + cd /home/jose/rpmbuild/BUILD + rm -rf exiv2-0.27.5-Source + /usr/bin/gzip -dc /home/jose/rpmbuild/SOURCES/exiv2-0.27.5-Source.tar.gz + /usr/bin/tar -xof - + STATUS=0 + '[' 0 -ne 0 ']' + cd exiv2-0.27.5-Source + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + /usr/bin/cat /home/jose/rpmbuild/SOURCES/exiv2-0.27.4-fix-pkgconfig-file.patch + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch 1 out of 1 hunk FAILED -- saving rejects to file cmake/exiv2.pc.in.rej error: Estado de salida erróneo de /var/tmp/rpm-tmp.n6APuC (%prep) Errores de construcción RPM: Estado de salida erróneo de /var/tmp/rpm-tmp.n6APuC (%prep) [jose@Mageia SPECS]$
I can't build the package from the updated Lua 5.4 spec here:"http://sophie.zarb.org/rpms/c97d2e0b2294cea29d36e79e8fdd3ba1/files"either, it also gives me errors even if I have the patch in SOURCES.
Here the terminal log: [jose@Mageia SPECS]$ rpmbuild -ba darktable.spec Ejecutando(%prep): /bin/sh -e /var/tmp/rpm-tmp.AMzAPl + umask 022 + cd /home/jose/rpmbuild/BUILD + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + cd /home/jose/rpmbuild/BUILD + rm -rf darktable-3.8.1 + /usr/bin/xz -dc /home/jose/rpmbuild/SOURCES/darktable-3.8.1.tar.xz + /usr/bin/tar -xof - + STATUS=0 + '[' 0 -ne 0 ']' + cd darktable-3.8.1 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + /usr/bin/cat /home/jose/rpmbuild/SOURCES/0001-Define-__DT_CLONE_TARGETS__-on-aarch64.patch + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch Reversed (or previously applied) patch detected! Assume -R? [n] Apply anyway? [n] 1 out of 1 hunk ignored -- saving rejects to file src/common/darktable.h.rej error: Estado de salida erróneo de /var/tmp/rpm-tmp.AMzAPl (%prep) Errores de construcción RPM: Estado de salida erróneo de /var/tmp/rpm-tmp.AMzAPl (%prep) [jose@Mageia SPECS]$
(In reply to Jose Manuel López from comment #15) > Reversed (or previously applied) patch detected! Assume -R? [n] Type y there and it should run trough.
I have the same error messages for exiv2 and can't build it with these patches.
I built exiv2 after removing Patch1 and Patch2. Than i tried to build darktable with Christian's spec and patches. And the built process fails again because of the darktable-3.8.0-compiler_fix.patch Sooo, either my and Jose's build environment are borked or there is something wrong with these patches.
The problem seems to be the spec files: If i change %prep %setup -q -n %{name}-%{version} %autopatch -p1 to %prep %setup -q -n %{name}-%{version} %patch -p1 the build process works.
(In reply to sturmvogel from comment #12) > For me it looked like you are using the system lua 5.2 from Mageia. But this > will not work as darktable 3.8 requires lua 5.4 for proper building. No, it is lua 5.4 from darktable which is used. %bcond_with systemlua means darktable lua is used. In fact, there is a double negation: DONT_USE_INTERNAL_LUA:BOOL=OFF It might be a bit misleading, but it is the Cauldron way and I decided to preserve it. In the log, I have: "-- Lua support: System library not found (using darktable's version)" (In reply to Jose Manuel López from comment #13) > I have bugs still, after download and rename the patches like into spec file. > > [jose@Mageia SPECS]$ rpmbuild -ba exiv2.spec > Ejecutando(%prep): /bin/sh -e /var/tmp/rpm-tmp.n6APuC > + umask 022 > + cd /home/jose/rpmbuild/BUILD > + '[' 1 -eq 1 ']' > + '[' 1 -eq 1 ']' > + '[' 1 -eq 1 ']' > + cd /home/jose/rpmbuild/BUILD > + rm -rf exiv2-0.27.5-Source > + /usr/bin/gzip -dc /home/jose/rpmbuild/SOURCES/exiv2-0.27.5-Source.tar.gz > + /usr/bin/tar -xof - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd exiv2-0.27.5-Source > + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . > + /usr/bin/cat > /home/jose/rpmbuild/SOURCES/exiv2-0.27.4-fix-pkgconfig-file.patch > + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch > 1 out of 1 hunk FAILED -- saving rejects to file cmake/exiv2.pc.in.rej > error: Estado de salida erróneo de /var/tmp/rpm-tmp.n6APuC (%prep) > > Do you use the same source tarball, is what I wonder? Because I get: + umask 022 + cd /builddir/build/BUILD + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + cd /builddir/build/BUILD + rm -rf exiv2-0.27.5-Source + /usr/bin/gzip -dc /builddir/build/SOURCES/exiv2-0.27.5-Source.tar.gz + /usr/bin/tar -xof - + STATUS=0 + '[' 0 -ne 0 ']' + cd exiv2-0.27.5-Source + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + /usr/bin/cat /builddir/build/SOURCES/exiv2-0.27.4-fix-pkgconfig-file.patch + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch + /usr/bin/cat /builddir/build/SOURCES/CVE-2021-29457-exiv-0.27.4.patch + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch + /usr/bin/cat /builddir/build/SOURCES/mga-fix-check-rpaths-errors.patch + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch + find . -type f -name '._*' -delete + RPM_EC=0 ++ jobs -p + exit 0 I attached the complete log for your reference. (In reply to Jose Manuel López from comment #15) > Here the terminal log: > > [jose@Mageia SPECS]$ rpmbuild -ba darktable.spec > Ejecutando(%prep): /bin/sh -e /var/tmp/rpm-tmp.AMzAPl > + umask 022 > + cd /home/jose/rpmbuild/BUILD > + '[' 1 -eq 1 ']' > + '[' 1 -eq 1 ']' > + '[' 1 -eq 1 ']' > + cd /home/jose/rpmbuild/BUILD > + rm -rf darktable-3.8.1 > + /usr/bin/xz -dc /home/jose/rpmbuild/SOURCES/darktable-3.8.1.tar.xz > + /usr/bin/tar -xof - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd darktable-3.8.1 > + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . > + /usr/bin/cat > /home/jose/rpmbuild/SOURCES/0001-Define-__DT_CLONE_TARGETS__-on-aarch64.patch > + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch > Reversed (or previously applied) patch detected! Assume -R? [n] > Apply anyway? [n] > 1 out of 1 hunk ignored -- saving rejects to file src/common/darktable.h.rej > error: Estado de salida erróneo de /var/tmp/rpm-tmp.AMzAPl (%prep) > > > Errores de construcción RPM: > I am a bit confused. This patch is deprecated and is not part of the spec file I have attached. So, it is normal you don't have it. Are you using the spec file I have attached? Or is it so it is corrupted? Or is it because I use mock to build? I doubt though as this type of patch error, I do get usually. (In reply to sturmvogel from comment #18) > I built exiv2 after removing Patch1 and Patch2. Than i tried to build > darktable with Christian's spec and patches. And the built process fails > again because of the darktable-3.8.0-compiler_fix.patch > > Sooo, either my and Jose's build environment are borked or there is > something wrong with these patches. What is the error you get? I don't see why changing %autopatch by %patch would solve an issue with the patch itself. But maybe someone has an explanation. Could mock lead to that? No sure either. Here attached is also the log file of darktable build.
Created attachment 13140 [details] exiv2 build log file
Created attachment 13141 [details] darktable build log file
I did not use mock for building. The errors for exiv2 with these 3 patches (and %autopatch -p1) are: $ LC_ALL=C rpmbuild -ba exiv2.spec Executing(%prep): /bin/sh -e /home/wikiuser/rpmbuild/tmp/rpm-tmp.c3IW3l + umask 022 + cd /home/wikiuser/rpmbuild//BUILD + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + cd /home/wikiuser/rpmbuild/BUILD + rm -rf exiv2-0.27.5-Source + /usr/bin/gzip -dc /home/wikiuser/rpmbuild/SOURCES/exiv2-0.27.5-Source.tar.gz + /usr/bin/tar -xof - + STATUS=0 + '[' 0 -ne 0 ']' + cd exiv2-0.27.5-Source + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + /usr/bin/cat /home/wikiuser/rpmbuild/SOURCES/exiv2-0.27.4-fix-pkgconfig-file.patch + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch + /usr/bin/cat /home/wikiuser/rpmbuild/SOURCES/CVE-2021-29457-exiv-0.27.4.patch + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch 1 out of 1 hunk FAILED -- saving rejects to file src/jp2image.cpp.rej error: Bad exit status from /home/wikiuser/rpmbuild/tmp/rpm-tmp.c3IW3l (%prep) RPM build errors: Bad exit status from /home/wikiuser/rpmbuild/tmp/rpm-tmp.c3IW3l (%prep)
Hi Do you clean up your build folder before launching another one? I am asking because looking at the file to be patched (src/jp2image.cpp) in the source tarball, it is clear exiv2-0.27.4-fix-pkgconfig-file.patch is not applied yet.
Created attachment 13142 [details] Mock build fail exiv2 Yep, all folders empty except SPECS and SOURCES. I did also a first time install of mock and tried to build exiv2. Also fails with attached log.
Finish: build setup for exiv2-0.27.5-1.mga8.src.rpm Start: Outputting list of installed packages Finish: Outputting list of installed packages Start: rpmbuild exiv2-0.27.5-1.mga8.src.rpm Building target platforms: x86_64 Building for target x86_64 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.Sm4EPX + umask 022 + cd /builddir/build/BUILD + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + cd /builddir/build/BUILD + rm -rf exiv2-0.27.5-Source + /usr/bin/gzip -dc /builddir/build/SOURCES/exiv2-0.27.5-Source.tar.gz + /usr/bin/tar -xof - + STATUS=0 + '[' 0 -ne 0 ']' + cd exiv2-0.27.5-Source + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + /usr/bin/cat /builddir/build/SOURCES/exiv2-0.27.4-fix-pkgconfig-file.patch + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch + /usr/bin/cat /builddir/build/SOURCES/CVE-2021-29457-exiv-0.27.4.patch 1 out of 1 hunk FAILED -- saving rejects to file src/jp2image.cpp.rej RPM build errors: error: Bad exit status from /var/tmp/rpm-tmp.Sm4EPX (%prep) Bad exit status from /var/tmp/rpm-tmp.Sm4EPX (%prep) Finish: rpmbuild exiv2-0.27.5-1.mga8.src.rpm Finish: build phase for exiv2-0.27.5-1.mga8.src.rpm ERROR: Exception(/home/wikiuser/rpmbuild/RPMS/exiv2-0.27.5-1.mga8.src.rpm) Config(mageia-8-x86_64) 0 minutes 46 seconds INFO: Results and/or logs in: /home/wikiuser/rpmbuild/RPMS/ INFO: Cleaning up build root ('cleanup_on_failure=True') Start: clean chroot Finish: clean chroot ERROR: Command failed: # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/originals/exiv2.spec
What I just did: -unpack my exiv2.0.27.5-1.src.rpm into SOURCES -use the unpacked spec with mock to build the package It works.... What I am wondering is whether when the patch is downloaded, it could introduce or skip an empty line, for instance. Then, the patch becomes incomplete. Could you post or attach the src/jp2image.cpp.rej ? Thanks
Created attachment 13143 [details] Rejectet patch I use the exiv2-0.27.5-Source.tar.gz downloaded from upstream for building. Attached the rejected patch jp2image.cpp.rej
Created attachment 13144 [details] Original jp2image.cpp before patch And here the original file jp2image.cpp before the patch is tried to apply.
Ok, i'm so sorry for the trouble! I downloaded your patches again and removed my set which i had previuosly. You were right with (In reply to christian barranco from comment #27) > it could introduce or skip an empty line, for instance. Now it builds properly. Sorry again :(
Created attachment 13145 [details] difference between the CVE patch Here is the difference between the patch I have and the .rej file, which an image of patch your build tries to apply (if I don't mistake). On "your" patch, there is a trailing space and a blank line at the end. If I use this patch, indeed, the build fails. Is there indeed an empty line at the end of your version of CVE-2021-29457-exiv-0.27.4.patch and, also, a space after switch(box.type)? If so, if you remove both, does it work any better?
(In reply to sturmvogel from comment #30) > Ok, i'm so sorry for the trouble! I downloaded your patches again and > removed my set which i had previuosly. > You were right with > (In reply to christian barranco from comment #27) > > it could introduce or skip an empty line, for instance. > > Now it builds properly. > > Sorry again :( :) No worries, it is only the beginning of a new partnership together ;)
At least you can laugh that i wasted your time :)
(In reply to sturmvogel from comment #33) > At least you can laugh that i wasted your time :) I always take a humble position in such situation; it might happen to me one day ! :D
Gosh, what a lot of work has gone in here. And many thanks to all for that. To see the wood from the trees, can somebody please clarify exactly which attached patches & spec files now can be passed onwards? The bug is for Mageia 8.
Source RPM: darktable-3.8.0-1.1.mga8 => darktable-3.8.0-1.1.mga8, exiv2-0.27.3-1.4.mga8.src.rpmCC: (none) => lewyssmith
Attachment 13142 is obsolete: 0 => 1
Attachment 13144 is obsolete: 0 => 1
Attachment 13143 is obsolete: 0 => 1
Attachment 13141 is obsolete: 0 => 1
Attachment 13145 is obsolete: 0 => 1
Attachment 13140 is obsolete: 0 => 1
All stuff which is not needed got obsoleted.
Thank you for that instant reply. (I am glad I asked the question!) Assigning this to akien who does 'daktable'.
Assignee: bugsquad => rverscheldeCC: lewyssmith => (none)
Hello everyone! I have deleted everything I did yesterday and re-downloaded the attachments. Now it builds fine, but here's a hint. I had to modify in the "darktable.spec" file, the BuildRequires line of exiv and remove ">= 0.27.4", because it doesn't match neither with the exiv2 version of Mageia nor with the 0.27.5 version that I have built with the patches, and this generates error when trying to "urpmi darktable.spec" indicating that the dependencies cannot be installed because it doesn't match that version of exiv2. After Darktable builds, I tried to install the resulting package and I get the error for version 0.27.4 and it won't continue with the install: [jose@Mageia x86_64]$ sudo urpmi darktable-3.8.1-0.2.mga8.x86_64.rpm [sudo] password for jose: Unable to install the requested package: darktable-3.8.1-0.2.mga8.x86_64 (because lib64exiv2_27[>= 0.27.4] was not satisfied). Go ahead with the installation? (Y/n) I have built the whole thing from Vbox Mageia 8 with the test repositories enabled. Great work, thanks to all!
Hi Jose You need to keep ">= 0.27.4", otherwise the ISOBMFF support will not be built into darktable. cr3 files will not be handled then. In order to build darktable with that, you need to have lib64exiv2-devel-0.27.5 installed or part of the repo you use when you build DT. Then, when you install this DT 3.8.1 rpm, you need also to install (together or before or part of a repo) lib64exiv2_27-0.27.5 , newly built. It is why I created this report with DT and exiv2 together. If you don't use the new version of exiv2 by removing the version condition as you did, it will build but cr3 support will not be enabled. Do not hesitate to ask more question if I was not clear.
(In reply to Jose Manuel López from comment #38) > Hello everyone! > > I have deleted everything I did yesterday and re-downloaded the attachments. > Now it builds fine, but here's a hint. > > I had to modify in the "darktable.spec" file, the BuildRequires line of exiv > and remove ">= 0.27.4", because it doesn't match neither with the exiv2 > version of Mageia nor with the 0.27.5 version that I have built with the > patches, and this generates error when trying to "urpmi darktable.spec" > indicating that the dependencies cannot be installed because it doesn't > match that version of exiv2. > > After Darktable builds, I tried to install the resulting package and I get > the error for version 0.27.4 and it won't continue with the install: > > [jose@Mageia x86_64]$ sudo urpmi darktable-3.8.1-0.2.mga8.x86_64.rpm > [sudo] password for jose: > Unable to install the requested package: > darktable-3.8.1-0.2.mga8.x86_64 (because lib64exiv2_27[>= 0.27.4] was not > satisfied). > Go ahead with the installation? (Y/n) > > I have built the whole thing from Vbox Mageia 8 with the test repositories > enabled. > > Great work, thanks to all! You didn't get the complete picture. You have to first build exiv2 0.27.5 and install them to your system including the devel packages. After that you are able to build darktable 3.8.1 exiv2 0.27.5 is a build require for darktable 3.8.1
Ok, Ok, I understand. I have tried what you say. Now, Darktable is installed without issues Then, I think that we can upload this to testing repositories for QA team validate it. (I am a member of QA, :)). Thanks and greetings!
Hi. I just got a message from a user on the forum, confirming he can now read his cr3 files (from his Canon 90D) with this update; he is super happy!
Hi Rémi. If you are too busy, do you want me to take care of this? This package has been used for about a month by many users, without any issue raised. Regarding the 2 optional packages I have added (tools-noise and tools-basecurve), the users' feedbacks are: "good to have them, but don't install them by default". I can adjust the spec accordingly. Let me know your view.
Hi Christian, The proposed changes look good overall, there's a few potential packaging issues that I'll have to see how to improve. If you're working on an update to the spec I'll wait for that to try it out and give my feedback. I agree with adding tools-noise and tools-basecurve as optional (could be Recommends possibly).
Hi Rémi Actually, I was only going to remove: Recommends: darktable-tools-noise = %{version}-%{release} Recommends: darktable-tools-basecurve = %{version}-%{release} It will enforce their installations for some users, and it is what, eventually, we'd like not to do. The user will decide whether to install them. I am really eager to learn and to improve. I am curious then about the few packaging issues you have noticed. Could you elaborate, in order for me to try to propose fixes? Thanks :)
Thanks for your work, and sorry for the delay reviewing the changes. It all looks pretty good, I provided some feedback on the #mageia-mentoring channel (mostly nitpicks) but overall it's good and I committed most of the changes: - Update to 3.8.1: http://svnweb.mageia.org/packages/cauldron/darktable/current/SPECS/darktable.spec?revision=1858249&view=markup&pathrev=1858273 - Adding gmic-devel, iso-codes, and sdl2 deps, and PROJECT_VERSION: http://svnweb.mageia.org/packages/cauldron/darktable/current/SPECS/darktable.spec?revision=1858256&view=markup&pathrev=1858273 - Enabling LTO for rawspeed and recommending roboto fonts: http://svnweb.mageia.org/packages/cauldron/darktable/current/SPECS/darktable.spec?revision=1858257&view=markup&pathrev=1858273 - Adding noise and basecurve tools: http://svnweb.mageia.org/packages/cauldron/darktable/current/SPECS/darktable.spec?revision=1858272&view=markup&pathrev=1858273 I did not add Recommends for the added tools because they seem like they're intended only for power users, and they're command line tools with little to no documentation. So I think most users shouldn't need to have them and their dependencies to use darktable. I'm happy to be contradicted on this though, I don't have much experience with those tools myself :) I also noticed that darktable has other optional dependencies on libavif, and on LLVM (to test compiling opencl kernels). The former seemed useful and the latter not so I added these changes: - BR libavif, disable opencl test compile: http://svnweb.mageia.org/packages/cauldron/darktable/current/SPECS/darktable.spec?revision=1858272&view=markup&pathrev=1858273 If that works OK, I can then look at bumping the version of exiv2 in Mageia 8 and making an update candidate for darktable.
Component: New RPM package request => RPM PackagesVersion: 8 => CauldronWhiteboard: (none) => MGA8TOO
Hi. I have been leaving with the update of exiv2 on MGA8 for some time, as other users. Not sure though it is worth the effort now, as MGA9 is closer and closer. Should this report just be closed?
Obsolète
Status: NEW => RESOLVEDResolution: (none) => WONTFIX