Discussion:
URGENT: Need to build new version based on 4.1.4
(too old to reply)
Patricia Shanahan
2017-11-18 19:11:35 UTC
Permalink
There is a bug in my LinkManager changes. Specifically, I made the
totally newbie mistake of accessing memory based on a pointer without
allowing for it being null, and it turns out it can be null :-(

The primary report for this is
https://bz.apache.org/ooo/show_bug.cgi?id=127581, "Writer crashes after
copying all content".

I would have expected the failure to be some form of access violation.
However, recent e-mails have convinced me that some paths include catch
blocks that conceal all exceptions, so it may be the root cause of other
problems.

I have checked a fix into the trunk, revision 1814994. However, trunk
has other changes.

The simplest way to check whether other bug reports are due to this is
to build a version that is identical to 4.1.4 except for the one fix.
Anything that works with that but not with 4.1.4 is a duplicate. Of
course, the more duplicates we have the worse the problem and the more
urgent a fix.

I am going ahead and doing the fix in my 4.1.5 working copy, but
activating 4.1.5 is a broader decision.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Patricia Shanahan
2017-11-18 20:49:43 UTC
Permalink
I'm attaching the patch in case anyone else wants to build their own
test version.
Post by Patricia Shanahan
There is a bug in my LinkManager changes. Specifically, I made the
totally newbie mistake of accessing memory based on a pointer without
allowing for it being null, and it turns out it can be null :-(
The primary report for this is
https://bz.apache.org/ooo/show_bug.cgi?id=127581, "Writer crashes after
copying all content".
I would have expected the failure to be some form of access violation.
However, recent e-mails have convinced me that some paths include catch
blocks that conceal all exceptions, so it may be the root cause of other
problems.
I have checked a fix into the trunk, revision 1814994. However, trunk
has other changes.
The simplest way to check whether other bug reports are due to this is
to build a version that is identical to 4.1.4 except for the one fix.
Anything that works with that but not with 4.1.4 is a duplicate. Of
course, the more duplicates we have the worse the problem and the more
urgent a fix.
I am going ahead and doing the fix in my 4.1.5 working copy, but
activating 4.1.5 is a broader decision.
---------------------------------------------------------------------
Jim Jagielski
2017-11-19 15:11:12 UTC
Permalink
Just to be clear:

SetUserAllowsLinkUpdate(pLink, GetUserAllowsLinkUpdate(parent));

is OK if parent == NULL? That is, does GetUserAllowsLinkUpdate()
work OK if passed NULL? Or, if parent is NULL, should we skip
calling SetUserAllowsLinkUpdate()?
I'm attaching the patch in case anyone else wants to build their own test version.
There is a bug in my LinkManager changes. Specifically, I made the totally newbie mistake of accessing memory based on a pointer without allowing for it being null, and it turns out it can be null :-(
The primary report for this is https://bz.apache.org/ooo/show_bug.cgi?id=127581, "Writer crashes after copying all content".
I would have expected the failure to be some form of access violation. However, recent e-mails have convinced me that some paths include catch blocks that conceal all exceptions, so it may be the root cause of other problems.
I have checked a fix into the trunk, revision 1814994. However, trunk has other changes.
The simplest way to check whether other bug reports are due to this is to build a version that is identical to 4.1.4 except for the one fix. Anything that works with that but not with 4.1.4 is a duplicate. Of course, the more duplicates we have the worse the problem and the more urgent a fix.
I am going ahead and doing the fix in my 4.1.5 working copy, but activating 4.1.5 is a broader decision.
---------------------------------------------------------------------
<null_pointer.patch>
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Patricia Shanahan
2017-11-19 15:21:39 UTC
Permalink
The null check inside the mAutoAskUpdateAllLinks test is something of an
over-reaction on my part, in the direction of defensive programming.
mAutoAskUpdateAllLinks is only true in two specific cases, both of which
I have reviewed. The bug was doing the parent look-up outside that if block.

I have tested forcing the parent to null in a debugger. It does not
crash. I suspect it would not necessarily pick the right parent window
if multiple windows are open.
Post by Jim Jagielski
SetUserAllowsLinkUpdate(pLink, GetUserAllowsLinkUpdate(parent));
is OK if parent == NULL? That is, does GetUserAllowsLinkUpdate()
work OK if passed NULL? Or, if parent is NULL, should we skip
calling SetUserAllowsLinkUpdate()?
I'm attaching the patch in case anyone else wants to build their own test version.
There is a bug in my LinkManager changes. Specifically, I made the totally newbie mistake of accessing memory based on a pointer without allowing for it being null, and it turns out it can be null :-(
The primary report for this is https://bz.apache.org/ooo/show_bug.cgi?id=127581, "Writer crashes after copying all content".
I would have expected the failure to be some form of access violation. However, recent e-mails have convinced me that some paths include catch blocks that conceal all exceptions, so it may be the root cause of other problems.
I have checked a fix into the trunk, revision 1814994. However, trunk has other changes.
The simplest way to check whether other bug reports are due to this is to build a version that is identical to 4.1.4 except for the one fix. Anything that works with that but not with 4.1.4 is a duplicate. Of course, the more duplicates we have the worse the problem and the more urgent a fix.
I am going ahead and doing the fix in my 4.1.5 working copy, but activating 4.1.5 is a broader decision.
---------------------------------------------------------------------
<null_pointer.patch>
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Patricia Shanahan
2017-11-19 15:40:05 UTC
Permalink
Jim,

I am going to be away from computers for most of the day. If you have
everything you want tested in 4.1.5 checked in, I would like you to
trigger a request for general testing.

In particular, anyone who is working a bug report that is a regression
between 4.1.3 and 4.1.4 should test it with the 4.1.5 branch, regardless
of the symptoms.

Originally, I expected my null point bug to manifest as an access
violation, as is the case for the original report. I was monitoring
bugzilla for any similar reports. From dev@ discussion, I have learned
there are instances of catching and hiding all exceptions. That means
data structures could be left in an inconsistent state without AOO
crashing or the access violation being reported, and almost any symptom
could result.
Post by Patricia Shanahan
The null check inside the mAutoAskUpdateAllLinks test is something of an
over-reaction on my part, in the direction of defensive programming.
mAutoAskUpdateAllLinks is only true in two specific cases, both of which
I have reviewed. The bug was doing the parent look-up outside that if block.
I have tested forcing the parent to null in a debugger. It does not
crash. I suspect it would not necessarily pick the right parent window
if multiple windows are open.
     SetUserAllowsLinkUpdate(pLink, GetUserAllowsLinkUpdate(parent));
is OK if parent == NULL? That is, does GetUserAllowsLinkUpdate()
work OK if passed NULL? Or, if parent is NULL, should we skip
calling SetUserAllowsLinkUpdate()?
I'm attaching the patch in case anyone else wants to build their own test version.
Post by Patricia Shanahan
There is a bug in my LinkManager changes. Specifically, I made the
totally newbie mistake of accessing memory based on a pointer
without allowing for it being null, and it turns out it can be null :-(
The primary report for this is
https://bz.apache.org/ooo/show_bug.cgi?id=127581, "Writer crashes
after copying all content".
I would have expected the failure to be some form of access
violation. However, recent e-mails have convinced me that some paths
include catch blocks that conceal all exceptions, so it may be the
root cause of other problems.
I have checked a fix into the trunk, revision 1814994. However,
trunk has other changes.
The simplest way to check whether other bug reports are due to this
is to build a version that is identical to 4.1.4 except for the one
fix. Anything that works with that but not with 4.1.4 is a
duplicate. Of course, the more duplicates we have the worse the
problem and the more urgent a fix.
I am going ahead and doing the fix in my 4.1.5 working copy, but
activating 4.1.5 is a broader decision.
---------------------------------------------------------------------
<null_pointer.patch>
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Jim Jagielski
2017-11-19 16:08:32 UTC
Permalink
I think I will spend some time creating some 4.1.5-dev builds for people to
play with...
Jim,
I am going to be away from computers for most of the day. If you have everything you want tested in 4.1.5 checked in, I would like you to trigger a request for general testing.
In particular, anyone who is working a bug report that is a regression between 4.1.3 and 4.1.4 should test it with the 4.1.5 branch, regardless of the symptoms.
The null check inside the mAutoAskUpdateAllLinks test is something of an over-reaction on my part, in the direction of defensive programming. mAutoAskUpdateAllLinks is only true in two specific cases, both of which I have reviewed. The bug was doing the parent look-up outside that if block.
I have tested forcing the parent to null in a debugger. It does not crash. I suspect it would not necessarily pick the right parent window if multiple windows are open.
Post by Jim Jagielski
SetUserAllowsLinkUpdate(pLink, GetUserAllowsLinkUpdate(parent));
is OK if parent == NULL? That is, does GetUserAllowsLinkUpdate()
work OK if passed NULL? Or, if parent is NULL, should we skip
calling SetUserAllowsLinkUpdate()?
I'm attaching the patch in case anyone else wants to build their own test version.
There is a bug in my LinkManager changes. Specifically, I made the totally newbie mistake of accessing memory based on a pointer without allowing for it being null, and it turns out it can be null :-(
The primary report for this is https://bz.apache.org/ooo/show_bug.cgi?id=127581, "Writer crashes after copying all content".
I would have expected the failure to be some form of access violation. However, recent e-mails have convinced me that some paths include catch blocks that conceal all exceptions, so it may be the root cause of other problems.
I have checked a fix into the trunk, revision 1814994. However, trunk has other changes.
The simplest way to check whether other bug reports are due to this is to build a version that is identical to 4.1.4 except for the one fix. Anything that works with that but not with 4.1.4 is a duplicate. Of course, the more duplicates we have the worse the problem and the more urgent a fix.
I am going ahead and doing the fix in my 4.1.5 working copy, but activating 4.1.5 is a broader decision.
---------------------------------------------------------------------
<null_pointer.patch>
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Kay Schenk
2017-11-19 17:47:05 UTC
Permalink
Post by Jim Jagielski
I think I will spend some time creating some 4.1.5-dev builds for people to
play with...
Post by Patricia Shanahan
Jim,
​That would be great. :)
Post by Jim Jagielski
Post by Patricia Shanahan
I am going to be away from computers for most of the day. If you have
everything you want tested in 4.1.5 checked in, I would like you to trigger
a request for general testing.
Post by Patricia Shanahan
In particular, anyone who is working a bug report that is a regression
between 4.1.3 and 4.1.4 should test it with the 4.1.5 branch, regardless of
the symptoms.
Post by Patricia Shanahan
Originally, I expected my null point bug to manifest as an access
violation, as is the case for the original report. I was monitoring
there are instances of catching and hiding all exceptions. That means data
structures could be left in an inconsistent state without AOO crashing or
the access violation being reported, and almost any symptom could result.
Post by Patricia Shanahan
Post by Patricia Shanahan
The null check inside the mAutoAskUpdateAllLinks test is something of
an over-reaction on my part, in the direction of defensive programming.
mAutoAskUpdateAllLinks is only true in two specific cases, both of which I
have reviewed. The bug was doing the parent look-up outside that if block.
Post by Patricia Shanahan
Post by Patricia Shanahan
I have tested forcing the parent to null in a debugger. It does not
crash. I suspect it would not necessarily pick the right parent window if
multiple windows are open.
Post by Patricia Shanahan
Post by Patricia Shanahan
Post by Jim Jagielski
SetUserAllowsLinkUpdate(pLink, GetUserAllowsLinkUpdate(parent));
is OK if parent == NULL? That is, does GetUserAllowsLinkUpdate()
work OK if passed NULL? Or, if parent is NULL, should we skip
calling SetUserAllowsLinkUpdate()?
Post by Patricia Shanahan
I'm attaching the patch in case anyone else wants to build their own
test version.
Post by Patricia Shanahan
Post by Patricia Shanahan
Post by Jim Jagielski
Post by Patricia Shanahan
Post by Patricia Shanahan
There is a bug in my LinkManager changes. Specifically, I made the
totally newbie mistake of accessing memory based on a pointer without
allowing for it being null, and it turns out it can be null :-(
Post by Patricia Shanahan
Post by Patricia Shanahan
Post by Jim Jagielski
Post by Patricia Shanahan
Post by Patricia Shanahan
The primary report for this is https://bz.apache.org/ooo/
show_bug.cgi?id=127581, "Writer crashes after copying all content".
Post by Patricia Shanahan
Post by Patricia Shanahan
Post by Jim Jagielski
Post by Patricia Shanahan
Post by Patricia Shanahan
I would have expected the failure to be some form of access
violation. However, recent e-mails have convinced me that some paths
include catch blocks that conceal all exceptions, so it may be the root
cause of other problems.
Post by Patricia Shanahan
Post by Patricia Shanahan
Post by Jim Jagielski
Post by Patricia Shanahan
Post by Patricia Shanahan
I have checked a fix into the trunk, revision 1814994. However,
trunk has other changes.
Post by Patricia Shanahan
Post by Patricia Shanahan
Post by Jim Jagielski
Post by Patricia Shanahan
Post by Patricia Shanahan
The simplest way to check whether other bug reports are due to this
is to build a version that is identical to 4.1.4 except for the one fix.
Anything that works with that but not with 4.1.4 is a duplicate. Of course,
the more duplicates we have the worse the problem and the more urgent a fix.
Post by Patricia Shanahan
Post by Patricia Shanahan
Post by Jim Jagielski
Post by Patricia Shanahan
Post by Patricia Shanahan
I am going ahead and doing the fix in my 4.1.5 working copy, but
activating 4.1.5 is a broader decision.
Post by Patricia Shanahan
Post by Patricia Shanahan
Post by Jim Jagielski
Post by Patricia Shanahan
Post by Patricia Shanahan
------------------------------------------------------------
---------
Post by Patricia Shanahan
Post by Patricia Shanahan
Post by Jim Jagielski
Post by Patricia Shanahan
<null_pointer.patch>
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
--
----------------------------------------------------------------------
MzK

"Only the truth will save you now."
-- Ensei Tankado, "Digital Fortress"
Patricia Shanahan
2017-11-19 22:43:27 UTC
Permalink
Now that I have a bit more time, I wanted to thank Jim for raising the
question. I really want people to review my code and question anything
that seems dubious.
Post by Patricia Shanahan
The null check inside the mAutoAskUpdateAllLinks test is something of an
over-reaction on my part, in the direction of defensive programming.
mAutoAskUpdateAllLinks is only true in two specific cases, both of which
I have reviewed. The bug was doing the parent look-up outside that if block.
I have tested forcing the parent to null in a debugger. It does not
crash. I suspect it would not necessarily pick the right parent window
if multiple windows are open.
     SetUserAllowsLinkUpdate(pLink, GetUserAllowsLinkUpdate(parent));
is OK if parent == NULL? That is, does GetUserAllowsLinkUpdate()
work OK if passed NULL? Or, if parent is NULL, should we skip
calling SetUserAllowsLinkUpdate()?
I'm attaching the patch in case anyone else wants to build their own test version.
Post by Patricia Shanahan
There is a bug in my LinkManager changes. Specifically, I made the
totally newbie mistake of accessing memory based on a pointer
without allowing for it being null, and it turns out it can be null :-(
The primary report for this is
https://bz.apache.org/ooo/show_bug.cgi?id=127581, "Writer crashes
after copying all content".
I would have expected the failure to be some form of access
violation. However, recent e-mails have convinced me that some paths
include catch blocks that conceal all exceptions, so it may be the
root cause of other problems.
I have checked a fix into the trunk, revision 1814994. However,
trunk has other changes.
The simplest way to check whether other bug reports are due to this
is to build a version that is identical to 4.1.4 except for the one
fix. Anything that works with that but not with 4.1.4 is a
duplicate. Of course, the more duplicates we have the worse the
problem and the more urgent a fix.
I am going ahead and doing the fix in my 4.1.5 working copy, but
activating 4.1.5 is a broader decision.
---------------------------------------------------------------------
<null_pointer.patch>
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Jim Jagielski
2017-11-18 21:20:37 UTC
Permalink
We do have the AOO415 branch! :)
There is a bug in my LinkManager changes. Specifically, I made the totally newbie mistake of accessing memory based on a pointer without allowing for it being null, and it turns out it can be null :-(
The primary report for this is https://bz.apache.org/ooo/show_bug.cgi?id=127581, "Writer crashes after copying all content".
I would have expected the failure to be some form of access violation. However, recent e-mails have convinced me that some paths include catch blocks that conceal all exceptions, so it may be the root cause of other problems.
I have checked a fix into the trunk, revision 1814994. However, trunk has other changes.
The simplest way to check whether other bug reports are due to this is to build a version that is identical to 4.1.4 except for the one fix. Anything that works with that but not with 4.1.4 is a duplicate. Of course, the more duplicates we have the worse the problem and the more urgent a fix.
I am going ahead and doing the fix in my 4.1.5 working copy, but activating 4.1.5 is a broader decision.
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Patricia Shanahan
2017-11-18 23:01:35 UTC
Permalink
I see you have checked in some Mac building changes. Would it be better
to keep the two fixes separate, or encourage testing both of them together?
Post by Jim Jagielski
We do have the AOO415 branch! :)
There is a bug in my LinkManager changes. Specifically, I made the totally newbie mistake of accessing memory based on a pointer without allowing for it being null, and it turns out it can be null :-(
The primary report for this is https://bz.apache.org/ooo/show_bug.cgi?id=127581, "Writer crashes after copying all content".
I would have expected the failure to be some form of access violation. However, recent e-mails have convinced me that some paths include catch blocks that conceal all exceptions, so it may be the root cause of other problems.
I have checked a fix into the trunk, revision 1814994. However, trunk has other changes.
The simplest way to check whether other bug reports are due to this is to build a version that is identical to 4.1.4 except for the one fix. Anything that works with that but not with 4.1.4 is a duplicate. Of course, the more duplicates we have the worse the problem and the more urgent a fix.
I am going ahead and doing the fix in my 4.1.5 working copy, but activating 4.1.5 is a broader decision.
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Peter kovacs
2017-11-19 11:06:52 UTC
Permalink
+1 for testing together. If it doesn't work we can go into analysis.
Post by Patricia Shanahan
I see you have checked in some Mac building changes. Would it be better
to keep the two fixes separate, or encourage testing both of them together?
Post by Jim Jagielski
We do have the AOO415 branch! :)
Post by Patricia Shanahan
There is a bug in my LinkManager changes. Specifically, I made the
totally newbie mistake of accessing memory based on a pointer without
allowing for it being null, and it turns out it can be null :-(
Post by Jim Jagielski
Post by Patricia Shanahan
The primary report for this is
https://bz.apache.org/ooo/show_bug.cgi?id=127581, "Writer crashes after
copying all content".
Post by Jim Jagielski
Post by Patricia Shanahan
I would have expected the failure to be some form of access
violation. However, recent e-mails have convinced me that some paths
include catch blocks that conceal all exceptions, so it may be the root
cause of other problems.
Post by Jim Jagielski
Post by Patricia Shanahan
I have checked a fix into the trunk, revision 1814994. However,
trunk has other changes.
Post by Jim Jagielski
Post by Patricia Shanahan
The simplest way to check whether other bug reports are due to this
is to build a version that is identical to 4.1.4 except for the one
fix. Anything that works with that but not with 4.1.4 is a duplicate.
Of course, the more duplicates we have the worse the problem and the
more urgent a fix.
Post by Jim Jagielski
Post by Patricia Shanahan
I am going ahead and doing the fix in my 4.1.5 working copy, but
activating 4.1.5 is a broader decision.
---------------------------------------------------------------------
Post by Jim Jagielski
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Jim Jagielski
2017-11-19 13:49:01 UTC
Permalink
I think together is best. :)
I see you have checked in some Mac building changes. Would it be better to keep the two fixes separate, or encourage testing both of them together?
Post by Jim Jagielski
We do have the AOO415 branch! :)
There is a bug in my LinkManager changes. Specifically, I made the totally newbie mistake of accessing memory based on a pointer without allowing for it being null, and it turns out it can be null :-(
The primary report for this is https://bz.apache.org/ooo/show_bug.cgi?id=127581, "Writer crashes after copying all content".
I would have expected the failure to be some form of access violation. However, recent e-mails have convinced me that some paths include catch blocks that conceal all exceptions, so it may be the root cause of other problems.
I have checked a fix into the trunk, revision 1814994. However, trunk has other changes.
The simplest way to check whether other bug reports are due to this is to build a version that is identical to 4.1.4 except for the one fix. Anything that works with that but not with 4.1.4 is a duplicate. Of course, the more duplicates we have the worse the problem and the more urgent a fix.
I am going ahead and doing the fix in my 4.1.5 working copy, but activating 4.1.5 is a broader decision.
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Matthias Seidel
2017-11-19 22:54:16 UTC
Permalink
Hi Jim,

I saw that you updated the metadata for 4.1.5.

One file is still missing, see:
https://bz.apache.org/ooo/show_bug.cgi?id=127552#c2

Regards, Matthias
Post by Jim Jagielski
We do have the AOO415 branch! :)
There is a bug in my LinkManager changes. Specifically, I made the totally newbie mistake of accessing memory based on a pointer without allowing for it being null, and it turns out it can be null :-(
The primary report for this is https://bz.apache.org/ooo/show_bug.cgi?id=127581, "Writer crashes after copying all content".
I would have expected the failure to be some form of access violation. However, recent e-mails have convinced me that some paths include catch blocks that conceal all exceptions, so it may be the root cause of other problems.
I have checked a fix into the trunk, revision 1814994. However, trunk has other changes.
The simplest way to check whether other bug reports are due to this is to build a version that is identical to 4.1.4 except for the one fix. Anything that works with that but not with 4.1.4 is a duplicate. Of course, the more duplicates we have the worse the problem and the more urgent a fix.
I am going ahead and doing the fix in my 4.1.5 working copy, but activating 4.1.5 is a broader decision.
---------------------------------------------------------------------
---------------------------------------------------------------------
Jim Jagielski
2017-11-20 15:49:24 UTC
Permalink
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: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Rory O'Farrell
2017-11-20 16:01:20 UTC
Permalink
On Mon, 20 Nov 2017 10:49:24 -0500
Post by Jim Jagielski
I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
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.
I'm getting "No permission message" when I attempt to access http://home.apache.org/~jim/AOO-builds/AOO-4.1.5-dev-20171120/en-US/Apache_OpenOffice_4.1.5_Linux_x86-64_install-deb_en-US.tar.gz

I don't use many of the features of OO - merely Writer, simple (trivial) Calc, and occasional Impress, but I will try 4.1.5 for my daily use.
--
Rory O'Farrell <***@iol.ie>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Jim Jagielski
2017-11-20 16:07:49 UTC
Permalink
Permissions should be fixed now. Thx. and Sorry :)
Post by Rory O'Farrell
On Mon, 20 Nov 2017 10:49:24 -0500
Post by Jim Jagielski
I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
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.
I'm getting "No permission message" when I attempt to access http://home.apache.org/~jim/AOO-builds/AOO-4.1.5-dev-20171120/en-US/Apache_OpenOffice_4.1.5_Linux_x86-64_install-deb_en-US.tar.gz
I don't use many of the features of OO - merely Writer, simple (trivial) Calc, and occasional Impress, but I will try 4.1.5 for my daily use.
--
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Rory O'Farrell
2017-11-20 16:14:53 UTC
Permalink
On Mon, 20 Nov 2017 11:07:49 -0500
Post by Jim Jagielski
Permissions should be fixed now. Thx. and Sorry :)
Thanks, downloading now.

Rory
Post by Jim Jagielski
Post by Rory O'Farrell
On Mon, 20 Nov 2017 10:49:24 -0500
Post by Jim Jagielski
I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
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.
I'm getting "No permission message" when I attempt to access http://home.apache.org/~jim/AOO-builds/AOO-4.1.5-dev-20171120/en-US/Apache_OpenOffice_4.1.5_Linux_x86-64_install-deb_en-US.tar.gz
I don't use many of the features of OO - merely Writer, simple (trivial) Calc, and occasional Impress, but I will try 4.1.5 for my daily use.
--
---------------------------------------------------------------------
---------------------------------------------------------------------
--
Rory O'Farrell <***@iol.ie>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Rory O'Farrell
2017-11-20 16:33:35 UTC
Permalink
On Mon, 20 Nov 2017 16:14:53 +0000
Post by Rory O'Farrell
On Mon, 20 Nov 2017 11:07:49 -0500
Post by Jim Jagielski
Permissions should be fixed now. Thx. and Sorry :)
Thanks, downloading now.
Rory
Now installed, opened and running.

Rory
Post by Rory O'Farrell
Post by Jim Jagielski
Post by Rory O'Farrell
On Mon, 20 Nov 2017 10:49:24 -0500
Post by Jim Jagielski
I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
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.
I'm getting "No permission message" when I attempt to access http://home.apache.org/~jim/AOO-builds/AOO-4.1.5-dev-20171120/en-US/Apache_OpenOffice_4.1.5_Linux_x86-64_install-deb_en-US.tar.gz
I don't use many of the features of OO - merely Writer, simple (trivial) Calc, and occasional Impress, but I will try 4.1.5 for my daily use.
--
---------------------------------------------------------------------
---------------------------------------------------------------------
--
---------------------------------------------------------------------
--
Rory O'Farrell <***@iol.ie>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Larry Gusaas
2017-11-20 18:18:11 UTC
Permalink
Database & spreadsheet regressions fixed.
Larry
Post by Jim Jagielski
I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
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: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Dave Fisher
2017-11-21 18:35:29 UTC
Permalink
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.

I tried to test issue 127600 but I can’t understand what was done in the first place.

Regards,
Dave
Post by Larry Gusaas
Database & spreadsheet regressions fixed.
Larry
Post by Jim Jagielski
I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
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
---------------------------------------------------------------------
Matthias Seidel
2017-11-21 22:52:31 UTC
Permalink
Post by 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
Post by Dave Fisher
I tried to test issue 127600 but I can’t understand what was done in the first place.
Regards,
Dave
Post by Larry Gusaas
Database & spreadsheet regressions fixed.
Larry
Post by Jim Jagielski
I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
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
---------------------------------------------------------------------
Damjan Jovanovic
2017-11-22 10:37:31 UTC
Permalink
Thank you, but when are these 4.1.x releases going to stop?

We have so much lined up for 4.2.0.

Damjan
Post by Jim Jagielski
I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
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.
---------------------------------------------------------------------
Patricia Shanahan
2017-11-22 12:05:14 UTC
Permalink
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.
Post by Damjan Jovanovic
Thank you, but when are these 4.1.x releases going to stop?
We have so much lined up for 4.2.0.
Damjan
Post by Jim Jagielski
I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
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.
---------------------------------------------------------------------
---
This email has been checked for viruses by AVG.
http://www.avg.com


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Damjan Jovanovic
2017-11-22 12:31:45 UTC
Permalink
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.
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.
Post by Damjan Jovanovic
Thank you, but when are these 4.1.x releases going to stop?
We have so much lined up for 4.2.0.
Damjan
I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
Post by Jim Jagielski
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.
---------------------------------------------------------------------
---
This email has been checked for viruses by AVG.
http://www.avg.com
---------------------------------------------------------------------
Matthias Seidel
2017-11-22 12:52:27 UTC
Permalink
We have buildbots building 4.1.4 every week...

Would it make sense to switch them to 4.1.5?

Regards, Matthias
Post by 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.
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.
Post by Damjan Jovanovic
Thank you, but when are these 4.1.x releases going to stop?
We have so much lined up for 4.2.0.
Damjan
I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
Post by Jim Jagielski
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.
---------------------------------------------------------------------
---
This email has been checked for viruses by AVG.
http://www.avg.com
---------------------------------------------------------------------
Pedro Lino
2017-11-22 14:17:54 UTC
Permalink
Hi Matthias, all
Post by Matthias Seidel
We have buildbots building 4.1.4 every week...
In my opinion that is a waste of electric power and computing resources
Post by Matthias Seidel
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
Post by Matthias Seidel
Post by Damjan Jovanovic
Post by 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.
Post by Damjan Jovanovic
Post by Damjan Jovanovic
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.
Post by Damjan Jovanovic
Post by Damjan Jovanovic
Thank you, but when are these 4.1.x releases going to stop?
We have so much lined up for 4.2.0.
Damjan
I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
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.
---------------------------------------------
Post by Damjan Jovanovic
---
This email has been checked for viruses by AVG.
http://www.avg.com
---------------------------------------------
Matthias Seidel
2017-11-22 14:40:30 UTC
Permalink
Post by Pedro Lino
Hi Matthias, all
Post by Matthias Seidel
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...
Post by Pedro Lino
Post by Matthias Seidel
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
Post by Pedro Lino
Regards,
Pedro
Post by Matthias Seidel
Post by Damjan Jovanovic
Post by 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.
Post by Damjan Jovanovic
Post by Damjan Jovanovic
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.
Post by Damjan Jovanovic
Post by Damjan Jovanovic
Thank you, but when are these 4.1.x releases going to stop?
We have so much lined up for 4.2.0.
Damjan
I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
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.
---------------------------------------------
Post by Damjan Jovanovic
---
This email has been checked for viruses by AVG.
http://www.avg.com
---------------------------------------------
Pedro Lino
2017-11-22 16:11:01 UTC
Permalink
Post by Matthias Seidel
Post by Matthias Seidel
Post by Matthias Seidel
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)
Post by Matthias Seidel
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 ?
Peter kovacs
2017-11-22 16:34:04 UTC
Permalink
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.
Post by 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.
Post by Damjan Jovanovic
Thank you, but when are these 4.1.x releases going to stop?
We have so much lined up for 4.2.0.
Damjan
Post by Jim Jagielski
I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
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.
---------------------------------------------------------------------
---
This email has been checked for viruses by AVG.
http://www.avg.com
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Dave Fisher
2017-11-22 16:48:12 UTC
Permalink
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
Post by Peter kovacs
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.
Post by 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.
Post by Damjan Jovanovic
Thank you, but when are these 4.1.x releases going to stop?
We have so much lined up for 4.2.0.
Damjan
Post by Jim Jagielski
I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
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.
---------------------------------------------------------------------
---
This email has been checked for viruses by AVG.
http://www.avg.com
---------------------------------------------------------------------
---------------------------------------------------------------------
Damjan Jovanovic
2017-11-22 17:36:53 UTC
Permalink
Post by Dave Fisher
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.
Patricia Shanahan
2017-11-22 20:00:26 UTC
Permalink
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.
Post by Damjan Jovanovic
Post by Dave Fisher
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
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: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Marcus
2017-11-22 20:24:33 UTC
Permalink
Post by 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.
Post by Patricia Shanahan
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
Post by Patricia Shanahan
Post by Damjan Jovanovic
Post by Dave Fisher
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
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: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Jim Jagielski
2017-11-23 03:26:49 UTC
Permalink
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: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Marcus
2017-11-23 11:52:06 UTC
Permalink
Post by 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: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Matthias Seidel
2017-11-23 16:50:09 UTC
Permalink
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! ;-)
Post by 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!
---------------------------------------------------------------------
Pedro Lino
2017-11-24 00:33:57 UTC
Permalink
Post by Matthias Seidel
Let's test! ;-)
It's a bit difficult since neither the OP nor joesch describe the steps to test DDE in https://bz.apache.org/ooo/show_bug.cgi?id=127601

However if the idea is to load dde-test.odt and then Update the values so that the values in odt reflect a change in the ods, then I do not get a crash but the values are never updated under Windows 10 (see attached image).

In fact these values are not updated regardless of the AOO or LO version used under Windows 10...
Rory O'Farrell
2017-11-23 17:31:48 UTC
Permalink
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 <***@iol.ie>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Matthias Seidel
2017-11-23 17:43:13 UTC
Permalink
Hi Rory,
Post by 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?
Post by Rory O'Farrell
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
2017-11-23 18:02:14 UTC
Permalink
On Thu, 23 Nov 2017 18:43:13 +0100
Post by Matthias Seidel
Hi Rory,
Post by 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.
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?
Post by Rory O'Farrell
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 <***@iol.ie>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Matthias Seidel
2017-11-23 18:20:30 UTC
Permalink
Post by Rory O'Farrell
On Thu, 23 Nov 2017 18:43:13 +0100
Post by Matthias Seidel
Hi Rory,
Post by 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.
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?
Post by Rory O'Farrell
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:

Loading Image...

This is the Start Center:

Loading Image...

;-)
Post by Rory O'Farrell
BTW, I am running on Xubuntu 64 bit 16.04.03 (fully updated)
Rory O'Farrell
2017-11-23 18:30:13 UTC
Permalink
On Thu, 23 Nov 2017 19:20:30 +0100
Post by Matthias Seidel
Post by Rory O'Farrell
On Thu, 23 Nov 2017 18:43:13 +0100
Post by Matthias Seidel
Hi Rory,
Post by 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.
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?
Post by Rory O'Farrell
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.
https://svn.apache.org/repos/asf/openoffice/trunk/main/default_images/introabout/intro.png
https://home.apache.org/~mseidel/Start%20Center%20+%20ASF%20logo.png
;-)
Post by Rory O'Farrell
BTW, I am running on Xubuntu 64 bit 16.04.03 (fully updated)
OK, then where I said "Splash Screen", I meant "Start Center".

