Re: Tips on uploading builds for 4.1.4-RC
> On Aug 5, 2017, at 7:22 PM, Andrea Pescettiwrote: > > Jim Jagielski wrote: >> My prep scripts are now on devtools/release-scripts. > > Thanks, one things less to redo next time! > >>> ## 3. How is the source code obtained? >>> $ cd instsetoo_native/util >>> $ dmake aoo_srcrelease >> % pwd >> /Users/jim/src/asf/code/aoo-414/main/instsetoo_native/util >> % dmake aoo_srcrelease >> dmake: makefile.mk: line 26: Error: -- Include file settings.mk, not found > > I've just tested on my AOO414 build tree and it works: I get the zip, gz, bz2 > and also the tar just in case. > > Had you initialized your shell, same as when you build? (you run the > OS-dependent shell script as suggested by configure). > > That was the rub. I had to source the env script. Thx. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Tips on uploading builds for 4.1.4-RC
Jim Jagielski wrote: My prep scripts are now on devtools/release-scripts. Thanks, one things less to redo next time! ## 3. How is the source code obtained? $ cd instsetoo_native/util $ dmake aoo_srcrelease % pwd /Users/jim/src/asf/code/aoo-414/main/instsetoo_native/util % dmake aoo_srcrelease dmake: makefile.mk: line 26: Error: -- Include file settings.mk, not found I've just tested on my AOO414 build tree and it works: I get the zip, gz, bz2 and also the tar just in case. Had you initialized your shell, same as when you build? (you run the OS-dependent shell script as suggested by configure). All source packages so far were obtained on a Mac so it should definitely work on a Mac. It is an "ant" task. I have ant 1.9.2 on the machine where I tried, but any version of ant that passes ./configure should be OK. I can of course provide the packages if needed, but my build tree has an extra patch compared to the current status of AOO414 so I would need to prepare them again tomorrow (European time). Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Tips on uploading builds for 4.1.4-RC
Am 05.08.2017 um 20:46 schrieb Jim Jagielski: > My prep scripts are now on devtools/release-scripts. Since I am building for Windows in a VM I can use your hash-script on Ubuntu. I only had to extend it to sign *.exe ;-) Matthias >> On Aug 5, 2017, at 1:13 PM, Andrea Pescettiwrote: >> >> >> ## 3. How is the source code obtained? >> >> It is *NOT* obtained via SVN export as one could imagine. You get it in a >> source tree by running: >> $ cd instsetoo_native/util >> $ dmake aoo_srcrelease >> > % pwd > /Users/jim/src/asf/code/aoo-414/main/instsetoo_native/util > % dmake aoo_srcrelease > dmake: makefile.mk: line 26: Error: -- Include file settings.mk, not found > > ?? > - > 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: Tips on uploading builds for 4.1.4-RC
My prep scripts are now on devtools/release-scripts. > On Aug 5, 2017, at 1:13 PM, Andrea Pescettiwrote: > > > ## 3. How is the source code obtained? > > It is *NOT* obtained via SVN export as one could imagine. You get it in a > source tree by running: > $ cd instsetoo_native/util > $ dmake aoo_srcrelease > % pwd /Users/jim/src/asf/code/aoo-414/main/instsetoo_native/util % dmake aoo_srcrelease dmake: makefile.mk: line 26: Error: -- Include file settings.mk, not found ?? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Tips on uploading builds for 4.1.4-RC
I see that https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release does not contain many details on where/how to upload builds once we reach (and it looks like we are almost there, thanks to everybody who helped!) the Release Candidate stage. Here are some notes based on past experiences (feel free to copy them to the wiki as needed): ## 1. Files and folders structure See http://archive.apache.org/dist/openoffice/4.1.3/ for an example. Note in particular that we have: source/ - more on this below binaries/ - they do include SDK, but they do NOT include kid You'll probably want to assemble a quick script to move things into the right place. Then please copy it to http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/ (I wrote a similar script but can't find it right now). Note: we can't change the structure since our download pages assume it is identical for any 4.1.x release. ## 2. Everything must come with hashes and signatures. http://www.apache.org/legal/release-policy.html#release-signing All files need: - md5 hash as filename.md5 - sha256 hash as filename.sha256 - A detached signature as filename.asc see https://www.apache.org/dev/release-signing.html#openpgp-ascii-detach-sig for details Who should make the signatures? - The Release Manager signs source - Other packages are signed by the person who provided them Again, script should be copied to devtools/. ## 3. How is the source code obtained? It is *NOT* obtained via SVN export as one could imagine. You get it in a source tree by running: $ cd instsetoo_native/util $ dmake aoo_srcrelease I've modified it for 4.1.4 see https://bz.apache.org/ooo/show_bug.cgi?id=127148 and also https://bz.apache.org/ooo/show_bug.cgi?id=126605 so the output will not be identical to 4.1.3 as some minor test files were not handled properly. We still get the three formats (ZIP, gz, bz2). This will probably change after 4.1.x as discussed a long time ago, but for 4.1.4 we should still use the three of them. ## 4. How are packages uploaded? It's going to be a huge SVN commit to the dev area. My experience from a couple years ago: - The SVN server has good reliability but it is slow, much slower than I expected. - First, assemble all the tree in one location. In my case, I had setup a space on fast-connected server where people uploaded their builds. This is the best option, otherwise people will have to wait for each other and do a full checkout (slow and huge). - Then structure files/folders as above - Then do the SVN commit. Due to speed issues, I recommend to script this and upload one language at a time - unless the SVN server speed has increased dramatically, but still you need one minute to script it so it's worth doing. In my case, the SVN server was reliable but the gigantic SVN commit took something like 20 hours from a machine that had no bandwidth problems; script it and be safe (even if I expect that speed is better now). Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Expat 2.2.3 and Windows woes
W00t!! I am starting on the Linux 32, 64 and macOS builds as we speak. > On Aug 5, 2017, at 3:52 AM, Matthias Seidel> wrote: > > That looks like a successful build to me! > > I will start a build on my machine based on Rev. 1804159... > > > Am 05.08.2017 um 00:57 schrieb Matthias Seidel: >> Done! >> >> You can see the results here: >> https://ci.apache.org/projects/openoffice/buildlogs/win41x/log/wntmsci12.pro.build.html >> >> Bedtime for me... ;-) >> >> >> Am 05.08.2017 um 00:38 schrieb Jim Jagielski: >>> r1804159 >>> >>> Just when you thought this work-around couldn't get uglier :) >>> >>> Let's kick off another, please. On Aug 4, 2017, at 6:17 PM, Matthias Seidel wrote: https://ci.apache.org/projects/openoffice/buildlogs/win41x/main/expat/wntmsci12.pro/misc/logs/expat.txt Am 05.08.2017 um 00:14 schrieb Jim Jagielski: > Grr... > > 1 module(s): > expat > need(s) to be rebuilt > > Reason(s): > > ERROR: error 65280 occurred while making > /cygdrive/e/slave14/aoo-w741x/build/main/expat > > When you have fixed the errors in that module you can resume the build by > running: > > build --from expat > > > I really wish I had more direct access to a Win build environ. Or > at least that the buildbot was more vocal. :/ > - > 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: Expat 2.2.3 and Windows woes
Am 05.08.2017 um 09:52 schrieb Matthias Seidel: > That looks like a successful build to me! > > I will start a build on my machine based on Rev. 1804159... Meanwhile I installed the build from our buildbot. Quick and easy. Note: The environment of the Windows buildbot is slightly different and the build is for testing only! > > > Am 05.08.2017 um 00:57 schrieb Matthias Seidel: >> Done! >> >> You can see the results here: >> https://ci.apache.org/projects/openoffice/buildlogs/win41x/log/wntmsci12.pro.build.html >> >> Bedtime for me... ;-) >> >> >> Am 05.08.2017 um 00:38 schrieb Jim Jagielski: >>> r1804159 >>> >>> Just when you thought this work-around couldn't get uglier :) >>> >>> Let's kick off another, please. On Aug 4, 2017, at 6:17 PM, Matthias Seidelwrote: https://ci.apache.org/projects/openoffice/buildlogs/win41x/main/expat/wntmsci12.pro/misc/logs/expat.txt Am 05.08.2017 um 00:14 schrieb Jim Jagielski: > Grr... > > 1 module(s): > expat > need(s) to be rebuilt > > Reason(s): > > ERROR: error 65280 occurred while making > /cygdrive/e/slave14/aoo-w741x/build/main/expat > > When you have fixed the errors in that module you can resume the build by > running: > > build --from expat > > > I really wish I had more direct access to a Win build environ. Or > at least that the buildbot was more vocal. :/ > - > 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: Expat 2.2.3 and Windows woes
That looks like a successful build to me! I will start a build on my machine based on Rev. 1804159... Am 05.08.2017 um 00:57 schrieb Matthias Seidel: > Done! > > You can see the results here: > https://ci.apache.org/projects/openoffice/buildlogs/win41x/log/wntmsci12.pro.build.html > > Bedtime for me... ;-) > > > Am 05.08.2017 um 00:38 schrieb Jim Jagielski: >> r1804159 >> >> Just when you thought this work-around couldn't get uglier :) >> >> Let's kick off another, please. >>> On Aug 4, 2017, at 6:17 PM, Matthias Seidel>>> wrote: >>> >>> https://ci.apache.org/projects/openoffice/buildlogs/win41x/main/expat/wntmsci12.pro/misc/logs/expat.txt >>> >>> >>> Am 05.08.2017 um 00:14 schrieb Jim Jagielski: Grr... 1 module(s): expat need(s) to be rebuilt Reason(s): ERROR: error 65280 occurred while making /cygdrive/e/slave14/aoo-w741x/build/main/expat When you have fixed the errors in that module you can resume the build by running: build --from expat I really wish I had more direct access to a Win build environ. Or at least that the buildbot was more vocal. :/ - 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