English Dictionaries updated - 2016-02-01 + Autocorrect pt_PT updated 2016-01-29

2016-01-29 Thread Marco A.G.Pinto 

Hello!

I have updated the English Dictionaries:
http://extensions.openoffice.org/en/project/english-dictionaries-apache-openoffice

Changes:
- American (Kevin Atkinson)
- Canadian (Kevin Atkinson)
- British (Marco A.G.Pinto)*
  * British has 1622 new words.

As usual I always update a couple of days or so before the official date 
because I have it packed for several days already and it is risky to 
leave things to be done in the last moment.



Also notice that I have updated the Autocorrect for pt_PT adding around 
168 new words. This is an ongoing task since I have grammar books from 
where I am taking the words and it will take months to add the many 
dozens or even hundreds of words. The .DAT file became 5 kB compared to 
the old 15 kB from 2010 because I used commercial software to compress.



Andreas, I have opened the following cases on Bugzilla:

Bugzilla - English Dictionaries:
https://bz.apache.org/ooo/show_bug.cgi?id=126814

Bugzilla - Autocorrect pt_PT
https://bz.apache.org/ooo/show_bug.cgi?id=126815


Thanks for your time!

Kind regards from your friend,
   >Marco A.G.Pinto
 ---

--

Re: Let's fix the Windows build bots

2016-01-29 Thread Damjan Jovanovic 
On Fri, Jan 29, 2016 at 9:18 AM, Damjan Jovanovic  wrote:

> Hi
>
> I am to get our build bots working again.
>
> So far I've committed a patch to fix #126787 (build breaking regression in
> main/sal due to  and  being included) in r1727413, and
> deleted an unused empty file that the RAT scan was treating as missing the
> ASL in r1727463. The Windows aoo-win7 build bot now gets further,
> infamously breaking in apr, but now also breaking in jpeg (
> https://ci.apache.org/builders/aoo-win7/builds/156/steps/build.pl%20--all/logs/stdio
> ).
>
> The error for the jpeg module is:
> dmake:  Error: -- `./
> wntmsci12.pro/misc/52654eb3b2e60c35731ea8fc87f1bd29-jpeg-8d.unpack' not
> found, and can't be made
>
>
I can reproduce this error on my own Windows build by deleting or renaming
ext_sources/52654eb3b2e60c35731ea8fc87f1bd29-jpeg-8d.tar.gz and then
running "build" from inside main/jpeg. The problem on the buildbot appears
to be that libjpeg couldn't be downloaded (
https://ci.apache.org/builders/aoo-win7/builds/156/steps/bootstrap/logs/stdio
):

downloading to
E:/slave14/aoo-win7/build/ext_sources/52654eb3b2e60c35731ea8fc87f1bd29-jpeg-8d.tar.gz.part
download from http://www.ijg.org/files/jpegsrc.v8d.tar.gz failed
download failed
downloading to
E:/slave14/aoo-win7/build/ext_sources/52654eb3b2e60c35731ea8fc87f1bd29-jpeg-8d.tar.gz.part
download from
http://sourceforge.net/projects/oooextras.mirror/files/52654eb3b2e60c35731ea8fc87f1bd29-jpeg-8d.tar.gz
failed
download failed

Maybe it was a temporary networking glitch - 5 downloads failed in total
(maybe we need a mirror internal to Apache?). Let's see how it looks
tomorrow.



> What looks interesting, if you get the stdio log and look for the
> "Entering ..." lines and sort and count them, is that the only modules that
> are entered more than once are the same ones that the build breaks in: apr
> and jpeg:
>
> $ grep Entering /tmp/stdio | sort | uniq -c | grep "^  1 " -v
>   2 Entering /cygdrive/e/slave14/aoo-win7/build/ext_libraries/apr
>   2 Entering /cygdrive/e/slave14/aoo-win7/build/main/jpeg
>
> Is it breaking because build.pl is trying to build those modules more
> than once (or is it re-entering them because they broke the build)?
>
> Our build page https://ci.apache.org/projects/openoffice/index.html is
> also messed up - eg. "Windows Nightly Build Logs" is listed under "FreeBSD
> nightly Install Packages". How do we edit it?
>
> What else? How do we get SSH access to the build bots for further
> debugging?
>
> Thank you
> Damjan
>
>

Re: Going

2016-01-29 Thread Marcus 

Hi Louis,

thats very sad to read. But thats life. Things are coming and they are 
going and you have to juggle them on your schedule plan.


Thanks a lot for your work and dedication in all these many years. I 
hope you will return someday. :-)


Marcus



Am 01/29/2016 12:39 AM, schrieb Louis Suárez-Potts:

I'm stepping down from the AOO PMC after many years. If one includes the decade 
plus I dedicated to Openoffice.org as the community manager and chair of the 
community council, as well as lead and co-lead of many projects, big and small, 
and the five years since on the PMC, it's been 16 years of OpenOffice. A span 
that has been wonderful, exasperating, exhilarating; and now, for me, it's 
becoming a rut. I'm not contributing much at all, and other open source efforts 
and works take up my time and intellectual focus. Some of these will surely 
intersect with OpenOffice and other Apache projects….

I'll remain subscribed to this and other lists, but am leaving the PMC. You can 
always reach me via the usual ways.


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

Re: Let's fix the Windows build bots

2016-01-29 Thread Kay Schenk 
On Thu, Jan 28, 2016 at 11:18 PM, Damjan Jovanovic 
wrote:

> Hi
>
> I am to get our build bots working again.
>
> So far I've committed a patch to fix #126787 (build breaking regression in
> main/sal due to  and  being included) in r1727413, and
> deleted an unused empty file that the RAT scan was treating as missing the
> ASL in r1727463. The Windows aoo-win7 build bot now gets further,
> infamously breaking in apr, but now also breaking in jpeg (
>
> https://ci.apache.org/builders/aoo-win7/builds/156/steps/build.pl%20--all/logs/stdio
> ).
>
> The error for the jpeg module is:
> dmake:  Error: -- `./
> wntmsci12.pro/misc/52654eb3b2e60c35731ea8fc87f1bd29-jpeg-8d.unpack' not
> found, and can't be made
>
> What looks interesting, if you get the stdio log and look for the "Entering
> ..." lines and sort and count them, is that the only modules that are
> entered more than once are the same ones that the build breaks in: apr and
> jpeg:
>
> $ grep Entering /tmp/stdio | sort | uniq -c | grep "^  1 " -v
>   2 Entering /cygdrive/e/slave14/aoo-win7/build/ext_libraries/apr
>   2 Entering /cygdrive/e/slave14/aoo-win7/build/main/jpeg
>
> Is it breaking because build.pl is trying to build those modules more than
> once (or is it re-entering them because they broke the build)?
>

