<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=126409#c40">Comment # 40</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Notarize LibreOffice builds so that it launches without warnings on macOS 10.15 Catalina"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=126409">bug 126409</a>
from <span class="vcard"><a class="email" href="mailto:eisa01@gmail.com" title="eisa01 <eisa01@gmail.com>"> <span class="fn">eisa01</span></a>
</span></b>
<pre>cloph: Are we doing all the required steps?
Current instructions say you need to staple the ticket to the binary
On 6.4.1.2 the output I get is:
stapler validate LibreOffice.app/
Processing: /Applications/LibreOffice.app
LibreOffice.app does not have a ticket stapled to it.
So either we don't do the step, or something breaks
(although it says this is only needed for offline validation, but I'
Also there's an issue with the embedded python:
<span class="quote">>codesign -vvv --deep --strict LibreOffice.app/
>LibreOffice.app/: a sealed resource is missing or invalid
>In subcomponent: >/Applications/LibreOffice.app/Contents/Frameworks/LibreOfficePython.framework</span >
So that may be what it complains about:
<span class="quote">>spctl -vvv --assess --type exec LibreOffice.app/
>LibreOffice.app/: a sealed resource is missing or invalid</span >
Notarizing macOS software:
<a href="https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution">https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution</a>
Customizing the notarization workflow:
<a href="https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution/customizing_the_notarization_workflow">https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution/customizing_the_notarization_workflow</a>
Resolving common issues:
<a href="https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution/resolving_common_notarization_issues">https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution/resolving_common_notarization_issues</a>
<span class="quote">>If you use an automated build system, you can integrate the notarization process into your existing build scripts.
>The altool and stapler command-line tools (included with Xcode) allow you to upload your software to the Apple notary service,
>and to staple the resulting ticket to your executable.</span ></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>