Re: patch to upgrade bundled curl in trunk

2018-09-09 Thread Don Lewis
On  9 Sep, Don Lewis wrote:
> On  9 Sep, Peter Kovacs wrote:
>> Hi Don,
>> 
>> what is the status on this? - Do you have a bug for this activity? Can 
>> some tester support you?
> 
> I committed the patch here:
> 
>   r1839837 | truckman | 2018-09-01 12:37:14 -0700 (Sat, 01 Sep 2018) | 3 lines
> 
>   Upgrade the bundled version of curl from 7.50.1 to 7.61.0.
> 
> and I committed an update to 7.61.1 within the last day in response to a
> new curl CVE.
> 
> Curl isn't used for much ... I think only for access to ftp and maybe
> webdav.  I've tested the former.
> 
> I'm also testing an update for 4.1.6 as well.

The bug report for 4.1.6 is here:
  https://bz.apache.org/ooo/show_bug.cgi?id=127886


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



4.1.6_release_blocker requested: [Issue 127886] Upgraded bundled curl from 7.19.7 to 7.61.1

2018-09-09 Thread bugzilla
Don Lewis  has asked  for 4.1.6_release_blocker:
Issue 127886: Upgraded bundled curl from 7.19.7 to 7.61.1
https://bz.apache.org/ooo/show_bug.cgi?id=127886



--- Description ---
These trunk commits should be merged to AOO416 to upgrade the bundled version
of curl from 7.19.7 to 7.61.1:
  https://svn.apache.org/viewvc?view=revision&revision=1754469
  https://svn.apache.org/viewvc?view=revision&revision=1756017
  https://svn.apache.org/viewvc?view=revision&revision=1761808
  https://svn.apache.org/viewvc?view=revision&revision=1772139
  https://svn.apache.org/viewvc?view=revision&revision=1825850
  https://svn.apache.org/viewvc?view=revision&revision=1839837
  https://svn.apache.org/viewvc?view=revision&revision=1840427

In the top level directory of AOO416:
  svn merge -c 1754469 '^/openoffice/trunk' .
take their side of conflict on external_deps.lst
  svn rm main/curl/curl-7.19.7.patch
  svn merge -c 1756017 '^/openoffice/trunk' .
  svn merge -c 1761808 '^/openoffice/trunk' .
  svn merge -c 1772139 '^/openoffice/trunk' .
  svn merge -c 1825850 '^/openoffice/trunk' .
  svn merge -c 1839837 '^/openoffice/trunk' .
  svn merge -c 1840427 '^/openoffice/trunk' .

Tested in 4.1.6 on 32-bit Windows 7 and CentOS 6 x86_64.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: [Discussion] Program for Sandro

2018-09-09 Thread Andrea Pescetti

Peter kovacs wrote:

If you see something on our wiki-pages.
You can decide on yourself. There is no real command structure here.
If you need a user for editing the wiki, just write a request here.


Right. Sandro, if we haven't created a MWiki account for you yet, please 
ask here. Otherwise, please give us your username so that we can (if 
needed) extend permissions for you in order to be able to do some 
configuration tasks.


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: A 4.1.6 Release

2018-09-09 Thread Andrea Pescetti

On 09/09/2018 Matthias Seidel wrote:

But I know that Andrea wanted to ask for a blocker, but we hadn't
enabled the flag at that time.


It worked now: https://bz.apache.org/ooo/show_bug.cgi?id=127712

Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



4.1.6_release_blocker requested: [Issue 127712] Allow building when gcc -dumpversion does not use the canonical x.y.z format

2018-09-09 Thread bugzilla
Andrea Pescetti  has asked  for 4.1.6_release_blocker:
Issue 127712: Allow building when gcc -dumpversion does not use the canonical
x.y.z format
https://bz.apache.org/ooo/show_bug.cgi?id=127712

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: patch to upgrade bundled curl in trunk