In all cases I have ever seen the Splash Screen immediately transitions to the Start Center screen; on Forum we usually refer to the "Start Center" as the Splash Screen.
--
Rory O'Farrell <***@iol.ie>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Matthias Seidel
2017-11-23 18:36:50 UTC
Permalink
Post by Rory O'Farrell
On Thu, 23 Nov 2017 19:20:30 +0100
Post by Matthias Seidel
Post by Rory O'Farrell
On Thu, 23 Nov 2017 18:43:13 +0100
Post by Matthias Seidel
Hi Rory,
Post by 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.
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?
Post by Rory O'Farrell
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.
https://svn.apache.org/repos/asf/openoffice/trunk/main/default_images/introabout/intro.png
https://home.apache.org/~mseidel/Start%20Center%20+%20ASF%20logo.png
;-)
Post by Rory O'Farrell
BTW, I am running on Xubuntu 64 bit 16.04.03 (fully updated)
OK, then where I said "Splash Screen", I meant "Start Center".
In all cases I have ever seen the Splash Screen immediately transitions to the Start Center screen; on Forum we usually refer to the "Start Center" as the Splash Screen.
Sorry, that is very confusing for the user...

The Start Center is part of the program, while the Splash Screen is part
of the startup process.

https://en.wikipedia.org/wiki/Splash_screen
Jim Jagielski
2017-11-24 15:23:08 UTC
Permalink
Post by Matthias Seidel
Hi Rory,
Post by 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.
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?
Question: Is CentOS 5 still our preferred version, or should we deprecate
CentOS5 for CentOS 6?

