That solution is a patch, not a solution.
As I have explained right now 255 IS NOT the correct lens id for the Tamron lens
I expect that a program or library that says is able to automatically identify your lens do that : automatically identify your lens.
And when it fails to do so, it is a bug or misfunction of the program/library.
So I expect that users can contribute with info to solve the problem and in this case help to fix incorrectly identified lenses for future versions.
If I just correct it in my config file for me and do not provide feedback at all the problem will remain for upcoming releases.
That is how OPENSOURCE WORKS: if there is a problem, users provide feedback about the problem and are provided instructions about which tests they can do or what info they can provide to fix it.
Of course developers do that at their own pace you cannot expect every problem fixed inmediatly (neither in commercial software).
I don’t expect anybody to do my work.
Your response was not clear enough for me because it missed that I was using windows and not linux, and because a user of darktable does not know which other libraries/tools uses darktable.
But thanks to your contribution and others I could managed to find where the config file was.
I was convinced that the 255 was the correct ID for this lens, so I tried to provide it to be fix.
But it is not, as I was told 255 just means than your lens was not correctly identified.
Any lens not correctly identified would be assigned this ID. If you have two of this lenses you have a problem.
So making this change in my config is only a patch, that may work if you have only one lens with this problem and it won’t be fixed in the future meanwhile the algorithm that detects this lens is not changed.
I have used several other software that has no problem identifying the lens.
So yes, it is a software problem.