​Good that some more eyes are looking into this. I haven't looked at last
night's runs yet but for the last week, I have been making the buildbots a
priority also.

​


>
> Our build page https://ci.apache.org/projects/openoffice/index.html is
> also
> messed up - eg. "Windows Nightly Build Logs" is listed under "FreeBSD
> nightly Install Packages". How do we edit it?
>

​Ok, yeah, it's a bit of odd formatting. I understand what you're saying.
Look at the other areas and you'll see that the HRs come under the Build
Logs headings. So this is not just a Windows anomaly.​

​ ​ We can definitely change this.

Here is the svn info for this page if you want to change things:

https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/public_html/projects/openoffice

Have fun.



> What else? How do we get SSH access to the build bots for further
> debugging?
>

​Our buildbot script, openofficeorg.conf is at:

https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects

along with buildbots for other projects.

The ASF is running buildbot 0.8.9. We don't have direct access to the
buldbot throught SSH. (You need to be part of infra to do that). If you
look at the buildbot documents, you'll see that there are some tools for
directly accessing the buildbot's directories, though.
​


>
> Thank you
> Damjan
>

​Thank you!​




-- 
--
MzK

"Though no one can go back and make a brand new start,
 anyone can start from now and make a brand new ending."
  -- Carl Bard

Re: Going

2016-01-29 Thread Kay Schenk 
On Thu, Jan 28, 2016 at 3:39 PM, Louis Suárez-Potts 
wrote:

> Hi All,
> I'm stepping down from the AOO PMC after many years. If one includes the
> decade plus I dedicated to Openoffice.org as the community manager and
> chair of the community council, as well as lead and co-lead of many
> projects, big and small, and the five years since on the PMC, it's been 16
> years of OpenOffice. A span that has been wonderful, exasperating,
> exhilarating; and now, for me, it's becoming a rut. I'm not contributing
> much at all, and other open source efforts and works take up my time and
> intellectual focus. Some of these will surely intersect with OpenOffice and
> other Apache projects….
>
> I'll remain subscribed to this and other lists, but am leaving the PMC.
> You can always reach me via the usual ways.
>
> Cheers,
> Louis
>
>
> ---
>
> Louis Suárez-Potts
> Skype: louisiam
> Twitter: @luispo
> Personal: http://www.luispo.com/
>
>
>
​Thank you for your service to the PMC since OpenOffice moved to the Apache
Software Foundation.​

