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
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 :
>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
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 wrote:
>>
>> The redland/raptor/rasqal upgrade
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
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
>
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
https://bz.apache.org/ooo/show_bug.cgi?id=127887 got backed out.
Someone with
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
>>> https://bz.apache.org/ooo/show_bug.cgi?id=127887 got backed out.
>>> Someone with a Mac needs to see if the configure.in
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 :
>raptor 1.4.18 has CVE-2012-0037, otherwise I would not have
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 wrote:
>>
>> On 26 Oct, Jim Jagielski wrote:
>>>
>>>
On Oct 26,
Isn't the main issue whether these are blockers or not?
> On Oct 26, 2018, at 3:39 PM, Don Lewis wrote:
>
> On 26 Oct, Jim Jagielski wrote:
>>
>>
>>> On Oct 26, 2018, at 2:30 PM, Don Lewis wrote:
>>>
>>> The redland/raptor/rasqal upgrade
>>> https://bz.apache.org/ooo/show_bug.cgi?id=127887
On 26 Oct, Jim Jagielski wrote:
>
>
>> On Oct 26, 2018, at 2:30 PM, Don Lewis 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
> On Oct 26, 2018, at 2:30 PM, Don Lewis 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.
I have no idea how to parse the
On 26 Oct, Matthias Seidel wrote:
> Hi Don,
>
> Am 26.10.18 um 20:30 schrieb Don Lewis:
>> On 23 Oct, Peter Kovacs wrote:
>>> 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?
>> The redland/raptor/rasqal upgrade
>>
Hi Don,
Am 26.10.18 um 20:30 schrieb Don Lewis:
> On 23 Oct, Peter Kovacs wrote:
>> 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?
> The redland/raptor/rasqal upgrade
>
It is most likely better if we start tagging RCs. Anytime we need to "record"
some version, a tag make sense, IMO.
> On Oct 26, 2018, at 2:16 PM, Andrea Pescetti wrote:
>
> Jim Jagielski wrote:
>> I went ahead and tagged AOO-4.1.6RC1. If it passes then we can copy that tag
>> to the GA.
>
>
On 23 Oct, Peter Kovacs wrote:
> 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?
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
Jim Jagielski wrote:
I went ahead and tagged AOO-4.1.6RC1. If it passes then we can copy that tag to
the GA.
We don't tag RCs normally, only releases (and we thus do it AFTER the
vote has passed). No problem, it just means that if the vote passes the
tag will be renamed (moved instead of
I went ahead and tagged AOO-4.1.6RC1. If it passes then we can copy that tag to
the GA.
> On Oct 26, 2018, at 10:56 AM, Matthias Seidel
> wrote:
>
> Hi Marcus,
>
> Am 25.10.18 um 23:56 schrieb Marcus:
>> Am 25.10.2018 um 23:42 schrieb Andrea Pescetti:
>>> On 23/10/2018 Matthias Seidel wrote:
Hi Marcus,
Am 25.10.18 um 23:56 schrieb Marcus:
> Am 25.10.2018 um 23:42 schrieb Andrea Pescetti:
>> On 23/10/2018 Matthias Seidel wrote:
>>> 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
Am 25.10.2018 um 23:42 schrieb Andrea Pescetti:
On 23/10/2018 Matthias Seidel wrote:
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
Hi Andrea,
Am 25.10.18 um 23:42 schrieb Andrea Pescetti:
> On 23/10/2018 Matthias Seidel wrote:
>> 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
On 23/10/2018 Matthias Seidel wrote:
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?
This has always been an
Yes.
> On Oct 23, 2018, at 7:19 AM, Peter kovacs wrote:
>
> Important is we build with the same revision.
> Are all builds now with r1844436?
>
> Great if I do not have to sign anything. I gladly delegate that to the
> builders. ;-)
>
>
> Am 23. Oktober 2018 13:12:37 MESZ schrieb Matthias
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
Important is we build with the same revision.
Are all builds now with r1844436?
Great if I do not have to sign anything. I gladly delegate that to the
builders. ;-)
Am 23. Oktober 2018 13:12:37 MESZ schrieb Matthias Seidel
:
>Am 23.10.18 um 13:06 schrieb Jim Jagielski:
>> r1844555 was the
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
r1844555 was the SVN version of HEAD at the time of the email.
FWIW, my macOS builds of RC1 are ready... CentOS5-64 are in progress.
> On Oct 23, 2018, at 6:03 AM, Matthias Seidel
> wrote:
>
> Hi Peter,
>
> Am 23.10.18 um 05:03 schrieb Peter Kovacs:
>> I am a bit confused where we all are
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
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.
Thank you all for your efforts!
On 22.10.18 15:12, Jim Jagielski wrote:
> I
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: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail:
30 matches
Mail list logo