Re: Does AOO 4.1.8 run under macOS Big Sur?

2020-11-26 Thread Bidouille
We have confirmation on french forum that AOO 4.1.8 can not open OOXML documents 3 users confirms this crash when opening DOCX, XLSX and PPTX with Big Sur. - Mail original - > De: "Bidouille" > À: dev@openoffice.apache.org > Envoyé: Vendredi 20 Novembre 2020 16:12:26 > Objet: Re: Does AO

Re: Does AOO 4.1.8 run under macOS Big Sur?

2020-11-26 Thread Matthias Seidel
Hi, Am 26.11.20 um 11:56 schrieb Bidouille: > We have confirmation on french forum that AOO 4.1.8 can not open OOXML > documents > 3 users confirms this crash when opening DOCX, XLSX and PPTX with Big Sur. Do we have a test document? Regards,    Matthias > > > - Mail original - >> De:

Re: Does AOO 4.1.8 run under macOS Big Sur?

2020-11-26 Thread Bidouille
Hello Mathias, I ask it to OP and wait. Once provided, I will open a report on Bugzilla - Mail original - > De: "Matthias Seidel" > À: dev@openoffice.apache.org > Envoyé: Jeudi 26 Novembre 2020 12:10:59 > Objet: Re: Does AOO 4.1.8 run under macOS Big Sur? > > Hi, > > Am 26.11.20 um 11:

Re: Does AOO 4.1.8 run under macOS Big Sur?

2020-11-26 Thread Matthias Seidel
Hi, Am 26.11.20 um 15:49 schrieb Bidouille: > Hello Mathias, > > I ask it to OP and wait. > Once provided, I will open a report on Bugzilla Thanks! I think we have "macOS 11.0" now in Bugzilla. I assume this is not reproducible with older macOS? Regards,    Matthias > > - Mail original --

Re: New EPM Maintainer... me!

2020-11-26 Thread Jim Jagielski
Yeah, all that is because of the weird way GitHub names "releases"... We hit the same thing w/ EPM as you may recall. With DMAKE 4.13.0, all that will be fixed. > On Nov 25, 2020, at 4:40 PM, Matthias Seidel > wrote: > > Hi Jim, > > With dmake-4.12.3 I have following problem when trying to b

Re: New EPM Maintainer... me!

2020-11-26 Thread Matthias Seidel
Hi Jim, Am 26.11.20 um 17:35 schrieb Jim Jagielski: > Yeah, all that is because of the weird way GitHub names "releases"... We hit > the same thing w/ EPM as you may recall. With DMAKE 4.13.0, all that will be > fixed. Thanks! I solved it for the moment by renaming the directory inside the .ta