http://blog.gmane.org/gmane.comp.gnome.ximian.openoffice hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4599 <pre>Dear fellow ooo-build hackers, as announced last year, the ooo-build project has joined forces with LibreOffice. With the successful LibreOffice 3.3 release, we'll now formally discontinue this project. Effective today, this mailing list will be switched off - please use the libreoffice&lt; at &gt;lists.freedesktop.org list instead, for everything development-related. See http://www.libreoffice.org/get-involved/developers/ for more information on LibreOffice development. Rest in peace go-oo, and long live LibreOffice! :) Best regards, and many thanks for your past and future contributions, </pre> Thorsten Behrens 2011-02-09T08:10:51 http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4597 <pre>First my apologize to address this topic to this list, because it is probably a bit off-topic, nevertheless, I'd appreciate if a developer could quickly feedback. I wrote an extension for OOo in Java which works fine in native OOo. Recently I switched to Debian Squeeze and am using the packaged OOo 3.2.1 which afaik is based on Go-oo. Here, this extension throws an exception Now my question: Are you aware a some features of the api that were disabled in Go-OO, which might cause this effect? Or some more stringent compiler options (i.e. a mistake in my programming that is tolerated in native OOo but not in Go-oo?) The same occurs on Ubuntu 10.10 with Libreoffice 3.3. I also checked with Sun-Java 6 in Debian, same result as with OpenJDK 6. Thanks for your support Dietmar </pre> Dietmar 2011-02-06T10:22:24 http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4594 <pre> Hi. I get this error while building new version of openoffice. I completely lost and can't solve this problem. ============= Building module cli_ure Entering /root/rpmbuild/BUILD/ooo-build-3.2.0.9/build/ooo320-m12/cli_ure/inc Entering /root/rpmbuild/BUILD/ooo-build-3.2.0.9/build/ooo320-m12/cli_ure/source Entering /root/rpmbuild/BUILD/ooo-build-3.2.0.9/build/ooo320-m12/cli_ure/version Entering /root/rpmbuild/BUILD/ooo-build-3.2.0.9/build/ooo320-m12/cli_ure/source/basetypes Entering /root/rpmbuild/BUILD/ooo-build-3.2.0.9/build/ooo320-m12/cli_ure/source/climaker Making: all_climaker.dpslo Entering /root/rpmbuild/BUILD/ooo-build-3.2.0.9/build/ooo320-m12/cli_ure/unotypes MONO_PATH=../unxlngi6.pro/bin: LD_LIBRARY_PATH=/root/rpmbuild/BUILD/ooo-build-3.2.0.9/build/ooo320-m12/solver/320/unxlngi6.pro/lib:../unxlngi6.pro/lib ../unxlngi6.pro/bin/climaker \ --out ../unxlngi6.pro/bin/cli_uretypes.dll \ --keyfile ../unxlngi6.pro/bin/cliuno.snk \ --assembly-version 1.0.4.0 \ --assembly-description "This assembly contains metadata for the StarOffice/OpenOffice.org API." \ --assembly-company "OpenOffice.org" \ /root/rpmbuild/BUILD/ooo-build-3.2.0.9/build/ooo320-m12/solver/320/unxlngi6.pro/bin/udkapi.rdb MONO_PATH=../unxlngi6.pro/bin:: Too many arguments. dmake: Error code 1, while making '../unxlngi6.pro/bin/cli_uretypes.dll' ERROR: Error 65280 occurred while making /root/rpmbuild/BUILD/ooo-build-3.2.0.9/build/ooo320-m12/cli_ure/unotypes rmdir /root/tmp/CDurRDEbTp </pre> Morgoth Evil 2011-01-05T09:09:38 http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4591 <pre>Dear fellow ooo-build hackers, no news to many of you, just to give a formal heads-up: we're in the process of joining forces with LibreOffice, and are currently merging most of the patches there. So going forward, this list and the go-oo.org website really don't make much sense anymore. Please move over to libreoffice&lt; at &gt;lists.freedesktop.org for technical discussions, or join us at #libreoffice on irc.freenode.net Cheers, </pre> Thorsten Behrens 2010-10-25T13:50:47 http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4576 <pre></pre> Gökçen Eraslan 2010-10-02T15:12:50 http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4572 <pre>Dear go-oo developeres, My name is Branislav Klocok and I am the leader of Slovak localization team of OOo. It was brought to my attention by one of the Slovak users of go-oo that the Slovak translation are not 100% up to date and I would like to ask you what is the process here in go-oo concerning translations? Do you take translations only from the OOo (which sometimes in not updated for Slovak since we are using a different build system) or you are having a another process? Best regards, </pre> Branislav Klocok 2010-10-01T15:59:27 http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4569 <pre>Dear Go-oo developers, Do you consider Go-oo project, your project, to be a fork of OpenOffice.org? General public opinion seems to be quite sure and general perception is that it is a fork or at least branch; considering Go-oo as fork is matter of habit for most forum speakers. My stance same is – Go-oo is a patchset, with a lively community, providing own build, forums, but still it is primarily a patchset. I would consider a bed news for whole open-source community if such important project would fork. Wikipedia is inconsistent here. This does not help. In OpenOffice.org Wikipedia entry (http://en.wikipedia.org/wiki/OpenOffice.org) is clearly stated that Go-oo is fork (details below). In Go-oo Wikipedia entry (http://en.wikipedia.org/wiki/Go-oo) is however: Go-oo .. is a concentrated set of patches for the cross-platform OpenOffice.org office suite. Details from OpenOffice.org Wikipedia entry (http://en.wikipedia.org/wiki/OpenOffice.org): [citation] Although branded as OpenOffice.org, the office suite included in most Linux distributions (including Ubuntu, openSUSE and Mandriva Linux) is actually a fork or an unofficial branch called Go-oo.[citation end] Are there any better articles on that topic? If yes, they should be added and replace the weaker existing. My reaction in “talk” page (http://en.wikipedia.org/wiki/Talk:OpenOffice.org): [citation] Go-oo is a patchset. Full stop. Go-oo team is committed to upstream the changes and they upmerge changes from official (Oracle driven) OO.o source. Therefore they are not a fork. Please check the Go-oo article they have it right there. There is NO official source (Go-oo site preferably) suggesting we are a fork. Even the links provided are not suggesting that or are of a questionable quality. I am suggesting to change the offending sentence: Although branded as OpenOffice.org, the office suite included in most Linux distributions (including Ubuntu, openSUSE and Mandriva Linux) is actually a fork or an unofficial branch called Go-oo.[9][10][11] to Application branded as OpenOffice.org in most Linux distributions (including Ubuntu, openSUSE and Mandriva Linux) extensively use patchset called [Go-oo], sometimes arguably [9][10] considered to be a special branch of OpenOffice.org. Any comments on this? (2 May 2010) [citation end] Reply from jonathon (is it someone relevant from this community?): [citation] It is a fork because it excludes code from upstream, and includes code that will not be included upstream. It is called "a special branch", precisely because it is a fork, with different bugs, features, and functions. (13 August 2010) [citation end] I was most struck by this statement: “it [go-oo] excludes code from upstream”. That completely breaks my go-oo perception. The 2.3.1 go-oo is build on top of 2.3.1 vanilla OOo. The 2.3.0 go-oo is build on top of 2.3.0 vanilla OOo etc. Or do I miss something important here? I somewhat see situation with go-oo and OpenOffice.org similar to Linux kernel. No distribution really use vanilla kernel but patched kernel using patches from existing patchsets and distribution own modifications. Similar is also that some kernel patches contains code never or hardly make it into the upstream (Suspend2/TuxOnIce, Colivas scheduler patches, proprietary drivers, various splash screens,..) I intend to use reply to this post (if there are any) as a reference to Wikipedia. Best Regards Espinosa </pre> espinosa_cz 2010-09-30T00:39:19 http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4565 <pre></pre> Jonas Finnemann Jensen 2010-09-27T19:47:17 http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4562 <pre>Hi folks, I installed and setup opengrok to run on go-oo.org on Friday. You can reach it at the following URL: http://opengrok.go-oo.org Please note that this is still experimental and may require some config changes. Don't hesitate to report the annoying stuffs you encounter when using it. If you need to have repos like l10n, libs-extern or libs-extern-sys indexed, please ask! I hope this will be useful for you! -- Cedric </pre> Cédric Bosdonnat 2010-09-27T09:29:11 http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4556 <pre></pre> Nadav Vinik 2010-09-25T05:52:43 http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4550 <pre>There have been some commits to the GNOME repo http://git.gnome.org/browse/ooo-build/ that have updated some translations. I'm pretty sure they have missed the THIS_REPO_IS_DEAD warning and just commited and went away. I don't know if you're tracking any activity from that repo; if not, I think setting up some triggers (e.g. an automatic email every time something in po/ gets changed) would help. </pre> Lucian Adrian Grijincu 2010-09-24T00:08:59 http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4549 <pre>Please CC me if you need any further info. </pre> Lucian Adrian Grijincu 2010-09-24T00:04:52 http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4548 <pre></pre> Miklos Vajna 2010-09-23T22:59:32 http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4541 <pre>Hi Noel, Rene told me that smoke test does not work in master. It ends with --- cut --- officeconnection.cxx:138:Assertion Test name: (anonymous namespace)::Test::test setUp() failed --- cut --- It is started when you just run build in smoktestoo_native. Could you please have a look? Best Regards, Petr </pre> Petr Mladek 2010-09-21T08:01:03 http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4537 <pre></pre> Gökçen Eraslan 2010-09-19T13:52:48 http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4536 <pre>Hello, I tried to build from the current ooo-build snaphot and I encountered an error. The sed command that is defined in bin/setup.in did not generate the expected result. I don't know why I have not triggered this error before. The currend sed commad has the following result: completelangiso="af This is wrong, eval dies on it (quote mismatch). The attached patch solved the problem. May I push it? Best regards, Andras </pre> Andras Timar 2010-09-18T20:52:19 http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4529 <pre>Hi, I am happy to announce 3.3-alpha1 release of ooo-build master. You might find it at http://download.go-oo.org/3.3/ooo-build-3.2.98.1.tar.gz http://download.go-oo.org/3.3/ooo-build-3.2.98.1.tar.gz.md5 It took very long time because of many changes, vacations, ... New source tarballs: -------------------- As announced in other mails, we started to move patches from ooo-build to the OOo git sources. It means that the plain OOo source tarballs are not longer usable. Instead, ooo-build-&lt;version&gt;-&lt;piece&gt;.tar.bz2 are needed. They are automatically downloaded by the script ./download. Alternatively, you might get them at http://download.go-oo.org/3.3/ We started to provide the prebuilt tarballs again because people had troubles with CGIT... The tarballs has the structure: + ooo-build-&lt;version&gt;-&lt;piece&gt; + module1 + prj + source + module2 +prj This structure is typical for software sources. It will be nice for the split build. We really need got forward and get split build into life. All module dirs are automatically moved into single dir build/ooo-build-&lt;version&gt; during non-split build. If you want to unpack and move somewhere else, you might do it by the helper script http://cgit.freedesktop.org/ooo-build/ooo-build/plain/bin/ooo-unpack-sources It will be ooo-build/bin in the next release. Configure options: ------------------ + use --without-git if you want the prebuilt sources; otherwise, git clone is created by default + use --with-source-version if you want to use another version of the OOo piece sources; this is useful for test builds with non-official tarballs; it will be even more useful in the future after we move "all" patches from ooo-build and there won't be any changes in ooo-build between releases + remove obsolete --with-tag option New processes: -------------- + suggested workflow for packagers and developers is described at http://www.freedesktop.org/wiki/Software/ooo-build/BuildingIt#Buildingfordifferentpurposes Known bugs: ----------- + application stop immediately after the first start; it is because the new framework for registering extensions; we need to find a solution for it + GNOME quickstarter is enabled by default + unopkg does not add .zip extensions (see a problems with PostgreSQL driver extension here) + more at http://alturl.com/qaq5 Upcoming deadlines: ------------------- I would like to do another release (alpha2/beta1) within next two weeks. Status of branches and plans: ----------------------------- + master (3.3 development): + currently based on ooo330-m7 + few late features allowed; all should concentrate on bugfixing from now on + alpha2/beta1 planed within next two weeks + ooo-build-3-2-1 (3.2 maintenance mode): + only save and well tested fixes are allowed in the common sections + security bug fix release at http://download.go-oo.org/OOO320/ooo-build-3.2.1.6.tar.gz + might do more releases for a maintenance update in the future Changes in this release against 3.2.1.6 (filtered NEWS file): ------------------------------------------------------------- ooo-build-3.2.98.1 (3.2.1-alpha1) + features: + based on ooo330-m7 [all] + RTF export rewrite [Miklos] + writer navigation [Ovcica, Cédric] + new Typography toolbar extension [Andras] + remove obsolete Industrial icon theme [Kendy] + update Extensionaids to version 20100813 [KAMI] + update Numbertext extension to version 0.9.2 [KAMI] + update WatchWindow extension to version 1.1.2.1 [KAMI] + update Magyar Linux Libertine fonts to version 20100611 [Andras] + common bits: + smoketest crasher (i#112758) [Rene] + gray read-only styles (i#85003) [Thorsten] + Accelerators for OK/Cancel buttons in GTK (bnc#608572) [Kohei] + Calc bits: + cell borders not saved (bnc#612263) [Cédric] + external reference rework (bnc#628876) [Kohei] + Flat MSO XML file type detection (bnc#631993) [Muthu] + disable custom tab colors in high contrast mode [Kohei] + display correct field in data pilot (bnc#629920) [Kohei] + Watch Window extension doesn't show sheet name (bnc#604638) [Kohei] + Draw bits: + associate application/x-wpg with oodraw (bnc#589624) [Petr] + Impress bits: + More on avmedia soundhandler (i#83753, bnc#515553) [Thorsten] + Writer bits: + ww8 styles import (i#21939) [Cédric] + hairline table borders export [Miklos] + saving new document comparison data [Thorsten] + Ruby in MS Word format (i#79246) [Cédric, Eike] + OOXML: + chart XLSX export [Bubli] + notes XLSX export/import [Muthu] + showDropDown PPTX export [Muthu] + page setting XLSX export [Muthu] + graph PPTX import (bnc#593611) [Radek] + title PPTX import (bnc#621744) [Radek] + pageSetup, dateCompatibility in XLSX [Muthu] + differences between ECMA and ISO in DOCX [Cédric] + docprops, page-date, and paneexp XLSX import [Muthu] + better internal hlinks XLSX export (bnc#594248) [Bubli] + numbering roundtripping issues in DOCX (bnc#569266) [Cédric] + untis translation from EMU in PPTX import (bnc#621739) [Radek] + group shapes geometry calculation in PPTX import (bnc#621739) [Radek] + VBA bits: + changes in event handling [Noel] + more container control fixes [Noel] + hlink/macro XLS import/export [Noel] + UNO-ise msvbahelper for the split build [Noel] + more on invalid code name import for sheet (bnc#507768) [Noel] + Win32 bits: + use --disable-nss-module [Tor] + help content: + no limit for minimal password length [Andras] + l10n bits: + German translation fixes [Rene] + Hungarian translation fixes [Andras] + build bits: + Add distcc support [Miklos] + new "make test" target [Cédric] + subsequenttest failure [Thorsten] + fix --with-srcdir handling [Fridrich] + various cws-extract improvements [Miklos] + update prebuilt cli dlls for OOo-3.3 [Petr] + new --with-system-mdds configure option [Andras] + allow using system cppunit with stlport [Caolan] + add offset info to idlc errors (i#81780) [Cédric] + do not install obsolete Writer-javamail.xcu [Rene] + new script "ooo-pack-sources" for test builds [Petr] + new --disable-fetch-external configure option [Rene] + use --with-vba-package-format for all distros [Thorsten] + moving ooo-build patches to ooo git sources [Kendy, others] + new script "g" to work with the cloned git repos [Kendy, others] + Frugalware: + update branding [Miklos] + switch to OpenJDK [Miklos] + use system-lucene [Miklos] + FSFhu: + update config [Andras] + update branding [Andras] + progress bar on the splash screen [Andras] + Gentoo: + better check for libdb [Hanno] + Novell bits: + update Win32 branding [Tor] + use --without-junit on Win32 and openSUSE &lt; 11.2 [Tor, Thorsten] + OxygenOffice bits: + update config [KAMI] + Impress toolbar fix [KAMI] + add Magyar Linux Libertine fonts [KAMI] + fix progress bar in the splash screen [KAMI] + set CaptionOrderNumberingFirst true for Hungarian [Andras, KAMI] + Ubuntu bits: + support to turn off locking for cifs [Chris] + pending: + bulk conversion [Muthu, Thorsten] + support mono components and extensions [Noel] </pre> Petr Mladek 2010-09-16T15:17:12 http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4514 <pre>Hi, there is still confusion how to use ooo-build after we started to move the diffs to git. It is clear that developers and packagers has a bit different needs. I tried to describe the current suggested workflow at http://www.freedesktop.org/wiki/Software/ooo-build/BuildingIt#Buildingfordifferentpurposes There are currently two FIXME's: 1. I think that --with-git=/path-to-another-clone-dir should cause that the other clone is used as reference to create the new clone; the new clone still should push directly to freedesktop. Is this true? Kendy, Thorsten? 2. I think that --with-tag option does not longer make sense. If you want to use another ooo sources, you should use the new --with-source-version option that is more descriptive I am going to remove the --with-tag option Feel free to suggest a better workflow. Point out problems with the current one, ... Add more tips, e.g. the Fridrich's --with-src dir, ... BTW: I think that we can't longer support build of pure OOo sources. I think about to remove the related things from configure/download/unpack to make them a bit easier. Best Regards, Petr </pre> Petr Mladek 2010-09-10T18:52:43 http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4512 <pre>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, good people, I would like to explain once again what mean the variable SRCDIR. If one passes the --with-srcdir option, the SRCDIR will be set to a dedicated directory where ./download will download tarballs and other files that are used for build. This is useful if you have several builds coexisting on the same machine. Because it is saving quite a considerable amount of space since a lot of the tarballs will be having only one instance on the disk. Now, if you don't pass the --with-srcdir option, the SRCDIR will be set to the subdirectory "src" in ooo-build sources. But this is a coincidence. If you want to refer to that directory as such, you should use TOOLSDIR/src. TOOLSDIR/src contains files that are part of ooo-build tarball and not downloaded during the build process. Please, keep this in mind because once the SRCDIR and TOOLSDIR/src get messed up, it is pretty complicated to unwind. Cheers Fridrich -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkyF7t4ACgkQu9a1imXPdA981wCaA+ai3W1OneafGhzSgVm4ufi9 1egAoIVR3NSIIBd2WOi6L55Ya5Cs9VjJ =tfzZ -----END PGP SIGNATURE----- </pre> Fridrich Strba 2010-09-07T07:50:54 http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4511 <pre></pre> Miklos Vajna 2010-09-06T20:28:48 http://comments.gmane.org/gmane.comp.gnome.ximian.openoffice/4509 <pre>Hi Kendy, I had to improve the "g" script to be able to tag the git repositories and push the tags. Please, find the diff attached. The changes are: + add quotes around the message string for commit command; I wonder how it worked + git tag does not support --message=&lt;msg&gt;, so I had to pass -m &lt;msg&gt; as a single paramete; I think that we could actually use the same hack for "commit" as well + the extra parameter for "tag" is not file path + the new tag is not detected by "status", so I need to force the "push" Any comments before I commit it ;-) Best Regards, Petr </pre> Petr Mladek 2010-08-31T13:20:05 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.gnome.ximian.openoffice