There are some things that 4.2.0 requires requires some updated 3rd party
libs, like zip 3.0.0 or later, etc.

If I had to vote, I'd say w/ assume (and stay w/) CentOS 5 since the upgrade to
CentOS 6 will likely cause a lot of potential for regressions.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Peter Kovacs
2017-11-24 15:39:24 UTC
Permalink
I thought we add all dependencies to the build process. (thats why our
build takes ages.)
I thought the only distibution dependency is the build environment.
Maybe I am wrong. If so I do not understand how CentOS5 can be
compatible to everything else.
Post by Jim Jagielski
Post by Matthias Seidel
Hi Rory,
Post by 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.
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?
Question: Is CentOS 5 still our preferred version, or should we deprecate
CentOS5 for CentOS 6?
There are some things that 4.2.0 requires requires some updated 3rd party
libs, like zip 3.0.0 or later, etc.
If I had to vote, I'd say w/ assume (and stay w/) CentOS 5 since the upgrade to
CentOS 6 will likely cause a lot of potential for regressions.
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Jim Jagielski
2017-11-24 15:46:57 UTC
Permalink
True, but not ALL dependencies... for example, we require egrep :)
dnl ===================================================================
dnl Zip must be available or else it is an error, all platforms
dnl ===================================================================
if test -z "$ZIP" -o -z "$UNZIP"; then
AC_MSG_ERROR([Zip/Unzip are required to build, please install or use --with-zip-home],,)
fi
if "$ZIP" -FS < /dev/null 2>&1 | $EGREP "no such option: S" > /dev/null; then
AC_MSG_ERROR([Zip version 3.0 or newer is required to build, please install or use --with-zip-home],,)
fi
It does look like all previous builds, up to and including 4.1.4 were done on
CentOS5 (for the released binaries).

