You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Pe...@apache.org on 2026/09/10 04:26:45 UTC
MacOS signing update and fix the blue button + black text
hello all,
I have now managed to fully sign the dmg.
in the branch mac-vcl-button-contrast created a signing script has been
addad that signs app and then the image.
I hove that passes notariation too. but that is not part of it. since i
do not have access to a release key.
The notary steps are (and currently missing):
- xcrun notarytool submit --wait
- stapler staple
I have created a signed developer dmg. but that will still trigger the
gatekeeper on any other machine then mine.
Which is okay since this is only a developer build. But you can test the
macOS silicon (no intel support yet)
And i have fixed this button issue. So buttons are now properly shown
with white text.
download:
https://drive.google.com/file/d/1HyZWjXyDSOgVX8QcBK71hPV4kzCFieN5/view?usp=sharing
sorry that i combined the 2 now. It took a while until it worked out.
All the best.
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: MacOS signing update and fix the blue button + black text
Posted by Pe...@apache.org.
Am 10.09.2026 um 19:15 schrieb Jim Jagielski:
> I went ahead and did that, as well as found and patched a few bugs. Folded into trunk and backported to AOO50X.
nice work! Then i can chill for now and look into other topics (none AOO
related.) Back with more next week.
>
>> On Sep 10, 2026, at 5:14 AM, Jim Jagielski <ji...@jagunet.com> wrote:
>>
>> Is there any way you could pull out just the signing bits into a separate commit?
>>
>>> On Sep 10, 2026, at 12:26 AM, petko@apache.org wrote:
>>>
>>>
>> --
>> Jim
>> "This is an outrage!"
>> Tony Harrison
>>
> --
> Jim
> "This is an outrage!"
> Tony Harrison
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: MacOS signing update and fix the blue button + black text
Posted by Pe...@apache.org.
Am 11.09.2026 um 13:55 schrieb Jim Jagielski:
> I've also added even more robustness to the macOS signing, including using, or dropping, EPM as required.
>
> Also, to support our traditional community build workflow where different machines _build_ the images than the one that _signs_ them, I've gone ahead and added a support script to our devtools/release-scripts to support that.
>
> So we should be able to sign both when building as well as after the fact.
Awesome work, Jim!
>
> PS: As a reminder, this is just for 5.0.x and above, since the 4.1.x builds use a too-old version of Xcode for full signing _and_ notary/stapling
>
>> On Sep 10, 2026, at 1:15 PM, Jim Jagielski <ji...@jagunet.com> wrote:
>>
>> I went ahead and did that, as well as found and patched a few bugs. Folded into trunk and backported to AOO50X.
>>
>>> On Sep 10, 2026, at 5:14 AM, Jim Jagielski <ji...@jagunet.com> wrote:
>>>
>>> Is there any way you could pull out just the signing bits into a separate commit?
>>>
>>>> On Sep 10, 2026, at 12:26 AM, petko@apache.org wrote:
>>>>
>>>>
> --
> Jim
> "We are havin' it large!"
> Tony Harrison
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: MacOS signing update and fix the blue button + black text
Posted by Jim Jagielski <ji...@jagunet.com>.
I've also added even more robustness to the macOS signing, including using, or dropping, EPM as required.
Also, to support our traditional community build workflow where different machines _build_ the images than the one that _signs_ them, I've gone ahead and added a support script to our devtools/release-scripts to support that.
So we should be able to sign both when building as well as after the fact.
PS: As a reminder, this is just for 5.0.x and above, since the 4.1.x builds use a too-old version of Xcode for full signing _and_ notary/stapling
> On Sep 10, 2026, at 1:15 PM, Jim Jagielski <ji...@jagunet.com> wrote:
>
> I went ahead and did that, as well as found and patched a few bugs. Folded into trunk and backported to AOO50X.
>
>> On Sep 10, 2026, at 5:14 AM, Jim Jagielski <ji...@jagunet.com> wrote:
>>
>> Is there any way you could pull out just the signing bits into a separate commit?
>>
>>> On Sep 10, 2026, at 12:26 AM, petko@apache.org wrote:
>>>
>>>
>>
--
Jim
"We are havin' it large!"
Tony Harrison
Re: MacOS signing update and fix the blue button + black text
Posted by Jim Jagielski <ji...@jagunet.com>.
I went ahead and did that, as well as found and patched a few bugs. Folded into trunk and backported to AOO50X.
> On Sep 10, 2026, at 5:14 AM, Jim Jagielski <ji...@jagunet.com> wrote:
>
> Is there any way you could pull out just the signing bits into a separate commit?
>
>> On Sep 10, 2026, at 12:26 AM, petko@apache.org wrote:
>>
>>
>
> --
> Jim
> "This is an outrage!"
> Tony Harrison
>
--
Jim
"This is an outrage!"
Tony Harrison
Re: MacOS signing update and fix the blue button + black text
Posted by Jim Jagielski <ji...@jagunet.com>.
https://infra.apache.org/code-signing-access.html
> On Sep 10, 2026, at 1:36 PM, Jim Jagielski <ji...@jagunet.com> wrote:
>
> How can that be? Apple signing doesn't use a service afaik.
>
>> On Sep 10, 2026, at 1:33 PM, petko@apache.org wrote:
>>
>>
>> Am 10.09.2026 um 16:32 schrieb Jim Jagielski:
>>> I believe that is just w/ Windows signing, and not Apple.
>>
>> That was true but even that changed when we switched the service.
>>
>> I need to experiment a bit around. I would like to keep the signing as part of the build.
>>
>> But maybe add it as Flag. Not sure, what is best. cool would be if you could reference the key to use with -signkey="key name"
>> If the Flag is not given the package is not signed. Maybe that could be nice for all build targets. Independant if windows, Linux or Mac.
>> In case of Linux would be maybe nice for flatpack or snap.
>>
>>>
>>>> On Sep 10, 2026, at 10:15 AM, Dave Fisher <wave@apache.org <ma...@apache.org>> wrote:
>>>>
>>>> Unless things have changed signing with ASF credentials is not free. If continuing with Peter’s plan then a distinction needs to be made between signing a developer’s or ci build, and signing a release build.
>>>>
>>>>> On Sep 10, 2026, at 4:24 AM, Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com>> wrote:
>>>>>
>>>>> Whatever you want. I'm done.
>>>>>
>>>>>> On Sep 10, 2026, at 6:54 AM, Peter Kovacs <legine@posteo.de <ma...@posteo.de> <ma...@posteo.de>> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> Am 10. September 2026 12:24:19 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com> <ma...@jagunet.com>>:
>>>>>>> On our builds, yes of course. But we should not force someone who downloads the source and builds for themselves to also sign that.
>>>>>>>
>>>>>>> Traditionally, we've always signed after we build as a separate process from building the community build DMGs.
>>>>>>>
>>>>>>> Hopefully that's a bit more clear :)
>>>>>> Ok. And what solution do you propose?
>>>>>> Apple says packaging involves signing. You can not change that.
>>>>>> I am for we release proper signed software or none at all. There is no in between anymore.
>>>>>>>> On Sep 10, 2026, at 5:59 AM, Peter Kovacs <peter.kovacs@posteo.de <ma...@posteo.de> <ma...@posteo.de>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Am 10. September 2026 11:47:21 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com>>:
>>>>>>>>> I can't imagine the regular user wanting/needing to sign...
>>>>>>>> Sorry maybe I was not clear.
>>>>>>>> I think we should enforce signing on all builds.
>>>>>>>> The user can always see if that build is from us or someone else. Development builds will always trigger the gatekeeper.
>>>>>>>>>> On Sep 10, 2026, at 5:38 AM, Peter Kovacs <peter.kovacs@posteo.de <ma...@posteo.de> <ma...@posteo.de>> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Am 10. September 2026 11:30:18 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com> <ma...@jagunet.com>>:
>>>>>>>>>>> I am also wondering if the actual signing script itself should be in devtools, somewhere under release-scripts instead.
>>>>>>>>>> The process ist to sign the app, then package the image, and then you need to sign again.
>>>>>>>>>>
>>>>>>>>>> I would rather enforce signing to be mandatory.
>>>>>>>>>> What we could put into Devtools maybe is the notarize of the installer. Which publishes the release at Apple. I guess. And then we could think about a process to publish in the store.
>>>>>>>>>>> Cool work.
>>>>>>>>>> Yes. I hope this will
>>>>>>>>>>>> On Sep 10, 2026, at 5:14 AM, Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Is there any way you could pull out just the signing bits into a separate commit?
>>>>>>>>>>>>
>>>>>>>>>>>>> On Sep 10, 2026, at 12:26 AM, petko@apache.org <ma...@apache.org> <ma...@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Jim
>>>>>>>>>>> "This is an outrage!"
>>>>>>>>>>> Tony Harrison
>>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>>>>>>> --
>>>>>>>>> Jim
>>>>>>>>> "This is an outrage!"
>>>>>>>>> Tony Harrison
>>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>>>>
>>>>>>> --
>>>>>>> Jim
>>>>>>> "This is an outrage!"
>>>>>>> Tony Harrison
>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>>> --
>>>>> Jim
>>>>> "This is an outrage!"
>>>>> Tony Harrison
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>> --
>>> Jim
>>> "This is an outrage!"
>>> Tony Harrison
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org>
>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org>
> --
> Jim
> "This is an outrage!"
> Tony Harrison
>
--
Jim
"This is an outrage!"
Tony Harrison
Re: MacOS signing update and fix the blue button + black text
Posted by Jim Jagielski <ji...@jagunet.com>.
I'm not sure that's right... We use the provided cert/key from Infra directly. No per-sign fee.
> On Sep 10, 2026, at 1:52 PM, petko@apache.org wrote:
>
>
> Am 10.09.2026 um 19:36 schrieb Jim Jagielski:
>> How can that be? Apple signing doesn't use a service afaik.
>
> Apple hides it as usual. As much as i understand the process is that Xcode downloads a cert chain from apple developer.
>
> And uses that cert to sign the binaries. All happens local. you find some explanations in our build script.
>
> https://github.com/apache/openoffice/blob/trunk/main/solenv/bin/macosx-codesign.sh
>
> I just have a high level understanding at the moment. did not have the time to deepdive.
>
> If you need more info look in the orig pushed branch: HEAD~2 there you see a .agent folder.
> In that folder should be a long detailed documentation about both topics from the branch.
> On bazel i usually request that the documentation is stored in the module, but i dont do that on trunk.
>
> Since normally i work on bazel since it is cheaper for the AI there. I just dont have bazel for mac yet.
>
>>
>>> On Sep 10, 2026, at 1:33 PM, petko@apache.org wrote:
>>>
>>>
>>> Am 10.09.2026 um 16:32 schrieb Jim Jagielski:
>>>> I believe that is just w/ Windows signing, and not Apple.
>>> That was true but even that changed when we switched the service.
>>>
>>> I need to experiment a bit around. I would like to keep the signing as part of the build.
>>>
>>> But maybe add it as Flag. Not sure, what is best. cool would be if you could reference the key to use with -signkey="key name"
>>> If the Flag is not given the package is not signed. Maybe that could be nice for all build targets. Independant if windows, Linux or Mac.
>>> In case of Linux would be maybe nice for flatpack or snap.
>>>
>>>>> On Sep 10, 2026, at 10:15 AM, Dave Fisher <wave@apache.org <ma...@apache.org>> wrote:
>>>>>
>>>>> Unless things have changed signing with ASF credentials is not free. If continuing with Peter’s plan then a distinction needs to be made between signing a developer’s or ci build, and signing a release build.
>>>>>
>>>>>> On Sep 10, 2026, at 4:24 AM, Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com>> wrote:
>>>>>>
>>>>>> Whatever you want. I'm done.
>>>>>>
>>>>>>> On Sep 10, 2026, at 6:54 AM, Peter Kovacs <legine@posteo.de <ma...@posteo.de> <ma...@posteo.de>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Am 10. September 2026 12:24:19 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com> <ma...@jagunet.com>>:
>>>>>>>> On our builds, yes of course. But we should not force someone who downloads the source and builds for themselves to also sign that.
>>>>>>>>
>>>>>>>> Traditionally, we've always signed after we build as a separate process from building the community build DMGs.
>>>>>>>>
>>>>>>>> Hopefully that's a bit more clear :)
>>>>>>> Ok. And what solution do you propose?
>>>>>>> Apple says packaging involves signing. You can not change that.
>>>>>>> I am for we release proper signed software or none at all. There is no in between anymore.
>>>>>>>>> On Sep 10, 2026, at 5:59 AM, Peter Kovacs <peter.kovacs@posteo.de <ma...@posteo.de> <ma...@posteo.de>> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Am 10. September 2026 11:47:21 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com>>:
>>>>>>>>>> I can't imagine the regular user wanting/needing to sign...
>>>>>>>>> Sorry maybe I was not clear.
>>>>>>>>> I think we should enforce signing on all builds.
>>>>>>>>> The user can always see if that build is from us or someone else. Development builds will always trigger the gatekeeper.
>>>>>>>>>>> On Sep 10, 2026, at 5:38 AM, Peter Kovacs <peter.kovacs@posteo.de <ma...@posteo.de> <ma...@posteo.de>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Am 10. September 2026 11:30:18 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com> <ma...@jagunet.com>>:
>>>>>>>>>>>> I am also wondering if the actual signing script itself should be in devtools, somewhere under release-scripts instead.
>>>>>>>>>>> The process ist to sign the app, then package the image, and then you need to sign again.
>>>>>>>>>>>
>>>>>>>>>>> I would rather enforce signing to be mandatory.
>>>>>>>>>>> What we could put into Devtools maybe is the notarize of the installer. Which publishes the release at Apple. I guess. And then we could think about a process to publish in the store.
>>>>>>>>>>>> Cool work.
>>>>>>>>>>> Yes. I hope this will
>>>>>>>>>>>>> On Sep 10, 2026, at 5:14 AM, Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Is there any way you could pull out just the signing bits into a separate commit?
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sep 10, 2026, at 12:26 AM, petko@apache.org <ma...@apache.org> <ma...@apache.org> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Jim
>>>>>>>>>>>> "This is an outrage!"
>>>>>>>>>>>> Tony Harrison
>>>>>>>>>>>>
>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>>>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>>>>>>>> --
>>>>>>>>>> Jim
>>>>>>>>>> "This is an outrage!"
>>>>>>>>>> Tony Harrison
>>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>>>>>
>>>>>>>> --
>>>>>>>> Jim
>>>>>>>> "This is an outrage!"
>>>>>>>> Tony Harrison
>>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>>>> --
>>>>>> Jim
>>>>>> "This is an outrage!"
>>>>>> Tony Harrison
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>> --
>>>> Jim
>>>> "This is an outrage!"
>>>> Tony Harrison
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org>
>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org>
>> --
>> Jim
>> "This is an outrage!"
>> Tony Harrison
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org>
> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org>
--
Jim
"This is an outrage!"
Tony Harrison
Re: MacOS signing update and fix the blue button + black text
Posted by Pe...@apache.org.
Am 10.09.2026 um 19:36 schrieb Jim Jagielski:
> How can that be? Apple signing doesn't use a service afaik.
Apple hides it as usual. As much as i understand the process is that
Xcode downloads a cert chain from apple developer.
And uses that cert to sign the binaries. All happens local. you find
some explanations in our build script.
https://github.com/apache/openoffice/blob/trunk/main/solenv/bin/macosx-codesign.sh
I just have a high level understanding at the moment. did not have the
time to deepdive.
If you need more info look in the orig pushed branch: HEAD~2 there you
see a .agent folder.
In that folder should be a long detailed documentation about both topics
from the branch.
On bazel i usually request that the documentation is stored in the
module, but i dont do that on trunk.
Since normally i work on bazel since it is cheaper for the AI there. I
just dont have bazel for mac yet.
>
>> On Sep 10, 2026, at 1:33 PM, petko@apache.org wrote:
>>
>>
>> Am 10.09.2026 um 16:32 schrieb Jim Jagielski:
>>> I believe that is just w/ Windows signing, and not Apple.
>> That was true but even that changed when we switched the service.
>>
>> I need to experiment a bit around. I would like to keep the signing as part of the build.
>>
>> But maybe add it as Flag. Not sure, what is best. cool would be if you could reference the key to use with -signkey="key name"
>> If the Flag is not given the package is not signed. Maybe that could be nice for all build targets. Independant if windows, Linux or Mac.
>> In case of Linux would be maybe nice for flatpack or snap.
>>
>>>> On Sep 10, 2026, at 10:15 AM, Dave Fisher <wave@apache.org <ma...@apache.org>> wrote:
>>>>
>>>> Unless things have changed signing with ASF credentials is not free. If continuing with Peter’s plan then a distinction needs to be made between signing a developer’s or ci build, and signing a release build.
>>>>
>>>>> On Sep 10, 2026, at 4:24 AM, Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com>> wrote:
>>>>>
>>>>> Whatever you want. I'm done.
>>>>>
>>>>>> On Sep 10, 2026, at 6:54 AM, Peter Kovacs <legine@posteo.de <ma...@posteo.de> <ma...@posteo.de>> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> Am 10. September 2026 12:24:19 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com> <ma...@jagunet.com>>:
>>>>>>> On our builds, yes of course. But we should not force someone who downloads the source and builds for themselves to also sign that.
>>>>>>>
>>>>>>> Traditionally, we've always signed after we build as a separate process from building the community build DMGs.
>>>>>>>
>>>>>>> Hopefully that's a bit more clear :)
>>>>>> Ok. And what solution do you propose?
>>>>>> Apple says packaging involves signing. You can not change that.
>>>>>> I am for we release proper signed software or none at all. There is no in between anymore.
>>>>>>>> On Sep 10, 2026, at 5:59 AM, Peter Kovacs <peter.kovacs@posteo.de <ma...@posteo.de> <ma...@posteo.de>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Am 10. September 2026 11:47:21 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com>>:
>>>>>>>>> I can't imagine the regular user wanting/needing to sign...
>>>>>>>> Sorry maybe I was not clear.
>>>>>>>> I think we should enforce signing on all builds.
>>>>>>>> The user can always see if that build is from us or someone else. Development builds will always trigger the gatekeeper.
>>>>>>>>>> On Sep 10, 2026, at 5:38 AM, Peter Kovacs <peter.kovacs@posteo.de <ma...@posteo.de> <ma...@posteo.de>> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Am 10. September 2026 11:30:18 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com> <ma...@jagunet.com>>:
>>>>>>>>>>> I am also wondering if the actual signing script itself should be in devtools, somewhere under release-scripts instead.
>>>>>>>>>> The process ist to sign the app, then package the image, and then you need to sign again.
>>>>>>>>>>
>>>>>>>>>> I would rather enforce signing to be mandatory.
>>>>>>>>>> What we could put into Devtools maybe is the notarize of the installer. Which publishes the release at Apple. I guess. And then we could think about a process to publish in the store.
>>>>>>>>>>> Cool work.
>>>>>>>>>> Yes. I hope this will
>>>>>>>>>>>> On Sep 10, 2026, at 5:14 AM, Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Is there any way you could pull out just the signing bits into a separate commit?
>>>>>>>>>>>>
>>>>>>>>>>>>> On Sep 10, 2026, at 12:26 AM, petko@apache.org <ma...@apache.org> <ma...@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Jim
>>>>>>>>>>> "This is an outrage!"
>>>>>>>>>>> Tony Harrison
>>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>>>>>>> --
>>>>>>>>> Jim
>>>>>>>>> "This is an outrage!"
>>>>>>>>> Tony Harrison
>>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>>>>
>>>>>>> --
>>>>>>> Jim
>>>>>>> "This is an outrage!"
>>>>>>> Tony Harrison
>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>>> --
>>>>> Jim
>>>>> "This is an outrage!"
>>>>> Tony Harrison
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>> --
>>> Jim
>>> "This is an outrage!"
>>> Tony Harrison
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org>
>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org>
> --
> Jim
> "This is an outrage!"
> Tony Harrison
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: MacOS signing update and fix the blue button + black text
Posted by Jim Jagielski <ji...@jagunet.com>.
How can that be? Apple signing doesn't use a service afaik.
> On Sep 10, 2026, at 1:33 PM, petko@apache.org wrote:
>
>
> Am 10.09.2026 um 16:32 schrieb Jim Jagielski:
>> I believe that is just w/ Windows signing, and not Apple.
>
> That was true but even that changed when we switched the service.
>
> I need to experiment a bit around. I would like to keep the signing as part of the build.
>
> But maybe add it as Flag. Not sure, what is best. cool would be if you could reference the key to use with -signkey="key name"
> If the Flag is not given the package is not signed. Maybe that could be nice for all build targets. Independant if windows, Linux or Mac.
> In case of Linux would be maybe nice for flatpack or snap.
>
>>
>>> On Sep 10, 2026, at 10:15 AM, Dave Fisher <wave@apache.org <ma...@apache.org>> wrote:
>>>
>>> Unless things have changed signing with ASF credentials is not free. If continuing with Peter’s plan then a distinction needs to be made between signing a developer’s or ci build, and signing a release build.
>>>
>>>> On Sep 10, 2026, at 4:24 AM, Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com>> wrote:
>>>>
>>>> Whatever you want. I'm done.
>>>>
>>>>> On Sep 10, 2026, at 6:54 AM, Peter Kovacs <legine@posteo.de <ma...@posteo.de> <ma...@posteo.de>> wrote:
>>>>>
>>>>>
>>>>>
>>>>> Am 10. September 2026 12:24:19 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com> <ma...@jagunet.com>>:
>>>>>> On our builds, yes of course. But we should not force someone who downloads the source and builds for themselves to also sign that.
>>>>>>
>>>>>> Traditionally, we've always signed after we build as a separate process from building the community build DMGs.
>>>>>>
>>>>>> Hopefully that's a bit more clear :)
>>>>> Ok. And what solution do you propose?
>>>>> Apple says packaging involves signing. You can not change that.
>>>>> I am for we release proper signed software or none at all. There is no in between anymore.
>>>>>>> On Sep 10, 2026, at 5:59 AM, Peter Kovacs <peter.kovacs@posteo.de <ma...@posteo.de> <ma...@posteo.de>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Am 10. September 2026 11:47:21 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com>>:
>>>>>>>> I can't imagine the regular user wanting/needing to sign...
>>>>>>> Sorry maybe I was not clear.
>>>>>>> I think we should enforce signing on all builds.
>>>>>>> The user can always see if that build is from us or someone else. Development builds will always trigger the gatekeeper.
>>>>>>>>> On Sep 10, 2026, at 5:38 AM, Peter Kovacs <peter.kovacs@posteo.de <ma...@posteo.de> <ma...@posteo.de>> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Am 10. September 2026 11:30:18 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com> <ma...@jagunet.com>>:
>>>>>>>>>> I am also wondering if the actual signing script itself should be in devtools, somewhere under release-scripts instead.
>>>>>>>>> The process ist to sign the app, then package the image, and then you need to sign again.
>>>>>>>>>
>>>>>>>>> I would rather enforce signing to be mandatory.
>>>>>>>>> What we could put into Devtools maybe is the notarize of the installer. Which publishes the release at Apple. I guess. And then we could think about a process to publish in the store.
>>>>>>>>>> Cool work.
>>>>>>>>> Yes. I hope this will
>>>>>>>>>>> On Sep 10, 2026, at 5:14 AM, Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Is there any way you could pull out just the signing bits into a separate commit?
>>>>>>>>>>>
>>>>>>>>>>>> On Sep 10, 2026, at 12:26 AM, petko@apache.org <ma...@apache.org> <ma...@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Jim
>>>>>>>>>> "This is an outrage!"
>>>>>>>>>> Tony Harrison
>>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>>>>>> --
>>>>>>>> Jim
>>>>>>>> "This is an outrage!"
>>>>>>>> Tony Harrison
>>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>>>
>>>>>> --
>>>>>> Jim
>>>>>> "This is an outrage!"
>>>>>> Tony Harrison
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>> --
>>>> Jim
>>>> "This is an outrage!"
>>>> Tony Harrison
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>> --
>> Jim
>> "This is an outrage!"
>> Tony Harrison
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org>
> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org>
--
Jim
"This is an outrage!"
Tony Harrison
Re: MacOS signing update and fix the blue button + black text
Posted by Pe...@apache.org.
Am 10.09.2026 um 16:32 schrieb Jim Jagielski:
> I believe that is just w/ Windows signing, and not Apple.
That was true but even that changed when we switched the service.
I need to experiment a bit around. I would like to keep the signing as
part of the build.
But maybe add it as Flag. Not sure, what is best. cool would be if you
could reference the key to use with -signkey="key name"
If the Flag is not given the package is not signed. Maybe that could be
nice for all build targets. Independant if windows, Linux or Mac.
In case of Linux would be maybe nice for flatpack or snap.
>
>> On Sep 10, 2026, at 10:15 AM, Dave Fisher <wa...@apache.org> wrote:
>>
>> Unless things have changed signing with ASF credentials is not free. If continuing with Peter’s plan then a distinction needs to be made between signing a developer’s or ci build, and signing a release build.
>>
>>> On Sep 10, 2026, at 4:24 AM, Jim Jagielski <jim@jagunet.com <ma...@jagunet.com>> wrote:
>>>
>>> Whatever you want. I'm done.
>>>
>>>> On Sep 10, 2026, at 6:54 AM, Peter Kovacs <legine@posteo.de <ma...@posteo.de>> wrote:
>>>>
>>>>
>>>>
>>>> Am 10. September 2026 12:24:19 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com>>:
>>>>> On our builds, yes of course. But we should not force someone who downloads the source and builds for themselves to also sign that.
>>>>>
>>>>> Traditionally, we've always signed after we build as a separate process from building the community build DMGs.
>>>>>
>>>>> Hopefully that's a bit more clear :)
>>>> Ok. And what solution do you propose?
>>>> Apple says packaging involves signing. You can not change that.
>>>> I am for we release proper signed software or none at all. There is no in between anymore.
>>>>>> On Sep 10, 2026, at 5:59 AM, Peter Kovacs <peter.kovacs@posteo.de <ma...@posteo.de>> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> Am 10. September 2026 11:47:21 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com>>:
>>>>>>> I can't imagine the regular user wanting/needing to sign...
>>>>>> Sorry maybe I was not clear.
>>>>>> I think we should enforce signing on all builds.
>>>>>> The user can always see if that build is from us or someone else. Development builds will always trigger the gatekeeper.
>>>>>>>> On Sep 10, 2026, at 5:38 AM, Peter Kovacs <peter.kovacs@posteo.de <ma...@posteo.de>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Am 10. September 2026 11:30:18 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com>>:
>>>>>>>>> I am also wondering if the actual signing script itself should be in devtools, somewhere under release-scripts instead.
>>>>>>>> The process ist to sign the app, then package the image, and then you need to sign again.
>>>>>>>>
>>>>>>>> I would rather enforce signing to be mandatory.
>>>>>>>> What we could put into Devtools maybe is the notarize of the installer. Which publishes the release at Apple. I guess. And then we could think about a process to publish in the store.
>>>>>>>>> Cool work.
>>>>>>>> Yes. I hope this will
>>>>>>>>>> On Sep 10, 2026, at 5:14 AM, Jim Jagielski <jim@jagunet.com <ma...@jagunet.com>> wrote:
>>>>>>>>>>
>>>>>>>>>> Is there any way you could pull out just the signing bits into a separate commit?
>>>>>>>>>>
>>>>>>>>>>> On Sep 10, 2026, at 12:26 AM, petko@apache.org <ma...@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Jim
>>>>>>>>> "This is an outrage!"
>>>>>>>>> Tony Harrison
>>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>>>>> --
>>>>>>> Jim
>>>>>>> "This is an outrage!"
>>>>>>> Tony Harrison
>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>>
>>>>> --
>>>>> Jim
>>>>> "This is an outrage!"
>>>>> Tony Harrison
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>> --
>>> Jim
>>> "This is an outrage!"
>>> Tony Harrison
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org>
>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org>
> --
> Jim
> "This is an outrage!"
> Tony Harrison
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: MacOS signing update and fix the blue button + black text
Posted by Jim Jagielski <ji...@jagunet.com>.
I believe that is just w/ Windows signing, and not Apple.
> On Sep 10, 2026, at 10:15 AM, Dave Fisher <wa...@apache.org> wrote:
>
> Unless things have changed signing with ASF credentials is not free. If continuing with Peter’s plan then a distinction needs to be made between signing a developer’s or ci build, and signing a release build.
>
>> On Sep 10, 2026, at 4:24 AM, Jim Jagielski <jim@jagunet.com <ma...@jagunet.com>> wrote:
>>
>> Whatever you want. I'm done.
>>
>>> On Sep 10, 2026, at 6:54 AM, Peter Kovacs <legine@posteo.de <ma...@posteo.de>> wrote:
>>>
>>>
>>>
>>> Am 10. September 2026 12:24:19 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com>>:
>>>> On our builds, yes of course. But we should not force someone who downloads the source and builds for themselves to also sign that.
>>>>
>>>> Traditionally, we've always signed after we build as a separate process from building the community build DMGs.
>>>>
>>>> Hopefully that's a bit more clear :)
>>> Ok. And what solution do you propose?
>>> Apple says packaging involves signing. You can not change that.
>>> I am for we release proper signed software or none at all. There is no in between anymore.
>>>>
>>>>> On Sep 10, 2026, at 5:59 AM, Peter Kovacs <peter.kovacs@posteo.de <ma...@posteo.de>> wrote:
>>>>>
>>>>>
>>>>>
>>>>> Am 10. September 2026 11:47:21 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com>>:
>>>>>> I can't imagine the regular user wanting/needing to sign...
>>>>> Sorry maybe I was not clear.
>>>>> I think we should enforce signing on all builds.
>>>>> The user can always see if that build is from us or someone else. Development builds will always trigger the gatekeeper.
>>>>>>
>>>>>>> On Sep 10, 2026, at 5:38 AM, Peter Kovacs <peter.kovacs@posteo.de <ma...@posteo.de>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Am 10. September 2026 11:30:18 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com> <ma...@jagunet.com>>:
>>>>>>>> I am also wondering if the actual signing script itself should be in devtools, somewhere under release-scripts instead.
>>>>>>>
>>>>>>> The process ist to sign the app, then package the image, and then you need to sign again.
>>>>>>>
>>>>>>> I would rather enforce signing to be mandatory.
>>>>>>> What we could put into Devtools maybe is the notarize of the installer. Which publishes the release at Apple. I guess. And then we could think about a process to publish in the store.
>>>>>>>>
>>>>>>>> Cool work.
>>>>>>> Yes. I hope this will
>>>>>>>>
>>>>>>>>> On Sep 10, 2026, at 5:14 AM, Jim Jagielski <jim@jagunet.com <ma...@jagunet.com>> wrote:
>>>>>>>>>
>>>>>>>>> Is there any way you could pull out just the signing bits into a separate commit?
>>>>>>>>>
>>>>>>>>>> On Sep 10, 2026, at 12:26 AM, petko@apache.org <ma...@apache.org> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Jim
>>>>>>>> "This is an outrage!"
>>>>>>>> Tony Harrison
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>>>>> --
>>>>>> Jim
>>>>>> "This is an outrage!"
>>>>>> Tony Harrison
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>
>>>>
>>>> --
>>>> Jim
>>>> "This is an outrage!"
>>>> Tony Harrison
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org> <ma...@openoffice.apache.org>
>> --
>> Jim
>> "This is an outrage!"
>> Tony Harrison
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org>
> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org>
--
Jim
"This is an outrage!"
Tony Harrison
Re: MacOS signing update and fix the blue button + black text
Posted by Dave Fisher <wa...@apache.org>.
Unless things have changed signing with ASF credentials is not free. If continuing with Peter’s plan then a distinction needs to be made between signing a developer’s or ci build, and signing a release build.
> On Sep 10, 2026, at 4:24 AM, Jim Jagielski <ji...@jagunet.com> wrote:
>
> Whatever you want. I'm done.
>
>> On Sep 10, 2026, at 6:54 AM, Peter Kovacs <le...@posteo.de> wrote:
>>
>>
>>
>> Am 10. September 2026 12:24:19 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com>>:
>>> On our builds, yes of course. But we should not force someone who downloads the source and builds for themselves to also sign that.
>>>
>>> Traditionally, we've always signed after we build as a separate process from building the community build DMGs.
>>>
>>> Hopefully that's a bit more clear :)
>> Ok. And what solution do you propose?
>> Apple says packaging involves signing. You can not change that.
>> I am for we release proper signed software or none at all. There is no in between anymore.
>>>
>>>> On Sep 10, 2026, at 5:59 AM, Peter Kovacs <pe...@posteo.de> wrote:
>>>>
>>>>
>>>>
>>>> Am 10. September 2026 11:47:21 MESZ schrieb Jim Jagielski <ji...@jagunet.com>:
>>>>> I can't imagine the regular user wanting/needing to sign...
>>>> Sorry maybe I was not clear.
>>>> I think we should enforce signing on all builds.
>>>> The user can always see if that build is from us or someone else. Development builds will always trigger the gatekeeper.
>>>>>
>>>>>> On Sep 10, 2026, at 5:38 AM, Peter Kovacs <pe...@posteo.de> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> Am 10. September 2026 11:30:18 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com>>:
>>>>>>> I am also wondering if the actual signing script itself should be in devtools, somewhere under release-scripts instead.
>>>>>>
>>>>>> The process ist to sign the app, then package the image, and then you need to sign again.
>>>>>>
>>>>>> I would rather enforce signing to be mandatory.
>>>>>> What we could put into Devtools maybe is the notarize of the installer. Which publishes the release at Apple. I guess. And then we could think about a process to publish in the store.
>>>>>>>
>>>>>>> Cool work.
>>>>>> Yes. I hope this will
>>>>>>>
>>>>>>>> On Sep 10, 2026, at 5:14 AM, Jim Jagielski <ji...@jagunet.com> wrote:
>>>>>>>>
>>>>>>>> Is there any way you could pull out just the signing bits into a separate commit?
>>>>>>>>
>>>>>>>>> On Sep 10, 2026, at 12:26 AM, petko@apache.org wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Jim
>>>>>>> "This is an outrage!"
>>>>>>> Tony Harrison
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org>
>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org>
>>>>> --
>>>>> Jim
>>>>> "This is an outrage!"
>>>>> Tony Harrison
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>
>>>
>>> --
>>> Jim
>>> "This is an outrage!"
>>> Tony Harrison
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org>
>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org>
> --
> Jim
> "This is an outrage!"
> Tony Harrison
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: (offlist) MacOS signing update and fix the blue button + black text
Posted by Jim Jagielski <ji...@jagunet.com>.
I have no real leaning one way or another... if you feel that the current method that you proposed is best, then fine. It's not worth the discussion or the debate. So whatever you feel is best works for me.
> On Sep 10, 2026, at 7:41 AM, Peter Kovacs <pe...@posteo.de> wrote:
>
> Hey Jim,
>
> I hope you are not offended. I am not sure how to read your words.
> I am not sure but i might have communicated in a German tone. Which is usually very blunt.
> If you are, I am sorry. My excuse is I wrote during work. I know it's a lame excuse but I did not think about it.
> I am as you open for all solutions. Important to me is to meet Apple's requirements.
>
> All the best
> Peter
>
> Am 10. September 2026 13:24:45 MESZ schrieb Jim Jagielski <ji...@jagunet.com>:
>> Whatever you want. I'm done.
>>
>>> On Sep 10, 2026, at 6:54 AM, Peter Kovacs <le...@posteo.de> wrote:
>>>
>>>
>>>
>>> Am 10. September 2026 12:24:19 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com>>:
>>>> On our builds, yes of course. But we should not force someone who downloads the source and builds for themselves to also sign that.
>>>>
>>>> Traditionally, we've always signed after we build as a separate process from building the community build DMGs.
>>>>
>>>> Hopefully that's a bit more clear :)
>>> Ok. And what solution do you propose?
>>> Apple says packaging involves signing. You can not change that.
>>> I am for we release proper signed software or none at all. There is no in between anymore.
>>>>
>>>>> On Sep 10, 2026, at 5:59 AM, Peter Kovacs <pe...@posteo.de> wrote:
>>>>>
>>>>>
>>>>>
>>>>> Am 10. September 2026 11:47:21 MESZ schrieb Jim Jagielski <ji...@jagunet.com>:
>>>>>> I can't imagine the regular user wanting/needing to sign...
>>>>> Sorry maybe I was not clear.
>>>>> I think we should enforce signing on all builds.
>>>>> The user can always see if that build is from us or someone else. Development builds will always trigger the gatekeeper.
>>>>>>
>>>>>>> On Sep 10, 2026, at 5:38 AM, Peter Kovacs <pe...@posteo.de> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Am 10. September 2026 11:30:18 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com>>:
>>>>>>>> I am also wondering if the actual signing script itself should be in devtools, somewhere under release-scripts instead.
>>>>>>>
>>>>>>> The process ist to sign the app, then package the image, and then you need to sign again.
>>>>>>>
>>>>>>> I would rather enforce signing to be mandatory.
>>>>>>> What we could put into Devtools maybe is the notarize of the installer. Which publishes the release at Apple. I guess. And then we could think about a process to publish in the store.
>>>>>>>>
>>>>>>>> Cool work.
>>>>>>> Yes. I hope this will
>>>>>>>>
>>>>>>>>> On Sep 10, 2026, at 5:14 AM, Jim Jagielski <ji...@jagunet.com> wrote:
>>>>>>>>>
>>>>>>>>> Is there any way you could pull out just the signing bits into a separate commit?
>>>>>>>>>
>>>>>>>>>> On Sep 10, 2026, at 12:26 AM, petko@apache.org wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Jim
>>>>>>>> "This is an outrage!"
>>>>>>>> Tony Harrison
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org>
>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org>
>>>>>> --
>>>>>> Jim
>>>>>> "This is an outrage!"
>>>>>> Tony Harrison
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>
>>>>
>>>> --
>>>> Jim
>>>> "This is an outrage!"
>>>> Tony Harrison
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org>
>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org>
>> --
>> Jim
>> "This is an outrage!"
>> Tony Harrison
>>
--
Jim
"This is an outrage!"
Tony Harrison
(offlist) MacOS signing update and fix the blue button + black text
Posted by Peter Kovacs <pe...@posteo.de>.
Hey Jim,
I hope you are not offended. I am not sure how to read your words.
I am not sure but i might have communicated in a German tone. Which is usually very blunt.
If you are, I am sorry. My excuse is I wrote during work. I know it's a lame excuse but I did not think about it.
I am as you open for all solutions. Important to me is to meet Apple's requirements.
All the best
Peter
Am 10. September 2026 13:24:45 MESZ schrieb Jim Jagielski <ji...@jagunet.com>:
>Whatever you want. I'm done.
>
>> On Sep 10, 2026, at 6:54 AM, Peter Kovacs <le...@posteo.de> wrote:
>>
>>
>>
>> Am 10. September 2026 12:24:19 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com>>:
>>> On our builds, yes of course. But we should not force someone who downloads the source and builds for themselves to also sign that.
>>>
>>> Traditionally, we've always signed after we build as a separate process from building the community build DMGs.
>>>
>>> Hopefully that's a bit more clear :)
>> Ok. And what solution do you propose?
>> Apple says packaging involves signing. You can not change that.
>> I am for we release proper signed software or none at all. There is no in between anymore.
>>>
>>>> On Sep 10, 2026, at 5:59 AM, Peter Kovacs <pe...@posteo.de> wrote:
>>>>
>>>>
>>>>
>>>> Am 10. September 2026 11:47:21 MESZ schrieb Jim Jagielski <ji...@jagunet.com>:
>>>>> I can't imagine the regular user wanting/needing to sign...
>>>> Sorry maybe I was not clear.
>>>> I think we should enforce signing on all builds.
>>>> The user can always see if that build is from us or someone else. Development builds will always trigger the gatekeeper.
>>>>>
>>>>>> On Sep 10, 2026, at 5:38 AM, Peter Kovacs <pe...@posteo.de> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> Am 10. September 2026 11:30:18 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com>>:
>>>>>>> I am also wondering if the actual signing script itself should be in devtools, somewhere under release-scripts instead.
>>>>>>
>>>>>> The process ist to sign the app, then package the image, and then you need to sign again.
>>>>>>
>>>>>> I would rather enforce signing to be mandatory.
>>>>>> What we could put into Devtools maybe is the notarize of the installer. Which publishes the release at Apple. I guess. And then we could think about a process to publish in the store.
>>>>>>>
>>>>>>> Cool work.
>>>>>> Yes. I hope this will
>>>>>>>
>>>>>>>> On Sep 10, 2026, at 5:14 AM, Jim Jagielski <ji...@jagunet.com> wrote:
>>>>>>>>
>>>>>>>> Is there any way you could pull out just the signing bits into a separate commit?
>>>>>>>>
>>>>>>>>> On Sep 10, 2026, at 12:26 AM, petko@apache.org wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Jim
>>>>>>> "This is an outrage!"
>>>>>>> Tony Harrison
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org>
>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org>
>>>>> --
>>>>> Jim
>>>>> "This is an outrage!"
>>>>> Tony Harrison
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>
>>>
>>> --
>>> Jim
>>> "This is an outrage!"
>>> Tony Harrison
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org>
>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org>
>--
>Jim
> "This is an outrage!"
> Tony Harrison
>
Re: MacOS signing update and fix the blue button + black text
Posted by Jim Jagielski <ji...@jagunet.com>.
Whatever you want. I'm done.
> On Sep 10, 2026, at 6:54 AM, Peter Kovacs <le...@posteo.de> wrote:
>
>
>
> Am 10. September 2026 12:24:19 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com>>:
>> On our builds, yes of course. But we should not force someone who downloads the source and builds for themselves to also sign that.
>>
>> Traditionally, we've always signed after we build as a separate process from building the community build DMGs.
>>
>> Hopefully that's a bit more clear :)
> Ok. And what solution do you propose?
> Apple says packaging involves signing. You can not change that.
> I am for we release proper signed software or none at all. There is no in between anymore.
>>
>>> On Sep 10, 2026, at 5:59 AM, Peter Kovacs <pe...@posteo.de> wrote:
>>>
>>>
>>>
>>> Am 10. September 2026 11:47:21 MESZ schrieb Jim Jagielski <ji...@jagunet.com>:
>>>> I can't imagine the regular user wanting/needing to sign...
>>> Sorry maybe I was not clear.
>>> I think we should enforce signing on all builds.
>>> The user can always see if that build is from us or someone else. Development builds will always trigger the gatekeeper.
>>>>
>>>>> On Sep 10, 2026, at 5:38 AM, Peter Kovacs <pe...@posteo.de> wrote:
>>>>>
>>>>>
>>>>>
>>>>> Am 10. September 2026 11:30:18 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com>>:
>>>>>> I am also wondering if the actual signing script itself should be in devtools, somewhere under release-scripts instead.
>>>>>
>>>>> The process ist to sign the app, then package the image, and then you need to sign again.
>>>>>
>>>>> I would rather enforce signing to be mandatory.
>>>>> What we could put into Devtools maybe is the notarize of the installer. Which publishes the release at Apple. I guess. And then we could think about a process to publish in the store.
>>>>>>
>>>>>> Cool work.
>>>>> Yes. I hope this will
>>>>>>
>>>>>>> On Sep 10, 2026, at 5:14 AM, Jim Jagielski <ji...@jagunet.com> wrote:
>>>>>>>
>>>>>>> Is there any way you could pull out just the signing bits into a separate commit?
>>>>>>>
>>>>>>>> On Sep 10, 2026, at 12:26 AM, petko@apache.org wrote:
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Jim
>>>>>> "This is an outrage!"
>>>>>> Tony Harrison
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org>
>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org>
>>>> --
>>>> Jim
>>>> "This is an outrage!"
>>>> Tony Harrison
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>>
>> --
>> Jim
>> "This is an outrage!"
>> Tony Harrison
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org>
> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org>
--
Jim
"This is an outrage!"
Tony Harrison
Re: MacOS signing update and fix the blue button + black text
Posted by Peter Kovacs <le...@posteo.de>.
Am 10. September 2026 12:24:19 MESZ schrieb Jim Jagielski <ji...@jagunet.com>:
>On our builds, yes of course. But we should not force someone who downloads the source and builds for themselves to also sign that.
>
>Traditionally, we've always signed after we build as a separate process from building the community build DMGs.
>
>Hopefully that's a bit more clear :)
Ok. And what solution do you propose?
Apple says packaging involves signing. You can not change that.
I am for we release proper signed software or none at all. There is no in between anymore.
>
>> On Sep 10, 2026, at 5:59 AM, Peter Kovacs <pe...@posteo.de> wrote:
>>
>>
>>
>> Am 10. September 2026 11:47:21 MESZ schrieb Jim Jagielski <ji...@jagunet.com>:
>>> I can't imagine the regular user wanting/needing to sign...
>> Sorry maybe I was not clear.
>> I think we should enforce signing on all builds.
>> The user can always see if that build is from us or someone else. Development builds will always trigger the gatekeeper.
>>>
>>>> On Sep 10, 2026, at 5:38 AM, Peter Kovacs <pe...@posteo.de> wrote:
>>>>
>>>>
>>>>
>>>> Am 10. September 2026 11:30:18 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com>>:
>>>>> I am also wondering if the actual signing script itself should be in devtools, somewhere under release-scripts instead.
>>>>
>>>> The process ist to sign the app, then package the image, and then you need to sign again.
>>>>
>>>> I would rather enforce signing to be mandatory.
>>>> What we could put into Devtools maybe is the notarize of the installer. Which publishes the release at Apple. I guess. And then we could think about a process to publish in the store.
>>>>>
>>>>> Cool work.
>>>> Yes. I hope this will
>>>>>
>>>>>> On Sep 10, 2026, at 5:14 AM, Jim Jagielski <ji...@jagunet.com> wrote:
>>>>>>
>>>>>> Is there any way you could pull out just the signing bits into a separate commit?
>>>>>>
>>>>>>> On Sep 10, 2026, at 12:26 AM, petko@apache.org wrote:
>>>>>>>
>>>>>>>
>>>>>
>>>>> --
>>>>> Jim
>>>>> "This is an outrage!"
>>>>> Tony Harrison
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org>
>>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org>
>>> --
>>> Jim
>>> "This is an outrage!"
>>> Tony Harrison
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>
>--
>Jim
> "This is an outrage!"
> Tony Harrison
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: MacOS signing update and fix the blue button + black text
Posted by Jim Jagielski <ji...@jagunet.com>.
On our builds, yes of course. But we should not force someone who downloads the source and builds for themselves to also sign that.
Traditionally, we've always signed after we build as a separate process from building the community build DMGs.
Hopefully that's a bit more clear :)
> On Sep 10, 2026, at 5:59 AM, Peter Kovacs <pe...@posteo.de> wrote:
>
>
>
> Am 10. September 2026 11:47:21 MESZ schrieb Jim Jagielski <ji...@jagunet.com>:
>> I can't imagine the regular user wanting/needing to sign...
> Sorry maybe I was not clear.
> I think we should enforce signing on all builds.
> The user can always see if that build is from us or someone else. Development builds will always trigger the gatekeeper.
>>
>>> On Sep 10, 2026, at 5:38 AM, Peter Kovacs <pe...@posteo.de> wrote:
>>>
>>>
>>>
>>> Am 10. September 2026 11:30:18 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com>>:
>>>> I am also wondering if the actual signing script itself should be in devtools, somewhere under release-scripts instead.
>>>
>>> The process ist to sign the app, then package the image, and then you need to sign again.
>>>
>>> I would rather enforce signing to be mandatory.
>>> What we could put into Devtools maybe is the notarize of the installer. Which publishes the release at Apple. I guess. And then we could think about a process to publish in the store.
>>>>
>>>> Cool work.
>>> Yes. I hope this will
>>>>
>>>>> On Sep 10, 2026, at 5:14 AM, Jim Jagielski <ji...@jagunet.com> wrote:
>>>>>
>>>>> Is there any way you could pull out just the signing bits into a separate commit?
>>>>>
>>>>>> On Sep 10, 2026, at 12:26 AM, petko@apache.org wrote:
>>>>>>
>>>>>>
>>>>
>>>> --
>>>> Jim
>>>> "This is an outrage!"
>>>> Tony Harrison
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org>
>>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org>
>> --
>> Jim
>> "This is an outrage!"
>> Tony Harrison
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
--
Jim
"This is an outrage!"
Tony Harrison
Re: MacOS signing update and fix the blue button + black text
Posted by Peter Kovacs <pe...@posteo.de>.
Am 10. September 2026 11:47:21 MESZ schrieb Jim Jagielski <ji...@jagunet.com>:
>I can't imagine the regular user wanting/needing to sign...
Sorry maybe I was not clear.
I think we should enforce signing on all builds.
The user can always see if that build is from us or someone else. Development builds will always trigger the gatekeeper.
>
>> On Sep 10, 2026, at 5:38 AM, Peter Kovacs <pe...@posteo.de> wrote:
>>
>>
>>
>> Am 10. September 2026 11:30:18 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com>>:
>>> I am also wondering if the actual signing script itself should be in devtools, somewhere under release-scripts instead.
>>
>> The process ist to sign the app, then package the image, and then you need to sign again.
>>
>> I would rather enforce signing to be mandatory.
>> What we could put into Devtools maybe is the notarize of the installer. Which publishes the release at Apple. I guess. And then we could think about a process to publish in the store.
>>>
>>> Cool work.
>> Yes. I hope this will
>>>
>>>> On Sep 10, 2026, at 5:14 AM, Jim Jagielski <ji...@jagunet.com> wrote:
>>>>
>>>> Is there any way you could pull out just the signing bits into a separate commit?
>>>>
>>>>> On Sep 10, 2026, at 12:26 AM, petko@apache.org wrote:
>>>>>
>>>>>
>>>
>>> --
>>> Jim
>>> "This is an outrage!"
>>> Tony Harrison
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org>
>> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org>
>--
>Jim
> "This is an outrage!"
> Tony Harrison
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: MacOS signing update and fix the blue button + black text
Posted by Jim Jagielski <ji...@jagunet.com>.
I can't imagine the regular user wanting/needing to sign...
> On Sep 10, 2026, at 5:38 AM, Peter Kovacs <pe...@posteo.de> wrote:
>
>
>
> Am 10. September 2026 11:30:18 MESZ schrieb Jim Jagielski <jim@jagunet.com <ma...@jagunet.com>>:
>> I am also wondering if the actual signing script itself should be in devtools, somewhere under release-scripts instead.
>
> The process ist to sign the app, then package the image, and then you need to sign again.
>
> I would rather enforce signing to be mandatory.
> What we could put into Devtools maybe is the notarize of the installer. Which publishes the release at Apple. I guess. And then we could think about a process to publish in the store.
>>
>> Cool work.
> Yes. I hope this will
>>
>>> On Sep 10, 2026, at 5:14 AM, Jim Jagielski <ji...@jagunet.com> wrote:
>>>
>>> Is there any way you could pull out just the signing bits into a separate commit?
>>>
>>>> On Sep 10, 2026, at 12:26 AM, petko@apache.org wrote:
>>>>
>>>>
>>
>> --
>> Jim
>> "This is an outrage!"
>> Tony Harrison
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org <ma...@openoffice.apache.org>
> For additional commands, e-mail: dev-help@openoffice.apache.org <ma...@openoffice.apache.org>
--
Jim
"This is an outrage!"
Tony Harrison
Re: MacOS signing update and fix the blue button + black text
Posted by Peter Kovacs <pe...@posteo.de>.
Am 10. September 2026 11:30:18 MESZ schrieb Jim Jagielski <ji...@jagunet.com>:
>I am also wondering if the actual signing script itself should be in devtools, somewhere under release-scripts instead.
The process ist to sign the app, then package the image, and then you need to sign again.
I would rather enforce signing to be mandatory.
What we could put into Devtools maybe is the notarize of the installer. Which publishes the release at Apple. I guess. And then we could think about a process to publish in the store.
>
>Cool work.
Yes. I hope this will
>
>> On Sep 10, 2026, at 5:14 AM, Jim Jagielski <ji...@jagunet.com> wrote:
>>
>> Is there any way you could pull out just the signing bits into a separate commit?
>>
>>> On Sep 10, 2026, at 12:26 AM, petko@apache.org wrote:
>>>
>>>
>
>--
>Jim
> "This is an outrage!"
> Tony Harrison
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: MacOS signing update and fix the blue button + black text
Posted by Jim Jagielski <ji...@jagunet.com>.
I am also wondering if the actual signing script itself should be in devtools, somewhere under release-scripts instead.
Cool work.
> On Sep 10, 2026, at 5:14 AM, Jim Jagielski <ji...@jagunet.com> wrote:
>
> Is there any way you could pull out just the signing bits into a separate commit?
>
>> On Sep 10, 2026, at 12:26 AM, petko@apache.org wrote:
>>
>>
--
Jim
"This is an outrage!"
Tony Harrison
Re: MacOS signing update and fix the blue button + black text
Posted by Peter Kovacs <pe...@posteo.de>.
Am 10. September 2026 11:14:47 MESZ schrieb Jim Jagielski <ji...@jagunet.com>:
>Is there any way you could pull out just the signing bits into a separate commit?
I think you need everything except commits that start with vcl or Framework. And the gitignore one as the document one are optional.
I can check tonight.if you want to get a clean branch together.
>
>> On Sep 10, 2026, at 12:26 AM, petko@apache.org wrote:
>>
>>
>
>--
>Jim
> "This is an outrage!"
> Tony Harrison
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: MacOS signing update and fix the blue button + black text
Posted by Jim Jagielski <ji...@jagunet.com>.
Is there any way you could pull out just the signing bits into a separate commit?
> On Sep 10, 2026, at 12:26 AM, petko@apache.org wrote:
>
>
--
Jim
"This is an outrage!"
Tony Harrison