AOO 4.1.6-RC1 m1 r1844555

classic Classic list List threaded Threaded
30 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.6-RC1 m1 r1844555

Jim Jagielski
Isn't the main issue whether these are blockers or not?

> On Oct 26, 2018, at 3:39 PM, Don Lewis <[hidden email]> wrote:
>
> On 26 Oct, Jim Jagielski wrote:
>>
>>
>>> On Oct 26, 2018, at 2:30 PM, Don Lewis <[hidden email]> wrote:
>>>
>>> The redland/raptor/rasqal upgrade
>>> https://bz.apache.org/ooo/show_bug.cgi?id=127887 got backed out.
>>> Someone with a Mac needs to see if the configure.in 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 https://svn.apache.org/viewvc?view=revision&revision=1805089
> to unbreak things on the Mac, which include some changes to
> configure.ac.  AOO416 has configure.in instead of configure.ac, so in my
> instructions for merging this upgrade back to AOO416 here:
> https://bz.apache.org/ooo/show_bug.cgi?id=127887 I said to hand apply
> the configure.ac changes to configure.in.  That broke the buildbot
> builds at the configure stage due to shell syntax errors:
> https://ci.apache.org/builders/openoffice-linux64-41x/builds/159/steps/configure/logs/stdio
> 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 configure.in to get a
> successful build.  My testing without any configure.in changes worked on
> Linux and Windows.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.6-RC1 m1 r1844555

Don Lewis-2
raptor 1.4.18 has CVE-2012-0037, otherwise I would not have bothered
with the upgrade.

On 26 Oct, Jim Jagielski wrote:

> Isn't the main issue whether these are blockers or not?
>
>> On Oct 26, 2018, at 3:39 PM, Don Lewis <[hidden email]> wrote:
>>
>> On 26 Oct, Jim Jagielski wrote:
>>>
>>>
>>>> On Oct 26, 2018, at 2:30 PM, Don Lewis <[hidden email]> wrote:
>>>>
>>>> The redland/raptor/rasqal upgrade
>>>> https://bz.apache.org/ooo/show_bug.cgi?id=127887 got backed out.
>>>> Someone with a Mac needs to see if the configure.in 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 https://svn.apache.org/viewvc?view=revision&revision=1805089
>> to unbreak things on the Mac, which include some changes to
>> configure.ac.  AOO416 has configure.in instead of configure.ac, so in my
>> instructions for merging this upgrade back to AOO416 here:
>> https://bz.apache.org/ooo/show_bug.cgi?id=127887 I said to hand apply
>> the configure.ac changes to configure.in.  That broke the buildbot
>> builds at the configure stage due to shell syntax errors:
>> https://ci.apache.org/builders/openoffice-linux64-41x/builds/159/steps/configure/logs/stdio
>> 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 configure.in to get a
>> successful build.  My testing without any configure.in changes worked on
>> Linux and Windows.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.6-RC1 m1 r1844555

Peter Kovacs-3
Well it is a bummer we can not fix it with 4.1.6. However this one is 6 year old. It can wait a view month. It is not worth to backport if the same effort can bring 4.2.0 to live.

Am 26. Oktober 2018 22:04:54 MESZ schrieb Don Lewis <[hidden email]>:

>raptor 1.4.18 has CVE-2012-0037, otherwise I would not have bothered
>with the upgrade.
>
>On 26 Oct, Jim Jagielski wrote:
>> Isn't the main issue whether these are blockers or not?
>>
>>> On Oct 26, 2018, at 3:39 PM, Don Lewis <[hidden email]> wrote:
>>>
>>> On 26 Oct, Jim Jagielski wrote:
>>>>
>>>>
>>>>> On Oct 26, 2018, at 2:30 PM, Don Lewis <[hidden email]>
>wrote:
>>>>>
>>>>> The redland/raptor/rasqal upgrade
>>>>> https://bz.apache.org/ooo/show_bug.cgi?id=127887 got backed out.
>>>>> Someone with a Mac needs to see if the configure.in 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
>https://svn.apache.org/viewvc?view=revision&revision=1805089
>>> to unbreak things on the Mac, which include some changes to
>>> configure.ac.  AOO416 has configure.in instead of configure.ac, so
>in my
>>> instructions for merging this upgrade back to AOO416 here:
>>> https://bz.apache.org/ooo/show_bug.cgi?id=127887 I said to hand
>apply
>>> the configure.ac changes to configure.in.  That broke the buildbot
>>> builds at the configure stage due to shell syntax errors:
>>>
>https://ci.apache.org/builders/openoffice-linux64-41x/builds/159/steps/configure/logs/stdio
>>> 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 configure.in to get a
>>> successful build.  My testing without any configure.in changes
>worked on
>>> Linux and Windows.
>>>
>>>
>>>
>---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [hidden email]
>For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.6-RC1 m1 r1844555