So the question is that w/ 4.2.0, do we no longer support CentOS 5 as a
supported build platform. Another dependency seems to be GIO, but we
can build w/o that. But is that really an option for our community builds??
I thought we add all dependencies to the build process. (thats why our build takes ages.)
I thought the only distibution dependency is the build environment.
Maybe I am wrong. If so I do not understand how CentOS5 can be compatible to everything else.
Post by Jim Jagielski
Post by Matthias Seidel
Hi Rory,
Post by 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.
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?
Question: Is CentOS 5 still our preferred version, or should we deprecate
CentOS5 for CentOS 6?
There are some things that 4.2.0 requires requires some updated 3rd party
libs, like zip 3.0.0 or later, etc.
If I had to vote, I'd say w/ assume (and stay w/) CentOS 5 since the upgrade to
CentOS 6 will likely cause a lot of potential for regressions.
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Damjan Jovanovic
2017-11-24 16:47:06 UTC
Permalink
CentOS 5 is now EOL, even its maintenance updates ended on 31 March 2017. I
think we have to move to CentOS 6.

I made GIO the default VFS searched by configure instead of GnomeVFS, as
that's what everybody has been using for years; AOO is pretty much the only
application still pulling in that ancient package with who knows what
security issues. It was done in this commit:

r1812655 | damjan | 2017-10-19 18:35:49 +0200 (Thu, 19 Oct 2017) | 6 lines
Changed paths:
M /openoffice/trunk/main/configure.ac

