https://bugs.documentfoundation.org/show_bug.cgi?id=126409
Telesto changed:
What|Removed |Added
See Also||https://bugs.documentfounda
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
Christian Lohmaier changed:
What|Removed |Added
Resolution|--- |WORKSFORME
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
--- Comment #55 from Tor Lillqvist ---
But the LibreOffice.app one downloads from TDF is still not notarized, is it?
So in what way could this bug be seen as resolved?
Even if it apparently now is still possible, after all, to run
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
--- Comment #54 from MattJ ---
I installed 6.4.4.2 on the same system I had problem with before. This time it
started with the expected warning that the application was downloaded from the
internet. Once I clicked OK on that dialog LO
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
--- Comment #53 from eisa01 ---
(In reply to Christian Lohmaier from comment #50)
> Creation of compiled py files (pyc) is also something that only happens
> after LO was launched. So similar to the languagepack installation it is a
>
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
--- Comment #52 from Tor Lillqvist ---
steve, so are you saying that this bug, that LibreOffice builds should be
notarized, is invalid, as it works for you anyway? Interesting.
--
You are receiving this mail because:
You are the
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
--- Comment #51 from steve -_- ---
Tested LO 6.4.4 on macOS 10.15.4 and all checks were fine.
No problem after re-installing 6.4.4 to open on macOS. The expected dialog to
visit website (from which download was made) or cancle or open
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
--- Comment #50 from Christian Lohmaier ---
(In reply to eisa01 from comment #49)
> Created attachment 161186 [details]
> Failed code sign due to Python framework
Creation of compiled py files (pyc) is also something that only happens
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
--- Comment #49 from eisa01 ---
Created attachment 161186
--> https://bugs.documentfoundation.org/attachment.cgi?id=161186=edit
Failed code sign due to Python framework
The code-signing shows non-clean results on a fresh install (no
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
--- Comment #48 from Christian Lohmaier ---
Created attachment 161165
--> https://bugs.documentfoundation.org/attachment.cgi?id=161165=edit
no problem with notarization on my fresh Catalina...
can anyone actually reproduce the
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
Telesto changed:
What|Removed |Added
See Also||https://bugs.documentfounda
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
--- Comment #47 from Tor Lillqvist ---
I wrote:
> No, I am not volunteering to fix this
But I did not have to volunteer, I am now in the progress of fixing it as part
of my job.
--
You are receiving this mail because:
You are the
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
--- Comment #46 from eisa01 ---
I really don't know anything about this at all, but saw a reference to a helper
app for notarizing that may help solve this?
https://github.com/akeru-inc/xcnotary
>From this comment chain:
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
--- Comment #45 from Tor Lillqvist ---
I see Python mentioned. If the problem is that Python writes bytecode files
into the app bundle, would 4e124fd1409af419990bacade74fcf355624243f help? Are
the notarized builds configured with
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
--- Comment #44 from Tor Lillqvist ---
> Langpack installer installs additional files to the app directory
That is and has always been a HORRIBLE idea. The intent has always been, I
assume, that an app bundle should be read-only, even
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
eisa01 changed:
What|Removed |Added
See Also||https://bugs.documentfounda
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
eisa01 changed:
What|Removed |Added
See Also||https://bugs.documentfounda
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
eisa01 changed:
What|Removed |Added
Blocks||128233
Referenced Bugs:
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
--- Comment #43 from mimaj...@163.com ---
The same issue still reproducible on Libreoffice 6.4.2.2:
$ cat LibreOffice.app/Contents/Info.plist | grep -i "LibreOffice 6"
LibreOffice 6.4.2.2
$ /Applications stapler validate LibreOffice.app
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
Julien Nabet changed:
What|Removed |Added
Severity|major |critical
Priority|high
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
--- Comment #41 from eisa01 ---
The Python issue is definitely holding up the notarization, this was not an
issue in comment #24, so we've actually regressed on achieving a proper
notarization :)
Use the vvv flag to perform a
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
--- Comment #40 from eisa01 ---
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:
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
--- Comment #39 from mimaj...@163.com ---
So what is the plan for this bug now? Is there a plan to fix it or do we have
to go and get LibreOffice Vanilla from the Mac AppStore:
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
steve -_- changed:
What|Removed |Added
Version|6.3.1.2 release |Inherited From OOo
--
You are
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
steve -_- changed:
What|Removed |Added
URL||https://developer.apple.com
https://bugs.documentfoundation.org/show_bug.cgi?id=126409
steve -_- changed:
What|Removed |Added
Summary|LibreOffice does not launch |Notarize LibreOffice builds
26 matches
Mail list logo
