++1
> On Oct 6, 2020, at 12:33 PM, Don Lewis wrote:
>
> On 6 Oct, Jim Jagielski wrote:
>> Thanks! Since these are relatively new, I think that this can hold for 4.1.9
>
> I'd at least like to get the nss update into trunk/AOO42X where it can
> soak for a while.
>
>>> On Oct 6, 2020, at 12:19
On 6 Oct, Jim Jagielski wrote:
> Thanks! Since these are relatively new, I think that this can hold for 4.1.9
I'd at least like to get the nss update into trunk/AOO42X where it can
soak for a while.
>> On Oct 6, 2020, at 12:19 PM, Don Lewis wrote:
>>
>> On 6 Oct, Jim Jagielski wrote:
>>> OK..
Thanks! Since these are relatively new, I think that this can hold for 4.1.9
> On Oct 6, 2020, at 12:19 PM, Don Lewis wrote:
>
> On 6 Oct, Jim Jagielski wrote:
>> OK... as expected, it fails on macOS.
>>
>> 2 things I see: in the nss.patch file there is a line:
>>
>>Only in misc/build/nss
On 6 Oct, Jim Jagielski wrote:
> OK... as expected, it fails on macOS.
>
> 2 things I see: in the nss.patch file there is a line:
>
> Only in misc/build/nss-3.39/nss/coreconf: Darwin.mk.rej
>
> So I'm wondering if the patch file itself or maybe even the whole pull
> request is borked.
>
>
OK... as expected, it fails on macOS.
2 things I see: in the nss.patch file there is a line:
Only in misc/build/nss-3.39/nss/coreconf: Darwin.mk.rej
So I'm wondering if the patch file itself or maybe even the whole pull request
is borked.
Also, we need to force 'g++' on the macOS build to
I am booting up the macOS VM for the 4.1.8-dev builds as we speak. Will update
to head and pull in nss
> On Oct 5, 2020, at 4:00 PM, Don Lewis wrote:
>
> Any progress on nss?
>
> On 30 Sep, Jim Jagielski wrote:
>> I'll see how the build on macOS goes, but likely won't be able to get to it
>>
Any progress on nss?
On 30 Sep, Jim Jagielski wrote:
> I'll see how the build on macOS goes, but likely won't be able to get to it
> until Monday.
>
>> On Sep 29, 2020, at 2:52 PM, Don Lewis wrote:
>>
>> On 29 Sep, Matthias Seidel wrote:
>>> Hi Don,
>>>
>>> Am 26.09.20 um 23:47 schrieb Don Le
I've got everything on my list for AOO418 in the queue:
* Fix for old java detection when building with new java
Set java compilation target to version 1.5 #101
https://github.com/apache/openoffice/pull/101
* Bug fixes from upstream for bundled libxml2 and serf modules
Libxml+serf
I'll see how the build on macOS goes, but likely won't be able to get to it
until Monday.
> On Sep 29, 2020, at 2:52 PM, Don Lewis wrote:
>
> On 29 Sep, Matthias Seidel wrote:
>> Hi Don,
>>
>> Am 26.09.20 um 23:47 schrieb Don Lewis:
>>> On 26 Sep, Matthias Seidel wrote:
Hi all,
On 29 Sep, Matthias Seidel wrote:
> Hi Don,
>
> Am 26.09.20 um 23:47 schrieb Don Lewis:
>> On 26 Sep, Matthias Seidel wrote:
>>> Hi all,
>>>
>>> Am 25.09.20 um 18:05 schrieb Matthias Seidel:
Am 25.09.20 um 14:01 schrieb Jim Jagielski:
> That looks quite a bit more straightforward :-)
Hi Don,
Am 26.09.20 um 23:47 schrieb Don Lewis:
> On 26 Sep, Matthias Seidel wrote:
>> Hi all,
>>
>> Am 25.09.20 um 18:05 schrieb Matthias Seidel:
>>> Am 25.09.20 um 14:01 schrieb Jim Jagielski:
That looks quite a bit more straightforward :-)
>>> Let's wait for Don's PR, this is only a minor
On 26 Sep, Matthias Seidel wrote:
> Hi all,
>
> Am 25.09.20 um 18:05 schrieb Matthias Seidel:
>> Am 25.09.20 um 14:01 schrieb Jim Jagielski:
>>> That looks quite a bit more straightforward :-)
>> Let's wait for Don's PR, this is only a minor update from Python 2.7.17
>> to 2.7.18.
>
> Merged now.
+1
> On Sep 26, 2020, at 2:53 PM, Matthias Seidel
> wrote:
>
> Hi all,
>
> Am 25.09.20 um 18:05 schrieb Matthias Seidel:
>> Am 25.09.20 um 14:01 schrieb Jim Jagielski:
>>> That looks quite a bit more straightforward :-)
>> Let's wait for Don's PR, this is only a minor update from Python 2.7.17
Hi all,
Am 25.09.20 um 18:05 schrieb Matthias Seidel:
> Am 25.09.20 um 14:01 schrieb Jim Jagielski:
>> That looks quite a bit more straightforward :-)
> Let's wait for Don's PR, this is only a minor update from Python 2.7.17
> to 2.7.18.
Merged now...
Unless Don wants to add something for the Ja
Am 25.09.20 um 14:01 schrieb Jim Jagielski:
> That looks quite a bit more straightforward :-)
Let's wait for Don's PR, this is only a minor update from Python 2.7.17
to 2.7.18.
>
>> On Sep 24, 2020, at 3:59 PM, Matthias Seidel
>> wrote:
>>
>> Great!
>>
>> We should also cherry-pick Don's Python u
That looks quite a bit more straightforward :-)
> On Sep 24, 2020, at 3:59 PM, Matthias Seidel
> wrote:
>
> Great!
>
> We should also cherry-pick Don's Python update:
>
> https://github.com/apache/openoffice/commit/26aca12f509e5c739c98db9ce5641a2c5feecea7
>
> And update LICENSE:
>
> https:/
On 24 Sep, Matthias Seidel wrote:
> Great!
>
> We should also cherry-pick Don's Python update:
>
> https://github.com/apache/openoffice/commit/26aca12f509e5c739c98db9ce5641a2c5feecea7
>
> And update LICENSE:
>
> https://github.com/apache/openoffice/commit/1dedf1ecff4aeffe2f7c7612cbf893530465764
Great!
We should also cherry-pick Don's Python update:
https://github.com/apache/openoffice/commit/26aca12f509e5c739c98db9ce5641a2c5feecea7
And update LICENSE:
https://github.com/apache/openoffice/commit/1dedf1ecff4aeffe2f7c7612cbf893530465764e
Regards,
Matthias
Am 24.09.20 um 21:31 schr
On 24 Sep, Jim Jagielski wrote:
> Well, gotten further but now there are packaging issues. Something with the
> new apr/apr-util/serf stuff is getting hosed... looking into it:
>
> ERROR: The following files could not be found:
> ERROR: File not found: libapr-1.0.5.2.dylib
> ERROR: File not foun
Thinking it's due to some changes not cherry picked from scp2 in AOO42X...
rebuilding
> On Sep 24, 2020, at 3:13 PM, Jim Jagielski wrote:
>
> Well, gotten further but now there are packaging issues. Something with the
> new apr/apr-util/serf stuff is getting hosed... looking into it:
>
> ERRO
Well, gotten further but now there are packaging issues. Something with the new
apr/apr-util/serf stuff is getting hosed... looking into it:
ERROR: The following files could not be found:
ERROR: File not found: libapr-1.0.5.2.dylib
ERROR: File not found: libaprutil-1.0.5.4.dylib
ERROR: File not
I have some ideas... with some changes to the proposed patch I have macOS
building further along than before... fingers crossed.
> On Sep 24, 2020, at 12:35 PM, Matthias Seidel
> wrote:
>
> Hi Don, Jim,
>
> Am 22.09.20 um 22:54 schrieb Don Lewis:
>> On 22 Sep, Jim Jagielski wrote:
>>> Just a
Hi Don, Jim,
Am 22.09.20 um 22:54 schrieb Don Lewis:
> On 22 Sep, Jim Jagielski wrote:
>> Just a FYI that HEAD of AOO418 builds on macOS with no issues so far...
> https://github.com/apache/openoffice/pull/94 has some macOS-specific
> changes from AOO42X.
If these changes have too much impact on
On 22 Sep, Jim Jagielski wrote:
> Just a FYI that HEAD of AOO418 builds on macOS with no issues so far...
https://github.com/apache/openoffice/pull/94 has some macOS-specific
changes from AOO42X.
-
To unsubscribe, e-mail: dev-
Just a FYI that HEAD of AOO418 builds on macOS with no issues so far...
> On Sep 19, 2020, at 5:43 AM, Matthias Seidel
> wrote:
>
> Hi Jim,
>
> Am 15.09.20 um 13:00 schrieb Jim Jagielski:
>> Hmmm... we still support 10.7 as the lowest macOS version on both truck and
>> AOO420 so somewhere, so
Hi Jim,
Am 15.09.20 um 13:00 schrieb Jim Jagielski:
> Hmmm... we still support 10.7 as the lowest macOS version on both truck and
> AOO420 so somewhere, somehow, that got reverted. So let's go ahead and pull
> those Issues into AOO418.
It got reverted here (and in some other commits):
https://g
Hmmm... we still support 10.7 as the lowest macOS version on both truck and
AOO420 so somewhere, somehow, that got reverted. So let's go ahead and pull
those Issues into AOO418.
> On Sep 8, 2020, at 2:30 PM, Matthias Seidel
> wrote:
>
> Hi Jim,
>
> Am 08.09.20 um 19:53 schrieb Jim Jagielski:
Hi Jim,
Am 08.09.20 um 19:53 schrieb Jim Jagielski:
> Are these in trunk, or 4.2.x?
I think so:
https://bz.apache.org/ooo/show_bug.cgi?id=127887#c0
Especially this one from you ;-)
https://svn.apache.org/viewvc?view=revision&revision=1805089
Regards,
Matthias
>
>> On Sep 7, 2020, at 10:3
Are these in trunk, or 4.2.x?
> On Sep 7, 2020, at 10:31 AM, Matthias Seidel
> wrote:
>
> Hi Jim,
>
> Am 07.09.20 um 15:14 schrieb Jim Jagielski:
>> For 4.1.x we have always supported 10.7 as the min macOS version. Changing
>> supported versions via a patch release does not seem right. IMO, w
Hi Jim,
Am 07.09.20 um 15:14 schrieb Jim Jagielski:
> For 4.1.x we have always supported 10.7 as the min macOS version. Changing
> supported versions via a patch release does not seem right. IMO, we pull the
> rug out from under people when bumping patch revs.
That's one of the reasons why it w
For 4.1.x we have always supported 10.7 as the min macOS version. Changing
supported versions via a patch release does not seem right. IMO, we pull the
rug out from under people when bumping patch revs.
> On Sep 4, 2020, at 9:18 AM, Matthias Seidel
> wrote:
>
> Hi Jim, Don,
>
> Am 28.08.20 u
Am 04.09.20 um 18:45 schrieb Don Lewis:
> On 4 Sep, Matthias Seidel wrote:
>> Hi Jim, Don,
>>
>> Am 28.08.20 um 15:17 schrieb Jim Jagielski:
>>> Let's commit and work after pushed.
>> We should try
>>
>> https://bz.apache.org/ooo/show_bug.cgi?id=127887
>>
>> again for 4.1.8.
> I've included it in
On 4 Sep, Matthias Seidel wrote:
> Hi Jim, Don,
>
> Am 28.08.20 um 15:17 schrieb Jim Jagielski:
>> Let's commit and work after pushed.
>
> We should try
>
> https://bz.apache.org/ooo/show_bug.cgi?id=127887
>
> again for 4.1.8.
I've included it in a large bundle of cherry-picks that I've been
Hi Jim, Don,
Am 28.08.20 um 15:17 schrieb Jim Jagielski:
> Let's commit and work after pushed.
We should try
https://bz.apache.org/ooo/show_bug.cgi?id=127887
again for 4.1.8.
Regards,
Matthias
>
>> On Aug 27, 2020, at 2:02 PM, Don Lewis wrote:
>>
>> On 27 Aug, Matthias Seidel wrote:
>>>
Let's commit and work after pushed.
> On Aug 27, 2020, at 2:02 PM, Don Lewis wrote:
>
> On 27 Aug, Matthias Seidel wrote:
>> Am 27.08.20 um 19:32 schrieb Matthias Seidel:
>>>
>>> Hi Don,
>>>
>>> Am 24.08.20 um 04:04 schrieb Don Lewis:
I've got a bunch of cherry picks that I'm planning to
Hi Don,
Am 27.08.20 um 20:02 schrieb Don Lewis:
> On 27 Aug, Matthias Seidel wrote:
>> Am 27.08.20 um 19:32 schrieb Matthias Seidel:
>>> Hi Don,
>>>
>>> Am 24.08.20 um 04:04 schrieb Don Lewis:
I've got a bunch of cherry picks that I'm planning to merge into AOO418.
There are two categori
On 27 Aug, Matthias Seidel wrote:
> Am 27.08.20 um 19:32 schrieb Matthias Seidel:
>>
>> Hi Don,
>>
>> Am 24.08.20 um 04:04 schrieb Don Lewis:
>>> I've got a bunch of cherry picks that I'm planning to merge into AOO418.
>>> There are two categories:
>>> * Fixes from the FreeBSD port that have been
Am 27.08.20 um 19:32 schrieb Matthias Seidel:
>
> Hi Don,
>
> Am 24.08.20 um 04:04 schrieb Don Lewis:
>> I've got a bunch of cherry picks that I'm planning to merge into AOO418.
>> There are two categories:
>> * Fixes from the FreeBSD port that have been upstreamed to the trunk
>> and AOO42X
Hi Don,
Am 24.08.20 um 04:04 schrieb Don Lewis:
> I've got a bunch of cherry picks that I'm planning to merge into AOO418.
> There are two categories:
> * Fixes from the FreeBSD port that have been upstreamed to the trunk
> and AOO42X branches, but I'm still carrying around in the FreeBSD
>
Hi Don,
Am 24.08.20 um 04:04 schrieb Don Lewis:
> I've got a bunch of cherry picks that I'm planning to merge into AOO418.
> There are two categories:
> * Fixes from the FreeBSD port that have been upstreamed to the trunk
> and AOO42X branches, but I'm still carrying around in the FreeBSD
>
On 24 Aug, Pedro Lino wrote:
> Hi Don, all
>
> I'm still trying to compile 418 on Ubuntu 18.04 x64
> I updated the 418 code but I get stuck at module graphite with the following
> error (log file at https://etherpad.wikimedia.org/p/config.log)
>
> Any ideas?
The error is happening during the co
Hi Don, all
I'm still trying to compile 418 on Ubuntu 18.04 x64
I updated the 418 code but I get stuck at module graphite with the following
error (log file at https://etherpad.wikimedia.org/p/config.log)
Any ideas?
Thanks!
configure: error: C compiler cannot create executables
See `config.log
42 matches
Mail list logo