GnomeVFS was deprecated 9 years ago. Make GIO, its replacement,
the default searched by configure.ac instead.

----

If we really need GnomeVFS back, we can revert that commit, or use
./configure switches to favor GnomeVFS over GIO.

Damjan
Post by Jim Jagielski
True, but not ALL dependencies... for example, we require egrep :)
dnl ===================================================================
dnl Zip must be available or else it is an error, all platforms
dnl ===================================================================
if test -z "$ZIP" -o -z "$UNZIP"; then
AC_MSG_ERROR([Zip/Unzip are required to build, please install or use
--with-zip-home],,)
fi
if "$ZIP" -FS < /dev/null 2>&1 | $EGREP "no such option: S" > /dev/null;
then
AC_MSG_ERROR([Zip version 3.0 or newer is required to build, please
install or use --with-zip-home],,)
fi
It does look like all previous builds, up to and including 4.1.4 were done on
CentOS5 (for the released binaries).
So the question is that w/ 4.2.0, do we no longer support CentOS 5 as a
supported build platform. Another dependency seems to be GIO, but we
can build w/o that. But is that really an option for our community builds??
I thought we add all dependencies to the build process. (thats why our
build takes ages.)
I thought the only distibution dependency is the build environment.
Maybe I am wrong. If so I do not understand how CentOS5 can be
compatible to everything else.
Post by Jim Jagielski
On Nov 23, 2017, at 12:43 PM, Matthias Seidel <
Hi Rory,
Post by 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
Post by Jim Jagielski
Post by Rory O'Farrell
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
Post by Jim Jagielski
Post by Rory O'Farrell
** (soffice:2353): WARNING **: Unknown type: GailWindow
The file then opens; it will accept a simple edit, and close
correctly.
Post by Jim Jagielski
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?
Question: Is CentOS 5 still our preferred version, or should we
deprecate
Post by Jim Jagielski
CentOS5 for CentOS 6?
There are some things that 4.2.0 requires requires some updated 3rd
party
Post by Jim Jagielski
libs, like zip 3.0.0 or later, etc.
If I had to vote, I'd say w/ assume (and stay w/) CentOS 5 since the
upgrade to
Post by Jim Jagielski
CentOS 6 will likely cause a lot of potential for regressions.
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
Jim Jagielski
2017-11-24 17:02:12 UTC
Permalink
The more I think about it, I agree that deprecating CentOS5 for 4.2.x is the
Right Way To Go.