2018-09-09 Thread Don Lewis
On  9 Sep, Peter Kovacs wrote:
> Hi Don,
> 
> what is the status on this? - Do you have a bug for this activity? Can 
> some tester support you?

I committed the patch here:

  r1839837 | truckman | 2018-09-01 12:37:14 -0700 (Sat, 01 Sep 2018) | 3 lines

  Upgrade the bundled version of curl from 7.50.1 to 7.61.0.

and I committed an update to 7.61.1 within the last day in response to a
new curl CVE.

Curl isn't used for much ... I think only for access to ftp and maybe
webdav.  I've tested the former.

I'm also testing an update for 4.1.6 as well.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: A 4.1.6 Release

2018-09-09 Thread Kay Schenk
On Sun, Sep 9, 2018, 15:43 Keith N. McKenna 
wrote:

> 
> >
> > I had been constructing release blocker queries for some of the other
> > releases.
> >
> > I just put together a query for the release block requests for 4.1.6 --
> >
> >
> https://bz.apache.org/ooo/buglist.cgi?cmdtype=dorem&list_id=236879&namedcmd=4.1.6_blocker_requested&remaction=run
> > (I didn't do this for 4.1.5 but for many of the previous releases.)
> >
> > Hopefully this will work once you are logged in to
> https://bz.apache.org/ooo
> > AND hopefully the same ones Peter has referenced. Of course someone can
> > always modify the query.
> >
> > HTH.
> Kay;
>
> I just tried tried your query and it came back as "The search named
> 4.1.6_blocker_requested does not exist." It does not appear that you
> have set it as shared.
>
> Regards
> Keith
>

Dang! I was sure I'd done that but maybe I didn't save it correctly. I'll
fix tomorrow and notify the list.


> 
>
>


Re: A 4.1.6 Release

2018-09-09 Thread Keith N. McKenna

> 
> I had been constructing release blocker queries for some of the other
> releases.
> 
> I just put together a query for the release block requests for 4.1.6 --
> 
> https://bz.apache.org/ooo/buglist.cgi?cmdtype=dorem&list_id=236879&namedcmd=4.1.6_blocker_requested&remaction=run
> (I didn't do this for 4.1.5 but for many of the previous releases.)
> 
> Hopefully this will work once you are logged in to https://bz.apache.org/ooo
> AND hopefully the same ones Peter has referenced. Of course someone can
> always modify the query.
> 
> HTH.
Kay;

I just tried tried your query and it came back as "The search named
4.1.6_blocker_requested does not exist." It does not appear that you
have set it as shared.

Regards
Keith



signature.asc
Description: OpenPGP digital signature


Re: App icons for Windows

2018-09-09 Thread Marcus

Am 08.09.2018 um 10:28 schrieb Matthias Seidel:

Is there a specific reason why we use old icons (OOo2 ?) for our Windows
executables?
All other platforms use Galaxy icons (OOo3 ?).

Not only do these icons look "old" but they do not contain higher
resolutions (256x256), whereas the Galaxy icons do.

Everything is already available here (Thanks to Pedro Lino to find this
out!):
https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/content/ui/VisualDesign/gifs/Icons/OOo30_final_mimetype/icos/

I would like to update the 6 icons for Writer, Calc, Impress, Draw, Base
and Math.

Opinions?


sounds good, do it.

Marcus


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: A 4.1.6 Release

2018-09-09 Thread Kay Schenk
Hi all --

On Sun, Sep 9, 2018 at 10:06 AM, Matthias Seidel  wrote:

> Hi Peter,
>
> Am 09.09.2018 um 18:03 schrieb Peter Kovacs:
> > Okay I had a look now.
> >
> > I have a bit of an issue in filtering on the blocker flag.
> >
> > I filtered now on the Version 4.1.6-dev and 4.1.6 and found 6 reports.
> >
> > Are these all of them?
>
> I don't know your list, can you post the issue numbers?
> Or just the filter string?
>
> >
> >
> > - The Patch I had in mind i did not find again. Next time I have to
> > note the issue number. :(
> >
> >
> > Thus I am fine with the Blockers so far. Anything that anyone wants
> > still to add from the dev list?
>
> I have a lot of them, but they do not qualify as blocker.
> But I know that Andrea wanted to ask for a blocker, but we hadn't
> enabled the flag at that time.
>
> Regards,
>Matthias
>

I had been constructing release blocker queries for some of the other
releases.

I just put together a query for the release block requests for 4.1.6 --

https://bz.apache.org/ooo/buglist.cgi?cmdtype=dorem&list_id=236879&namedcmd=4.1.6_blocker_requested&remaction=run
(I didn't do this for 4.1.5 but for many of the previous releases.)

Hopefully this will work once you are logged in to https://bz.apache.org/ooo
AND hopefully the same ones Peter has referenced. Of course someone can
always modify the query.

HTH.


> >
> > All the best
> >
> > Peter
> >
> > On 9/6/18 5:10 PM, Peter Kovacs wrote:
> >>   I plan to have a look on the weekend, what we have now. I want to
> >> add one patch concerning mailmerge.
> >> And then off we go, I Think.
> >>
> >>
> >> I agree with Jim in general. I see a possibility that the 4.1.x
> >> series gets maintenance till 2020, for centOS6 while every one else
> >> is moving to 4.2.0.
> >>
> >>
> >> Am 6. September 2018 15:25:19 MESZ schrieb Jim Jagielski
> >> :
> >>> Anyone can propose something as a blocker... it's up to the RM on
> >>> whether it really is one or not ;)
> >>>
> >>> BTW: I'm ready to go w/ Linux and macOS builds!
> >>>
>  On Sep 6, 2018, at 8:05 AM, Matthias Seidel
> >>>  wrote:
>  Hi Jim,
> 
>  Am 03.09.2018 um 23:45 schrieb Jim Jagielski:
> > For some users, AOO 4.1.6 will be the "last" version of OO that they
> >>> can use, since AOO 4.2.x will not provide some community build for
> >>> older platforms (eg: CentOS5,...). As such, I think we need to make
> >>> 4.1.6 as good and as stable and as useful, with as many patches and
> >>> fixes, as feasible for those users.
>  Definitely!
>  We already have some release blocker asked for.
> 
>  How to proceed?
> 
>  Regards,
>  Matthias
> 
> >> On Sep 3, 2018, at 4:49 PM, Matthias Seidel
> >>>  wrote:
> >> Hi Andrea,
> >>
> >> Am 03.09.2018 um 22:37 schrieb Andrea Pescetti:
> >>> Matthias Seidel wrote:
>  How about this one:
>  https://bz.apache.org/ooo/show_bug.cgi?id=126736
>  It fixes a typo in the build process.
> >>> This one has zero impact for users and, if 4.1.6 was just a
> >>> maintenance release and we had regular 4.x major releases, it
> >>> wouldn't
> >>> make sense to include fixes like this one. Still, it is zero-risk
> >>> and
> >>> (unfortunately) 4.2.0 is taking longer than expected, so I
> >>> understand
> >>> if we try to backport some fixes to 4.1.6. No objection.
> >>>
> >>> In general, release blockers should be:
> >>> - important bugfixes for users
> >>> - important build fixes (e.g., don't break with a new compiler)
> >>> - important infrastructure fixes (e.g., support newer JRE, or a
> >>> newer
> >>> Windows release... just an example)
> >> This is why I didn't ask for release blocker. ;-)
> >>
> >> It is just "nice to have" and another resolved issue that would
> >>> finally
> >> find its way into a release.
> >> There are a lot of them, that do not qualify as "blocker"...
> >>
> >> Regards,
> >>Matthias
> >>
> >>> Regards,
> >>>   Andrea.
> >>>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >>> 
> >>> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>> 
> 
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >>> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional co

Re: A 4.1.6 Release

2018-09-09 Thread Matthias Seidel
Hi Peter,

Am 09.09.2018 um 18:03 schrieb Peter Kovacs:
> Okay I had a look now.
>
> I have a bit of an issue in filtering on the blocker flag.
>
> I filtered now on the Version 4.1.6-dev and 4.1.6 and found 6 reports.
>
> Are these all of them?

I don't know your list, can you post the issue numbers?
Or just the filter string?

>
>
> - The Patch I had in mind i did not find again. Next time I have to
> note the issue number. :(
>
>
> Thus I am fine with the Blockers so far. Anything that anyone wants
> still to add from the dev list?

I have a lot of them, but they do not qualify as blocker.
But I know that Andrea wanted to ask for a blocker, but we hadn't
enabled the flag at that time.

Regards,
   Matthias

>
> All the best
>
> Peter
>
> On 9/6/18 5:10 PM, Peter Kovacs wrote:
>>   I plan to have a look on the weekend, what we have now. I want to
>> add one patch concerning mailmerge.
>> And then off we go, I Think.
>>
>>
>> I agree with Jim in general. I see a possibility that the 4.1.x
>> series gets maintenance till 2020, for centOS6 while every one else
>> is moving to 4.2.0.
>>
>>
>> Am 6. September 2018 15:25:19 MESZ schrieb Jim Jagielski
>> :
>>> Anyone can propose something as a blocker... it's up to the RM on
>>> whether it really is one or not ;)
>>>
>>> BTW: I'm ready to go w/ Linux and macOS builds!
>>>
 On Sep 6, 2018, at 8:05 AM, Matthias Seidel
>>>  wrote:
 Hi Jim,

 Am 03.09.2018 um 23:45 schrieb Jim Jagielski:
> For some users, AOO 4.1.6 will be the "last" version of OO that they
>>> can use, since AOO 4.2.x will not provide some community build for
>>> older platforms (eg: CentOS5,...). As such, I think we need to make
>>> 4.1.6 as good and as stable and as useful, with as many patches and
>>> fixes, as feasible for those users.
 Definitely!
 We already have some release blocker asked for.

 How to proceed?

 Regards,
     Matthias

>> On Sep 3, 2018, at 4:49 PM, Matthias Seidel
>>>  wrote:
>> Hi Andrea,
>>
>> Am 03.09.2018 um 22:37 schrieb Andrea Pescetti:
>>> Matthias Seidel wrote:
 How about this one:
 https://bz.apache.org/ooo/show_bug.cgi?id=126736
 It fixes a typo in the build process.
>>> This one has zero impact for users and, if 4.1.6 was just a
>>> maintenance release and we had regular 4.x major releases, it
>>> wouldn't
>>> make sense to include fixes like this one. Still, it is zero-risk
>>> and
>>> (unfortunately) 4.2.0 is taking longer than expected, so I
>>> understand
>>> if we try to backport some fixes to 4.1.6. No objection.
>>>
>>> In general, release blockers should be:
>>> - important bugfixes for users
>>> - important build fixes (e.g., don't break with a new compiler)
>>> - important infrastructure fixes (e.g., support newer JRE, or a
>>> newer
>>> Windows release... just an example)
>> This is why I didn't ask for release blocker. ;-)
>>
>> It is just "nice to have" and another resolved issue that would
>>> finally
>> find its way into a release.
>> There are a lot of them, that do not qualify as "blocker"...
>>
>> Regards,
>>    Matthias
>>
>>> Regards,
>>>   Andrea.
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> 
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>> 

>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>




smime.p7s
Description: S/MIME Cryptographic Signature


Re: patch to upgrade bundled curl in trunk

2018-09-09 Thread Peter Kovacs

Hi Don,

what is the status on this? - Do you have a bug for this activity? Can 
some tester support you?



All the best

Peter

On 9/1/18 9:09 PM, Don Lewis wrote:

That's the plan.  I need to do some test builds first.

On  1 Sep, Peter Kovacs wrote:

Can we Bundle this also with 1.4.6?

Am 1. September 2018 10:02:10 MESZ schrieb Matthias Seidel 
:

Hi Don,

My Windows build based on r1839722 and your patch applied was
successful.

First tests show no problems.

Regards
    Matthias

Am 31.08.2018 um 01:12 schrieb Don Lewis:

The attached patch upgrades the version of curl that we bundle in

trunk

from 7.50.1 to 7.61.0.  The old version has quite a few CVEs.
Fortunately we don't use curl for much in OpenOffice.



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: A 4.1.6 Release

2018-09-09 Thread Peter Kovacs

Okay I had a look now.

I have a bit of an issue in filtering on the blocker flag.

I filtered now on the Version 4.1.6-dev and 4.1.6 and found 6 reports.

Are these all of them?


- The Patch I had in mind i did not find again. Next time I have to note 
the issue number. :(



Thus I am fine with the Blockers so far. Anything that anyone wants 
still to add from the dev list?


All the best

Peter

On 9/6/18 5:10 PM, Peter Kovacs wrote:

  I plan to have a look on the weekend, what we have now. I want to add one 
patch concerning mailmerge.
And then off we go, I Think.


I agree with Jim in general. I see a possibility that the 4.1.x series gets 
maintenance till 2020, for centOS6 while every one else is moving to 4.2.0.


Am 6. September 2018 15:25:19 MESZ schrieb Jim Jagielski :

Anyone can propose something as a blocker... it's up to the RM on
whether it really is one or not ;)

BTW: I'm ready to go w/ Linux and macOS builds!


On Sep 6, 2018, at 8:05 AM, Matthias Seidel

 wrote:

Hi Jim,

Am 03.09.2018 um 23:45 schrieb Jim Jagielski:

For some users, AOO 4.1.6 will be the "last" version of OO that they

can use, since AOO 4.2.x will not provide some community build for
older platforms (eg: CentOS5,...). As such, I think we need to make
4.1.6 as good and as stable and as useful, with as many patches and
fixes, as feasible for those users.

Definitely!
We already have some release blocker asked for.

How to proceed?

Regards,
Matthias


On Sep 3, 2018, at 4:49 PM, Matthias Seidel

 wrote:

Hi Andrea,

Am 03.09.2018 um 22:37 schrieb Andrea Pescetti:

Matthias Seidel wrote:

How about this one:
https://bz.apache.org/ooo/show_bug.cgi?id=126736
It fixes a typo in the build process.

This one has zero impact for users and, if 4.1.6 was just a
maintenance release and we had regular 4.x major releases, it

wouldn't

make sense to include fixes like this one. Still, it is zero-risk

and

(unfortunately) 4.2.0 is taking longer than expected, so I

understand

if we try to backport some fixes to 4.1.6. No objection.

In general, release blockers should be:
- important bugfixes for users
- important build fixes (e.g., don't break with a new compiler)
- important infrastructure fixes (e.g., support newer JRE, or a

newer

Windows release... just an example)

This is why I didn't ask for release blocker. ;-)

It is just "nice to have" and another resolved issue that would

finally

find its way into a release.
There are a lot of them, that do not qualify as "blocker"...

Regards,
   Matthias


Regards,
  Andrea.



-

To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org



For additional commands, e-mail: dev-h...@openoffice.apache.org






-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



What can be done when interested in Quality Assurance. (was: QA Volunteer)

2018-09-09 Thread Peter Kovacs

Welcome Sharmistha,

I have noted following Tasks to do, from my own thoughts and what I am 
aware that had been called.


1) Bugzilla

1.1) uncomirmed Bug reports for evaluation.

Not sure if the List is accessible to anyone, but you can try this link.

https://bz.apache.org/ooo/buglist.cgi?cmdtype=runnamed&list_id=236868&namedcmd=unconfirmed

1.2) recheck old Bugzilla reports if they still apply.

Dont know if someone has considered this, but we have a lot of confirmed 
Bugs. I am not sure if they are all really open.


2)We are still in the preparation of a new Maintenance Release 4.1.6. 
First builds are already done, so you could have a look and make 
familiar with testing OpenOffice.


There will be a call for testing.

2.1) The same is true for 4.2.0, but there some issues have to be fixed 
first before we can give this to testers. But then you are already aware 
that something is coming in the next month.


3)We have Test cases on the Wiki. I do not know in what completeness or 
shape they are. Maybe someone else can elaborate?


