Sure, signed packages would be great, but are not a must have.
My goal here is to build the releases within github actions (and I actually built the upcoming 4.4.0 x86_64 package there) so the signing needs to be done there as well. The developer certificate needs to be stored within github secrets.
Github will provide action runners for M1 in Q4/2023.
Iām not that familiar with Github (we use BitBucket at work and Iāve self hosted git for 10+ years) but the certificate and application specific password for notarization can be stored and accessed from GitHub secrets it should be easy enough to do. I can build and sign/notarize the ARM64 release for now if you want.
For 10.14.5+ signed apps have to be notarized too or you get an even scarier warning than if it wasnāt signed at all.
current 4.4.x bugfixing branch + a couple of RF lensfun data from: Kameratrollet + corrected raw whitepoints for Canon M6
darktable-4.4.0+10~gb35aa35521_arm64.dmg
darktable-4.4.0+10~gb35aa35521_x86_64.dmg (macOS min 10.14)
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
difference to released 4.4.0 see: Comparing release-4.4.0...darktable-4.4.x Ā· darktable-org/darktable Ā· GitHub
I tried to open with control+click, and then select the āopenā item. But I still get the message " ādarktableā is damaged and canāt be opend. You should move it ot the Bin.ā
Do I need to do or change something additionally?
(MacOs 13.4.1 - MBP 2023)
see
Yep, problem solved. Many thanks!
ā¦
Sorry, I seen now that it is clearly mentioned in your instructions. 
Today, I had the same problem to install darktable 4.4.1 on my Mac mini (M1, 2020) running macOS Monterey v12.6.7. The downloaded package darktable-4.4.1-arm64.dmg threw the message that the file was damaged and could not be opened. I was still using v4.2.1
I did as āMStraetenā recommended to allow execution via terminal: " xattr -c <path/to/application.app> "
This worked!!! Thank you VERY much!
current 4.4.x bugfixing branch + a couple of RF lensfun data from: Kameratrollet + corrected raw whitepoints for Canon M6
darktable-4.4.1+3~g27f33c9166_arm64.dmg
darktable-4.4.1+3~g27f33c9166_x86_64.dmg (macOS >= 10.14)
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
difference to released 4.4.1 see: Comparing release-4.4.0ā¦darktable-4.4.x Ā· darktable-org/darktable Ā· GitHub
time to switch over to next release 
current master branch + a couple of RF lensfun data from: Kameratrollet + corrected raw whitepoints for Canon M6
darktable-4.5.0+191~ga097732672_arm64.dmg
darktable-4.5.0+191~ga097732672_x86_64.dmg (macOS >= 10.14)
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
difference to released 4.4.2 see: Comparing release-4.4.2ā¦current master Ā· darktable-org/darktable Ā· GitHub
Thank you @MStraeten for the new build. Interestingly the nightly builds for mac are temporarily disable ādue to an upstream bug with GraphicsMagickā which obviously does not seems to affect your builds.
Anyway your build is working as expected on x86 iMac OS 13.5.
Thanks again
Seems to be a homebrew specific issue - GraphicsMagick 1.3.40 is fine with my macports based build
there are known issues with improper display of menus on an external display when using retina macbooks.
A build using gtk3 3.24.38 doesnāt show this behaviour - but has redrawing issues. Since the latter is just annoying and can be handled by additional scaling attempts (if it occurs) using gtk3 3.24.38 seems to be the better solution.
so here a 4.4.2 arm release build with gtk3 3.24.38
darktable-4.4.2_arm64_gtk3.24.38.dmg
and also current master:
darktable-4.5.0+191~ga097732672_arm64_gtk3.24.38.dmg
darktable-4.5.0+191~ga097732672_x86_64_gtk3.24.38.dmg
not codesigned, so you might need to allow execution via terminal: xattr -c <path/to/application.app>
Interestingly the nightly builds for mac are temporarily disable ādue to an upstream bug with GraphicsMagickā
It is still possible to compile/build darktable if you have already installed the required dependencies.
libjpeg-turbo was recently updated to version 3.0.0 and this causes compile problems with GraphicsMagick.
The Github actions (nightly builds) are always build on a complete fresh environment, meaning the dependencies get freshly installed ā leading now to that problem with GraphicsMagick.
The problem is fixed in GraphicsMagick 1.4.0 but this is not yet released.
Thank you @zisoft for the explanation. I almost always download the nightly build and the builds from @MStraeten and use it as my regular darktable reporting if I find any issues. It is my very modest contribution to darktable.
Hi, new nightly build +209 crash on opening. I will put the report in a new thread to avoid polluting this one.
current master branch + a couple of RF lensfun data from: Kameratrollet + corrected raw whitepoints for Canon M6
darktable-4.5.0+263~g89c14ef3d6_arm64.dmg
darktable-4.5.0+263~g89c14ef3d6_x86_64.dmg (macOS >= 10.14)
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
difference to released 4.4.2 see: Comparing release-4.4.2ā¦current master Ā· darktable-org/darktable Ā· GitHub
current master branch + a couple of RF lensfun data from: Kameratrollet + corrected raw whitepoints for Canon M6
darktable-4.5.0+326~g64d57ebac6_arm64.dmg
darktable-4.5.0+326~g64d57ebac6_x86_64.dmg (macOS >= 10.14)
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
difference to released 4.4.2 see: Comparing release-4.4.2ā¦current master Ā· darktable-org/darktable Ā· GitHub
Working as expected on x86, while the night build still have some issues. Thank you for the build
current master branch + a couple of RF lensfun data from: Kameratrollet + corrected raw whitepoints for Canon M6
darktable-4.5.0+328~g1aca07c62d_arm64.dmg
darktable-4.5.0+328~g1aca07c6_x86_64.dmg (macOS >= 10.14)
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
difference to released 4.4.2 see: Comparing release-4.4.2ā¦current master Ā· darktable-org/darktable Ā· GitHub