I plan on creating 2 CentOS6 VMs this weekend: one 64 and the other 32bit.
I'll put the CentOS5 VMs "on storage" for 4.1.x.
Post by Damjan Jovanovic
CentOS 5 is now EOL, even its maintenance updates ended on 31 March 2017. I
think we have to move to CentOS 6.
I made GIO the default VFS searched by configure instead of GnomeVFS, as
that's what everybody has been using for years; AOO is pretty much the only
application still pulling in that ancient package with who knows what
r1812655 | damjan | 2017-10-19 18:35:49 +0200 (Thu, 19 Oct 2017) | 6 lines
M /openoffice/trunk/main/configure.ac
GnomeVFS was deprecated 9 years ago. Make GIO, its replacement,
the default searched by configure.ac instead.
----
If we really need GnomeVFS back, we can revert that commit, or use
./configure switches to favor GnomeVFS over GIO.
Damjan
Post by Jim Jagielski
True, but not ALL dependencies... for example, we require egrep :)
dnl ===================================================================
dnl Zip must be available or else it is an error, all platforms
dnl ===================================================================
if test -z "$ZIP" -o -z "$UNZIP"; then
AC_MSG_ERROR([Zip/Unzip are required to build, please install or use
--with-zip-home],,)
fi
if "$ZIP" -FS < /dev/null 2>&1 | $EGREP "no such option: S" > /dev/null;
then
AC_MSG_ERROR([Zip version 3.0 or newer is required to build, please
install or use --with-zip-home],,)
fi
It does look like all previous builds, up to and including 4.1.4 were done on
CentOS5 (for the released binaries).
So the question is that w/ 4.2.0, do we no longer support CentOS 5 as a
supported build platform. Another dependency seems to be GIO, but we
can build w/o that. But is that really an option for our community builds??
I thought we add all dependencies to the build process. (thats why our
build takes ages.)
I thought the only distibution dependency is the build environment.
Maybe I am wrong. If so I do not understand how CentOS5 can be
compatible to everything else.
Post by Jim Jagielski
On Nov 23, 2017, at 12:43 PM, Matthias Seidel <
Hi Rory,
Post by 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
Post by Jim Jagielski
Post by Rory O'Farrell
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
Post by Jim Jagielski
Post by Rory O'Farrell
** (soffice:2353): WARNING **: Unknown type: GailWindow
The file then opens; it will accept a simple edit, and close
correctly.
Post by Jim Jagielski
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?
Question: Is CentOS 5 still our preferred version, or should we
deprecate
Post by Jim Jagielski
CentOS5 for CentOS 6?
There are some things that 4.2.0 requires requires some updated 3rd
party
Post by Jim Jagielski
libs, like zip 3.0.0 or later, etc.
If I had to vote, I'd say w/ assume (and stay w/) CentOS 5 since the
upgrade to
Post by Jim Jagielski
CentOS 6 will likely cause a lot of potential for regressions.
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Jim Jagielski
2017-11-25 15:37:26 UTC
Permalink
I have my 2 CentOS6 build VMs up and running. I am attempting
to build 4.2.0 (trunk) on the 64bit CentOS 6.9 VM 1st.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Andrea Pescetti
2017-11-26 22:52:20 UTC
Permalink
Post by Jim Jagielski
Question: Is CentOS 5 still our preferred version, or should we deprecate
CentOS5 for CentOS 6?
We should move to CentOS 6. I've explained it in detail at
https://bz.apache.org/ooo/show_bug.cgi?id=127513 more than 3 months ago
and I'll happily discuss this in a thread bearing an appropriate title.
Post by Jim Jagielski
There are some things that 4.2.0 requires requires some updated 3rd party
libs, like zip 3.0.0 or later, etc.
If I had to vote, I'd say w/ assume (and stay w/) CentOS 5 since the upgrade to
CentOS 6 will likely cause a lot of potential for regressions.
For any further 4.1.x release (if need be) I would definitely stick with
CentOS 5; changing would not make sense. But for trunk there is no
reason to delay the upgrade, see again my issue above.

Regards,
Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Jim Jagielski
2017-11-27 19:36:04 UTC
Permalink
Test builds for 4.2.0-dev for Linux64, Windows and macOS are now
available at:

http://home.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/ <http://home.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/>
Dave Fisher
2017-11-28 01:27:13 UTC
Permalink
Hi Jim,

The two 4.1.4 macOS bugs test as fixed on Mac Sierra.

Regards,
Dave
Post by Jim Jagielski
Test builds for 4.2.0-dev for Linux64, Windows and macOS are now
http://home.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/ <http://home.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/>
Dave Fisher
2017-11-30 16:15:59 UTC
Permalink
Hi Jim,

When I try the 4.2.0-dev build on Lion - 10.7.5 I get the following error report.

Process: launchd [304]
Path: /Applications/OpenOffice.app/Contents/MacOS/soffice
Identifier: org.openoffice.script
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: launchd [124]

Date/Time: 2017-11-30 08:01:45.999 -0800
OS Version: Mac OS X 10.7.5 (11G63)
Report Version: 9

Interval Since Last Report: 123093 sec
Crashes Since Last Report: 26
Per-App Crashes Since Last Report: 10
Anonymous UUID: 3E2C95F9-7BA1-4D3B-A2CA-770E8D2ADA86

Crashed Thread: Unknown

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00007fff5fc01028

Backtrace not available

Unknown thread crashed with X86 Thread State (64-bit):
rax: 0x0000000000000055 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x0000000000000000
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x00007fff5fc01028 rfl: 0x0000000000010203 cr2: 0x00007fff5fc01028
Logical CPU: 0

Binary images description not available


External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 1
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 404
thread_create: 0
thread_set_state: 0

Model: iMac8,1, BootROM IM81.00C1.B00, 2 processors, Intel Core 2 Duo, 3.06 GHz, 4 GB, SMC 1.30f1
Graphics: NVIDIA GeForce 8800 GS, NVIDIA GeForce 8800 GS, PCIe, 512 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR2 SDRAM, 667 MHz, 0xCE00000000000000, 0x4D342037305435363633435A332D43453620
Memory Module: BANK 1/DIMM1, 2 GB, DDR2 SDRAM, 667 MHz, 0xCE00000000000000, 0x4D342037305435363633435A332D43453620
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8C), Broadcom BCM43xx 1.0 (5.10.131.36.15)
Bluetooth: Version 4.0.8f17, 2 service, 18 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: ST1000DX002-2DV162, 1 TB
Parallel ATA Device: PIONEER DVD-RW DVR-K06A
USB Device: Keyboard Hub, apple_vendor_id, 0x1006, 0xfa200000 / 2
USB Device: Apple Optical USB Mouse, apple_vendor_id, 0x0304, 0xfa230000 / 4
USB Device: Apple Keyboard, apple_vendor_id, 0x0220, 0xfa220000 / 3
USB Device: Built-in iSight, apple_vendor_id, 0x8502, 0xfd400000 / 2
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x1a100000 / 2
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x820f, 0x1a110000 / 3
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x5d100000 / 2

Same machine works with 4.1.5 build w/Apple Java6 legacy and latest Oracle Java8.

Regards,
Dave
Post by Matthias Seidel
Hi Jim,
The two 4.1.4 macOS bugs test as fixed on Mac Sierra.
Regards,
Dave
Post by Jim Jagielski
Test builds for 4.2.0-dev for Linux64, Windows and macOS are now
http://home.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/ <http://home.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/>
Jim Jagielski
2017-11-30 16:21:05 UTC
Permalink
I think the current version wasn't built supporting 10.7... I think
what I've uploaded just was for 10.8 and later. I'm working on getting
10.7 and 4.2.0 totally happy together.
Post by Matthias Seidel
Hi Jim,
When I try the 4.2.0-dev build on Lion - 10.7.5 I get the following error report.
Process: launchd [304]
Path: /Applications/OpenOffice.app/Contents/MacOS/soffice
Identifier: org.openoffice.script
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: launchd [124]
Date/Time: 2017-11-30 08:01:45.999 -0800
OS Version: Mac OS X 10.7.5 (11G63)
Report Version: 9
Interval Since Last Report: 123093 sec
Crashes Since Last Report: 26
Per-App Crashes Since Last Report: 10
Anonymous UUID: 3E2C95F9-7BA1-4D3B-A2CA-770E8D2ADA86
Crashed Thread: Unknown
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00007fff5fc01028
Backtrace not available
rax: 0x0000000000000055 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x0000000000000000
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x00007fff5fc01028 rfl: 0x0000000000010203 cr2: 0x00007fff5fc01028
Logical CPU: 0
Binary images description not available
task_for_pid: 1
thread_create: 0
thread_set_state: 0
task_for_pid: 0
thread_create: 0
thread_set_state: 0
task_for_pid: 404
thread_create: 0
thread_set_state: 0
Model: iMac8,1, BootROM IM81.00C1.B00, 2 processors, Intel Core 2 Duo, 3.06 GHz, 4 GB, SMC 1.30f1
Graphics: NVIDIA GeForce 8800 GS, NVIDIA GeForce 8800 GS, PCIe, 512 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR2 SDRAM, 667 MHz, 0xCE00000000000000, 0x4D342037305435363633435A332D43453620
Memory Module: BANK 1/DIMM1, 2 GB, DDR2 SDRAM, 667 MHz, 0xCE00000000000000, 0x4D342037305435363633435A332D43453620
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8C), Broadcom BCM43xx 1.0 (5.10.131.36.15)
Bluetooth: Version 4.0.8f17, 2 service, 18 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: ST1000DX002-2DV162, 1 TB
Parallel ATA Device: PIONEER DVD-RW DVR-K06A
USB Device: Keyboard Hub, apple_vendor_id, 0x1006, 0xfa200000 / 2
USB Device: Apple Optical USB Mouse, apple_vendor_id, 0x0304, 0xfa230000 / 4
USB Device: Apple Keyboard, apple_vendor_id, 0x0220, 0xfa220000 / 3
USB Device: Built-in iSight, apple_vendor_id, 0x8502, 0xfd400000 / 2
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x1a100000 / 2
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x820f, 0x1a110000 / 3
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x5d100000 / 2
Same machine works with 4.1.5 build w/Apple Java6 legacy and latest Oracle Java8.
Regards,
Dave
Post by Matthias Seidel
Hi Jim,
The two 4.1.4 macOS bugs test as fixed on Mac Sierra.
Regards,
Dave
Post by Jim Jagielski
Test builds for 4.2.0-dev for Linux64, Windows and macOS are now
http://home.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/ <http://home.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Jim Jagielski
2017-11-30 16:31:52 UTC
Permalink
Just a FYI that so far, my 4.2.0 tests that haven't been uploaded
yet seem to work under 10.7.5!
Dave Fisher
2017-11-30 16:47:03 UTC
Permalink
Cool!
Post by Jim Jagielski
Just a FYI that so far, my 4.2.0 tests that haven't been uploaded
yet seem to work under 10.7.5!
<Screen Shot 2017-11-30 at 11.29.54 AM.png>
Larry Gusaas
2017-11-28 05:08:11 UTC
Permalink
The 4.1.4 spreadsheet bug is fixed in 4.2.0