4) call for testing for the Icons on Windows (or ist this tested 
successfully? - I am unsure at the moment.)



(@ All) Anything more what can be done as interest QA?


All the Best

Peter


On 9/6/18 5:20 AM, sharmistha guha wrote:

Hi,

I am a QA engineer and would like to contribute to Apache projects. I have
4 years of QA experience.

Please let me know how I can be of help to Apache projects.

Thanks
Sharmistha Guha.


-- Forwarded message -
From: Peter Kovacs 
Date: Wed, Sep 5, 2018 at 4:53 PM
Subject: Re: QA Volunteer
To: 


Welcome Sharmistha,

I am sorry am not sure if anyone is monitoring the QA List and we had some
summertime. Most QA Reqeust these days are done via the dev mailing list.
Maybe you want to introduce there.


On 2018/08/15 05:03:57, sharmistha guha  wrote:

Hi,

I am a QA engineer and would like to contribute to Apache projects. I have
4 years of QA experience.

Please let me know how I can be of help to Apache projects.

Thanks
Sharmistha


-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: svn commit: r1839782 - in /openoffice/trunk/main: ./ rsc/ rsc/prj/ rsc/source/parser/ solenv/gbuild/

2018-09-09 Thread Matthias Seidel
Am 08.09.2018 um 13:32 schrieb Damjan Jovanovic:
> On Sat, Sep 8, 2018 at 10:47 AM Matthias Seidel 
> wrote:
>
>> Am 08.09.2018 um 10:16 schrieb Damjan Jovanovic:
>>> It should be fixed in 1840343:
>>>
>>> "When building other languages (--with-lang="..."), the build was
>> breaking
>>> because rsc couldn't compile certain resources (usually in main/sfx2).
>>>
>>> Apparently the RSC preprocessor, rscpp, uses very small buffers by
>> default.
>>> When the SOLAR preprocessor definition is defined, it uses bigger buffers
>>> instead. Previously dmake was explicitly passing "-DSOLAR" to the C
>> compiler
>>> but I missed it when porting main/rsc to gbuild. When added back,
>>> main/sfx2 builds languages successfully."
>> Hi Damjan,
>>
>> Great! Building as we speak...
>>
>> And thanks for the explanation. It helps me to (hopefully) understand
>> more and more. ;-)
>>
>> Regards,
>>Matthias
>>
>>
> Hi
>
> Pleasure :)
>
> Mine built successfully.

All 3 buildbots and my personal Windows build were successful!

Regards,
   Matthias

>
> Regards
> Damjan
>




smime.p7s
Description: S/MIME Cryptographic Signature


Findings after running a W3C Check on your site ..

2018-09-09 Thread David G. Stapleton
I believe you are interested in the findings automatically located and 
documented this morning as I was clicking around your site @ 
https://www.openoffice.org/documentation/index.html. All I did to be the almost 
instantaneous recipient of the enumerating documentation of coding errors / 
misnomers on the subject page was click the [ W3C XHTML 1.0 ] icon button in 
the lower left corner of this particular page. 

Please review and at least consider making W3C’s recommended edits to your 
pages codings following their examples found in the attached PDF I included 
with this my 1st email to your WebDev team. It would reflect well on your team 
of developers if you’d run this test completely on your site. This would give 
your open source software a good shot in the arm so to speak. 

I hope this helps your OS project I’ve enjoyed using from time to time since a 
couple of previous versions ago. 



Best regards,

David G Stapleton, AASD
Web Developer, Retired
Author, Singer-Songwriter




-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org