openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthias Seidel <>
Subject Re: AOO 4.1.6-RC1 m1 r1844555
Date Fri, 26 Oct 2018 22:15:25 GMT
Am 27.10.18 um 00:10 schrieb Don Lewis:
> On 27 Oct, Matthias Seidel wrote:
>> Am 26.10.18 um 21:39 schrieb Don Lewis:
>>> On 26 Oct, Jim Jagielski wrote:
>>>>> On Oct 26, 2018, at 2:30 PM, Don Lewis <> wrote:
>>>>> The redland/raptor/rasqal upgrade
>>>>> got backed out.
>>>>> Someone with a Mac needs to see if the changes are needed
>>>>> or if it builds on a Mac as-is.
>>> When we upgraded those in trunk, it broke the Mac build.  You committed
>>> this change
>>> to unbreak things on the Mac, which include some changes to
>>>  AOO416 has instead of, so in my
>>> instructions for merging this upgrade back to AOO416 here:
>>> I said to hand apply
>>> the changes to  That broke the buildbot
>>> builds at the configure stage due to shell syntax errors:
>>> so the entire upgrade was backed out of AOO416 with r1843571.
>>> The question is whether we can merge the four commits from trunk to
>>> AOO416 and skip the configure changes and get a successful build on the
>>> Mac, or do we need to do some other change to to get a
>>> successful build.  My testing without any changes worked on
>>> Linux and Windows.
>> I am building for Windows at the moment (omitting the changes in
>> No problems so far...
> As I previously mentioned, I built and tested that on both Windows and
> Linux, specifically CentOS 6.  I didn't test CentOS 5 since my VM broke
> and it's difficult to set up a new CentOS 5 VM since that release has
> been archived.

So macOS remains to be tested...

I am not sure now what caused the buildbots to break, but they all
stopped early in configure.



> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

View raw message