Thanks. I will be updating and closing the issue since I have no control
over any of this.
On Thu, Oct 22, 2020, 1:15 PM Jeremy Whiting wrote:
> Notarizing and signing are actually separate things on MacOS, signing the
> app or checking the signature of the dmg are orthogonal to the issue
> desc
Thanks.
On Thu, Oct 22, 2020, 1:15 PM Jeremy Whiting wrote:
> Notarizing and signing are actually separate things on MacOS, signing the
> app or checking the signature of the dmg are orthogonal to the issue
> described and the popup in that report. Notarization is sending the app
> (zipped) to a
Could someone familiar with the CI and OS X signing machinism look at this.
https://bugs.kde.org/show_bug.cgi?id=428062
I have no way to test or fix this issue. Which as far as I know is an issue
with the CI on binary factory.
Notarizing and signing are actually separate things on MacOS, signing the
app or checking the signature of the dmg are orthogonal to the issue
described and the popup in that report. Notarization is sending the app
(zipped) to apple's notarization service so they can check it doesn't use
any apis t
On Fri, Oct 23, 2020 at 6:08 AM Michael Reeves wrote:
> Could someone familiar with the CI and OS X signing machinism look at this.
>
> https://bugs.kde.org/show_bug.cgi?id=428062
>
> I have no way to test or fix this issue. Which as far as I know is an
> issue with the CI on binary factory.
>
T