At first, database wouldn't open at all. Had to reinstall the legacy Apple Java 6. Database
then worked. 4.1.4 worked without having the legacy Apple Java 6 installed on my computer. I
have the latest Java 9 installed. 4.2.0 sees Java 9 in the preferences but won't open database
without legacy Java.

Larry
Post by Jim Jagielski
Test builds for 4.2.0-dev for Linux64, Windows and macOS are now
http://home.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/ <http://home.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/>
--
_________________________________

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: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Jim Jagielski
2017-11-30 14:23:12 UTC
Permalink
What system? I am still on Sierra w/o legacy Java6 and 4.2.0-dev works
fine.
Post by Larry Gusaas
The 4.1.4 spreadsheet bug is fixed in 4.2.0
At first, database wouldn't open at all. Had to reinstall the legacy Apple Java 6. Database then worked. 4.1.4 worked without having the legacy Apple Java 6 installed on my computer. I have the latest Java 9 installed. 4.2.0 sees Java 9 in the preferences but won't open database without legacy Java.
Larry
Post by Jim Jagielski
Test builds for 4.2.0-dev for Linux64, Windows and macOS are now
http://home.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/ <http://home.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/>
--
_________________________________
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: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Larry Gusaas
2017-11-30 17:17:39 UTC
Permalink
High Sierra (10.13.1). I'll test later today on my other Mac which is still on Sierra.
Post by Jim Jagielski
What system? I am still on Sierra w/o legacy Java6 and 4.2.0-dev works
fine.
Post by Larry Gusaas
The 4.1.4 spreadsheet bug is fixed in 4.2.0
At first, database wouldn't open at all. Had to reinstall the legacy Apple Java 6. Database then worked. 4.1.4 worked without having the legacy Apple Java 6 installed on my computer. I have the latest Java 9 installed. 4.2.0 sees Java 9 in the preferences but won't open database without legacy Java.
Larry
Post by Jim Jagielski
Test builds for 4.2.0-dev for Linux64, Windows and macOS are now
http://home.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/ <http://home.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/>
--
_________________________________

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: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Larry Gusaas
2017-11-30 17:46:12 UTC
Permalink
I uninstalled legacy Java 6 on my Mac (High Sierra). Database still works. Very weird.
Post by Larry Gusaas
High Sierra (10.13.1). I'll test later today on my other Mac which is still on Sierra.
Post by Jim Jagielski
What system? I am still on Sierra w/o legacy Java6 and 4.2.0-dev works
fine.
Post by Larry Gusaas
The 4.1.4 spreadsheet bug is fixed in 4.2.0
At first, database wouldn't open at all. Had to reinstall the legacy Apple Java 6. Database
then worked. 4.1.4 worked without having the legacy Apple Java 6 installed on my computer.
I have the latest Java 9 installed. 4.2.0 sees Java 9 in the preferences but won't open
database without legacy Java.
Larry
Post by Jim Jagielski
Test builds for 4.2.0-dev for Linux64, Windows and macOS are now
http://home.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/
<http://home.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/>
__________
--
_________________________________

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: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Larry Gusaas
2017-12-01 00:58:07 UTC
Permalink
Installed 4.2.0-dev on my 2015 MacBook Pro, macOS Sierra 10.12.6, Java jdk-9.0.1. No legacy Java.
Database works fine.

On my 2013 MacBook Pro macOS High Sierra 10.13.1, Java jdk-9.0.1, AOO 4.2.0-dev the database is
still working after uninstalling legacy Java 6.

I have not clue why database wouldn't open with 4.2.0-dev until I installed Apple's legacy Java
6. Nothing else was changed.
Some strange anomaly on instalation.

Anyways, I have no problems with 4.2.0-dev  on two different computers.

Larry
Post by Larry Gusaas
High Sierra (10.13.1). I'll test later today on my other Mac which is still on Sierra.
Post by Jim Jagielski
What system? I am still on Sierra w/o legacy Java6 and 4.2.0-dev works
fine.
Post by Larry Gusaas
The 4.1.4 spreadsheet bug is fixed in 4.2.0
At first, database wouldn't open at all. Had to reinstall the legacy Apple Java 6. Database
then worked. 4.1.4 worked without having the legacy Apple Java 6 installed on my computer.
I have the latest Java 9 installed. 4.2.0 sees Java 9 in the preferences but won't open
database without legacy Java.
Larry
Post by Jim Jagielski
Test builds for 4.2.0-dev for Linux64, Windows and macOS are now
http://home.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/
<http://home.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/>
__________
--
_________________________________

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: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Jim Jagielski
2017-11-25 23:09:44 UTC
Permalink
I am uploading to:

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

4.2.0-dev builds for Linux64 and Windows... After that will
come Linux32 and macOS (assuming it builds... I've had
issues before).

These are based on HEAD of trunk, ~r1816311. The Linux builds
are built on CentOS 6.9.
Matthias Seidel
2017-11-26 10:54:39 UTC
Permalink
Post by Jim Jagielski
http://home.apache.org/~jim/AOO-builds/ <http://home.apache.org/~jim/AOO-builds/>
4.2.0-dev builds for Linux64 and Windows... After that will
come Linux32 and macOS (assuming it builds... I've had
issues before).
These are based on HEAD of trunk, ~r1816311. The Linux builds
are built on CentOS 6.9.
"You don't have permission to access
/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/de/Apache_OpenOffice_4.2.0_Linux_x86-64_install-deb_de.tar.gzon
this server."

;-)
Jim Jagielski
2017-11-26 14:03:54 UTC
Permalink
should be fixed now.
Post by Matthias Seidel
Post by Jim Jagielski
http://home.apache.org/~jim/AOO-builds/ <http://home.apache.org/~jim/AOO-builds/>
4.2.0-dev builds for Linux64 and Windows... After that will
come Linux32 and macOS (assuming it builds... I've had
issues before).
These are based on HEAD of trunk, ~r1816311. The Linux builds
are built on CentOS 6.9.
"You don't have permission to access
/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/de/Apache_OpenOffice_4.2.0_Linux_x86-64_install-deb_de.tar.gzon
this server."
;-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Matthias Seidel
2017-11-26 18:30:03 UTC
Permalink
Thanks, I could download and install the build now.

However, the bug [1] is still present for me on Ubuntu 16.04.3 (64bit).

So it is not only an issue when building on Ubuntu 14.04 (like our
buildbots do).

Regards, Matthias

[1] https://bz.apache.org/ooo/show_bug.cgi?id=127315
Post by Jim Jagielski
should be fixed now.
Post by Matthias Seidel
Post by Jim Jagielski
http://home.apache.org/~jim/AOO-builds/ <http://home.apache.org/~jim/AOO-builds/>
4.2.0-dev builds for Linux64 and Windows... After that will
come Linux32 and macOS (assuming it builds... I've had
issues before).
These are based on HEAD of trunk, ~r1816311. The Linux builds
are built on CentOS 6.9.
"You don't have permission to access
/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/de/Apache_OpenOffice_4.2.0_Linux_x86-64_install-deb_de.tar.gzon
this server."
;-)
---------------------------------------------------------------------
Damjan Jovanovic
2017-11-26 18:47:19 UTC
Permalink
When you get that error, before clicking "OK", please attach gdb and run
"thread apply all bt", and post the output.

