Victor Forsiuk

> Alright. Then tell me how Windows users report warnings based in Lensfun or GTK, none of which use the DT's logging system. Windows users report these warnings because they...

> Could at least the log timestamp be altered to a date + time format instead of time from start, which makes it harder to review logs later? You can...

> Ok so what about dev release ends with 0 first release ends with 1, corrective release with 2, 3... > > It would give us: > > * 24.12.1...

> Yes I think I agree regarding use of the month number in the version name being confusing. I would probably prefer to have some other way to mark development...

> > Our main problem is that we have not formulated exactly what changes in the program will justify the increment of the major, and the change of the major...

In Debain, they are already going to make an experimental darktable `5.0.0-rc0` package. I think it's time to make up our minds and make a decision whether we stay (at...

As @wpferguson explained, this is not a bug in the program, but an incorrect usage (image file naming that competes with the duplicate naming mechanism). So I'm closing the issue.

@wwwFrank So it's actually working as designed. Do you have any arguments why the behavior should be different, or can we close this issue?

OK, Houston, we have a problem. Examining the nightly build logs showed that this problem appeared on github runners on February 15th. Before that, everything was fine. Either some questionable...

The log of exactly what failed is in build\CMakeFiles\CMakeConfigureLog.yaml. In my local build it contains the following (hidden behind the header to not pollute the comment). Details kind: "try_compile-v1" backtrace:...