URGENT: Need to build new version based on 4.1.4

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
73 messages Options
1234
Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.5-dev builds

Matthias Seidel
Am 21.11.2017 um 19:35 schrieb Dave Fisher:
> Hi -
>
> Both regressions are fixed in the new build.
>
> Also, it looks like all of the versioning has been changed correctly. At least on the about box and readme files.

The update URL is still pointing to 4.1.4:
http://svn.apache.org/repos/asf/openoffice/branches/AOO415/main/instsetoo_native/util/openoffice.lst

Windows builds are ready for testing:
https://home.apache.org/~mseidel/AOO-builds/AOO-415-Dev/

Regards, Matthias

>
> I tried to test issue 127600 but I can’t understand what was done in the first place.
>
> Regards,
> Dave
>
>> On Nov 20, 2017, at 10:18 AM, Larry Gusaas <[hidden email]> wrote:
>>
>> Database & spreadsheet regressions fixed.
>> Larry
>>
>> On 2017-11-20, 9:49 AM Jim Jagielski wrote:
>>> I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
>>> AOO415 branch) available for fun and games (and testing) at:
>>>
>>>     http://home.apache.org/~jim/AOO-builds/
>>>
>>> I've built all langs but have just uploaded: de, en-US, es, fr
>>> and ja (for now). Let me know if people want/need others
>>> uploaded.
>>>
>>> __________
>>>
>>
>> --
>> _________________________________
>>
>> Larry I. Gusaas
>> Moose Jaw, Saskatchewan Canada
>> Website: http://larry-gusaas.com
>>
>> "An artist is never ahead of his time but most people are far behind theirs." - Edgard Varese
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>


smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.5-dev builds

Damjan Jovanovic
In reply to this post by Jim Jagielski
Thank you, but when are these 4.1.x releases going to stop?

We have so much lined up for 4.2.0.

Damjan

On Mon, Nov 20, 2017 at 5:49 PM, Jim Jagielski <[hidden email]> wrote:

> I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
> AOO415 branch) available for fun and games (and testing) at:
>
>     http://home.apache.org/~jim/AOO-builds/
>
> I've built all langs but have just uploaded: de, en-US, es, fr
> and ja (for now). Let me know if people want/need others
> uploaded.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.5-dev builds

Patricia Shanahan
I see 4.1.5-dev as a device for testing whether a bug is due to a
specific problem. That change is already checked in to the trunk.

We still have to decide whether to go straight to 4.2.0. The upside is,
as Damjam points out, that we need to get the general benefits of 4.2
out in the field. The downside is that, because of more changes, 4.2.0
has a higher risk of regression. Should 4.2.0 go through field beta-testing?

Going to 4.2.0 would simplify my activities. Because of better debug
building and on general principles, I do my debug and fixing in trunk. I
then have to back port the fixes to the 4.1.x line.

On 11/22/2017 2:37 AM, Damjan Jovanovic wrote:

> Thank you, but when are these 4.1.x releases going to stop?
>
> We have so much lined up for 4.2.0.
>
> Damjan
>
> On Mon, Nov 20, 2017 at 5:49 PM, Jim Jagielski <[hidden email]> wrote:
>
>> I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
>> AOO415 branch) available for fun and games (and testing) at:
>>
>>      http://home.apache.org/~jim/AOO-builds/
>>
>> I've built all langs but have just uploaded: de, en-US, es, fr
>> and ja (for now). Let me know if people want/need others
>> uploaded.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>

---
This email has been checked for viruses by AVG.
http://www.avg.com


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.5-dev builds

Damjan Jovanovic
What's the alternative to going to 4.2.0?

I only test trunk. So it's 4.1.x that lacks testing from me.

We also really should start running the various tests and comparing results
from trunk against 4.1's.

On Wed, Nov 22, 2017 at 2:05 PM, Patricia Shanahan <[hidden email]> wrote:

> I see 4.1.5-dev as a device for testing whether a bug is due to a specific
> problem. That change is already checked in to the trunk.
>
> We still have to decide whether to go straight to 4.2.0. The upside is, as
> Damjam points out, that we need to get the general benefits of 4.2 out in
> the field. The downside is that, because of more changes, 4.2.0 has a
> higher risk of regression. Should 4.2.0 go through field beta-testing?
>
> Going to 4.2.0 would simplify my activities. Because of better debug
> building and on general principles, I do my debug and fixing in trunk. I
> then have to back port the fixes to the 4.1.x line.
>
>
> On 11/22/2017 2:37 AM, Damjan Jovanovic wrote:
>
>> Thank you, but when are these 4.1.x releases going to stop?
>>
>> We have so much lined up for 4.2.0.
>>
>> Damjan
>>
>> On Mon, Nov 20, 2017 at 5:49 PM, Jim Jagielski <[hidden email]> wrote:
>>
>> I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
>>> AOO415 branch) available for fun and games (and testing) at:
>>>
>>>      http://home.apache.org/~jim/AOO-builds/
>>>
>>> I've built all langs but have just uploaded: de, en-US, es, fr
>>> and ja (for now). Let me know if people want/need others
>>> uploaded.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>>
>>
> ---
> This email has been checked for viruses by AVG.
> http://www.avg.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.5-dev builds

Matthias Seidel
We have buildbots building 4.1.4 every week...

Would it make sense to switch them to 4.1.5?

Regards, Matthias


Am 22.11.2017 um 13:31 schrieb Damjan Jovanovic:

