Package Details: darktable-git 3.5.0.r2438.g941122872d-1

Git Clone URL: (read-only, click to copy)
Package Base: darktable-git
Description: A virtual lighttable and darkroom for photographers
Upstream URL:
Licenses: GPL3
Conflicts: darktable
Provides: darktable
Submitter: marco44
Maintainer: marco44
Last Packager: marco44
Votes: 20
Popularity: 0.000248
First Submitted: 2015-08-09 17:40 (UTC)
Last Updated: 2021-06-23 09:25 (UTC)

Latest Comments

marco44 commented on 2022-07-20 08:35 (UTC)

Can people stop flagging this package out of date ? That's a git package… the version is autogenerated by pkgver. It's of course generating a darktable 4 binary right now. And you'll end up with a package that has the correct version

otula commented on 2022-04-17 21:22 (UTC)

@marco44: I'm sorry, it's my fault, I had an older PKGBUILD that stopped working for me just now, so I assumed the year-old PKGBUILD wouldn't work.

marco44 commented on 2022-04-09 05:48 (UTC)

update what ? all urls are git+https, so it seems it's ok

otula commented on 2022-04-08 17:42 (UTC) (edited on 2022-04-08 17:44 (UTC) by otula)

Please, update the PKGBUILD

bartus commented on 2021-09-19 18:29 (UTC)

Won't build against librsvg:2.52

Until porting is finished you can turn off -Werror with