Matthias Seidel
In reply to this post by Don Lewis-2
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 <[hidden email]> wrote:
>>>
>>> The redland/raptor/rasqal upgrade
>>> https://bz.apache.org/ooo/show_bug.cgi?id=127887 got backed out.
>>> Someone with a Mac needs to see if the configure.in 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 https://svn.apache.org/viewvc?view=revision&revision=1805089
> to unbreak things on the Mac, which include some changes to
> configure.ac.  AOO416 has configure.in instead of configure.ac, so in my
> instructions for merging this upgrade back to AOO416 here:
> https://bz.apache.org/ooo/show_bug.cgi?id=127887 I said to hand apply
> the configure.ac changes to configure.in.  That broke the buildbot
> builds at the configure stage due to shell syntax errors:
> https://ci.apache.org/builders/openoffice-linux64-41x/builds/159/steps/configure/logs/stdio
> 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 configure.in to get a
> successful build.  My testing without any configure.in changes worked on
> Linux and Windows.
I am building for Windows at the moment (omitting the changes in
configure.in).

No problems so far...

>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.6-RC1 m1 r1844555

Don Lewis-2
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 <[hidden email]> wrote:
>>>>
>>>> The redland/raptor/rasqal upgrade
>>>> https://bz.apache.org/ooo/show_bug.cgi?id=127887 got backed out.
>>>> Someone with a Mac needs to see if the configure.in 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 https://svn.apache.org/viewvc?view=revision&revision=1805089
>> to unbreak things on the Mac, which include some changes to
>> configure.ac.  AOO416 has configure.in instead of configure.ac, so in my
>> instructions for merging this upgrade back to AOO416 here:
>> https://bz.apache.org/ooo/show_bug.cgi?id=127887 I said to hand apply
>> the configure.ac changes to configure.in.  That broke the buildbot
>> builds at the configure stage due to shell syntax errors:
>> https://ci.apache.org/builders/openoffice-linux64-41x/builds/159/steps/configure/logs/stdio
>> 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 configure.in to get a
>> successful build.  My testing without any configure.in changes worked on
>> Linux and Windows.
>
> I am building for Windows at the moment (omitting the changes in
> configure.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.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.6-RC1 m1 r1844555

Matthias Seidel
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 <[hidden email]> wrote:
>>>>>
>>>>> The redland/raptor/rasqal upgrade
>>>>> https://bz.apache.org/ooo/show_bug.cgi?id=127887 got backed out.
>>>>> Someone with a Mac needs to see if the configure.in 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 https://svn.apache.org/viewvc?view=revision&revision=1805089
>>> to unbreak things on the Mac, which include some changes to
>>> configure.ac.  AOO416 has configure.in instead of configure.ac, so in my
>>> instructions for merging this upgrade back to AOO416 here:
>>> https://bz.apache.org/ooo/show_bug.cgi?id=127887 I said to hand apply
>>> the configure.ac changes to configure.in.  That broke the buildbot
>>> builds at the configure stage due to shell syntax errors:
>>> https://ci.apache.org/builders/openoffice-linux64-41x/builds/159/steps/configure/logs/stdio
>>> 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 configure.in to get a
>>> successful build.  My testing without any configure.in changes worked on
>>> Linux and Windows.
>> I am building for Windows at the moment (omitting the changes in
>> configure.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.

Regards,

   Matthias

>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.6-RC1 m1 r1844555

Don Lewis-2
In reply to this post by Don Lewis-2
On 26 Oct, Don Lewis wrote:

> In addition the bundled version of nss has a bunch of CVEs.  Even the
> version in trunk has two I believe.  I spent most of a week trying to
> upgrade the trunk version and got a successful build on Windows, but
> haven't had time to test it, and my patches need further cleanup.  The
> big problems is that newer versions are C99 which the version of Visual
> C++ that we use for the Windows build does not support.  I also remember
> the pain that we went through to get this working properly when we did
> the previous trunk upgrade.  It is used for document signing.

nss-3.14.4 (in 4.1.5):
  CVE-2014-1561
  CVE-2014-1560
  CVE-2014-1559
  CVE-2014-1558
  CVE-2014-1557
  CVE-2014-1556
  CVE-2014-1555
  CVE-2014-1552
  CVE-2014-1551
  CVE-2014-1550
  CVE-2014-1549
  CVE-2014-1548
  CVE-2014-1547
  CVE-2014-1544

nss-3.25 (in trunk):
  CVE-2017-5462
  CVE-2017-5461

Upgrading to 3.25 looks like it would require merging r1753163,
r1753962, maybe r1799750, r1811598, and r1811604.  The latter two are Mac
fixes.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.6-RC1 m1 r1844555

Don Lewis-2
In reply to this post by Matthias Seidel
On 27 Oct, Matthias Seidel wrote:

> 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 <[hidden email]> wrote:
>>>>>>
>>>>>> The redland/raptor/rasqal upgrade
>>>>>> https://bz.apache.org/ooo/show_bug.cgi?id=127887 got backed out.
>>>>>> Someone with a Mac needs to see if the configure.in 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 https://svn.apache.org/viewvc?view=revision&revision=1805089
>>>> to unbreak things on the Mac, which include some changes to
>>>> configure.ac.  AOO416 has configure.in instead of configure.ac, so in my
>>>> instructions for merging this upgrade back to AOO416 here:
>>>> https://bz.apache.org/ooo/show_bug.cgi?id=127887 I said to hand apply
>>>> the configure.ac changes to configure.in.  That broke the buildbot
>>>> builds at the configure stage due to shell syntax errors:
>>>> https://ci.apache.org/builders/openoffice-linux64-41x/builds/159/steps/configure/logs/stdio
>>>> 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 configure.in to get a
>>>> successful build.  My testing without any configure.in changes worked on
>>>> Linux and Windows.
>>> I am building for Windows at the moment (omitting the changes in
>>> configure.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.

I think it was the step where the configure.ac changes for the Mac were
manually applied to configure.in.  It is unclear whether they are
actually required for the Mac or if they need to be reworked for
configure.in.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.6-RC1 m1 r1844555

Peter Kovacs-3
Yes I applied them manually. And I took only changes from the version that I thought the change is about.

Am 27. Oktober 2018 00:22:55 MESZ schrieb Don Lewis <[hidden email]>:

>On 27 Oct, Matthias Seidel wrote:
>> 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 <[hidden email]>
>wrote:
>>>>>>>
>>>>>>> The redland/raptor/rasqal upgrade
>>>>>>> https://bz.apache.org/ooo/show_bug.cgi?id=127887 got backed out.
>>>>>>> Someone with a Mac needs to see if the configure.in 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
>https://svn.apache.org/viewvc?view=revision&revision=1805089
>>>>> to unbreak things on the Mac, which include some changes to
>>>>> configure.ac.  AOO416 has configure.in instead of configure.ac, so
>in my
>>>>> instructions for merging this upgrade back to AOO416 here:
>>>>> https://bz.apache.org/ooo/show_bug.cgi?id=127887 I said to hand
>apply
>>>>> the configure.ac changes to configure.in.  That broke the buildbot
>>>>> builds at the configure stage due to shell syntax errors:
>>>>>
>https://ci.apache.org/builders/openoffice-linux64-41x/builds/159/steps/configure/logs/stdio
>>>>> 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 configure.in to get
>a
>>>>> successful build.  My testing without any configure.in changes
>worked on
>>>>> Linux and Windows.
>>>> I am building for Windows at the moment (omitting the changes in
>>>> configure.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.
>
>I think it was the step where the configure.ac changes for the Mac were
>manually applied to configure.in.  It is unclear whether they are
>actually required for the Mac or if they need to be reworked for
>configure.in.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [hidden email]
>For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.6-RC1 m1 r1844555

Matthias Seidel
In reply to this post by Matthias Seidel
Am 23.10.18 um 13:24 schrieb Matthias Seidel:

> Hi Peter,
>
> Am 23.10.18 um 13:19 schrieb Peter kovacs:
>> Important is we build with the same revision.
>> Are all builds now with r1844436?
> Revision 1844436 confirmed for Windows.
>
>> Great if I do not have to sign anything. I gladly delegate that to the builders. ;-)
> The release manager builds the source build (after the final release)
> and signs it...
> So you have some time left... ;-)
I stand corrected, the source build has to be done with every Release
Candidate... ;-)

Matthias

>
> Matthias
>
>>
>> Am 23. Oktober 2018 13:12:37 MESZ schrieb Matthias Seidel <[hidden email]>:
>>> Am 23.10.18 um 13:06 schrieb Jim Jagielski:
>>>> r1844555 was the SVN version of HEAD at the time of the email.
>>> Yes, and it increases by the time of writing...
>>> So it gives no information about what revision the RC should be build
>>> upon?
>>>
>>>> FWIW, my macOS builds of RC1 are ready... CentOS5-64 are in progress.
>>> My build is also running (r1844436), just in case. ;-)
>>>
>>> Regards,
>>>
>>> Matthias
>>>
>>>>> On Oct 23, 2018, at 6:03 AM, Matthias Seidel
>>> <[hidden email]> wrote:
>>>>> Hi Peter,
>>>>>
>>>>> Am 23.10.18 um 05:03 schrieb Peter Kovacs:
>>>>>> I am a bit confused where we all are now. I think all Issues are
>>>>>> resolved and currently we are not aware on regressions right?
>>>>>>
>>>>>> If r1844555 has not been build yet, then please start. :) I would
>>> like
>>>>>> to do some signing.
>>>>> Now I am a bit confused. The last commit in 4.1.6 was r1844436:
>>>>> https://svn.apache.org/viewvc?view=revision&revision=1844436
>>>>>
>>>>> I can start a new build, will this be a RC?
>>>>>
>>>>> And builds are signed by those who do the builds. ;-)
>>>>>
>>>>> Matthias
>>>>>
>>>>>> Thank you all for your efforts!
>>>>>>
>>>>>> On 22.10.18 15:12, Jim Jagielski wrote:
>>>>>>> I am ready to start building macOS and Linux 64&32bit builds of
>>> HEAD of AOO416, which is m1 at r1844555
>>>>>>> Just say the word :)
>>>>>>>
>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: [hidden email]
>>>>>>> For additional commands, e-mail: [hidden email]
>>>>>>>
>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: [hidden email]
>>>>>> For additional commands, e-mail: [hidden email]
>>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>


smime.p7s (5K) Download Attachment
12