On 12/26/2020 4:19 PM, Marcus wrote:
> The Apache OpenOffice project is happy to have a new committer on board:
>
> Arrigo Marchiori
>
> Please give him a warm welcome. :-)
>
> Marcus
> (on behalf of the Apache OpenOffice PMC)
Welcome and congratulations Arrigio.
Regards
Keith
signature.asc
Hi Arrigo,
Welcome!
I promise we get some more of your PRs merged. ;-)
Regards,
Matthias
Am 26.12.20 um 22:19 schrieb Marcus:
> The Apache OpenOffice project is happy to have a new committer on board:
>
> Arrigo Marchiori
>
> Please give him a warm welcome. :-)
>
> Marcus
> (on behalf of th
Hi Jim,
Am 26.12.20 um 21:59 schrieb Jim Jagielski:
> I have uploaded a test build of en-US AOO419-dev for macOS. I have confirmed
> on my macOS11/BigSur VM that this version opens docx files w/ no problems,
> edits and saves them, etc...
>
> Please test:
>
> http://home.apache.org/~jim/AOO-
The Apache OpenOffice project is happy to have a new committer on board:
Arrigo Marchiori
Please give him a warm welcome. :-)
Marcus
(on behalf of the Apache OpenOffice PMC)
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice
As Jim is bumping the version numbers for a new release.
I know we have a script to increase the version number for a new build /
release. And the 4.1.x releases up to now are a good proof that it works.
However, when looking at the code I think there are too many places (5
different files wi
> -Original Message-
> From: Jörg Schmidt [mailto:joe...@j-m-schmidt.de]
> Sent: Saturday, December 26, 2020 10:05 PM
> To: dev@openoffice.apache.org
> Subject: RE: How should we proceed with BigSur? (was: Does
> AOO 4.1.8 run under macOS Big Sur?)
>
> > -Original Message-
> >
Hi Jim,
Am 26.12.20 um 21:59 schrieb Jim Jagielski:
> I have uploaded a test build of en-US AOO419-dev for macOS. I have confirmed
> on my macOS11/BigSur VM that this version opens docx files w/ no problems,
> edits and saves them, etc...
>
> Please test:
>
> http://home.apache.org/~jim/AOO-
> -Original Message-
> From: Jim Jagielski [mailto:j...@jagunet.com]
> Sent: Saturday, December 26, 2020 3:18 PM
> To: dev
> Subject: Re: How should we proceed with BigSur? (was: Does
> AOO 4.1.8 run under macOS Big Sur?)
>
> It is more than likely that we may need to release a 4.1.9
>
BUGZ seems to be a build issue, not a code one, but it still needs to be fixed
and noted, likely with some autoconf checks that fakeroot exists.
> On Dec 26, 2020, at 3:43 PM, Matthias Seidel
> wrote:
>
> Hi Jim,
>
> Am 26.12.20 um 20:45 schrieb Jim Jagielski:
>> So there is for sure a bug in
I have uploaded a test build of en-US AOO419-dev for macOS. I have confirmed on
my macOS11/BigSur VM that this version opens docx files w/ no problems, edits
and saves them, etc...
Please test:
http://home.apache.org/~jim/AOO-builds/
Cheers!
> On Dec 26, 2020, at 3:54 PM, Rory O'Farrell
On Sat, 26 Dec 2020 21:43:06 +0100
Matthias Seidel wrote:
> Hi Jim,
>
> Am 26.12.20 um 20:45 schrieb Jim Jagielski:
> > So there is for sure a bug in AOO41X, but why it only seems to affect macOS
> > BigSur is
> > unknown. It is this:
> >
> >> diff --git a/main/bridges/source/cpp_uno/shared/vta
Am 26.12.20 um 21:43 schrieb Matthias Seidel:
Am 26.12.20 um 20:45 schrieb Jim Jagielski:
So there is for sure a bug in AOO41X, but why it only seems to affect macOS
BigSur is
unknown. It is this:
diff --git a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
b/main/bridges/source/cpp_uno
Hi Jim,
Am 26.12.20 um 20:45 schrieb Jim Jagielski:
> So there is for sure a bug in AOO41X, but why it only seems to affect macOS
> BigSur is
> unknown. It is this:
>
>> diff --git a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
>> b/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
>>
So there is for sure a bug in AOO41X, but why it only seems to affect macOS
BigSur is
unknown. It is this:
> diff --git a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
> b/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
> index f4d6c56..2ca9b8f 100644
> --- a/main/bridges/source/cpp_
I've confirmed that my 4.2.0 builds work fine on BigSur but
the 4.1.8 builds, even using Xcode10 and the 10.13SDK still
result in core on macOS11. Below you'll find the stack.
My initial thoughts are that it is NOT a build issue, but
rather a code one, so I'll start some investigation with that
mi
For me, the issue is whether it is, indeed, a code problem in 4.1.8 that
requires fixes
and thus a 4.1.9 release, or whether it is a *build* problem, that implies that
building
4.1.8 with a newer SDK will resolve the problem. AFAICT, that question is still
unresolved.
What we DO know is that 4.2
Hi Jim,
Am 26.12.20 um 15:17 schrieb Jim Jagielski:
> It is more than likely that we may need to release a 4.1.9 just to
> accommodate BigSur. However, AOO
> is hardly unique in being an app that no longer works when someone upgrades
> to BigSur. The macOS
> community is replete w/ such apps. I'
It is more than likely that we may need to release a 4.1.9 just to accommodate
BigSur. However, AOO
is hardly unique in being an app that no longer works when someone upgrades to
BigSur. The macOS
community is replete w/ such apps. I'm not using that as an excuse, but that is
what it is.
> On
18 matches
Mail list logo