Apply with git am -s < <(curl -q

marco44 commented on 2021-07-28 13:26 (UTC)

Yeah, so it means you have to recompile openexr, right ?

marco44 commented on 2021-06-23 09:25 (UTC)

Ok, let's do this. I reverted the gcc-10 patch

flannelhead commented on 2021-06-22 09:35 (UTC)

@ayr0 I can confirm that after the exiv2 upgrade.

Also now that I built again with GCC11, I can't at least easily reproduce the previous issue. Perhaps the compiler change can be reverted and if issues arise, they should be fixed with the upstream?

ayr0 commented on 2021-06-21 05:13 (UTC) (edited on 2021-06-21 05:15 (UTC) by ayr0)

I'm getting a compile error after upgrading exiv2 that I think is related to using gcc10.

/bin/ld: /usr/lib/ undefined reference to `std::__throw_bad_array_new_length()@GLIBCXX_3.4.29'

This is happening after upgrading from exiv2 0.27.3 to 0.27.4 in the official repos.

marco44 commented on 2021-06-15 08:00 (UTC)

@flannelhead: done. Please tell me if that solves you problem

flannelhead commented on 2021-06-14 16:14 (UTC)

There's a potential bug when compiled with GCC11 which is the current GCC version in Arch. See e.g. this bug report:

I just hit a similar behaviour myself. Darktable is not currently tested by upstream with GCC11. In the meantime, could it be considered to build this package with GCC10 which exists in Arch repos as well?

marco44 commented on 2021-05-14 21:45 (UTC)

Wow, sorry, my mistake. Fixed

ayr0 commented on 2021-05-14 21:12 (UTC)

The latest update appears to be building darktable twice. Am I missing something? On my machine, darktable builds and then appears to rebuild everything again in tools/basecurve.

marco44 commented on 2021-05-12 08:03 (UTC)

Wow. Damn right :) Only for 10 years :) Fixed..

pitbuster commented on 2021-05-12 00:54 (UTC)

It seems that the libglade dependency is not really needed.

simona commented on 2021-01-21 14:05 (UTC)

now ok!!!!!!!! thx very much. you are an hero.

simona commented on 2021-01-21 14:02 (UTC)

OHOHOHOHHOHHOHOHOHHO find!!!!!!!! thx thx thx i have svt-av1-git instead of svt-av1 i try change.

marco44 commented on 2021-01-21 14:01 (UTC)

That's really weird, these symbols seem to all be in

what's the version of svt-av1 on your system ? try to reinstall it, who knows...

[marc@marco ~]$ readelf -Ws /usr/lib/ | grep svt_av1_enc 69: 0000000000145010 3 FUNC GLOBAL DEFAULT 9 svt_av1_enc_eos_nal 77: 0000000000145d30 70 FUNC GLOBAL DEFAULT 9 svt_av1_enc_get_stream_info 78: 0000000000145630 141 FUNC GLOBAL DEFAULT 9 svt_av1_enc_get_packet 86: 0000000000144fd0 50 FUNC GLOBAL DEFAULT 9 svt_av1_enc_stream_header_release 88: 0000000000145020 1552 FUNC GLOBAL DEFAULT 9 svt_av1_enc_send_picture 93: 0000000000142d90 8447 FUNC GLOBAL DEFAULT 9 svt_av1_enc_set_parameter 94: 0000000000141cf0 144 FUNC GLOBAL DEFAULT 9 svt_av1_enc_deinit_handle 102: 0000000000144e90 316 FUNC GLOBAL DEFAULT 9 svt_av1_enc_stream_header 104: 0000000000145bf0 318 FUNC GLOBAL DEFAULT 9 svt_av1_enc_init_handle 111: 000000000013d820 17259 FUNC GLOBAL DEFAULT 9 svt_av1_enc_init 116: 0000000000141b90 259 FUNC GLOBAL DEFAULT 9 svt_av1_enc_deinit 122: 00000000001456c0 89 FUNC GLOBAL DEFAULT 9 svt_av1_enc_release_out_buffer

simona commented on 2021-01-21 13:53 (UTC)

ldd -r -d /usr/lib/ (0x00007fffa0335000)
/usr/${LIB}/ => /usr/lib/ (0x00007f4350371000) => /usr/lib/ (0x00007f435016d000) => /usr/lib/ (0x00007f434ff1e000) => /usr/lib/ (0x00007f43457ee000) => /usr/lib/ (0x00007f434511a000) => /usr/lib/ (0x00007f43450af000) => /usr/lib/ (0x00007f4344ee4000) => /usr/lib/ (0x00007f4344ede000) => /usr/lib/ (0x00007f4344ebc000) => /usr/lib/ (0x00007f4344ea2000) => /usr/lib/ (0x00007f4344d5c000)
/usr/lib64/ (0x00007f4350598000) => /usr/lib/ (0x00007f4344cd8000) => /usr/lib/ (0x00007f4344af9000)
undefined symbol: svt_av1_enc_init (/usr/lib/
undefined symbol: svt_av1_enc_get_packet (/usr/lib/
undefined symbol: svt_av1_enc_send_picture (/usr/lib/
undefined symbol: svt_av1_enc_init_handle (/usr/lib/
undefined symbol: svt_av1_enc_set_parameter (/usr/lib/
undefined symbol: svt_av1_enc_deinit_handle (/usr/lib/
undefined symbol: svt_av1_enc_release_out_buffer (/usr/lib/
undefined symbol: svt_av1_enc_deinit (/usr/lib/

simona commented on 2021-01-21 13:51 (UTC)

it seem ok:
pacman -Qo /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/
/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/ è contenuto in libavif 0.8.4-2
pacman -Qo /usr/lib/
/usr/lib/ è contenuto in libavif 0.8.4-2
where is that wrong?

marco44 commented on 2021-01-21 13:49 (UTC)

So yes, that's broken somewhere else on your system.

Try "ldd -r -d /usr/lib/", this will probably give you a hint. But your symbol is contained in the svt-av1 package

simona commented on 2021-01-21 13:44 (UTC)

"pacman -S libabif " give me error: "(3/7) Probing GDK-Pixbuf loader modules... g_module_open() failed for /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/ /usr/lib/ undefined symbol: svt_av1_enc_init"

simona commented on 2021-01-21 13:42 (UTC)

I have rav1e.h in my system:
locate rav1e.h
pacman -Qo /usr/include/rav1e/rav1e.h
/usr/include/rav1e/rav1e.h è contenuto in rav1e 0.4.0-1

simona commented on 2021-01-21 13:22 (UTC) (edited on 2021-01-21 13:24 (UTC) by simona)

yes. rav1e 0.4.0-1 is installed.
and with libavif 0.8.4-2 / darktable 3.4.0-2 from community the runtime error is:
"darktable: symbol lookup error: /usr/lib/ undefined symbol: svt_av1_enc_init",
that seem quite identical to the "/bin/ld: /usr/lib/ undefined reference to `svt_av1_enc_init'"
it give me same compiling libavif-git.
What is missing? is present and seem ok.
Already tryied uninstall/reinstall libavif / darktable.
I don't know what try to do.

marco44 commented on 2021-01-21 11:21 (UTC)

Seems that there are new dependencies :)

