Re: 4.1.3 building
Patricia Shanahan wrote: 1. My current policy for release blocker is to grant it immediately if it seems obvious to me that a fix is needed to build 4.1.3. I will also do so based on prior security@ discussion. Otherwise, I'll ask for input on dev@ before deciding. OK. 4.1.4 is a good fallback solution for important but not critical bugs anyway. 2. I would like to get a list of environments in which 4.1.3 has been successfully built. I'll announce time to build a release candidate when it builds in the required environments. I've built AOO413 on Linux-64 with the following details: - CentOS 5 VM as described in https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#CentOS_5 - Source revision r1761818 - Real source revision r1761381 (both are obtained using "svn info"; the latter is the one that matters, as the former increases for any commit in any ASF project) - Build scripts as per http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.3/unxlngix6/ Sample builds (English, German, Italian) from a few hours ago -but not from my latest build- are at http://home.apache.org/~pescetti/openoffice-4.1.3-dev-r1761683/ There are a few differences in the configure options, namely: 1) Build Version is a bit richer in https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Configure but I went for the more compact one from the 4.1.2 scripts 2) Language list is much longer in the 4.1.2 scripts and I maintained that one - even though I usually build with fewer languages 3) Package format does not have "installed" in the 4.1.2 scripts, which looks OK (we only ship RPM+DEB) 4) We were using ant 1.7.1 (from the repositories?) for 4.1.2 builds, see http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.2/unxlngix6/config.log?revision=1736814=markup#l1134 ; we download and use 1.9.7 now; I haven't checked this properly yet, but we had a recent discussion with Kay saying that configure (which checks for ant >= 1.7.0) was wrong. 5) We are now explicitly passing --without-stlport which looks good since (if I recall correctly) this was the default anyway. 6) We are now passing --without-junit ; I'm still not completely clear if this makes any difference in our case. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
4.1.3 building
1. My current policy for release blocker is to grant it immediately if it seems obvious to me that a fix is needed to build 4.1.3. I will also do so based on prior security@ discussion. Otherwise, I'll ask for input on dev@ before deciding. 2. I would like to get a list of environments in which 4.1.3 has been successfully built. I'll announce time to build a release candidate when it builds in the required environments. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Ready to setup release build machines?
Ariel Constenla-Haile wrote: On Wed, Sep 21, 2016 at 12:10:29AM +0200, Andrea Pescetti wrote: (the way it is now; I haven't checked https://bz.apache.org/ooo/show_bug.cgi?id=127120 yet) it uses only packages from CentOS and EPEL repositories, plus custom Ant and Perl as the versions shipping with CentOS 5 are too old. With the commit for this bug, in AOO413 you can use Perl from CentOS repos Thanks Ariel, I've now regenerated the VM using system Perl. Everything worked correctly. https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#CentOS_5 is now updated to work with distribution-supplied packages only. The only package we don't download from the distribution is Ant, but that is unavoidable. So the recipe is now as simple and clean as it can be. New Linux-64 binaries are uploaded to http://home.apache.org/~pescetti/openoffice-4.1.3-dev-r1761683/ For Patricia's roadmap, this means that anyone can take the recipe at https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#CentOS_5 and produce a full set of Linux release builds from scratch, using documented processes and tools, in less than 24 hours (perhaps a bit more considering we are all volunteers, but still a matter of days and not months). Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Fwd: 4.1.3_release_blocker requested: [Issue 127127] English dictionary included in 4.1.3 installer is outdated
Am 09/21/2016 10:17 PM, schrieb Andrea Pescetti: Patricia Shanahan wrote: How would granting 4.1.3_release_blocker on this impact progress on the builds? It wouldn't have had a major impact, but in this case (as later clarified in the issue) the blocker request is simply a misunderstanding. if the following is and was always the case then it's maybe my fault as I said Pedro to flag the issue as blocker when he wanted to fix the outdated dic versions in 4.1.3. Sorry when I've produced this confusion. As a general rule, we first apply fixes on trunk and then copy them to AOO413. Dictionary updates were considered "release-specific" in this case and thus only applied to AOO413, but it's clearer to always update on trunk and then port; so I've just merged the fixes back to trunk -where they conflicted, since we had already updated a few dictionaries on trunk- to align the branches. Anyway, progress on the builds is independent of specific issues; once you deem that people should start building (i.e., that no important issues are left; it seems we do not have pending work), just state the revision that people should build and we'll coordinate for the Release Candidate build. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Fwd: 4.1.3_release_blocker requested: [Issue 127127] English dictionary included in 4.1.3 installer is outdated
Patricia Shanahan wrote: How would granting 4.1.3_release_blocker on this impact progress on the builds? It wouldn't have had a major impact, but in this case (as later clarified in the issue) the blocker request is simply a misunderstanding. As a general rule, we first apply fixes on trunk and then copy them to AOO413. Dictionary updates were considered "release-specific" in this case and thus only applied to AOO413, but it's clearer to always update on trunk and then port; so I've just merged the fixes back to trunk -where they conflicted, since we had already updated a few dictionaries on trunk- to align the branches. Anyway, progress on the builds is independent of specific issues; once you deem that people should start building (i.e., that no important issues are left; it seems we do not have pending work), just state the revision that people should build and we'll coordinate for the Release Candidate build. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How do all the binaries get built?
I'll set one up in the next day. > On Sep 20, 2016, at 6:25 PM, Andrea Pescettiwrote: > > On 19/09/2016 Jim Jagielski wrote: >> If useful, I can replace my 64bit CentOS5 vm with a 32bit one. > > It would be useful (to have more coverage) to test > https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#CentOS_5 > on a 32-bit VM, and adapting -it's trivial- the script at > http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.3/ > to check that we have a good recipe to obtain Linux-32 binaries as well as > the Linux-64 binaries I've just uploaded to > http://home.apache.org/~pescetti/openoffice-4.1.3-dev-r1761552 > > Thanks, > 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
Re: [PROPOSAL] Buildbot builds should include mor than en-US only
Where is this documented? I can see the ./configure line in the puppet files but we should also have this on a wiki someplace, right? > On Sep 19, 2016, at 2:08 PM, Marcuswrote: > > I remember that old times at Sun where we have done builds with more than > just en-US. > > In order to cover problems that could be language-related we have built: > > - en-US - as default > - de - for the lazy German guys ;-) , can be left out now > - pt - as these language has mostly the longest strings > - one Asian language (ko, ja, zh-CN, zh-TW) to cover BIDI and font > problems > > So, I suggest to expand the build.lst to this setup. > > Marcus > > - > 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
Fwd: 4.1.3_release_blocker requested: [Issue 127127] English dictionary included in 4.1.3 installer is outdated
How would granting 4.1.3_release_blocker on this impact progress on the builds? Forwarded Message Subject: 4.1.3_release_blocker requested: [Issue 127127] English dictionary included in 4.1.3 installer is outdated Date: Wed, 21 Sep 2016 18:37:17 + From: bugzi...@apache.org Reply-To: dev@openoffice.apache.org To: dev@openoffice.apache.org Pedrohas asked for 4.1.3_release_blocker: Issue 127127: English dictionary included in 4.1.3 installer is outdated https://bz.apache.org/ooo/show_bug.cgi?id=127127 - 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
4.1.3_release_blocker requested: [Issue 127127] English dictionary included in 4.1.3 installer is outdated
Pedrohas asked for 4.1.3_release_blocker: Issue 127127: English dictionary included in 4.1.3 installer is outdated https://bz.apache.org/ooo/show_bug.cgi?id=127127 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Windows 10 ./bootstrap failure
I use this URL for successfully downloading dmake: http://sourceforge.net/projects/oooextras.mirror/files/dmake-4.12.tar.bz2 HTH Marcus Am 09/21/2016 07:26 PM, schrieb Patricia Shanahan: I missed a couple of configure parameter changes I need. On 9/21/2016 10:03 AM, Patricia Shanahan wrote: I believe I have done all the preliminary steps. configure appeared to work, but I have a persistent bootstrap failure: ... all external libraries present downloading dmake-4.12.tar.bz2 downloading to C:/OpenOfficeDev/AOO413/ext_sources/dmake-4.12.tar.bz2.part download from http://dmake.apache-extras.org.codespot.com/files/dmake-4.12.tar.bz2 failed (404 Not Found) download failed epm-3.7.tar.gz exists making and entering C:/OpenOfficeDev/AOO413/main/solenv/wntmsci12.pro/misc/build/ can not find the dmake package - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Windows 10 ./bootstrap failure
I missed a couple of configure parameter changes I need. On 9/21/2016 10:03 AM, Patricia Shanahan wrote: I believe I have done all the preliminary steps. configure appeared to work, but I have a persistent bootstrap failure: ... all external libraries present downloading dmake-4.12.tar.bz2 downloading to C:/OpenOfficeDev/AOO413/ext_sources/dmake-4.12.tar.bz2.part download from http://dmake.apache-extras.org.codespot.com/files/dmake-4.12.tar.bz2 failed (404 Not Found) download failed epm-3.7.tar.gz exists making and entering C:/OpenOfficeDev/AOO413/main/solenv/wntmsci12.pro/misc/build/ can not find the dmake package - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Windows 10 ./bootstrap failure
I believe I have done all the preliminary steps. configure appeared to work, but I have a persistent bootstrap failure: ... all external libraries present downloading dmake-4.12.tar.bz2 downloading to C:/OpenOfficeDev/AOO413/ext_sources/dmake-4.12.tar.bz2.part download from http://dmake.apache-extras.org.codespot.com/files/dmake-4.12.tar.bz2 failed (404 Not Found) download failed epm-3.7.tar.gz exists making and entering C:/OpenOfficeDev/AOO413/main/solenv/wntmsci12.pro/misc/build/ can not find the dmake package - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Release-Planung
Hallo Michael, > Am 21.09.2016 um 07:06 schrieb Dr. Michael Stehmann >: > > Hallo, > > wer etwas über die Release-Planung unseres Projekts erfahren will, aber > sich nicht durch die internationale dev-ML lesen möchte: > > https://blogs.apache.org/OOo/entry/stop_the_lazy_season_start > > Es ist nur ein grober Aufriss, aber es gilt auch das Motto: Erst wenn es > fertig ist, wird es verbreitet. Super! Ich freue mich, dass es nun doch weitergeht. Und bugfixes sind tatsächlich an manchen Stellen nötig. Bin sehr neugierig, welche dies dann gewesen sein werden. Danke für den Hinweis! Gruß Günter - To unsubscribe, e-mail: dev-de-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-de-h...@openoffice.apache.org
Re: Apache OpenOffice on google+
I am quite sure it was Rob Weir who managed it. As for the AOO-community (https://plus.google.com/u/0/communities/103683488250592271079) there are some members listed as "Moderator" who still should have access/rights to the profile. Some of them might be still active. regards Matthias Am 20.09.2016 um 21:47 schrieb Marcus: > Am 09/19/2016 01:11 PM, schrieb Matthias Seidel: >> Is anyone actually moderating the AOO-profile on google+? (This >> mailadress is listed as contact) >> https://plus.google.com/u/0/+openoffice/posts > > IMHO Rob Weir has managed this until he has left. I don't know who is > managing this now or is able to access the account. Does anybody else > know? > >> It has been quite active sometimes but now there is no news since >> 29.10.2015. >> >> Maybe a good place to announce the upcoming 4.1.3? > > Yes, sure. Thanks in the meantime. :-) > > Marcus > > > - > 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: Last call for 4.1.3 patches
I installed the german DEB on Ubuntu 16.04.1 (64bit) So far everything is working as expected... regards Matthias Am 21.09.2016 um 01:04 schrieb Andrea Pescetti: > On 17/09/2016 Mechtilde wrote: >> Am 17.09.2016 um 07:25 schrieb Mechtilde: >>> is there a first "nightly build for version 4.1.3 available? >> I forgot: >> my system is Debian 64-bit > > Buildbots aside (they were not working last time I checked), you can > use the 4.1.3-dev builds at > > http://home.apache.org/~pescetti/openoffice-4.1.3-dev-r1761552/ > > ...and I've already spammed three different threads, so I'll stop here! > > DEBs are completely untested, so testing is at your own risk as usual. > > Regards, > Andrea. > > - > 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: Fwd: [Issue 125147] CRASH applying styles to text
On 9/19/2016 9:20 AM, Pedro Giffuni wrote: ... Given this is already late you should probably reconsider bringing in some fixes to known bugs. If the idea is just that 4.1.3 = 4.1.2 + CVE-2016-15-13, then it seems to be a huge waste of bandwidth for both mirrors and end users. All just IMHO, ... From a bandwidth point of view, the end users are what matters - they generate the tens of thousands of transfers. If we release 4.1.3 with release notes and press releases that say what is in it, they can decide for themselves whether to download or not. If we effectively combine 4.1.3 with 4.1.4 and delay it until we get more fixes in, the end users don't get that choice. In addition to the security fixes, in my view a major objective of 4.1.3 is to reestablish the ability to release AOO. The more often we produce point releases, the better we will get at generating them, and the less vulnerable we will be if a security issue needs to be fixed quickly. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Release-Planung
Am 21.09.2016 um 07:50 schrieb Dave: > Danke habe den Blog gerade gelesen. Das macht einem Mut! > Schade, dass Du das im Blog nicht kommentieren kannst. Aber es ist auch nachvollziehbar, warum dort diese Funktion abgeschaltet ist. Gruß Michael signature.asc Description: OpenPGP digital signature