Let's fix the Windows build bots

[Damjan Jovanovic]

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)?

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

[Dennis E. Hamilton]

+1

Louis, thank you for your continuous and consistent devotion to OpenOffice, 
ODF, and the whole idea of a multi-platform productivity suite that is freely 
available to everyone.

 - Dennis

> -Original Message-
> From: Carl Marcum [mailto:cmar...@apache.org]
> Sent: Thursday, January 28, 2016 16:39
> To: dev@openoffice.apache.org
> Subject: Re: Going
> 
> On 01/28/2016 06: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/
> >
> 
> Louis,
> 
> Thank you for all of your contributions.
> 
> Good luck on all your endeavors.
> 
> Best regards,
> Carl
> 
> 
> 
> -
> 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: Going

[Carl Marcum]

On 01/28/2016 06: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/



Louis,

Thank you for all of your contributions.

Good luck on all your endeavors.

Best regards,
Carl



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

Re: linux32 buildbot

[Kay Schenk]

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

* 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 1200, but...

* there are some other extra steps -- some removes -- that seem to
be tacked onto the svn step that are outside of our config commands
that ARE timing out and seem to NOT be governed by the total timeout
for this step, yet they time out in successful builds also.

* there are some buildbot setup instructions that differ for our
linux-64 and linux-32 builds.

Detailed in:
My INFRA ticket to track Linux-32 buildbot problems:

https://issues.apache.org/jira/browse/INFRA-10997

So, still a mystery to me at this point.







-- 

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

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

Release Manager for 4.2.0?

[Andrea Pescetti]

As I wrote a few day ago, in theory it would be good to release 
OpenOffice 4.2.0 in February. If it happens a bit later it wouldn't be a 
big issue, but I believe that, in the constant balance between periods 
where we are focused on talks (internal to OpenOffice and with the 
enlarged community) and periods where we are more focused on the 
OpenOffice product, it's time to start working again towards a release.


For 4.2.0 we need a Release Manager. I would prefer NOT to be the 
Release Manager for 4.2.0 since I'm finding that in this period I can 
help more productively with tasks that do not require constant 
interaction than with tasks that require a constant monitoring of 
project channels.


I am surely available to have a significant role in the 4.2.0 release, 
especially with getting localization working again (actually, this mail 
also serves as announcement that I am going to ask for higher privileges 
on the Pootle server in order to check the translation workflow); but if 
someone else steps in as a Release Manager we could deliver earlier.


So if anyone is interested feel free to discuss this on list, or to 
contact me off-list if you prefer, or to discuss in person at FOSDEM 
next weekend!


Regards,
  Andrea.

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

Going

[Louis Suárez-Potts]

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/














signature.asc
Description: Message signed with OpenPGP using GPGMail

.AFF and apostrophes

[Marco A.G.Pinto]

Hello!

A person has posted in my GitHub that some software has problems with 
the apostrophe 0x039 vs Unicode (US+CA+GB):

https://github.com/marcoagpinto/aoo-mozilla-en-dict/issues/23

I have tested his examples, and they work 100% okay with Mozilla and 
OpenOffice (no issues found):

*didn't  <-- 0x039**
**didn’t  <-- unicode**
**'apple'   <- 0x39**
**someone's  <- 0x39**
**someone’s  <--- unicode*


He asked me to add to the GB .AFF:
WORDCHARS ’

Right now I can't make any changes since for days that I have everything 
packed and ready to upload tomorrow, but I need advice if I should do 
this within a month and how to test it, since it works okay on our software.


What is your advice?

Thanks!

Kind regards,
 >Marco A.G.Pinto
  

--

Fwd: FOSDEM: Practical information

[Andrea Pescetti]

Forwarding Daniel's excellent message in case someone plans to attend 
FOSDEM and is not on the dev@community list. I've updated 
https://cwiki.apache.org/confluence/display/COMDEV/FOSDEM+2016 with the 
information earlier discussed on this list. See you there!

Andrea

  Forwarded Message  
Date: Thu, 28 Jan 2016 09:21:24 +0100
From: Daniel Gruno

Hi folks!

FOSDEM is now less than two days away, so here's some practical
information, which you'll also find on the wiki:

SETUP:
The booth will be set up on Saturday between 9:00 and 10:00. The
conference starts at 10:00. Anyone willing to help out here, please meet
up at the K building a bit before 9.

SWAG:
Due to the new logo (and the uncertainty of whether we'd be able to use
it or not), we have been pressed for time, as we had very few days to
procure swag for this. Luckily, we had some awesome print shops help us
out, and we have the following items available (IN SMALL QUANTITIES!):

- t-shirts (various sizes/sexes)
- mugs (veeery few, probably gonna use them for coffee at the booth)
- key chains with LED lights
- fridge magnets (lots of those, like...hundreds!)
- round 3" powered-by stickers (loads of them)
- pens with full color logo
- small badges with logo (not a whole lot, 30-40 or so)
- beer coasters
- 180x80cm banner for the booth with a quadpod
- Some other stickers that Sally doesn't like ;)

I'll be very "Scottish" about this and divide it into two piles - one
for saturday, one for sunday, and only bring half the swag from my hotel
each day.

SWAG RULES:
No talk, no swag! If people want even a pen, it requires a conversation
with us. Do they know what the ASF does? Can they name 3 projects? Do
they know who our president is? etc etc. The more they talk, the better
swag they'll get :) Please be very sparse with handing out swag,
especially at first, or it'll be gone within 25 minutes.


BOOTH SCHEDULE:
See the wiki for exact project schedules.
The booth is open Saturday from 10:00 till 19:00,
and Sunday from 10:00 till 17:00. The schedule can be changed if more
projects show up. Besides, we have nearly 4 meters of booth space, so...

TEARDOWN:
teardown is on Sunday at 17:00 and should be done before 17:30. This
should be simple, but help is appreciated. Jimjag has dibs on the
banner, so I'll mail it to him once we're done using it.

Hope to see you there!

With regards,
Daniel.




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