Damjan
Post by Matthias Seidel
Thanks, I could download and install the build now.
However, the bug [1] is still present for me on Ubuntu 16.04.3 (64bit).
So it is not only an issue when building on Ubuntu 14.04 (like our
buildbots do).
Regards, Matthias
[1] https://bz.apache.org/ooo/show_bug.cgi?id=127315
Post by Jim Jagielski
should be fixed now.
On Nov 26, 2017, at 5:54 AM, Matthias Seidel <
Post by Jim Jagielski
http://home.apache.org/~jim/AOO-builds/ <
http://home.apache.org/~jim/AOO-builds/>
Post by Jim Jagielski
Post by Jim Jagielski
4.2.0-dev builds for Linux64 and Windows... After that will
come Linux32 and macOS (assuming it builds... I've had
issues before).
These are based on HEAD of trunk, ~r1816311. The Linux builds
are built on CentOS 6.9.
"You don't have permission to access
/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/de/Apache_
OpenOffice_4.2.0_Linux_x86-64_install-deb_de.tar.gzon
Post by Jim Jagielski
this server."
;-)
---------------------------------------------------------------------
Matthias Seidel
2017-12-01 17:34:16 UTC
Permalink
Post by Damjan Jovanovic
When you get that error, before clicking "OK", please attach gdb and run
"thread apply all bt", and post the output.
Damjan
Hi Damjan,

I will do this as soon as I figured out how it works... ;-)

gdb=Gnu Debugger?

Regards, Matthias
Post by Damjan Jovanovic
Post by Matthias Seidel
Thanks, I could download and install the build now.
However, the bug [1] is still present for me on Ubuntu 16.04.3 (64bit).
So it is not only an issue when building on Ubuntu 14.04 (like our
buildbots do).
Regards, Matthias
[1] https://bz.apache.org/ooo/show_bug.cgi?id=127315
Post by Jim Jagielski
should be fixed now.
On Nov 26, 2017, at 5:54 AM, Matthias Seidel <
Post by Jim Jagielski
http://home.apache.org/~jim/AOO-builds/ <
http://home.apache.org/~jim/AOO-builds/>
Post by Jim Jagielski
Post by Jim Jagielski
4.2.0-dev builds for Linux64 and Windows... After that will
come Linux32 and macOS (assuming it builds... I've had
issues before).
These are based on HEAD of trunk, ~r1816311. The Linux builds
are built on CentOS 6.9.
"You don't have permission to access
/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/de/Apache_
OpenOffice_4.2.0_Linux_x86-64_install-deb_de.tar.gzon
Post by Jim Jagielski
this server."
;-)
---------------------------------------------------------------------
Damjan Jovanovic
2017-12-01 18:25:05 UTC
Permalink
Yes it is :)

Thank you.
Post by Matthias Seidel
Post by Damjan Jovanovic
When you get that error, before clicking "OK", please attach gdb and run
"thread apply all bt", and post the output.
Damjan
Hi Damjan,
I will do this as soon as I figured out how it works... ;-)
gdb=Gnu Debugger?
Regards, Matthias
Post by Damjan Jovanovic
On Sun, Nov 26, 2017 at 8:30 PM, Matthias Seidel <
Post by Matthias Seidel
Thanks, I could download and install the build now.
However, the bug [1] is still present for me on Ubuntu 16.04.3 (64bit).
So it is not only an issue when building on Ubuntu 14.04 (like our
buildbots do).
Regards, Matthias
[1] https://bz.apache.org/ooo/show_bug.cgi?id=127315
Post by Jim Jagielski
should be fixed now.
On Nov 26, 2017, at 5:54 AM, Matthias Seidel <
Post by Jim Jagielski
http://home.apache.org/~jim/AOO-builds/ <
http://home.apache.org/~jim/AOO-builds/>
Post by Jim Jagielski
Post by Jim Jagielski
4.2.0-dev builds for Linux64 and Windows... After that will
come Linux32 and macOS (assuming it builds... I've had
issues before).
These are based on HEAD of trunk, ~r1816311. The Linux builds
are built on CentOS 6.9.
"You don't have permission to access
/~jim/AOO-builds/AOO-4.2.0-dev-r1816311/de/Apache_
OpenOffice_4.2.0_Linux_x86-64_install-deb_de.tar.gzon
Post by Jim Jagielski
this server."
;-)
---------------------------------------------------------------------
Kay Schenk
2017-11-23 22:36:43 UTC
Permalink
Post by 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?
​I was happy that I could build 4.2 recently on Linux-32 without issue! WOO
HOO!

Re "new" features...there is quite a backlog of translations, including
items in the Help section that are now about 3 years in arrears until 4.2.0
is out. Likely many other improvements including the recent DB access
glitch that Damjen fixed. Timewise, I think there is a bit more to do for
4.2.0 but probably not much.

Like others, I'd like to see AOO move on to 4.2.0 rather than 4.1.5.

​
Post by Dave Fisher
Regards,
Dave
Post by Peter kovacs
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.
Post by Peter kovacs
If the fix is indeed successfull with the build changes, we should
release the new build, and go on.
Post by Peter kovacs
Am 22. November 2017 13:05:14 MEZ schrieb Patricia Shanahan <
Post by 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.
Post by Damjan Jovanovic
Thank you, but when are these 4.1.x releases going to stop?
We have so much lined up for 4.2.0.
Damjan
Post by Jim Jagielski
I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
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.
---------------------------------------------------------------------
---
This email has been checked for viruses by AVG.
http://www.avg.com
---------------------------------------------------------------------
---------------------------------------------------------------------
--
----------------------------------------------------------------------
MzK

"Only the truth will save you now."
-- Ensei Tankado, "Digital Fortress"
Larry Gusaas
2017-11-23 23:06:57 UTC
Permalink
Post by 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?
​I was happy that I could build 4.2 recently on Linux-32 without issue! WOO
HOO!
Re "new" features...there is quite a backlog of translations, including
items in the Help section that are now about 3 years in arrears until 4.2.0
is out. Likely many other improvements including the recent DB access
glitch that Damjen fixed. Timewise, I think there is a bit more to do for
4.2.0 but probably not much.
Like others, I'd like to see AOO move on to 4.2.0 rather than 4.1.5.
There are serious regressions in 4.1.4 for Macs. The fix needs to be released now, not wait
until 4.2.0
--
_________________________________

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: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Jim Jagielski
2017-11-24 16:23:42 UTC
Permalink
There are serious regressions in 4.1.4 for Macs. The fix needs to be released now, not wait until 4.2.0
And at least 1 fix that address all platforms as well, so I do think a 4.1.5 will
be required.

Also, as mentioned on a different thread, the move from 4.1.x to 4.2.x
will mean that some older platforms will likely need to be dropped
and/or deprecated. For example, CentOS 5 lacks GIO-2.0, which means
that it is no longer, afaict, a candidate for our community build server
setup (which is what 4.0 and 4.1 were built on). Also, OS X 10.7
will likely need to be deprecated for 4.2.0.

The long and short is that there are, and possible will be,
some AOO users that cannot move to 4.2.0 and so we should
make sure that our "final" 4.1.x build is as good and solid and as
stable as we can make it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Patricia Shanahan
2017-11-24 16:48:03 UTC
Permalink
Post by Jim Jagielski
There are serious regressions in 4.1.4 for Macs. The fix needs to be released now, not wait until 4.2.0
And at least 1 fix that address all platforms as well, so I do think a 4.1.5 will
be required.
Also, as mentioned on a different thread, the move from 4.1.x to 4.2.x
will mean that some older platforms will likely need to be dropped
and/or deprecated. For example, CentOS 5 lacks GIO-2.0, which means
that it is no longer, afaict, a candidate for our community build server
setup (which is what 4.0 and 4.1 were built on). Also, OS X 10.7
will likely need to be deprecated for 4.2.0.
The long and short is that there are, and possible will be,
some AOO users that cannot move to 4.2.0 and so we should
make sure that our "final" 4.1.x build is as good and solid and as
stable as we can make it.
To answer Damjan's question "when are these 4.1.x releases going to
stop?", we need to continue with 4.1.x builds, and releases as needed,
at least until 4.2.0 development is complete.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Andrea Pescetti
2017-11-26 23:01:32 UTC
Permalink
Post by Patricia Shanahan
To answer Damjan's question "when are these 4.1.x releases going to
stop?", we need to continue with 4.1.x builds, and releases as needed,
at least until 4.2.0 development is complete.
This is correct but it misses a (probably taken for granted) detail: the
focus is only on 4.2.0.

Future 4.1.x releases may happen only if we need to fix regressions or
need to push a security fix. But no feature or "normal" bugfix work
should happen on 4.1.x any longer.

If we agree on this, then we are probably all on the same page as for
the roles of 4.1.x and 4.2.0.

Regards,
Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Continue reading on narkive:
Loading...