Peter, I had the same problem today when compiling darktable on Manjaro. The problem was that the Perl POD::Parser module was not installed on my system. I fixed it using the command:
$ sudo pacman -S perl-pod-parser
1 Like
Quick question.
Currently I see via git tag a ârelease-3.2.1â tag? Would this be the tag that I would need to checkout to compile the current status of the coming âstable releaseâ?
Cheers, Martin
Yep - 3.2.1 is THE 3.2 release.
But then so was 3.2 until it wasnât. No really. This is the 3.2 release.
The 3.2.0 build had a couple of problems that the dev team deemed serious enough to warrant a correction before public release. Although the 3.2.0 build had not been publicly announced yet, some people may have downloaded it already, so the safest course was to issue the corrections as a maintenance update, 3.2.1 (and it seems they removed the 3.2.0 tag from the repository to prevent anyone from accidentally downloading that broken build).
So, the public announcement for âDarktable 3.2â will be on the 3.2.1 release. If any further emergency corrections are required, then I expect theyâll reluctantly issue a 3.2.2 build, but in practice I think the devs will now focus on getting Darktable 3.4 ready for Christmas, and any non-critical fixes from now on will be delivered in the Christmas release.
2 Likes
Would you mind explaining what the difference is, just in a sort of big picture way? I donât know which one to install, and will this replace my current released installation? Or can I use it to update the 3.2 version I have been installing from the zip files?
Most of the added 3.4 stuff is listed here: current OSX Build - #98 by MStraeten
Both build are for testing purposes only, so backup your darktable settings and xmp files before using it. While the release 3.2. tag might be quite stable - fundamental changes are very unlikely, the 3.4 contains several work in progress stuff. So there might be changes until Christmas breaking edits done with earlier development builds.
1 Like
Thanks.
Thanks, thatâs exactly what the issue was. 
1 Like
The release has been reported for tomorrow!
6 Likes
Darktable 3.2.1 has been officially released! Thanks so much to all the devs who put in so much work to make it happen.
10 Likes
Thanks 
Thanks to everyone involved.
I have a GUI question. Running Windows. I installed 3.2 and it looks like this:
Then I tried replacing my dev version by copying the darktable folder to my J drive and changing the bat file used to start the dev version. I started it the new version, and it looks like this:
Both installations are set to run elegant-grey. Iâve looked at preferences and donât see a setting to account for the different look. Moreover, in the second installation, clicking on an image doesnât select/highlight it. When I double-clicked on one, it opened in darkroom, but upon returning to lighttable, it looks like this:
I admit I got the idea for copying the darktable folder from some post, and I donât really know what I am doing. 
Your .config/darktable folder most likely contains a style.css that overwrites the standard themes. Just delete it.
I started from scratch on another drive, just copying the bin, lib, and share directories from Program Files. Same problem.
You have to look for your personal config files, not for the files of the installation. In linux you find them in ~/.config/darktable in windows I donât know.
I want a separate, second installation. The same concept as when I had 3.02 and the Filmic V4 dev version installed with its own config and cache.
See darktable/README.md at master · darktable-org/darktable · GitHub and darktable/README.md at master · darktable-org/darktable · GitHub
On darktable 3.2 and dev versions, check before preferences dialog window and see which theme is used and if modify theme with css tweaks below is checked (if yes, start by unchecking it).
On what you made, you have an issue with a CSS personal tweak and especially a path issue. darktable donât find the correct CSS on your dev version, thatâs why you have that awful GUI.