> What's the alternative to going to 4.2.0?
>
> I only test trunk. So it's 4.1.x that lacks testing from me.
>
> We also really should start running the various tests and comparing results
> from trunk against 4.1's.
>
> On Wed, Nov 22, 2017 at 2:05 PM, Patricia Shanahan <[hidden email]> wrote:
>
>> I see 4.1.5-dev as a device for testing whether a bug is due to a specific
>> problem. That change is already checked in to the trunk.
>>
>> We still have to decide whether to go straight to 4.2.0. The upside is, as
>> Damjam points out, that we need to get the general benefits of 4.2 out in
>> the field. The downside is that, because of more changes, 4.2.0 has a
>> higher risk of regression. Should 4.2.0 go through field beta-testing?
>>
>> Going to 4.2.0 would simplify my activities. Because of better debug
>> building and on general principles, I do my debug and fixing in trunk. I
>> then have to back port the fixes to the 4.1.x line.
>>
>>
>> On 11/22/2017 2:37 AM, Damjan Jovanovic wrote:
>>
>>> Thank you, but when are these 4.1.x releases going to stop?
>>>
>>> We have so much lined up for 4.2.0.
>>>
>>> Damjan
>>>
>>> On Mon, Nov 20, 2017 at 5:49 PM, Jim Jagielski <[hidden email]> wrote:
>>>
>>> I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
>>>> AOO415 branch) available for fun and games (and testing) at:
>>>>
>>>>      http://home.apache.org/~jim/AOO-builds/
>>>>
>>>> I've built all langs but have just uploaded: de, en-US, es, fr
>>>> and ja (for now). Let me know if people want/need others
>>>> uploaded.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>>
>>>>
>> ---
>> This email has been checked for viruses by AVG.
>> http://www.avg.com
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>


smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.5-dev builds

Pedro Lino-3
Hi Matthias, all


> We have buildbots building 4.1.4 every week...
>


In my opinion that is a waste of electric power and computing resources


> Would it make sense to switch them to 4.1.5?
>


That would make a little more sense...

It should be enough to change the Snap buildbots that are currently still building 4.1.2 snapshots on a daily basis (or so I assume since it is impossible for Apache to details of the files but the page is built every day)

https://ci.apache.org/projects/openoffice/install/winsnap/

and

https://ci.apache.org/projects/openoffice/install/linsnap/


Regards,

Pedro



>     Am 22.11.2017 um 13:31 schrieb Damjan Jovanovic:
>
>         > > What's the alternative to going to 4.2.0?
> >
> >         I only test trunk. So it's 4.1.x that lacks testing from me.
> >
> >         We also really should start running the various tests and comparing results
> >         from trunk against 4.1's.
> >
> >         On Wed, Nov 22, 2017 at 2:05 PM, Patricia Shanahan wrote:
> >
> >             > > > I see 4.1.5-dev as a device for testing whether a bug is due to a specific
> > >             problem. That change is already checked in to the trunk.
> > >
> > >             We still have to decide whether to go straight to 4.2.0. The upside is, as
> > >             Damjam points out, that we need to get the general benefits of 4.2 out in
> > >             the field. The downside is that, because of more changes, 4.2.0 has a
> > >             higher risk of regression. Should 4.2.0 go through field beta-testing?
> > >
> > >             Going to 4.2.0 would simplify my activities. Because of better debug
> > >             building and on general principles, I do my debug and fixing in trunk. I
> > >             then have to back port the fixes to the 4.1.x line.
> > >
> > >
> > >             On 11/22/2017 2:37 AM, Damjan Jovanovic wrote:
> > >
> > >                 > > > > Thank you, but when are these 4.1.x releases going to stop?
> > > >
> > > >                 We have so much lined up for 4.2.0.
> > > >
> > > >                 Damjan
> > > >
> > > >                 On Mon, Nov 20, 2017 at 5:49 PM, Jim Jagielski wrote:
> > > >
> > > >                 I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
> > > >
> > > >                     > > > > > AOO415 branch) available for fun and games (and testing) at:
> > > > >
> > > > >                     http://home.apache.org/~jim/AOO-builds/
> > > > >
> > > > >                     I've built all langs but have just uploaded: de, en-US, es, fr
> > > > >                     and ja (for now). Let me know if people want/need others
> > > > >                     uploaded.
> > > > >
> > > > >                     ---------------------------------------------
> > > > >                     To unsubscribe, e-mail: [hidden email] mailto:[hidden email] .org
> > > > >                     For additional commands, e-mail: [hidden email] mailto:[hidden email] .org
> > > > >
> > > > >                 > > > >
> > > >             > > > ---
> > >             This email has been checked for viruses by AVG.
> > >             http://www.avg.com
> > >
> > >
> > >
> > >             ---------------------------------------------
> > >             To unsubscribe, e-mail: [hidden email] mailto:[hidden email] .org
> > >             For additional commands, e-mail: [hidden email] mailto:[hidden email] .org
> > >
> > >         > >
> >     >
Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.5-dev builds

Matthias Seidel
Am 22.11.2017 um 15:17 schrieb Pedro Lino:
> Hi Matthias, all
>
>
>> We have buildbots building 4.1.4 every week...
>>
>
> In my opinion that is a waste of electric power and computing resources

Well, it is important for the release process, but 4.1.4 is out now...

>
>
>> Would it make sense to switch them to 4.1.5?
>>
>
> That would make a little more sense...
>
> It should be enough to change the Snap buildbots that are currently still building 4.1.2 snapshots on a daily basis (or so I assume since it is impossible for Apache to details of the files but the page is built every day)
>
> https://ci.apache.org/projects/openoffice/install/winsnap/
>
> and
>
> https://ci.apache.org/projects/openoffice/install/linsnap/
Forget these pages, they are built by a useless script on Apache servers.

Currently all informations about our buildbots can be seen here:
https://www.openoffice.org/download/devbuilds.html

We are building trunk daily/nightly and branch (4.1.4) on a weekly base.
That could be easily switched to 4.1.5 although the naming of the bots
wouldn't change. I could try to get more generic names for them in the
future.

Regards, Matthias