Do you have rav1e installed ? If not that's probably what's missing in the package depends

simona commented on 2021-01-21 10:38 (UTC)

yay -S libavif-git give error
/home/simona/.cache/yay/libavif-git/src/libavif/src/codec_rav1e.c:6:10: fatal error: rav1e.h: File o directory non esistente 6 | #include "rav1e.h"

simona commented on 2021-01-21 10:32 (UTC) (edited on 2021-01-21 10:35 (UTC) by simona)

/bin/ld: /usr/lib/ undefined reference to `svt_av1_enc_init'

marco44 commented on 2021-01-18 06:52 (UTC)

Neat, merged. I hope they won't add submodules too often though, the advantage of the previous method was that there was no need to maintain the list :)

bartus commented on 2021-01-17 19:34 (UTC) (edited on 2021-01-17 19:35 (UTC) by bartus)

Could we please have submodules enlisted in source array, it would greatly speed up rebuild in clean container, preventing redownloading submodules every time rebuild is triggered.


#merge with
git am -s < <(curl -s

I've created a simple script to generate source array and prepare function for git submodules if you need to update other PKGBUILDs.

spider-mario commented on 2020-10-07 22:49 (UTC)

The PKGBUILD shouldn’t set CMAKE_BUILD_TYPE to Release:

Also, could we perhaps build with -DBUILD_NOISE_TOOLS enabled? It would make it easier to contribute noise profiles.


marco44 commented on 2020-08-26 10:19 (UTC) (edited on 2020-08-26 10:20 (UTC) by marco44)

The avif optdep was provided by avif-git which was merged into libavif-git. Please update the avif optdep to libavif.


polyzen commented on 2020-08-26 05:15 (UTC)

The avif optdep was provided by avif-git which was merged into libavif-git. Please update the avif optdep to libavif.

sflor commented on 2020-08-11 08:10 (UTC)

Thanks for your support!

marco44 commented on 2020-08-11 07:48 (UTC)

That's what I was going to tell you. Pod::Parser was removed from Perl 5.32.

but the thing is you only need Pod::Parser if you have po4a installed. So it's not that much of a dependency, but it would be better to add it as a builddepend to avoid problems. I'm going to do this

sflor commented on 2020-08-11 07:40 (UTC)

Fixed by installing perl-pod-parser! Should be a dependency, I guess?

sflor commented on 2020-08-11 07:36 (UTC)

Here it is:

[ 95%] Generating de/darktable-cmstest.pod
cd /tmp/makepkg/darktable-git/src/darktable/doc/man && /usr/bin/vendor_perl/po4a-translate -f pod -m darktable-cmstest.pod -p po/de.po -l /tmp/makepkg/darktable-git/src/darktable/build/doc/man/de/darktable-cmstest.pod -k 0
Unknown format type: pod.
List of valid formats:
  - asciidoc: AsciiDoc format.
  - dia: uncompressed Dia diagrams.
  - docbook: DocBook XML.
  - guide: Gentoo Linux's XML documentation format.
  - ini: INI format.
  - kernelhelp: Help messages of each kernel compilation option.
  - latex: LaTeX format.
  - man: Good old manual page format.
  - pod: Perl Online Documentation format.
  - rubydoc: Ruby Documentation (RD) format.
  - sgml: either DebianDoc or DocBook DTD.
  - texinfo: The info page format.
  - tex: generic TeX documents (see also latex).
  - text: simple text document.
  - wml: WML documents.
  - xhtml: XHTML documents.
  - xml: generic XML documents (see also docbook).
  - yaml: YAML documents.
make[2]: *** [doc/man/CMakeFiles/manpage-de-darktable-cmstest.1.dir/build.make:87: doc/man/de/darktable-cmstest.pod] Error 1
make[2]: Leaving directory '/tmp/makepkg/darktable-git/src/darktable/build'
make[1]: *** [CMakeFiles/Makefile2:9261: doc/man/CMakeFiles/manpage-de-darktable-cmstest.1.dir/all] Error 2
make[1]: Leaving directory '/tmp/makepkg/darktable-git/src/darktable/build'
make: *** [Makefile:171: all] Error 2

Thanks for your reply.

marco44 commented on 2020-08-11 06:51 (UTC)

Probably. It looks a lot like data/kernels/CMakeFiles/, but it's hard to tell. When this fails, try to cd to darktable-git/src/darktable/build, then run "make VERBOSE=1" so we can see the exact command that fails

sflor commented on 2020-08-10 10:09 (UTC)

darktable-git isn't building anymore for me. Has been like this for a while now. It fails like this:

[  9%] Built target
Unknown format type: pod.
List of valid formats:

Am I missing something?

bartus commented on 2020-05-11 12:51 (UTC) (edited on 2020-05-11 12:53 (UTC) by bartus)

Could we have release- prefix striped from version string, as described in wiki:vcs_package_guidelines ?

marco44 commented on 2020-05-01 14:53 (UTC)

Oh, sorry, you're the reporter of this bug :)

marco44 commented on 2020-05-01 14:52 (UTC)

Done. Beware for now though :)

trougnouf commented on 2020-05-01 12:36 (UTC)

Can you add avif as an optional dependency?

ctouze commented on 2019-07-27 08:30 (UTC)

Done. Thanks

marco44 commented on 2019-07-27 07:52 (UTC)

Yes you seem to be right, probably linked with this PR:

But it's not the right place to report this anyway, please report to darktable… there is nothing I can fix from here.

ctouze commented on 2019-07-27 07:30 (UTC)

@marco44 I use lensfun-git associated with the master branch of Darktable for several months and I have the build issue since 3 days.This is the only way for the lens correction module to recognize my objective profiles obtained with lensfun-convert-lcp from adobe profiles for my lenses that are not yet supported by lensfun. No build issue with ubuntu

marco44 commented on 2019-07-27 06:06 (UTC)

@ctouze: yup, that's been the case for a very long while. As far as I know, lensfun hasn't released a new version in years, and the HEAD version has these prototypes changes. So darktable doesn't build for these.

You probably don't need lensfun-git anyway. If that's for new lens support, just use the regular lensfun package and run lensfun-update-data

ctouze commented on 2019-07-26 13:21 (UTC)

Build issue with lensfun-git In file included from /tmp/trizen-ch/darktable-git/src/darktable/build/src/iop/ /tmp/trizen-ch/darktable-git/src/darktable/src/iop/ In function ‘lfModifier get_modifier(int, int, int, const dt_iop_lensfun_data_t, int)’: /tmp/trizen-ch/darktable-git/src/darktable/src/iop/ error: no matching function for call to ‘lfModifier::lfModifier(const float&, int&, int&, lfPixelFormat, const int&)’ 359 | mod = new lfModifier(d->crop, w, h, LF_PF_F32, d->inverse); | ^ In file included from /tmp/trizen-ch/darktable-git/src/darktable/src/iop/, from /tmp/trizen-ch/darktable-git/src/darktable/build/src/iop/ /usr/include/lensfun/lensfun.h:2486:5: note: candidate: ‘lfModifier::lfModifier(const lfLens, float, float, int, int, lfPixelFormat, bool)’ 2486 | lfModifier (const lfLens lens, float imgfocal, float imgcrop, int imgwidth, int imgheight, lfPixelFormat pixel_format, bool reverse = false); | ^~~~~~~~~~ /usr/include/lensfun/lensfun.h:2486:5: note: candidate expects 7 arguments, 5 provided /usr/include/lensfun/lensfun.h:2372:16: note: candidate: ‘lfModifier::lfModifier(const lfLens, float, int, int)’ 2372 | DEPRECATED lfModifier (const lfLens lens, float crop, int width, int height); | ^~~~~~~~~~ /usr/include/lensfun/lensfun.h:2372:16: note: candidate expects 4 arguments, 5 provided /usr/include/lensfun/lensfun.h:2348:18: note: candidate: ‘lfModifier::lfModifier(const lfModifier&)’ 2348 | struct LF_EXPORT lfModifier | ^~~~~~~~~~ /usr/include/lensfun/lensfun.h:2348:18: note: candidate expects 1 argument, 5 provided In file included from /tmp/trizen-ch/darktable-git/src/darktable/build/src/iop/ /tmp/trizen-ch/darktable-git/src/darktable/src/iop/ error: no matching function for call to ‘lfModifier::EnableDistortionCorrection(lfLens const&, const float&)’ 361 | mods_done_tmp |= mod->EnableDistortionCorrection(d->lens, d->focal); | ^ In file included from /tmp/trizen-ch/darktable-git/src/darktable/src/iop/, from /tmp/trizen-ch/darktable-git/src/darktable/build/src/iop/ /usr/include/lensfun/lensfun.h:2499:9: note: candidate: ‘int lfModifier::EnableDistortionCorrection(const lfLensCalibDistortion&)’ 2499 | int EnableDistortionCorrection (const lfLensCalibDistortion& lcd); | ^~~~~~~~~~~~~~~~~~~~~~~~~~ /usr/include/lensfun/lensfun.h:2499:9: note: candidate expects 1 argument, 2 provided /usr/include/lensfun/lensfun.h:2510:9: note: candidate: ‘int lfModifier::EnableDistortionCorrection()’ 2510 | int EnableDistortionCorrection (); | ^~~~~~~~~~~~~~~~~~~~~~~~~~ /usr/include/lensfun/lensfun.h:2510:9: note: candidate expects 0 arguments, 2 provided In file included from /tmp/trizen-ch/darktable-git/src/darktable/build/src/iop/ /tmp/trizen-ch/darktable-git/src/darktable/src/iop/ error: no matching function for call to ‘lfModifier::EnableProjectionTransform(lfLens* const&, const float&, const lfLensType&)’ 363 | ->EnableProjectionTransform(d->lens, d->focal, d->target_geom); | ^

In file included from /tmp/trizen-ch/darktable-git/src/darktable/src/iop/, from /tmp/trizen-ch/darktable-git/src/darktable/build/src/iop/ /usr/include/lensfun/lensfun.h:2570:9: note: candidate: ‘int lfModifier::EnableProjectionTransform(lfLensType)’ 2570 | int EnableProjectionTransform (lfLensType target_projection); | ^~~~~~~~~~~~~~~~~~~~~~~~~ /usr/include/lensfun/lensfun.h:2570:9: note: candidate expects 1 argument, 3 provided In file included from /tmp/trizen-ch/darktable-git/src/darktable/build/src/iop/ /tmp/trizen-ch/darktable-git/src/darktable/src/iop/ error: no matching function for call to ‘lfModifier::EnableTCACorrection(lfLens const&, const float&)’ 369 | else mods_done_tmp |= mod->EnableTCACorrection(d->lens, d->focal); | ^ In file included from /tmp/trizen-ch/darktable-git/src/darktable/src/iop/, from /tmp/trizen-ch/darktable-git/src/darktable/build/src/iop/ /usr/include/lensfun/lensfun.h:2520:9: note: candidate: ‘int lfModifier::EnableTCACorrection(const lfLensCalibTCA&)’ 2520 | int EnableTCACorrection (const lfLensCalibTCA& lctca); | ^~~~~~~~~~~~~~~~~~~ /usr/include/lensfun/lensfun.h:2520:9: note: candidate expects 1 argument, 2 provided /usr/include/lensfun/lensfun.h:2531:9: note: candidate: ‘int lfModifier::EnableTCACorrection()’ 2531 | int EnableTCACorrection (); | ^~~~~~~~~~~~~~~~~~~ /usr/include/lensfun/lensfun.h:2531:9: note: candidate expects 0 arguments, 2 provided In file included from /tmp/trizen-ch/darktable-git/src/darktable/build/src/iop/ /tmp/trizen-ch/darktable-git/src/darktable/src/iop/ error: no matching function for call to ‘lfModifier::EnableVignettingCorrection(lfLens const&, const float&, const float&, const float&)’ 372 | nettingCorrection(d->lens, d->focal, d->aperture, d->distance); | ^

In file included from /tmp/trizen-ch/darktable-git/src/darktable/src/iop/, from /tmp/trizen-ch/darktable-git/src/darktable/build/src/iop/ /usr/include/lensfun/lensfun.h:2541:9: note: candidate: ‘int lfModifier::EnableVignettingCorrection(const lfLensCalibVignetting&)’ 2541 | int EnableVignettingCorrection (const lfLensCalibVignetting& lcv); | ^~~~~~~~~~~~~~~~~~~~~~~~~~ /usr/include/lensfun/lensfun.h:2541:9: note: candidate expects 1 argument, 4 provided /usr/include/lensfun/lensfun.h:2556:9: note: candidate: ‘int lfModifier::EnableVignettingCorrection(float, float)’ 2556 | int EnableVignettingCorrection (float aperture, float distance); | ^~~~~~~~~~~~~~~~~~~~~~~~~~ /usr/include/lensfun/lensfun.h:2556:9: note: candidate expects 2 arguments, 4 provided In file included from /tmp/trizen-ch/darktable-git/src/darktable/build/src/iop/ /tmp/trizen-ch/darktable-git/src/darktable/src/iop/ In function ‘void commit_params(dt_iop_module_t, dt_iop_params_t, dt_dev_pixelpipe_t, dt_dev_pixelpipe_iop_t)’: /tmp/trizen-ch/darktable-git/src/darktable/src/iop/ error: no match for ‘operator=’ (operand types are ‘lfLensCalibTCA’ and ‘<brace-enclosed initializer list>’) 1150 | }; | ^ In file included from /tmp/trizen-ch/darktable-git/src/darktable/src/iop/, from /tmp/trizen-ch/darktable-git/src/darktable/build/src/iop/ /usr/include/lensfun/lensfun.h:733:8: note: candidate: ‘constexpr lfLensCalibTCA& lfLensCalibTCA::operator=(const lfLensCalibTCA&)’ 733 | struct lfLensCalibTCA | ^~~~~~~~~~~~~~ /usr/include/lensfun/lensfun.h:733:8: note: no known conversion for argument 1 from ‘<brace-enclosed initializer list>’ to ‘const lfLensCalibTCA&’ /usr/include/lensfun/lensfun.h:733:8: note: candidate: ‘constexpr lfLensCalibTCA& lfLensCalibTCA::operator=(lfLensCalibTCA&&)’ /usr/include/lensfun/lensfun.h:733:8: note: no known conversion for argument 1 from ‘<brace-enclosed initializer list>’ to ‘lfLensCalibTCA&&’ make[2]: [src/iop/CMakeFiles/lens.dir/build.make:68: src/iop/CMakeFiles/lens.dir/] Error 1 make[1]: [CMakeFiles/Makefile2:4393: src/iop/CMakeFiles/lens.dir/all] Error 2 make: *** [Makefile:152: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting... :: Unable to build darktable-git - makepkg exited with code: 4

marco44 commented on 2019-05-22 14:51 (UTC) (edited on 2019-05-22 14:51 (UTC) by marco44)

Yes, cannot build with exiv2 0.27 for now.

wilecoyote commented on 2019-05-22 07:04 (UTC)

The build fails with the following error:

Scanning dependencies of target darktable-curve-tool
[ 66%] Building C object CMakeFiles/darktable-curve-tool.dir/darktable-curve-tool.o
[ 66%] Building CXX object CMakeFiles/darktable-curve-tool.dir/exif-wrapper.o
/home/bjoern/.cache/yay/darktable-git/src/darktable/tools/basecurve/exif-wrapper.cpp: In function ‘int exif_get_ascii_datafield(const char*, const char*, char*, size_t)’:
/home/bjoern/.cache/yay/darktable-git/src/darktable/tools/basecurve/exif-wrapper.cpp:62:17: error: ‘Error’ in namespace ‘Exiv2’ does not name a type
   catch (Exiv2::Error& e)
make[2]: *** [CMakeFiles/darktable-curve-tool.dir/build.make:76: CMakeFiles/darktable-curve-tool.dir/exif-wrapper.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:73: CMakeFiles/darktable-curve-tool.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
==> ERROR: A failure occurred in build().
Error making: darktable-git

costalfy commented on 2018-11-13 20:16 (UTC)

Hi Marc, Of course i would like to help you and archlinux community But i think that i'll need help for my first submission because i have an error 403 when i want to "git push" my modification

marco44 commented on 2018-11-13 15:59 (UTC)

The build number in the PKGBUILD is only updated each time I push a new version of this package (it's not the build number you get when you install it). Or I don't understand what you mean (do you mean I'm not getting the commit value right ?

Anyway, if you want to maintain this package, I would gladly let it to you. I've already got quite a few to manage.

costalfy commented on 2018-11-13 15:05 (UTC)

Hi, I would like to help you to maintain this PKGBUILD. I'm cofounder of and we follow the github repository day by day. Actually, the build number in this PKGBUILD doesn't match to the last commit. If i can help you to push modifications don't hesitate to contect me Regards

Meltea commented on 2018-05-09 23:18 (UTC) (edited on 2018-05-14 11:35 (UTC) by Meltea) meh, that's all I could have been bothered to do. edit: and it has been merged.

marco44 commented on 2018-05-09 15:05 (UTC)

Hi Rinoceros. It appeared with GCC 8.1. Either you directly do a bugreport to the darktable team as you found it before me, or I can do it, as you want :)

Rhinoceros commented on 2018-05-08 23:34 (UTC) (edited on 2018-05-09 00:20 (UTC) by Rhinoceros)

I'm getting an error with makepkg:

Scanning dependencies of target soften
[ 77%] Building C object src/iop/CMakeFiles/tonecurve.dir/introspection_tonecurve.c.o
[ 77%] Building C object src/iop/CMakeFiles/soften.dir/introspection_soften.c.o
In file included from /tmp/darktable-git/src/darktable/src/iop/,
                 from /tmp/darktable-git/src/darktable/build/src/iop/
/tmp/darktable-git/src/darktable/src/bauhaus/bauhaus.h:37:32: error: unnecessary parentheses in declaration of ‘dt_bh_get_type’ [-Werror=parentheses]
 #define DT_BAUHAUS_WIDGET_TYPE (dt_bh_get_type())
/tmp/darktable-git/src/darktable/src/bauhaus/bauhaus.h:45:14: note: in expansion of macro ‘DT_BAUHAUS_WIDGET_TYPE’
[ 78%] Linking C shared module
cc1plus: all warnings being treated as errors
make[2]: *** [src/iop/CMakeFiles/tonemap.dir/build.make:68: src/iop/CMakeFiles/tonemap.dir/] Error 1
make[1]: *** [CMakeFiles/Makefile2:5177: src/iop/CMakeFiles/tonemap.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 78%] Built target soften
[ 78%] Linking C shared module
[ 78%] Built target tonecurve
[ 78%] Linking CXX shared module
[ 78%] Built target demosaic
make: *** [Makefile:152: all] Error 2
==> ERROR: A failure occurred in build().

marco44 commented on 2018-02-10 18:22 (UTC)

Removed -DUSE_GNOME_KEYRING=Off. It must have been useful once upon a time, I don't know. I'm using KDE, so please tell me if that's ok for gnome.

trougnouf commented on 2018-02-10 16:20 (UTC)

This appears to be built without gnome-keyring (-DUSE_GNOME_KEYRING=Off ) but it requires gnome-keyring.

@micdt this is a git version so it's always the latest when you reinstall it.

micdt commented on 2017-12-15 19:50 (UTC)

There is a new version: Will it be in AUR soon?

marco44 commented on 2017-12-08 16:57 (UTC)

That's weird, I don't have the problem on my machine…

hpd commented on 2017-12-08 10:05 (UTC)

This is currently affected by

holos commented on 2016-09-25 06:03 (UTC)

hi, the clean/reset in pkgver() is troublesome, it clobbers anything done in prepare() if one were to add things there (sometimes I add patches this way) also the {make,opt,}depends seem out of date/wrong. for instance, lua52 is missing completely. some of the others look misplaced

marco44 commented on 2016-06-23 13:19 (UTC)

aperez: it should be solved with the new version I just uploaded.

aperez commented on 2016-06-22 09:38 (UTC)

There's a small issue with the generated package: when buildingh in x86_64 machines it contains a “/usr/lib64/darktable” directory, which should be “/usr/lib/darktable”, because in x86_64 “/usr/lib64” is a symlink to “/usr/lib”. Probably it would be a good idea to see if this installation path can be changed passing some option to the “configure” script, or alternatively renaming the directory as the last step in the “package()” function.

marco44 commented on 2016-04-24 06:36 (UTC)

We're back into the master branch. labio has been merged.

marco44 commented on 2016-04-19 08:05 (UTC)

I will get back to main branch as soon as possible, but for now, I think it would be better to have a precise commit, as this is a more experimental branch, instead of getting tons of bug reports if things go wrong. BTW, the gigantic OTHER menu is corrected with this new version.

tuankiet65 commented on 2016-04-19 01:55 (UTC)

You might want to checkout the entire branch instead of a commit?

marco44 commented on 2016-04-18 19:13 (UTC)

I just pushed this: "Temporarily go to the lab-io branch to make darktable work with GTK 3.20" This works ONLY with GTK 3.20. It won't compile with 3.18.

marco44 commented on 2016-04-12 14:46 (UTC)

It's only about deprecated declarations… It's nothing we would care in a PKGBUILD I think.

tuankiet65 commented on 2016-04-12 14:44 (UTC) (edited on 2016-04-12 14:45 (UTC) by tuankiet65)

I'll probably make a ticket about this problem. And Wno-error is just a dirty hack so I wouldn't recommend adding it to the PKGBUILD. EDIT: There's one here

marco44 commented on 2016-04-11 07:55 (UTC)

I meant I froze GTK to 3.18 on my machine.

marco44 commented on 2016-04-11 07:55 (UTC)

I just added it. But as gtk destroys darktable's menus, cinnamon and probably everything all over the place, I froze GTK to 3.18. So I couldn't check if this works :)

tuankiet65 commented on 2016-04-11 07:51 (UTC)

Thanks to GNOME 3.20, now build breaks because Darktable uses deprecated features. While waiting for a fix, you can get around by adding "-DCMAKE_C_FLAGS=-Wno-error=deprecated-declarations" to the cmake command in PKGBUILD.

marco44 commented on 2016-02-28 09:22 (UTC)

Sorry about that. Corrected.

zebulon commented on 2016-02-28 09:10 (UTC) (edited on 2016-02-28 09:10 (UTC) by zebulon)

Hi, I have a version number issue. Package is release. but the PKGBUILD contains pkgver=release. This leads to a forever upgrade loop using AUR tools like yaourt or packer. Or am I doing something wrong?

marco44 commented on 2016-02-27 17:28 (UTC)


christoph.gysin commented on 2016-02-27 09:51 (UTC)

Please fix the depends to include osm-gps-map instead of osm-gps-map-gtk3.

marco44 commented on 2015-08-22 05:37 (UTC)

That is weird. I can build it with pugixml instead of pugixml-shared here. Can you try this: - rebuild pugixml - then rebuild darktable-git If you still have an error, please post the error

druneau commented on 2015-08-21 23:40 (UTC)

Not sure why but I had to manually uninstall pugixml then install pugixml-shared in order for it to build. I see the comment notes about pugixml-shared being a dependancy, but PKGBUILD shows pugixml on my end. Regards,

marco44 commented on 2015-08-10 07:28 (UTC)

Problem solved

marco44 commented on 2015-08-10 07:22 (UTC)

Damn, it has not been migrated to aur4 either. Will do :)

H-Bloxx commented on 2015-08-10 07:10 (UTC)

pugixml-shared cannot be found

marco44 commented on 2015-08-09 17:51 (UTC)

The package was not migrated to aur4. I took over. If you are the previous maintainer, tell me, I'll give it back to you. I added 'pugixml-shared' as a dependancy. Regards