Is this only an issue for Linux users? Do Windows and MacOS users have all the CR3 stuff bundled into the install file so smooth sailing?
Yes, this is a Linux only problem. MacOS and windows have the necessary dependencies bundled.
Actually, the flatpak and other similar formats should have everything they need as well.
So, you’ve already stated that you are not interested in workong out how to package an appropriately configured exiv2 library for your deb-based distro, and you are not willing to use a distro such as Arch that has the exiv2 library pre-built with the required options, so not really sure how we could proceed any further from this point…
fun fact … it is the same distribution statement as in the darktable changelog file.
do not download debs or rpms from the OBS. add the repository to your system and install packages via apt. then you would get the libexiv2 from the OBS project as well.
2 Likes
The dt team releases the source code. Releasing the binaries is the responsibility of distros and repos managers, who had an 8 days heads-up of complete code freeze over the darktable-release-3.8.x branch before the official source release announcement to prepare their repos and dependencies.
All the rest is distro management. During Christmas time. Making .deb shit probably not a priority for most.
9 Likes
People like you are motivating contributors like me who spent days to make shit work on dirt old distros. Thank you for that. next time you will do the job and I am sure you will do it much better. Welcome to the team.
14 Likes
There’s a lot of thankless work that’s involved in putting out these releases according to schedule on a volunteer basis during the holidays, so let me just say thank you.
14 Likes
And may I also add that all this is because the team have been working very hard to get CR3 in 3.8.0. This was a project in its own in a very short period of time with high stress to get it right.
At the end we could have hate from CR3 owner not having there camera supported or hate from others because a mismatch of libraries.
The development is hard and complex and the packaging is also hard and complex with all versions around that we try to support.
The 3.8 is born as it is, better helping ensuring 3.8.1 will be fixed than insulting devs and me as the release manager since some years now.
15 Likes
I think the problem is, that there were a lot of people (including me) waiting eagerly for CR3 support on the one hand and as far as I have seen no warnings, when the devs released 3.8, that there will be probably problems at the beginning having C3 support on Linux on the other hand.
Not a good combination. On the user side, I was a little disappointed as well. Anyway it is quite unfair to expect things from developers and their software when you get it for free (and for darktable free means in any aspect free, because I have never found a possibility to donate ;)).
So maybe it makes sense on both sides to cool down a little bit (especially on the users side).
I for myself have decided to wait a little bit longer for CR3 support. Quite sure, that it will not last too long until I can use darktable on my CR3 files directly. And looking on 3.8 leaving CR3 support aside, it is still a damned good piece of software with many improvements. THANK YOU DEVS!!!
Who is not willing to wait can still use the flatpak at any time. Even so there are some downsides, like the missing OpenCL support with modern AMD graphics, it works well and gives you the missing CR3 support.
Quoting the release notes:
- The Canon raw CR3 format is now supported (see list of supported cameras in the
section below). This support is provided by LibRaw and requires at least exiv2 version
0.27.4 with BMFF support activated.
3 Likes
@Pascal_Obry I have read that and I have 0.27.5 installed. Anyway there is no CR3 support. So it seems like (at least for an average user) this is just one part of the things which are necessary.
I have reported here: darktable 3.8.0 released - #71 by Popanz
So maybe it would have make sense to exactly write what users have to do if they want to have CR3 support. Or if it is too complex for the average user, Just tell us that we have to wait until everything is in the repo of the distros that are used or use the flatpak. I think that would avoid some harsh sounding posts. Unfortunately, I have to admit, that my first posts can as well be read like that. Rest assured, that this was never my intent, but my post were always meant as simple questions.
But like I said, it doesn’t hurt to wait a little bit longer. I have used darktable on my CR3 using Adobe DNG converter. I have no pain in doing that until everything is in place.
1 Like
There is a simple remedy to all this:
if your present operating system
and/or your present distro do not
offer what you want, then switch!
Have fun!
Claes in Lund, Sweden
3 Likes
@Claes …or wait until your distro offers you what you want 
I’m using KDE Neon and Manjaro. On Neon I have 3.8. but no CR3 on Manjaro 3.6.
I definitely don’t switch my distro for a single software just to be the first to have the newest version with all it’s features.
patience is a virtue 
4 Likes
I’m strongly ‘enervated’ by this recommendation - and, of course, by the referenced document - so my thanks to you for reminding the reader; it is, for me, a powerful and useful dcoument.
But I would not limit the application of the good sense/principles of the referenced document to just the reporting of bugs: I would find it of great value if those principle were applied to the contributions from the army of helpful people on this forum, upon whom I call with (what must be) annoying regularity. Too often I am unable to understand the advice I am given.
Further, these principles should be applied in general to any submission of so-called ‘information’ on the www. It would result in a reduction by about 98% of the amount of data that one needs to read through/examine. The chance of that happening is, sadly (given human nature), of the order of 1 in 10-to-a-very-large-negative-number.
1 Like
I’m guilty of not adding my thanks to all those who work voluntarily to provide me with this outstanding software, and to all those here who provide such generous support to me in my attempts to apply the software to my photographs.
Thank you, all. I simply could not do what I wish to do without your knowledge, skill and understanding. Sorry I’m more than a week late in recognising this wrt 3.8
1 Like
To all the devs, again: I know software development is hard and I know that you all do it (mostly) unpaid. I do not disregard all the hard work that went into the software - otherwise I would not be wanting to use it. I fully respect your efforts.
But - ain’t there always a but - throwing around that toxic “it’s open source, fix it yourself” attitude with the “hey, just use another OS” snark thrown in for good measure is not helping anyone.
darktable is way beyond - and has been for some time - the little hobby amateur project with weird quirks and custom approaches and all. Providing some source code that works under development circumstances is not the level you all are aspiring to, or are you? The old “it works on my computer” always has the same answer: “are you giving your computer to the user?”
Remember … all I was asking “how can I get it to run” … and almost all I got were elitist snarky comments from devs that are behaving like everyone should be on their level of expertise regarding darktable. If I weren’t available to debug a problem I wouldn’t be writing this in a public forum. Helping to make the software better goes both ways.
That is actually the first and truly helpful comment to my original question. The OBS deb packages (direct download) have been working out of the box on various debian distros for years for me, so I never looked into their repo system.
2 Likes
And thanks to the helpful comment by @darix here is an Ansible playbook to make it work.
# Ansible playbook .. darktable for debian 10 via Opensuse Build System
# run:
# _$ sudo ansible-playbook darktable.yml
- hosts: localhost
become: yes
tasks:
- name: Add OBS repo for darktable
apt_repository:
repo: deb http://download.opensuse.org/repositories/graphics:/darktable/Debian_10/ /
filename: darktable-opensuse
update_cache: yes
state: present
- name: Add release key for OBS darktable
apt_key:
url: https://download.opensuse.org/repositories/graphics:darktable/Debian_10/Release.key
state: present
- name: Install darktable latest via OBS
apt:
pkg: darktable
1 Like
almost all I got were elitist snarky comments from devs that are behaving like everyone should be on their level of expertise regarding darktable.
We don’t know what you do or do not understand. If you want further explanation just ask, don’t throw mud.
3 Likes
as long as darktable is using exiv2 there won’t be cr3 support without exiv2 built with bmff support 
maybe exiv2 1.0 will enable this by default…