>
>
> Regards,
>
> Pedro
>
>
>
>>     Am 22.11.2017 um 13:31 schrieb Damjan Jovanovic:
>>
>>         > > What's the alternative to going to 4.2.0?
>>>         I only test trunk. So it's 4.1.x that lacks testing from me.
>>>
>>>         We also really should start running the various tests and comparing results
>>>         from trunk against 4.1's.
>>>
>>>         On Wed, Nov 22, 2017 at 2:05 PM, Patricia Shanahan wrote:
>>>
>>>             > > > I see 4.1.5-dev as a device for testing whether a bug is due to a specific
>>>>             problem. That change is already checked in to the trunk.
>>>>
>>>>             We still have to decide whether to go straight to 4.2.0. The upside is, as
>>>>             Damjam points out, that we need to get the general benefits of 4.2 out in
>>>>             the field. The downside is that, because of more changes, 4.2.0 has a
>>>>             higher risk of regression. Should 4.2.0 go through field beta-testing?
>>>>
>>>>             Going to 4.2.0 would simplify my activities. Because of better debug
>>>>             building and on general principles, I do my debug and fixing in trunk. I
>>>>             then have to back port the fixes to the 4.1.x line.
>>>>
>>>>
>>>>             On 11/22/2017 2:37 AM, Damjan Jovanovic wrote:
>>>>
>>>>                 > > > > Thank you, but when are these 4.1.x releases going to stop?
>>>>>                 We have so much lined up for 4.2.0.
>>>>>
>>>>>                 Damjan
>>>>>
>>>>>                 On Mon, Nov 20, 2017 at 5:49 PM, Jim Jagielski wrote:
>>>>>
>>>>>                 I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
>>>>>
>>>>>                     > > > > > AOO415 branch) available for fun and games (and testing) at:
>>>>>>                     http://home.apache.org/~jim/AOO-builds/
>>>>>>
>>>>>>                     I've built all langs but have just uploaded: de, en-US, es, fr
>>>>>>                     and ja (for now). Let me know if people want/need others
>>>>>>                     uploaded.
>>>>>>
>>>>>>                     ---------------------------------------------
>>>>>>                     To unsubscribe, e-mail: [hidden email] mailto:[hidden email] .org
>>>>>>                     For additional commands, e-mail: [hidden email] mailto:[hidden email] .org
>>>>>>
>>>>>>                 > > > >
>>>>>             > > > ---
>>>>             This email has been checked for viruses by AVG.
>>>>             http://www.avg.com
>>>>
>>>>
>>>>
>>>>             ---------------------------------------------
>>>>             To unsubscribe, e-mail: [hidden email] mailto:[hidden email] .org
>>>>             For additional commands, e-mail: [hidden email] mailto:[hidden email] .org
>>>>
>>>>         > >
>>>     >


smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.5-dev builds

Pedro Lino-3

>
>         > >
> >             > > > We have buildbots building 4.1.4 every week...
> > >
> > >         > > In my opinion that is a waste of electric power and computing resources
> >
> >     >     Well, it is important for the release process, but 4.1.4 is out now...
>


Exactly my point.

If the idea is to test changes in the build environment with a known good source, it should be enough to run when/if the build environment is modified...

If this can not be controlled/detected then maybe create a env_test folder (and create the respective src, win, linux32 and linux64 folders inside it)


> We are building trunk daily/nightly and branch (4.1.4) on a weekly base.
>     That could be easily switched to 4.1.5 although the naming of the bots
>     wouldn't change. I could try to get more generic names for them in the
>     future.
>


Maybe rename the folders from Snapshot to Development? Both are daily/nightly/weekly builds except one is from Trunk and the other should be from the Development branch. E.g. win_trunk and win_dev ?
Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.5-dev builds

Peter Kovacs-3
In reply to this post by Patricia Shanahan
I think to use 4.2.0 directly is causing less regression then to backport  a subset of fixes on the 4.1.x tree and then test for regressions.

If the fix is indeed successfull with the build changes, we should release the new build, and go on.


Am 22. November 2017 13:05:14 MEZ schrieb Patricia Shanahan <[hidden email]>:

>I see 4.1.5-dev as a device for testing whether a bug is due to a
>specific problem. That change is already checked in to the trunk.
>
>We still have to decide whether to go straight to 4.2.0. The upside is,
>
>as Damjam points out, that we need to get the general benefits of 4.2
>out in the field. The downside is that, because of more changes, 4.2.0
>has a higher risk of regression. Should 4.2.0 go through field
>beta-testing?
>
>Going to 4.2.0 would simplify my activities. Because of better debug
>building and on general principles, I do my debug and fixing in trunk.
>I
>then have to back port the fixes to the 4.1.x line.
>
>On 11/22/2017 2:37 AM, Damjan Jovanovic wrote:
>> Thank you, but when are these 4.1.x releases going to stop?
>>
>> We have so much lined up for 4.2.0.
>>
>> Damjan
>>
>> On Mon, Nov 20, 2017 at 5:49 PM, Jim Jagielski <[hidden email]>
>wrote:
>>
>>> I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
>>> AOO415 branch) available for fun and games (and testing) at:
>>>
>>>      http://home.apache.org/~jim/AOO-builds/
>>>
>>> I've built all langs but have just uploaded: de, en-US, es, fr
>>> and ja (for now). Let me know if people want/need others
>>> uploaded.
>>>
>>>
>---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>
>
>---
>This email has been checked for viruses by AVG.
>http://www.avg.com
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [hidden email]
>For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.5-dev builds

Dave Fisher
We have regressions in 4.1.4. Until we get a fix out in either 4.2.0 or 4.1.5 we will continue to get bug reports. These will distract our volunteers and impact our users.

We owe it to our users to be quick.

Regarding 4.2.0. What are the new features and is everything being worked into trunk complete? If we were to decide to release it “quickly” what needs to be done?

Regards,
Dave

