Re: Apache OpenOffice Templates and Extensions new sites
Let me start by saying that by now at registration time language preferences are kept into account. We made this change because we got a number of complaints, especially from French folks. For improving the localization feel free to pass me privately some strings, or if you wish to contribute more heavily we could pass the .po file onto you. Let me know what works best for you. Thanks, Roberto 2016-01-14 15:45 GMT+01:00 FR web forum : > Bravo > I see that translation in french is not complete. > Some sentences are in english. > How can we contribute to translate it? > > - Mail original - > De: "Roberto Galoppini" > À: "dev" > Envoyé: Mardi 12 Janvier 2016 21:17:19 > Objet: Apache OpenOffice Templates and Extensions new sites > > Hi all, > > Over the last few months we have been busy redesigning the Apache > OpenOffice Templates and Extensions experience, basically incorporating > feedback and simplifying the existing procedures. > > As a result both sites are now easy to use both for end-users - see how > prominent is the search or how using different colors we made trivial to > understand for which application a given template has been designed for - > and admins - the most common actions are all in a top bar, and uploading is > now trivial. > > In the process we redesigned the look and feel, iconized all menu items and > more. > > I wrote a quick blog post at my blog, see > > http://robertogaloppini.net/2016/01/12/about-contributing-to-apache-openoffice/ > > Roberto > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: linux32 buildbot
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. -- -- 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: Apache OpenOffice Templates and Extensions new sites
Bravo I see that translation in french is not complete. Some sentences are in english. How can we contribute to translate it? - Mail original - De: "Roberto Galoppini" À: "dev" Envoyé: Mardi 12 Janvier 2016 21:17:19 Objet: Apache OpenOffice Templates and Extensions new sites Hi all, Over the last few months we have been busy redesigning the Apache OpenOffice Templates and Extensions experience, basically incorporating feedback and simplifying the existing procedures. As a result both sites are now easy to use both for end-users - see how prominent is the search or how using different colors we made trivial to understand for which application a given template has been designed for - and admins - the most common actions are all in a top bar, and uploading is now trivial. In the process we redesigned the look and feel, iconized all menu items and more. I wrote a quick blog post at my blog, see http://robertogaloppini.net/2016/01/12/about-contributing-to-apache-openoffice/ Roberto - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
linux32 buildbot
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. signature.asc Description: OpenPGP digital signature