I'm happy to see that you're still remaining on the "dev" list. ☺



-- 
--
MzK

"Though no one can go back and make a brand new start,
 anyone can start from now and make a brand new ending."
  -- Carl Bard

Re: Going

2016-01-29 Thread Louis Suárez-Potts 

> On 29 Jan 16, at 12:31, Kay Schenk  wrote:
> 
> I'm happy to see that you're still remaining on the "dev" list. ☺

I might that way help out or at least gripe entertainingly and occasionally 
voice the desire that users of AOO and LO be better served by not having to 
figure out which project to back…..

However…

@Dennis (or ?) can you remove committer privileges from my account? I had 
presumed that announcing my departure from the PMC was sufficient but it may 
not be. It may also be that I just have to do it myself….?

cheers,
Louis


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: linux32 buildbot

2016-01-29 Thread j.nitsc...@ok.de 
On Thu, 28 Jan 2016 16:10:52 -0800 Kay Schenk wrote:
>
> On 01/14/2016 09:48 AM, Kay Schenk wrote:
>> On Thu, Jan 14, 2016 at 4:04 AM, j.nitsc...@ok.de
>>  > > wrote:
>>
>> Hello,
>>
>> some may have noticed our linux-32 buildbot fails quite often. [1]
>> Here an analysis: (tl;dr jump to solutions)
>> * always fails in first buildbot step: svn updating
>> * failed step takes around 6 minutes, a successfull step uses ~37
>> minutes to complete
>> * the commands in the step take much time and often a timeout
>> triggers
>>
>> The commands and their timeouts (seconds) are:
>> 1) svn --version (1200)
>> 2) rm -rf
>> /home/buildslave20/slave20/openoffice-linux32-nightly/build (120)
>> 3) chmod -Rf u+rwx
>> /home/buildslave20/slave20/openoffice-linux32-nightly/build
>> (120) ah, why?
>> 4) rm -rf
>> /home/buildslave20/slave20/openoffice-linux32-nightly/build
>> (120) huh, again?
>> 5) svn info --xml --non-interactive --no-auth-cache (1200)
>> 6) svn update --non-interactive --no-auth-cache (1200)
>> 7) cp -R -P -p -v
>> /home/buildslave20/slave20/openoffice-linux32-nightly/source
>> /home/buildslave20/slave20/openoffice-linux32-nightly/build (120)
>> 8) svn info --xml (1200)
>>
>> Their results:
>> 1) Always finishes in ~15 seconds
>> 2) No output, almost always fails with command timed out: 120
>> seconds
>> without output, attempting to kill
>> 3) No output, almost always fails with command timed out: 120
>> seconds
>> without output, attempting to kill
>> 4) No output, finishes sometimes.
>> *if we fail here the build process is stopped and this the
>> reason for
>> the often failures*
>> 5) Local command completes in a sec.
>> 6) Can take a while depending in source changes. Gives tons of
>> output,
>> so timeout never triggers.
>> 7) Takes *very* long (over 20 minutes) but never triggers timeout as
>> '-v' the output spams the log.
>> 8) Local command again takes a sec.
>>
>> Conclusions:
>> *file operations don't have enough time to finish*
>>
>> Solutions:
>> Edit 'svn updating' buildstep
>> a) Remove rm and chmod commands and replace cp with
>> 'rsync -q -t -p -r --delete
>> /home/buildslave20/slave20/openoffice-linux32-nightly/source
>> /home/buildslave20/slave20/openoffice-linux32-nightly/build'
>>   This is much faster as very few copies needed and it's delete is
>> faster than rm command. But increase the timeout anyway just in
>> case.
>> (*preferred* solution but needs rsync on the box)
>> b) increase the timeouts and shut up cp by removing '-v'
>> c) remove unversioned files when updating and build in this folder
>> d) Make rm and chmod verbose by adding '-v' (or -c' for chmod).
>> Spam the
>> log even more, but the timeouts won't trigger.
>>   Who doesn't like 50MB logfiles? Yes, the log for this step of
>> every
>> succesfull build is over 50MB currently! Starting build #127 [1]
>> (before
>> this build there was only a build folder but no source
>>   Not a serious solution!
>>
>> *I suggest we fix this soon because the huge log files will blow
>> up a
>> server sooner or later.*
>>
>> Regards Jochen
>>
>> [1] https://ci.apache.org/builders/openoffice-linux32-nightly
>>
>> note: on linux64 buildbot the file operations are *much* faster. cp
>> takes 90 secs isn't verbose but in the 120 sec timeout limit.
>>
>>
>> ​Thanks for the suggestions, I will look into this. ​
>>
>>
> I just wanted to  give a short update on this.
>
> * our Linux-32 and linux-64 buildbots use the same mechanisms for an
> svn pull -- a "copy" -- so I left the 32-bit instructions as is
'copy' instructions differ in one detail
Linux-32: cp -R -P -p -v
/home/buildslave20/slave20/openoffice-linux32-nightly/source
/home/buildslave20/slave20/openoffice-linux32-nightly/build
Linux-64: cp -R -P -p
/home/buildslave19/slave19/openofficeorg-nightly/source
/home/buildslave19/slave19/openofficeorg-nightly/build

*-v* needs to go to reduce the log siz
but we have to increase timeout further before we do this or copy will
always fail

https://ci.apache.org/builders/openoffice-linux32-nightly/builds/162/steps/svn/logs/stdio
:
> cp -R -P -p -v
> /home/buildslave20/slave20/openoffice-linux32-nightly/source
> /home/buildslave20/slave20/openoffice-linux32-nightly/build in dir
> /home/buildslave20/slave20/openoffice-linux32-nightly (timeout 120 secs)
... humongous log ...
> elapsedTime=1370.929525 program finished with exit code 0
seems 1200 won't be enough, note that the timeout for cp was still 120

On Thu, 28 Jan 2016 16:10:52 -0800 Kay Schenk wrote:
> * I recently updated the timeout for the svn pull for linux-32 to
> 1200 secs. To me it looked like this was set to 120 though it IS
> supposed to default to

RE: Going

2016-01-29 Thread Dennis E. Hamilton 
Louis,

I am the one to do that.  

I did not know you wanted to drop your AOO committer karma.

I will take care of both PMC and committer today.

 - Dennis


> -Original Message-
> From: Louis Suárez-Potts [mailto:lui...@gmail.com]
> Sent: Friday, January 29, 2016 10:53
> To: dev@openoffice.apache.org
> Subject: Re: Going
> 
> 
> > On 29 Jan 16, at 12:31, Kay Schenk  wrote:
> >
> > I'm happy to see that you're still remaining on the "dev" list. ☺
> 
> I might that way help out or at least gripe entertainingly and
> occasionally voice the desire that users of AOO and LO be better served
> by not having to figure out which project to back…..
> 
> However…
> 
> @Dennis (or ?) can you remove committer privileges from my account? I
> had presumed that announcing my departure from the PMC was sufficient
> but it may not be. It may also be that I just have to do it myself….?
> 
> cheers,
> Louis


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

Re: linux32 buildbot

2016-01-29 Thread Kay Schenk 
On Fri, Jan 29, 2016 at 12:58 PM, j.nitsc...@ok.de  wrote:

> On Thu, 28 Jan 2016 16:10:52 -0800 Kay Schenk wrote:
> >
> > On 01/14/2016 09:48 AM, Kay Schenk wrote:
> >> On Thu, Jan 14, 2016 at 4:04 AM, j.nitsc...@ok.de
> >>   >> > wrote:
> >>
> >> Hello,
> >>
> >> some may have noticed our linux-32 buildbot fails quite often. [1]
> >> Here an analysis: (tl;dr jump to solutions)
> >> * always fails in first buildbot step: svn updating
> >> * failed step takes around 6 minutes, a successfull step uses ~37
> >> minutes to complete
> >> * the commands in the step take much time and often a timeout
> >> triggers
> >>
> >> The commands and their timeouts (seconds) are:
> >> 1) svn --version (1200)
> >> 2) rm -rf
> >> /home/buildslave20/slave20/openoffice-linux32-nightly/build (120)
> >> 3) chmod -Rf u+rwx
> >> /home/buildslave20/slave20/openoffice-linux32-nightly/build
> >> (120) ah, why?
> >> 4) rm -rf
> >> /home/buildslave20/slave20/openoffice-linux32-nightly/build
> >> (120) huh, again?
> >> 5) svn info --xml --non-interactive --no-auth-cache (1200)
> >> 6) svn update --non-interactive --no-auth-cache (1200)
> >> 7) cp -R -P -p -v
> >> /home/buildslave20/slave20/openoffice-linux32-nightly/source
> >> /home/buildslave20/slave20/openoffice-linux32-nightly/build (120)
> >> 8) svn info --xml (1200)
> >>
> >> Their results:
> >> 1) Always finishes in ~15 seconds
> >> 2) No output, almost always fails with command timed out: 120
> >> seconds
> >> without output, attempting to kill
> >> 3) No output, almost always fails with command timed out: 120
> >> seconds
> >> without output, attempting to kill
> >> 4) No output, finishes sometimes.
> >> *if we fail here the build process is stopped and this the
> >> reason for
> >> the often failures*
> >> 5) Local command completes in a sec.
> >> 6) Can take a while depending in source changes. Gives tons of
> >> output,
> >> so timeout never triggers.
> >> 7) Takes *very* long (over 20 minutes) but never triggers timeout as
> >> '-v' the output spams the log.
> >> 8) Local command again takes a sec.
> >>
> >> Conclusions:
> >> *file operations don't have enough time to finish*
> >>
> >> Solutions:
> >> Edit 'svn updating' buildstep
> >> a) Remove rm and chmod commands and replace cp with
> >> 'rsync -q -t -p -r --delete
> >> /home/buildslave20/slave20/openoffice-linux32-nightly/source
> >> /home/buildslave20/slave20/openoffice-linux32-nightly/build'
> >>   This is much faster as very few copies needed and it's delete is
> >> faster than rm command. But increase the timeout anyway just in
> >> case.
> >> (*preferred* solution but needs rsync on the box)
> >> b) increase the timeouts and shut up cp by removing '-v'
> >> c) remove unversioned files when updating and build in this folder
> >> d) Make rm and chmod verbose by adding '-v' (or -c' for chmod).
> >> Spam the
> >> log even more, but the timeouts won't trigger.
> >>   Who doesn't like 50MB logfiles? Yes, the log for this step of
> >> every
> >> succesfull build is over 50MB currently! Starting build #127 [1]
> >> (before
> >> this build there was only a build folder but no source
> >>   Not a serious solution!
> >>
> >> *I suggest we fix this soon because the huge log files will blow
> >> up a
> >> server sooner or later.*
> >>
> >> Regards Jochen
> >>
> >> [1] https://ci.apache.org/builders/openoffice-linux32-nightly
> >>
> >> note: on linux64 buildbot the file operations are *much* faster. cp
> >> takes 90 secs isn't verbose but in the 120 sec timeout limit.
> >>
> >>
> >> ​Thanks for the suggestions, I will look into this. ​
> >>
> >>
> > I just wanted to  give a short update on this.
> >
> > * our Linux-32 and linux-64 buildbots use the same mechanisms for an
> > svn pull -- a "copy" -- so I left the 32-bit instructions as is
> 'copy' instructions differ in one detail
> Linux-32: cp -R -P -p -v
> /home/buildslave20/slave20/openoffice-linux32-nightly/source
> /home/buildslave20/slave20/openoffice-linux32-nightly/build
> Linux-64: cp -R -P -p
> /home/buildslave19/slave19/openofficeorg-nightly/source
> /home/buildslave19/slave19/openofficeorg-nightly/build
>
> *-v* needs to go to reduce the log siz
>

​OK. and thank you.
Your eyes are better than mine! :)
​


> but we have to increase timeout further before we do this or copy will
> always fail
>
>
> https://ci.apache.org/builders/openoffice-linux32-nightly/builds/162/steps/svn/logs/stdio
> :
>

​I will try it again. It's these odd remove commands that we don't seem to
control that seem to be a problem.
​


> > cp -R -P -p -v
> > /home/buildslave20/slave20/openoffice-linux32-nightly/source
> > /home/buildslave20/slave20/openoffice-l

Re: Going

2016-01-29 Thread Louis Suárez-Potts 

> On 29 Jan 16, at 16:28, Dennis E. Hamilton  wrote:
> 
> Louis,
> 
> I am the one to do that.
> 
> I did not know you wanted to drop your AOO committer karma.
> 
> I will take care of both PMC and committer today.
> 

Thanks, Dennis.

louis


> - Dennis
> 
> 
>> -Original Message-
>> From: Louis Suárez-Potts [mailto:lui...@gmail.com]
>> Sent: Friday, January 29, 2016 10:53
>> To: dev@openoffice.apache.org
>> Subject: Re: Going
>> 
>> 
>>> On 29 Jan 16, at 12:31, Kay Schenk  wrote:
>>> 
>>> I'm happy to see that you're still remaining on the "dev" list. ☺
>> 
>> I might that way help out or at least gripe entertainingly and
>> occasionally voice the desire that users of AOO and LO be better served
>> by not having to figure out which project to back…..
>> 
>> However…
>> 
>> @Dennis (or ?) can you remove committer privileges from my account? I
>> had presumed that announcing my departure from the PMC was sufficient
>> but it may not be. It may also be that I just have to do it myself….?
>> 
>> cheers,
>> Louis
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Let's fix the Windows build bots

2016-01-29 Thread Damjan Jovanovic 
On Fri, Jan 29, 2016 at 7:25 PM, Kay Schenk  wrote:

> On Thu, Jan 28, 2016 at 11:18 PM, Damjan Jovanovic 
> wrote:
>
> > Hi
> >
> > I am to get our build bots working again.
> >
> > So far I've committed a patch to fix #126787 (build breaking regression
> in
> > main/sal due to  and  being included) in r1727413,
> and
> > deleted an unused empty file that the RAT scan was treating as missing
> the
> > ASL in r1727463. The Windows aoo-win7 build bot now gets further,
> > infamously breaking in apr, but now also breaking in jpeg (
> >
> >
> https://ci.apache.org/builders/aoo-win7/builds/156/steps/build.pl%20--all/logs/stdio
> > ).
> >
> > The error for the jpeg module is:
> > dmake:  Error: -- `./
> > wntmsci12.pro/misc/52654eb3b2e60c35731ea8fc87f1bd29-jpeg-8d.unpack' not
> > found, and can't be made
> >
> > What looks interesting, if you get the stdio log and look for the
> "Entering
> > ..." lines and sort and count them, is that the only modules that are
> > entered more than once are the same ones that the build breaks in: apr
> and
> > jpeg:
> >
> > $ grep Entering /tmp/stdio | sort | uniq -c | grep "^  1 " -v
> >   2 Entering /cygdrive/e/slave14/aoo-win7/build/ext_libraries/apr
> >   2 Entering /cygdrive/e/slave14/aoo-win7/build/main/jpeg
> >
> > Is it breaking because build.pl is trying to build those modules more
> than
> > once (or is it re-entering them because they broke the build)?
> >
>
> ​Good that some more eyes are looking into this. I haven't looked at last
> night's runs yet but for the last week, I have been making the buildbots a
> priority also.
>
>
Thank you.

I think the latter is true: it's re-entering them because they broke the
build.

Yesterday jpeg failed to download and broke the build, and today nss failed
to download and also broke the build. Why are downloads often failing
during ./bootstrap? Can we get a local mirror or cache external
dependencies somehow? Also, why does ./bootstrap seem to return an exit
code of 0 when needed dependencies can't be downloaded, and why is
haltOnFailure=False for the Windows buildbots but True for other platforms?



> ​
>
>
> >
> > Our build page https://ci.apache.org/projects/openoffice/index.html is
> > also
> > messed up - eg. "Windows Nightly Build Logs" is listed under "FreeBSD
> > nightly Install Packages". How do we edit it?
> >
>
> ​Ok, yeah, it's a bit of odd formatting. I understand what you're saying.
> Look at the other areas and you'll see that the HRs come under the Build
> Logs headings. So this is not just a Windows anomaly.​
>
> ​ ​ We can definitely change this.
>
> Here is the svn info for this page if you want to change things:
>
>
> https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/public_html/projects/openoffice
>
> Have fun.
>
>
I made several changes, but they aren't being applied. When/how does the
create-ooo-snapshots-index.sh script create the webpage?


>
>
> > What else? How do we get SSH access to the build bots for further
> > debugging?
> >
>
> ​Our buildbot script, openofficeorg.conf is at:
>
>
> https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects
>
> along with buildbots for other projects.
>
> The ASF is running buildbot 0.8.9. We don't have direct access to the
> buldbot throught SSH. (You need to be part of infra to do that). If you
> look at the buildbot documents, you'll see that there are some tools for
> directly accessing the buildbot's directories, though.
> ​
>
>
> >
> > Thank you
> > Damjan
> >
>
> ​Thank you!​
>
>
>
>
> --
> --
> MzK
>
> "Though no one can go back and make a brand new start,
>  anyone can start from now and make a brand new ending."
>   -- Carl Bard
>