> On Nov 22, 2017, at 8:34 AM, Peter kovacs <[hidden email]> wrote:
>
> I think to use 4.2.0 directly is causing less regression then to backport  a subset of fixes on the 4.1.x tree and then test for regressions.
>
> If the fix is indeed successfull with the build changes, we should release the new build, and go on.
>
>
> Am 22. November 2017 13:05:14 MEZ schrieb Patricia Shanahan <[hidden email]>:
>> I see 4.1.5-dev as a device for testing whether a bug is due to a
>> specific problem. That change is already checked in to the trunk.
>>
>> We still have to decide whether to go straight to 4.2.0. The upside is,
>>
>> as Damjam points out, that we need to get the general benefits of 4.2
>> out in the field. The downside is that, because of more changes, 4.2.0
>> has a higher risk of regression. Should 4.2.0 go through field
>> beta-testing?
>>
>> Going to 4.2.0 would simplify my activities. Because of better debug
>> building and on general principles, I do my debug and fixing in trunk.
>> I
>> then have to back port the fixes to the 4.1.x line.
>>
>> On 11/22/2017 2:37 AM, Damjan Jovanovic wrote:
>>> Thank you, but when are these 4.1.x releases going to stop?
>>>
>>> We have so much lined up for 4.2.0.
>>>
>>> Damjan
>>>
>>> On Mon, Nov 20, 2017 at 5:49 PM, Jim Jagielski <[hidden email]>
>> wrote:
>>>
>>>> I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
>>>> AOO415 branch) available for fun and games (and testing) at:
>>>>
>>>>     http://home.apache.org/~jim/AOO-builds/
>>>>
>>>> I've built all langs but have just uploaded: de, en-US, es, fr
>>>> and ja (for now). Let me know if people want/need others
>>>> uploaded.
>>>>
>>>>
>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>>
>>>
>>
>> ---
>> This email has been checked for viruses by AVG.
>> http://www.avg.com
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


