I installed the git version back in January. It showed as 2.5.0+4
I reinstalled it today (hoping to get the latest development), but it is still showing 2.5.0+4
Is this the latest git version?
Well… It depends on where you look 
Start darktable and it will look like this if you are up-to-date (as per a few minutes ago).
The xfce panel, however, still reports 2.5.0+4
Have fun!
Claes in Lund, Sweden
Don’t want open new thread
I have two version installed, one from repo Debian testing and second compiled development version from git.
Second one installed by default in /opt/darktable/
They use same database from .config/darktable I can swich between them and getting same setting, styles etc and last opened collections. The only thing is not working in development version – lua scripts. I have installed them in .config/darktable and can use from darktable from repo. But they are invisible for dev. darktable
Anyone can help
Thanks
I guess you are missing some dependices. Check the ouput of build.sh for:
-- Lua support: Enabled
and warnings on missing dev libs. On Debian you might need liblua5.3-dev.
Working on the same database with different versions of darktable is not recommended. If you are using die GIT version a small db update might render the database unuseable for the current stable release.
1 Like
Thank you for reply! I will check
And you are right, I need to learn how to point dev darktable to separated database.
Cheers
Thanks Claes.
I reviewed the ./build.sh output, and there are no errors, only some warnings. The files in /opt/darktables/bin are all newly dated files. I am using gnome3 on debian.
Are there something new in the new build that I can check to see if it is there?
Here are the warnings"
Scanning dependencies of target highlights
[ 89%] Building C object src/iop/CMakeFiles/highlights.dir/introspection_highlights.c.o
In file included from /home/shum/darktable/build/src/iop/introspection_colortransfer.c:33:0:
/home/shum/darktable/src/iop/colortransfer.c:181:1: warning: ISO C90 forbids variable length array ‘mi’ [-Wvla]
static void get_cluster_mapping(const int n, float mi[n][2], float mo[n][2], int mapio[n])
^~~~~~
/home/shum/darktable/src/iop/colortransfer.c:181:1: warning: ISO C90 forbids variable length array ‘mo’ [-Wvla]
/home/shum/darktable/src/iop/colortransfer.c:181:1: warning: ISO C90 forbids variable length array ‘mapio’ [-Wvla]
/home/shum/darktable/src/iop/colortransfer.c:201:1: warning: ISO C90 forbids variable length array ‘mean’ [-Wvla]
static void get_clusters(const float *col, const int n, float mean[n][2], float *weight)
^~~~~~
/home/shum/darktable/src/iop/colortransfer.c:220:1: warning: ISO C90 forbids variable length array ‘mean’ [-Wvla]
static int get_cluster(const float *col, const int n, float mean[n][2])
^~~~~~
/home/shum/darktable/src/iop/colortransfer.c:237:1: warning: ISO C90 forbids variable length array ‘mean_out’ [-Wvla]
static void kmeans(const float *col, const dt_iop_roi_t *const roi, const int n, float mean_out[n][2],
^~~~~~
/home/shum/darktable/src/iop/colortransfer.c:238:20: warning: ISO C90 forbids variable length array ‘var_out’ [-Wvla]
float var_out[n][2])
^~~~~
[ 90%] Linking C shared module libdither.so
[ 90%] Built target liquify
Scanning dependencies of target channelmixer
[ 90%] Building C object src/iop/CMakeFiles/channelmixer.dir/introspection_channelmixer.c.o
[ 90%] Built target clahe
Scanning dependencies of target graduatednd
In file included from /home/shum/darktable/build/src/iop/introspection_colormapping.c:54:0:
/home/shum/darktable/src/iop/colormapping.c:226:1: warning: ISO C90 forbids variable length array ‘mi’ [-Wvla]
static void get_cluster_mapping(const int n, float mi[n][2], float wi[n], float mo[n][2], float wo[n],
^~~~~~
/home/shum/darktable/src/iop/colormapping.c:226:1: warning: ISO C90 forbids variable length array ‘wi’ [-Wvla]
/home/shum/darktable/src/iop/colormapping.c:226:1: warning: ISO C90 forbids variable length array ‘mo’ [-Wvla]
/home/shum/darktable/src/iop/colormapping.c:226:1: warning: ISO C90 forbids variable length array ‘wo’ [-Wvla]
/home/shum/darktable/src/iop/colormapping.c:227:33: warning: ISO C90 forbids variable length array ‘mapio’ [-Wvla]
const float dominance, int mapio[n])
^~~~~
/home/shum/darktable/src/iop/colormapping.c:258:1: warning: ISO C90 forbids variable length array ‘mean’ [-Wvla]
static void get_clusters(const float *col, const int n, float mean[n][2], float *weight)
^~~~~~
/home/shum/darktable/src/iop/colormapping.c:278:1: warning: ISO C90 forbids variable length array ‘mean’ [-Wvla]
static int get_cluster(const float *col, const int n, float mean[n][2])
^~~~~~
/home/shum/darktable/src/iop/colormapping.c:295:1: warning: ISO C90 forbids variable length array ‘mean_out’ [-Wvla]
static void kmeans(const float *col, const int width, const int height, const int n, float mean_out[n][2],
^~~~~~
/home/shum/darktable/src/iop/colormapping.c:296:20: warning: ISO C90 forbids variable length array ‘var_out’ [-Wvla]
float var_out[n][2], float weight_out[n])
^~~~~
/home/shum/darktable/src/iop/colormapping.c:296:20: warning: ISO C90 forbids variable length array ‘weight_out’ [-Wvla]
If I understand you correctly…
/home/xxxx/repo-dt/ is the folder where git places the source for darktable on my machine.
Check in folder /home/xxxx/repo-dt/packaging/macosx/
there ought to be four files having a date of 2018-03-24,
for instance darktable.bundle
OK? If not please re-phrase your question and I will try to give a better reply
/Claes
Hi Claes
I do not have /home/shum/repo-dt
I only have /home/shum/darktable which has the src folder (the source files?) and a whole lot of others. It also has the build.sh which are all newly dated (from the new git pull).
ok. in /home/shum/darktable folder, it has packaging and macosx, i.e. /home/shum/darktable/packaging/macosx
These are all newly dated files. Yes, there are 15 files, and one of them is darktable bundle, and they all have 03 Apr 2018 date.
Please try this:
Start a terminal.
cd to the folder in which you have darktable’s build.sh
Type
git branch -a
Scroll up until you see the start of the lines that will appear, like this:
What branch is highlighted in green and asterisk’d?
master like I have it or something else?
Relax – sooner or later we will solve the problem 
Have fun!
Claes in Lund, Sweden
It is * master in green, just like what you posted.
shum@debian:~/darktable$ git branch -a
- master
remotes/origin/30bit
remotes/origin/HEAD → origin/master
remotes/origin/align_image_stack
remotes/origin/battery-indicator
remotes/origin/better-undo
remotes/origin/collect-local-copy
remotes/origin/d810-base-curve
remotes/origin/darktable-1.0.x
remotes/origin/darktable-1.1.x
remotes/origin/darktable-1.2.x
remotes/origin/darktable-1.4.x
remotes/origin/darktable-1.6.x
remotes/origin/darktable-2.0.x
remotes/origin/darktable-2.2.x
remotes/origin/darktable-2.4.x
remotes/origin/detachable
remotes/origin/dualiso
remotes/origin/ellipse-ctl-log
remotes/origin/ex/spot-content-aware
remotes/origin/experimental_plugins
remotes/origin/film-emulation
remotes/origin/grain-optimize
remotes/origin/liquify-distort-except
remotes/origin/lua
remotes/origin/master
remotes/origin/minimal-css
remotes/origin/raw-video
remotes/origin/rawdenoise
remotes/origin/smooth-undo-redo
remotes/origin/spot-removal-presets
remotes/origin/srw-makernote-bug
remotes/origin/turboprint
remotes/origin/undo-group
shum@debian:~/darktable$
Grrrrr. I am soon out of fresh ideas 
Start terminal and type
sudo apt install -f
What does your Debian say?
shum@debian:~/darktable/build$ sudo apt install -f
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following packages were automatically installed and are no longer required:
libkeybinder-3.0-0 linux-headers-4.9.0-2-amd64 linux-headers-4.9.0-2-common
linux-headers-4.9.0-3-amd64 linux-headers-4.9.0-3-common
linux-headers-4.9.0-4-amd64 linux-headers-4.9.0-4-common
linux-image-4.9.0-2-amd64 linux-image-4.9.0-3-amd64
linux-image-4.9.0-4-amd64 pastebinit
Use ‘sudo apt autoremove’ to remove them.
0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded.
All right.
Please follow the advice to use
sudo apt autoremove
at least that will save some space.
Since I am totally out of fresh ideas, how about performing a brand new darktable git install?
a) Check that all prerequisites are there (above link, Prerequisites). If not, install them.
b) Above link, go down to git version.
Follow the instructions verbatim, like
- Cloning for the first time,
- Getting rawspeed submodule, and
- Building with build.sh.
What happens?
Have fun!
Claes in Lund, Sweden
or just use the master snapshot packages linked in the 3rd party section on the install page. they are automatically updated on each git push. 
@Claes and darix
I am so sorry to waste all your time. It was my stupid mistake. I keep running the old version after the compile and install. I just have to do ./darktable instead of /darktable.
Thanks for all your help.
3 Likes
Good to hear! I marked the thread as solved for you.
Ah, superb!
Actually, I am quite relieved, because I was running out of additional “clever” ideas for you to test :-)))
Have fun!
Claes in Lund, Sweden
Thanks Claes. I still do not know why the first time the installed (2.5.0+4) went to /usr/local/bin/darktable (it should have been in /opt/darktable). So, when I type /darktable (when I am at /opt/darktable) it executed the version in /usr/local/bin/darktable. Now I have deleted it, and set my favorite menu to point at /opt/darktable/bin/darktable.
Thanks again for all your trouble.
1 Like
@krist Sorry, I should have asked before marked this as solved.
$ which darktable
/opt/darktable/bin/darktable
so the binary is in the subfolder /opt/darktable/bin/ not in /opt/darktable/. Could that caused the confusion?
Hi Christian,
github darktable places by default the executable in /opt/darktable/bin/
which darktable reports nothing.
After a
sudo updatedb locate darktable | grep bin
you will find the executable in /opt/darktable/bin
Have fun!
Claes in Lund, Sweden