Tonight I have restarted building cache after reverting the following
commits:

70626dd95bf0fab36f2d011dab075e3ebbf7aa28
e1b27201024c56747e81c46b9594290f20e1899b
3fc5cd4c6c2536689c4d9566b618f5ace49be520
ffbec14de21b0d3cf0b77e040308134c49632c22

No issue and I have passed the point where it failed yesterday (I have
copy of my latest working mipmap cache, this speed up the testing). 
So definitely one of those commits trigger the issue! 
-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://v2p.fr.eu.org
  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B


------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
darktable-devel mailing list
darktable-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-devel

Reply via email to