signature.asc (817 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.5-dev builds

Damjan Jovanovic
On Wed, Nov 22, 2017 at 6:48 PM, Dave Fisher <[hidden email]> wrote:

>
> Regarding 4.2.0. What are the new features and is everything being worked
> into trunk complete? If we were to decide to release it “quickly” what
> needs to be done?
>

I don't recommend releasing 4.2.0 immediately; maybe in a month or 2 after
my PostgreSQL driver and several other outstanding projects are complete.

I'll give you a summary of my own changes in trunk for the past year or so;
it's been a quiet year compared to the 2 years before it, and I've made at
least 365 total commits to trunk since AOO was an incubator project. You
can see why I want the improvements to get out there and people to use them:

Database connections through ODBC don't crash on 64 bit.
oowintool detects Java 8, and finds VC++ on Cygwin64.
Fixes for several fvt tests; they now pass.
Newer versions of JUnit work with Hamcrest for subsequent tests.
Database connections using JDBC now use the new driver rewritten in Java,
with tons of bug fixes and high reliability (Java doesn't corrupt memory,
reports exceptions instead of crashing).
New driver for the PostgreSQL database, supporting the advanced features
like relationships, views, keys, constraints, etc. (Development ongoing)
Buggy DXF files no longer crash AOO.
Various dependency improvements, eg. cairo and pixman are downloaded if
enabled and and system libraries aren't used.
Drop a dependency on ORbit which was last needed in 2003.
GIO instead of GnomeVFS (deprecated 9 years ago) is now the default backend
on GTK-based desktops.
Java's ComponentBase base class for UNO components now has isDisposed() and
checkDisposed() methods.
ComponentBase locking on disposal fix.
Require Apache Commons Lang for the build.
#i32546# - Java UnoRuntime.getUniqueKey/generateOid do not work reliably
Remove some incorrect API documentation for the
com.sun.star.sdbc.SQLException ErrorCode field.
We need the system Apache Commons Lang to be version 3.x.
Write a main/ant.properties file from main/set_soenv, which can be used in
Ant projects to work out settings, locations, and paths to dependencies
without getting them from a parent build tool (dmake/gbuild), which allows
Ant projects to build by themselves,  independently of AOO, and allows them
to be cleanly opened in (at least) Eclipse.
Remove the obsolete KDE address book SDBC driver, that only worked on KDE
3.2 - 3.6, which are obsolete since 9 years ago.
Update AnyConverter.toObject() to use Java 1.5+'s generics.
If called on an empty collection, don't let
OEnumerationByIndex.nextElement() call XIndexAccess.getByIndex() with an
invalid index, just like OEnumerationByName.nextElement() doesn't.
Fix some comment typos in javaunohelper's PropertySet.java,
Update javaunohelper's MultiTypeInterfaceContainer.java to use generics,
and fix performance bugs in getContainer() where O(n) iteration over all
keys was being done instead of an O(1) map.get(), and in
getContainedTypes() where iteration over keys and then n calls to map.get()
for the value was being done instead of iteration over entries.
Java boxing optimization and cleanups for l10ntools.
Use more efficient Java boxing in main/filter.
Use more efficient Java boxing for basic types in main/bean.
Add some Java performance optimizations with boxing of basic types: instead
of using "new <Type>(<value>)", use <Type>.valueOf(<value>), or better yet,
rely on autoboxing.
Add initial support for building AOO with Clang on Linux.
We need to pass "-DEBUG" to the linker on Windows for debugging to work.
When debug symbols are produced for C / C++ / Objective C, produce them for
Java too.
Add debug symbols to gbuild modules when any of --enable-debug,
--enable-symbols, or --enable-crashdump are passed to ./configure (just
like it already is for dmake modules), as opposed to the previous behaviour
of only doing it on --enable-debug.
Fix a FreeBSD regression in the gbuild gb_CPUDEFS variable caused by
r1773166, where it was always set to POWERPC64 due to a swapped if-else.
Don't use the "archive" package format, which is to be extrated by
smoketest as a side effect, for the subsequent tests. The smoketest is
currently broken and won't do that, and the path is wrong anyway. Instead,
use the office instance from the "installed" package format for subsequent
tests, as it doesn't have to zipped up and unzipped, resulting in faster
building and faster testing, and doesn't require a side effect.
Pass "-encoding UTF8" to javac, as some Java sources, particularly those
used in subsequent tests, contain special characters that are encoded in
UTF-8, and fail to compile without this option.
Correlate the Perl modules tested for in bulk with the Perl modules tested
for individually to be reported as missing, so that those reported as
missing are correct.
Add a main/sd subsequent test that wasn't hooked into the build.
Fix a configure.ac problem with hamcrest detection.
Fix a main/sw subsequent test.
Add a ./configure option for Hamcrest once again, this time optional, so
that newer versions of JUnit can work.
Fix a main/sc JunitTest typo.
Resurrect main/test, which was deleted by liuzhe in r1378870, probably by
accident, and which we need for test.jar and test-tools.jar for subsequent
tests.
Build fixes for vbaobj on Windows.
Fix a missing bracket problem in a main/cui makefile when BUILD_VER_STRING
is set.
Fix a Windows naming clash between main/cui, whose library, icuin.lib, was
clashing with main/icu's icuin.lib once we started using gbuild, which
places libraries in a common directory. The main/cui library is now just
icui.lib, and main/icu's is still icuin.lib.
Only set the BUILD_VER_STRING define if it is available as an environment
variable and non-empty. At least the Windows build breaks without this when
--with-build-version is not used.
The internal CoinMP comes as a single library on Windows.
Add shlwapi32, wsock32, ws2_32 to the list of known Windows DLLs.
Order of library linking fixes on *nix.
Tons of libraries ported to gbuild.
Google Test fixes that were breaking the build on the buildbots.
Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.5-dev builds

Patricia Shanahan
I don't think we should wait for more development before releasing fixes
for the 4.1.4 regressions. If 4.2.0 needs another month or so of
development, I'm in favor of releasing 4.1.5 as soon as we can get the
various bug reports checked against it.

On a side note, for those living outside the US, tomorrow is the US
Thanksgiving Day. It starts what is, for many people, a four day
weekend. Even today, some of us are involved in preparations - I need to
arrange furniture to seat 14 for dinner tomorrow. Do not expect too much
US open source involvement for a few days.

On 11/22/2017 9:36 AM, Damjan Jovanovic wrote:

> On Wed, Nov 22, 2017 at 6:48 PM, Dave Fisher <[hidden email]> wrote:
>
>>
>> Regarding 4.2.0. What are the new features and is everything being worked
>> into trunk complete? If we were to decide to release it “quickly” what
>> needs to be done?
>>
>
> I don't recommend releasing 4.2.0 immediately; maybe in a month or 2 after
> my PostgreSQL driver and several other outstanding projects are complete.
>
> I'll give you a summary of my own changes in trunk for the past year or so;
> it's been a quiet year compared to the 2 years before it, and I've made at
> least 365 total commits to trunk since AOO was an incubator project. You
> can see why I want the improvements to get out there and people to use them:
>
> Database connections through ODBC don't crash on 64 bit.
> oowintool detects Java 8, and finds VC++ on Cygwin64.
> Fixes for several fvt tests; they now pass.
> Newer versions of JUnit work with Hamcrest for subsequent tests.
> Database connections using JDBC now use the new driver rewritten in Java,
> with tons of bug fixes and high reliability (Java doesn't corrupt memory,
> reports exceptions instead of crashing).
> New driver for the PostgreSQL database, supporting the advanced features
> like relationships, views, keys, constraints, etc. (Development ongoing)
> Buggy DXF files no longer crash AOO.
> Various dependency improvements, eg. cairo and pixman are downloaded if
> enabled and and system libraries aren't used.
> Drop a dependency on ORbit which was last needed in 2003.
> GIO instead of GnomeVFS (deprecated 9 years ago) is now the default backend
> on GTK-based desktops.
> Java's ComponentBase base class for UNO components now has isDisposed() and
> checkDisposed() methods.
> ComponentBase locking on disposal fix.
> Require Apache Commons Lang for the build.
> #i32546# - Java UnoRuntime.getUniqueKey/generateOid do not work reliably
> Remove some incorrect API documentation for the
> com.sun.star.sdbc.SQLException ErrorCode field.
> We need the system Apache Commons Lang to be version 3.x.
> Write a main/ant.properties file from main/set_soenv, which can be used in
> Ant projects to work out settings, locations, and paths to dependencies
> without getting them from a parent build tool (dmake/gbuild), which allows
> Ant projects to build by themselves,  independently of AOO, and allows them
> to be cleanly opened in (at least) Eclipse.
> Remove the obsolete KDE address book SDBC driver, that only worked on KDE
> 3.2 - 3.6, which are obsolete since 9 years ago.
> Update AnyConverter.toObject() to use Java 1.5+'s generics.
> If called on an empty collection, don't let
> OEnumerationByIndex.nextElement() call XIndexAccess.getByIndex() with an
> invalid index, just like OEnumerationByName.nextElement() doesn't.
> Fix some comment typos in javaunohelper's PropertySet.java,
> Update javaunohelper's MultiTypeInterfaceContainer.java to use generics,
> and fix performance bugs in getContainer() where O(n) iteration over all
> keys was being done instead of an O(1) map.get(), and in
> getContainedTypes() where iteration over keys and then n calls to map.get()
> for the value was being done instead of iteration over entries.
> Java boxing optimization and cleanups for l10ntools.
> Use more efficient Java boxing in main/filter.
> Use more efficient Java boxing for basic types in main/bean.
> Add some Java performance optimizations with boxing of basic types: instead
> of using "new <Type>(<value>)", use <Type>.valueOf(<value>), or better yet,
> rely on autoboxing.
> Add initial support for building AOO with Clang on Linux.
> We need to pass "-DEBUG" to the linker on Windows for debugging to work.
> When debug symbols are produced for C / C++ / Objective C, produce them for
> Java too.
> Add debug symbols to gbuild modules when any of --enable-debug,
> --enable-symbols, or --enable-crashdump are passed to ./configure (just
> like it already is for dmake modules), as opposed to the previous behaviour
> of only doing it on --enable-debug.
> Fix a FreeBSD regression in the gbuild gb_CPUDEFS variable caused by
> r1773166, where it was always set to POWERPC64 due to a swapped if-else.
> Don't use the "archive" package format, which is to be extrated by
> smoketest as a side effect, for the subsequent tests. The smoketest is
> currently broken and won't do that, and the path is wrong anyway. Instead,
> use the office instance from the "installed" package format for subsequent
> tests, as it doesn't have to zipped up and unzipped, resulting in faster
> building and faster testing, and doesn't require a side effect.
> Pass "-encoding UTF8" to javac, as some Java sources, particularly those
> used in subsequent tests, contain special characters that are encoded in
> UTF-8, and fail to compile without this option.
> Correlate the Perl modules tested for in bulk with the Perl modules tested
> for individually to be reported as missing, so that those reported as
> missing are correct.
> Add a main/sd subsequent test that wasn't hooked into the build.
> Fix a configure.ac problem with hamcrest detection.
> Fix a main/sw subsequent test.
> Add a ./configure option for Hamcrest once again, this time optional, so
> that newer versions of JUnit can work.
> Fix a main/sc JunitTest typo.
> Resurrect main/test, which was deleted by liuzhe in r1378870, probably by
> accident, and which we need for test.jar and test-tools.jar for subsequent
> tests.
> Build fixes for vbaobj on Windows.
> Fix a missing bracket problem in a main/cui makefile when BUILD_VER_STRING
> is set.
> Fix a Windows naming clash between main/cui, whose library, icuin.lib, was
> clashing with main/icu's icuin.lib once we started using gbuild, which
> places libraries in a common directory. The main/cui library is now just
> icui.lib, and main/icu's is still icuin.lib.
> Only set the BUILD_VER_STRING define if it is available as an environment
> variable and non-empty. At least the Windows build breaks without this when
> --with-build-version is not used.
> The internal CoinMP comes as a single library on Windows.
> Add shlwapi32, wsock32, ws2_32 to the list of known Windows DLLs.
> Order of library linking fixes on *nix.
> Tons of libraries ported to gbuild.
> Google Test fixes that were breaking the build on the buildbots.
>

---
This email has been checked for viruses by AVG.
http://www.avg.com


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.5-dev builds

Marcus (OOo)
Am 22.11.2017 um 21:00 schrieb Patricia Shanahan:
> I don't think we should wait for more development before releasing fixes
> for the 4.1.4 regressions. If 4.2.0 needs another month or so of
> development, I'm in favor of releasing 4.1.5 as soon as we can get the
> various bug reports checked against it.

we have already 3 reports with some higher impacts (at least thats what
I've seen so far) that results in some "difficulties" from 4.1.4. IMHO
it would not be good to say we will fix them with 4.2.0 when it's not
sure when it will be ready.

> On a side note, for those living outside the US, tomorrow is the US
> Thanksgiving Day. It starts what is, for many people, a four day
> weekend. Even today, some of us are involved in preparations - I need to
> arrange furniture to seat 14 for dinner tomorrow. Do not expect too much
> US open source involvement for a few days.

Thanks for this side note. Enjoy your (offline) time and have fun with
your family.

Happy Thanksgiving :-)

Marcus



> On 11/22/2017 9:36 AM, Damjan Jovanovic wrote:
>> On Wed, Nov 22, 2017 at 6:48 PM, Dave Fisher <[hidden email]>
>> wrote:
>>
>>>
>>> Regarding 4.2.0. What are the new features and is everything being
>>> worked
>>> into trunk complete? If we were to decide to release it “quickly” what
>>> needs to be done?
>>>
>>
>> I don't recommend releasing 4.2.0 immediately; maybe in a month or 2
>> after
>> my PostgreSQL driver and several other outstanding projects are complete.
>>
>> I'll give you a summary of my own changes in trunk for the past year
>> or so;
>> it's been a quiet year compared to the 2 years before it, and I've
>> made at
>> least 365 total commits to trunk since AOO was an incubator project. You
>> can see why I want the improvements to get out there and people to use
>> them:
>>
>> Database connections through ODBC don't crash on 64 bit.
>> oowintool detects Java 8, and finds VC++ on Cygwin64.
>> Fixes for several fvt tests; they now pass.
>> Newer versions of JUnit work with Hamcrest for subsequent tests.
>> Database connections using JDBC now use the new driver rewritten in Java,
>> with tons of bug fixes and high reliability (Java doesn't corrupt memory,
>> reports exceptions instead of crashing).
>> New driver for the PostgreSQL database, supporting the advanced features
>> like relationships, views, keys, constraints, etc. (Development ongoing)
>> Buggy DXF files no longer crash AOO.
>> Various dependency improvements, eg. cairo and pixman are downloaded if
>> enabled and and system libraries aren't used.
>> Drop a dependency on ORbit which was last needed in 2003.
>> GIO instead of GnomeVFS (deprecated 9 years ago) is now the default
>> backend
>> on GTK-based desktops.
>> Java's ComponentBase base class for UNO components now has
>> isDisposed() and
>> checkDisposed() methods.
>> ComponentBase locking on disposal fix.
>> Require Apache Commons Lang for the build.
>> #i32546# - Java UnoRuntime.getUniqueKey/generateOid do not work reliably
>> Remove some incorrect API documentation for the
>> com.sun.star.sdbc.SQLException ErrorCode field.
>> We need the system Apache Commons Lang to be version 3.x.
>> Write a main/ant.properties file from main/set_soenv, which can be
>> used in
>> Ant projects to work out settings, locations, and paths to dependencies
>> without getting them from a parent build tool (dmake/gbuild), which
>> allows
>> Ant projects to build by themselves,  independently of AOO, and allows
>> them
>> to be cleanly opened in (at least) Eclipse.
>> Remove the obsolete KDE address book SDBC driver, that only worked on KDE
>> 3.2 - 3.6, which are obsolete since 9 years ago.
>> Update AnyConverter.toObject() to use Java 1.5+'s generics.
>> If called on an empty collection, don't let
>> OEnumerationByIndex.nextElement() call XIndexAccess.getByIndex() with an
>> invalid index, just like OEnumerationByName.nextElement() doesn't.
>> Fix some comment typos in javaunohelper's PropertySet.java,
>> Update javaunohelper's MultiTypeInterfaceContainer.java to use generics,
>> and fix performance bugs in getContainer() where O(n) iteration over all
>> keys was being done instead of an O(1) map.get(), and in
>> getContainedTypes() where iteration over keys and then n calls to
>> map.get()
>> for the value was being done instead of iteration over entries.
>> Java boxing optimization and cleanups for l10ntools.
>> Use more efficient Java boxing in main/filter.
>> Use more efficient Java boxing for basic types in main/bean.
>> Add some Java performance optimizations with boxing of basic types:
>> instead
>> of using "new <Type>(<value>)", use <Type>.valueOf(<value>), or better
>> yet,
>> rely on autoboxing.
>> Add initial support for building AOO with Clang on Linux.
>> We need to pass "-DEBUG" to the linker on Windows for debugging to work.
>> When debug symbols are produced for C / C++ / Objective C, produce
>> them for
>> Java too.
>> Add debug symbols to gbuild modules when any of --enable-debug,
>> --enable-symbols, or --enable-crashdump are passed to ./configure (just
>> like it already is for dmake modules), as opposed to the previous
>> behaviour
>> of only doing it on --enable-debug.
>> Fix a FreeBSD regression in the gbuild gb_CPUDEFS variable caused by
>> r1773166, where it was always set to POWERPC64 due to a swapped if-else.
>> Don't use the "archive" package format, which is to be extrated by
>> smoketest as a side effect, for the subsequent tests. The smoketest is
>> currently broken and won't do that, and the path is wrong anyway.
>> Instead,
>> use the office instance from the "installed" package format for
>> subsequent
>> tests, as it doesn't have to zipped up and unzipped, resulting in faster
>> building and faster testing, and doesn't require a side effect.
>> Pass "-encoding UTF8" to javac, as some Java sources, particularly those
>> used in subsequent tests, contain special characters that are encoded in
>> UTF-8, and fail to compile without this option.
>> Correlate the Perl modules tested for in bulk with the Perl modules
>> tested
>> for individually to be reported as missing, so that those reported as
>> missing are correct.
>> Add a main/sd subsequent test that wasn't hooked into the build.
>> Fix a configure.ac problem with hamcrest detection.
>> Fix a main/sw subsequent test.
>> Add a ./configure option for Hamcrest once again, this time optional, so
>> that newer versions of JUnit can work.
>> Fix a main/sc JunitTest typo.
>> Resurrect main/test, which was deleted by liuzhe in r1378870, probably by
>> accident, and which we need for test.jar and test-tools.jar for
>> subsequent
>> tests.
>> Build fixes for vbaobj on Windows.
>> Fix a missing bracket problem in a main/cui makefile when
>> BUILD_VER_STRING
>> is set.
>> Fix a Windows naming clash between main/cui, whose library, icuin.lib,
>> was
>> clashing with main/icu's icuin.lib once we started using gbuild, which
>> places libraries in a common directory. The main/cui library is now just
>> icui.lib, and main/icu's is still icuin.lib.
>> Only set the BUILD_VER_STRING define if it is available as an environment
>> variable and non-empty. At least the Windows build breaks without this
>> when
>> --with-build-version is not used.
>> The internal CoinMP comes as a single library on Windows.
>> Add shlwapi32, wsock32, ws2_32 to the list of known Windows DLLs.
>> Order of library linking fixes on *nix.
>> Tons of libraries ported to gbuild.
>> Google Test fixes that were breaking the build on the buildbots.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.5-dev builds

Jim Jagielski
And in honor of the (US) Holiday, I am uploading to

    http://home.apache.org/~jim/AOO-builds/

Windows builds for 4.1.5 (just the subset of langs).

This not only allows for tests of 4.1.5 for Windows users
but also that my Windows build setup is (finally) viable!

Cheers!

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.5-dev builds

Marcus (OOo)
Am 23.11.2017 um 04:26 schrieb Jim Jagielski:
> And in honor of the (US) Holiday, I am uploading to
>
>      http://home.apache.org/~jim/AOO-builds/
>
> Windows builds for 4.1.5 (just the subset of langs).
>
> This not only allows for tests of 4.1.5 for Windows users
> but also that my Windows build setup is (finally) viable!

great to have another Windows builder here.

Happy holidays. :-)

Marcus


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.1.5-dev builds

Matthias Seidel
In reply to this post by Jim Jagielski
Great!

Additionally I switched our Windows buildbot to branch 415:
https://ci.apache.org/projects/openoffice/install/win41x/

My personal builds are still available here:
https://home.apache.org/~mseidel/AOO-builds/AOO-415-Dev/

Let's test! ;-)


Am 23.11.2017 um 04:26 schrieb Jim Jagielski:

> And in honor of the (US) Holiday, I am uploading to
>
>     http://home.apache.org/~jim/AOO-builds/
>
> Windows builds for 4.1.5 (just the subset of langs).
>
> This not only allows for tests of 4.1.5 for Windows users
> but also that my Windows build setup is (finally) viable!
>
> Cheers!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

AOO 4.2.0-dev builds

Rory O'Farrell
In reply to this post by Damjan Jovanovic
I have downloaded and install AO0 4.2.0 for linux from
https://ci.apache.org/projects/openoffice/install/linux64/Apache_OpenOffice_4.2.0_Linux_x86-64_install-deb_en-US_2017-11-23_04%3A16%3A31_1816101.tar.gz

When opening a Writer file from the splash screen I get a "general error" message, then the file opens.  Starting AOO 4.2.0 from a terminal gives the message
** (soffice:2353): WARNING **: Unknown type: GailWindow
The file then opens; it will accept a simple edit, and close correctly.

Further information on Writer (mis)behaviour (if any) as I run into it.  However, little time at present, but I'll continue to use AOO 4.2.0

--
Rory O'Farrell <[hidden email]>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.2.0-dev builds

Matthias Seidel
Hi Rory,

Am 23.11.2017 um 18:31 schrieb Rory O'Farrell:
> I have downloaded and install AO0 4.2.0 for linux from
> https://ci.apache.org/projects/openoffice/install/linux64/Apache_OpenOffice_4.2.0_Linux_x86-64_install-deb_en-US_2017-11-23_04%3A16%3A31_1816101.tar.gz
>
> When opening a Writer file from the splash screen I get a "general error" message, then the file opens.  Starting AOO 4.2.0 from a terminal gives the message
> ** (soffice:2353): WARNING **: Unknown type: GailWindow
> The file then opens; it will accept a simple edit, and close correctly.

That sounds like this issue:
https://bz.apache.org/ooo/show_bug.cgi?id=127315

It would be interesting if it only affects builds based on Ubuntu
(14.04). Can someone build 4.2.0 on CentOS under release conditions?

Regards, Matthias

BTW: You are opening from the Start Center, not from the Splash Screen?

>
> Further information on Writer (mis)behaviour (if any) as I run into it.  However, little time at present, but I'll continue to use AOO 4.2.0
>



smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.2.0-dev builds

Rory O'Farrell
On Thu, 23 Nov 2017 18:43:13 +0100
Matthias Seidel <[hidden email]> wrote:

> Hi Rory,
>
> Am 23.11.2017 um 18:31 schrieb Rory O'Farrell:
> > I have downloaded and install AO0 4.2.0 for linux from
> > https://ci.apache.org/projects/openoffice/install/linux64/Apache_OpenOffice_4.2.0_Linux_x86-64_install-deb_en-US_2017-11-23_04%3A16%3A31_1816101.tar.gz
> >
> > When opening a Writer file from the splash screen I get a "general error" message, then the file opens.  Starting AOO 4.2.0 from a terminal gives the message
> > ** (soffice:2353): WARNING **: Unknown type: GailWindow
> > The file then opens; it will accept a simple edit, and close correctly.
>
> That sounds like this issue:
> https://bz.apache.org/ooo/show_bug.cgi?id=127315
>
> It would be interesting if it only affects builds based on Ubuntu
> (14.04). Can someone build 4.2.0 on CentOS under release conditions?
>
> Regards, Matthias
>
> BTW: You are opening from the Start Center, not from the Splash Screen?
>
> >
> > Further information on Writer (mis)behaviour (if any) as I run into it.  However, little time at present, but I'll continue to use AOO 4.2.0
> >
>
>

The "GailWindow" message is from opening in a Terminal, the "General error" message is from opening from either the Splash Screen or from double clicking an .odt file. If I start Writer directly, then pick a file off Recent Documents, I get the "general error" message; click on this and the file opens correctly.

BTW, I am running on Xubuntu 64 bit 16.04.03 (fully updated)




--
Rory O'Farrell <[hidden email]>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: AOO 4.2.0-dev builds

Matthias Seidel


Am 23.11.2017 um 19:02 schrieb Rory O'Farrell:

> On Thu, 23 Nov 2017 18:43:13 +0100
> Matthias Seidel <[hidden email]> wrote:
>
>> Hi Rory,
>>
>> Am 23.11.2017 um 18:31 schrieb Rory O'Farrell:
>>> I have downloaded and install AO0 4.2.0 for linux from
>>> https://ci.apache.org/projects/openoffice/install/linux64/Apache_OpenOffice_4.2.0_Linux_x86-64_install-deb_en-US_2017-11-23_04%3A16%3A31_1816101.tar.gz
>>>
>>> When opening a Writer file from the splash screen I get a "general error" message, then the file opens.  Starting AOO 4.2.0 from a terminal gives the message
>>> ** (soffice:2353): WARNING **: Unknown type: GailWindow
>>> The file then opens; it will accept a simple edit, and close correctly.
>> That sounds like this issue:
>> https://bz.apache.org/ooo/show_bug.cgi?id=127315
>>
>> It would be interesting if it only affects builds based on Ubuntu
>> (14.04). Can someone build 4.2.0 on CentOS under release conditions?
>>
>> Regards, Matthias
>>
>> BTW: You are opening from the Start Center, not from the Splash Screen?
>>
>>> Further information on Writer (mis)behaviour (if any) as I run into it.  However, little time at present, but I'll continue to use AOO 4.2.0
>>>
>>
> The "GailWindow" message is from opening in a Terminal, the "General error" message is from opening from either the Splash Screen or from double clicking an .odt file. If I start Writer directly, then pick a file off Recent Documents, I get the "general error" message; click on this and the file opens correctly.
This is the Splash Screen:

https://svn.apache.org/repos/asf/openoffice/trunk/main/default_images/introabout/intro.png

This is the Start Center:

https://home.apache.org/~mseidel/Start%20Center%20+%20ASF%20logo.png

;-)

> BTW, I am running on Xubuntu 64 bit 16.04.03 (fully updated)



smime.p7s (5K) Download Attachment
1234