Re: [DISCUSS] Release 4.2: General Topics

[Don Lewis]

On 24 Aug, Pedro Giffuni wrote:
> Hi Don;
> 
>> On 24 Aug, Pedro Giffuni wrote:
>>>
>>>
>>> On 08/24/16 10:34, Pedro Giffuni wrote:
 Hello;

>>> ...
>>>

>   * [low priority] Updated bundled CoinMP.  There has been an API
> change, which prevents the FreeBSD port from using the system
> version.  Difficulty unknown ...
>

 This is important, I was unaware of it. Sadly, I don't think I will
 have time for it before the release.

>>>
>>> A quick look at this ... FreeBSD is using version 1.8.3 which appears
>>> to be the latest.
>>>
>>> AOO could use the same version by default, it's just a matter of getting
>>> the new version to build on all platforms. I think.
>>
>> Unfortunately it is not that easy.  When I was cleaning up the the
>> FreeBSD port a while back, I went through all of the --with-system knobs
>> and CoinMP was one that did not work and broke the build.  My memory is
>> fuzzy, but I think there was an incompatible API change.
>>
> 
> Hmm ... I just looked and the openoffice-devel FreeBSD port is using
> the system coinmp. Actually CoinMP is only a wrapper around the core
> Coin libraries. I have always considered using the core libraries 
> directly as that provides more powerful options but I haven't found
> the time and motivation to work on it.

Hey, you're right.  It was a long time ago when I last worked on the
--with system stuff.

> I did try updating the CoinMP patches and it was not easy/fun. The Mac
> changes are likely to be troublesome.
> 
>> There are some other bundled bits that have the same problem, but CoinMP
>> is big and takes a while to build, which is my main motivation in this
>> case.  ICU also falls into this category, but I already know that it is
>> too difficult.
>>
> 
> Yes, that one is difficult and while Symphony has a most of what we may 
> need, the problem is that it has to be tested "multilingually".

I think even that stuff is pretty far behind the latest ICU.

> I did update most of the components you mention and even gave a talk 
> about it ;).
> 
>> It looks like the others are:
>>  ucpp
> 
> We are using the latest version.

Hmn, I wonder why the FreeBSD port is using the bundled one.

>>  mdds
> 
> The developer behind it broke compatibility with the AOO code (on
> purpose, for all I know). The code is actually calling for a replacement 
> but since it works we are leaving it untouched.
> 
>>  hsqldb
> 
> SUN had a branch with the required changes. I have some WIP patch for 
> that but there are other issues, like the database format is 
> incompatible. I have to spend more time on that but the change is
> worth the rescue.
> 
>>  libxmlsec
> 
> AOO uses a heavily modified version. Updating it requires a lot of 
> effort, basically forking libxmlsec.
> 
>>  stax
> 
> This is actually unused and can be thrown away, unless you are still
> using something older than Java 5.
> 
>>  rhino
> 
> Oh yes, we updated this once but it's category B so there's not a lot of 
> motivation to work on it. Newer java has functionality that can replace it.
> 
>>  xsltml
> 
> I don't remember well this one. I think it depended on something else 
> and ultimately I was just happy about using the system version.
> 
>>  saxon
> 
> The latest versions (saxon-he) lack the functionality AOO requires.
> We need to use saxon-B, and there is indeed a newer version but the
> packaging is different to what AOO carries. FreeBSD was using the system 
> one but we stopped using it due to conflicts with the saxon
> from another important package (Scilab),
> 
>>  icc
> 
> I think Giuseppe Castagno said it wasn't worth the effort and since
> he did the OOo related stuff I didn't look further. I like excuses to
> be lazy :).
> 
>> I do know that saxon is sort of funny case.
> 
> It is only used for very old MS-Office formats. It is probably not worth 
> the effort anyways. LibreOffice replaced it with C code and the author 
> actually offered to relicense it for us but I lost trace of him
> afterwards.
> 
> Hope that helps,
> 
> 
> Pedro.
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [DISCUSS] Release 4.2: General Topics

[Pedro Giffuni]

Hi Don;


On 24 Aug, Pedro Giffuni wrote:



On 08/24/16 10:34, Pedro Giffuni wrote:

Hello;


...




  * [low priority] Updated bundled CoinMP.  There has been an API
change, which prevents the FreeBSD port from using the system
version.  Difficulty unknown ...



This is important, I was unaware of it. Sadly, I don't think I will
have time for it before the release.



A quick look at this ... FreeBSD is using version 1.8.3 which appears
to be the latest.

AOO could use the same version by default, it's just a matter of getting
the new version to build on all platforms. I think.


Unfortunately it is not that easy.  When I was cleaning up the the
FreeBSD port a while back, I went through all of the --with-system knobs
and CoinMP was one that did not work and broke the build.  My memory is
fuzzy, but I think there was an incompatible API change.



Hmm ... I just looked and the openoffice-devel FreeBSD port is using
the system coinmp. Actually CoinMP is only a wrapper around the core
Coin libraries. I have always considered using the core libraries 
directly as that provides more powerful options but I haven't found

the time and motivation to work on it.

I did try updating the CoinMP patches and it was not easy/fun. The Mac
changes are likely to be troublesome.


There are some other bundled bits that have the same problem, but CoinMP
is big and takes a while to build, which is my main motivation in this
case.  ICU also falls into this category, but I already know that it is
too difficult.



Yes, that one is difficult and while Symphony has a most of what we may 
need, the problem is that it has to be tested "multilingually".


I did update most of the components you mention and even gave a talk 
about it ;).



It looks like the others are:
ucpp


We are using the latest version.


mdds


The developer behind it broke compatibility with the AOO code (on
purpose, for all I know). The code is actually calling for a replacement 
but since it works we are leaving it untouched.



hsqldb


SUN had a branch with the required changes. I have some WIP patch for 
that but there are other issues, like the database format is 
incompatible. I have to spend more time on that but the change is

worth the rescue.


libxmlsec


AOO uses a heavily modified version. Updating it requires a lot of 
effort, basically forking libxmlsec.



stax


This is actually unused and can be thrown away, unless you are still
using something older than Java 5.


rhino


Oh yes, we updated this once but it's category B so there's not a lot of 
motivation to work on it. Newer java has functionality that can replace it.



xsltml


I don't remember well this one. I think it depended on something else 
and ultimately I was just happy about using the system version.



saxon


The latest versions (saxon-he) lack the functionality AOO requires.
We need to use saxon-B, and there is indeed a newer version but the
packaging is different to what AOO carries. FreeBSD was using the system 
one but we stopped using it due to conflicts with the saxon

from another important package (Scilab),


icc


I think Giuseppe Castagno said it wasn't worth the effort and since
he did the OOo related stuff I didn't look further. I like excuses to
be lazy :).


I do know that saxon is sort of funny case.


It is only used for very old MS-Office formats. It is probably not worth 
the effort anyways. LibreOffice replaced it with C code and the author 
actually offered to relicense it for us but I lost trace of him

afterwards.

Hope that helps,


Pedro.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [DISCUSS] Release 4.2: General Topics

[Larry Gusaas]

On 2016-08-23, 1:14 PM Kay sch...@apache.org wrote concerning "[DISCUSS] Release 4.2: General 
Topics":



2. Update Java requirement from Java 1.5 to*at least*  Java 1.7


I replied earlier using gmane, but it doesn't seem to have gone through.

Has Issue 126622 - Base 4.1.2 does not open Tables and Queries in Mac OSX been 
fixed?
I don't see any comments on the issue page saying it has or that anyone is working on it. The 
issue is marked as P1 Critical.



--
_

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-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [DISCUSS] Release 4.2: General Topics

[Don Lewis]

Add another libxml2 update to the list.  There is a new batch of CVEs.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [DISCUSS] Release 4.2: General Topics

[Don Lewis]

On 24 Aug, Kay Schenk wrote:
> 
> 
> On 08/24/2016 11:56 AM, Don Lewis wrote:
>> On 24 Aug, Pedro Giffuni wrote:
>>>
>>>
>>> On 08/24/16 10:34, Pedro Giffuni wrote:
 Hello;

>>> ...
>>>

>   * [low priority] Updated bundled CoinMP.  There has been an API
> change, which prevents the FreeBSD port from using the system
> version.  Difficulty unknown ...
>

 This is important, I was unaware of it. Sadly, I don't think I will
 have time for it before the release.

>>>
>>> A quick look at this ... FreeBSD is using version 1.8.3 which appears
>>> to be the latest.
>>>
>>> AOO could use the same version by default, it's just a matter of getting 
>>> the new version to build on all platforms. I think.
>> 
>> Unfortunately it is not that easy.  When I was cleaning up the the
>> FreeBSD port a while back, I went through all of the --with-system knobs
>> and CoinMP was one that did not work and broke the build.  My memory is
>> fuzzy, but I think there was an incompatible API change.
>> 
>> There are some other bundled bits that have the same problem, but CoinMP
>> is big and takes a while to build, which is my main motivation in this
>> case.  ICU also falls into this category, but I already know that it is
>> too difficult.
>> 
>> It looks like the others are:
>>  ucpp
>>  mdds
>>  hsqldb
>>  libxmlsec
>>  stax
>>  rhino
>>  xsltml
>>  saxon
>>  icc
>> I do know that saxon is sort of funny case.
> 
> Right now we don't have a Mac buildbot. We shouldn't risk updating
> anything that will cause other problems, unless, of course, it's a
> security issue. Yes, many of the newer versions of our external items
> would likely necessitate API changes. That is definitely a big issue.

Yeah, I was going to mention that we really need some testing on the
Mac.  We need more than just a buildbot, we also need someone to
actually exercise the code.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [DISCUSS] Release 4.2: General Topics

[Kay Schenk]

On 08/24/2016 11:56 AM, Don Lewis wrote:
> On 24 Aug, Pedro Giffuni wrote:
>>
>>
>> On 08/24/16 10:34, Pedro Giffuni wrote:
>>> Hello;
>>>
>> ...
>>
>>>
   * [low priority] Updated bundled CoinMP.  There has been an API
 change, which prevents the FreeBSD port from using the system
 version.  Difficulty unknown ...

>>>
>>> This is important, I was unaware of it. Sadly, I don't think I will
>>> have time for it before the release.
>>>
>>
>> A quick look at this ... FreeBSD is using version 1.8.3 which appears
>> to be the latest.
>>
>> AOO could use the same version by default, it's just a matter of getting 
>> the new version to build on all platforms. I think.
> 
> Unfortunately it is not that easy.  When I was cleaning up the the
> FreeBSD port a while back, I went through all of the --with-system knobs
> and CoinMP was one that did not work and broke the build.  My memory is
> fuzzy, but I think there was an incompatible API change.
> 
> There are some other bundled bits that have the same problem, but CoinMP
> is big and takes a while to build, which is my main motivation in this
> case.  ICU also falls into this category, but I already know that it is
> too difficult.
> 
> It looks like the others are:
>   ucpp
>   mdds
>   hsqldb
>   libxmlsec
>   stax
>   rhino
>   xsltml
>   saxon
>   icc
> I do know that saxon is sort of funny case.

Right now we don't have a Mac buildbot. We shouldn't risk updating
anything that will cause other problems, unless, of course, it's a
security issue. Yes, many of the newer versions of our external items
would likely necessitate API changes. That is definitely a big issue.


-- 

Kay Schenk
Apache OpenOffice

"Things work out best for those who make
 the best of the way things work out."
 -- John Wooden

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [DISCUSS] Release 4.2: General Topics

[Don Lewis]

On 24 Aug, Pedro Giffuni wrote:
> 
> 
> On 08/24/16 10:34, Pedro Giffuni wrote:
>> Hello;
>>
> ...
> 
>>
>>>   * [low priority] Updated bundled CoinMP.  There has been an API
>>> change, which prevents the FreeBSD port from using the system
>>> version.  Difficulty unknown ...
>>>
>>
>> This is important, I was unaware of it. Sadly, I don't think I will
>> have time for it before the release.
>>
> 
> A quick look at this ... FreeBSD is using version 1.8.3 which appears
> to be the latest.
> 
> AOO could use the same version by default, it's just a matter of getting 
> the new version to build on all platforms. I think.

Unfortunately it is not that easy.  When I was cleaning up the the
FreeBSD port a while back, I went through all of the --with-system knobs
and CoinMP was one that did not work and broke the build.  My memory is
fuzzy, but I think there was an incompatible API change.

There are some other bundled bits that have the same problem, but CoinMP
is big and takes a while to build, which is my main motivation in this
case.  ICU also falls into this category, but I already know that it is
too difficult.

It looks like the others are:
ucpp
mdds
hsqldb
libxmlsec
stax
rhino
xsltml
saxon
icc
I do know that saxon is sort of funny case.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [DISCUSS] Release 4.2: General Topics

[Pedro Giffuni]

On 08/24/16 10:34, Pedro Giffuni wrote:

Hello;


...




  * [low priority] Updated bundled CoinMP.  There has been an API
change, which prevents the FreeBSD port from using the system
version.  Difficulty unknown ...



This is important, I was unaware of it. Sadly, I don't think I will
have time for it before the release.



A quick look at this ... FreeBSD is using version 1.8.3 which appears
to be the latest.

AOO could use the same version by default, it's just a matter of getting 
the new version to build on all platforms. I think.


Pedro.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [DISCUSS] Release 4.2: General Topics

[Don Lewis]

On 24 Aug, Pedro Giffuni wrote:
> Hello;
> 
>> Here is my list:
>>
>>   * Update bundled redland / rasqal / raptor to fix a CVE.  This is
>> currently in progress.  The FreeBSD port has been using the system
>> versions of the latest and greatest.
>>
> 
> 
> This is difficult because of dependencies between the three and the way
> the configure scripts are tied together :(.

Yes, I can confirm that it is a huge PITA.

>>   * Updated bundled serf to fix a CVE and a WebDAV issue.  The FreeBSD
>> port has been using the system version of the latest and greatest.
>>
> 
> Agreed, this is important.
> 
>>   * [low priority] Update bundled vigra.  This version is no longer
>> available upstream.  It is used by the basebmp module, but I don't
>> know what it is used for or how to test it.  I believe only the
>> headers are used.  The FreeBSD port uses the latest and greatest
>> version and I haven't heard of any problems.
>>
> 
> We are using the latest version that does NOT use CMake. TBH, the
> update is probably not worth it.

We do't actually build it.  We just unpack it and grab the headers from
the source.  This is what we've got in its makefile.mk:

CONFIGURE_DIR=
CONFIGURE_ACTION=

BUILD_DIR=
BUILD_ACTION=
BUILD_FLAGS=

>>   * [low priority] Updated bundled CoinMP.  There has been an API
>> change, which prevents the FreeBSD port from using the system
>> version.  Difficulty unknown ...
>>
> 
> This is important, I was unaware of it. Sadly, I don't think I will
> have time for it before the release.
> 
> While here ... In Kay's list there is BZ 123975, an update to Python 3.
> As stated in the BZ issue, this is not convenient at this time: we
> have tried hard to keep compatibility with OpenOffice.org and updating
> further would put that at risk.
> 
> Also the new Python versions upgraded the build scripts for Windows,
> which may require more work for our build system.
> 
> Somewhere in the distant future... we should also update ICU.

Yes.  I've looked at that and it looks difficult.  Something else that
falls in that category is silgraphite -> graphite2.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Fwd: Re: Questions about buildbot internals

[Kay Schenk]

[top posting]

Continuing discussion with infra due to EOL on both the systems we are
currently using indicates we will probably be moving to Ubuntu 14.04
buildbots for Linux 32 and Linux 64. I'll keep you updated.

On 08/23/2016 12:19 PM, Kay sch...@apache.org wrote:
> FYI: communication with pono from infra
> 
> 
>  Forwarded Message 
> Subject:  Re: Questions about buildbot internals
> Date: Tue, 23 Aug 2016 09:31:45 -0700
> From: Kay sch...@apache.org 
> Reply-To: ksch...@apache.org
> To:   Pono Takamori 
> CC:   infrastruct...@apache.org Infrastructure
> , kay.sch...@gmail.com
> 
> 
> 
> 
> On 08/23/2016 08:52 AM, Pono Takamori wrote:
>> Q1: Are you talking about during a job or as a one time action? I can
>> get lists of currently installed packages on the linux nodes fairly
>> easily, the windows one will be a bit trickier unless you want to know
>> specific versions of your dependencies.
> I'd be happy with a one time action currently. Yeah, Windows is tricky.
>>
>> Q2:  We can add those 2 jars to the build nodes.  maven 2 should be
>> installed on those boxes, did you need a specific version of it?
> 
> OK, I think whatever is out there now is fine for Maven. So, just
> installing these jars is /usr/share/java should do the trick.
> 
> and, hmmm...we recommend ant 1.9 or later yet it seems what's on the
> Linux32 buildbot is ant 1.8.2 and on Linux-64 it's ant 1.7.1. Time to
> re-edit our configure.ac -- again.
> 
> So, if you could bump the ant version to 1.9.2 on all these that would
> be great. More than 1.9.2 we have problems from my recollection.
> 
> 
>>
>> In regards to puppet, all three of the build nodes that you mentioned
>> are not in puppet since tethys is running Ubuntu 10.04, bb-vm2 is
>> running 12.04 and we do not have any puppet written for windows yet.
> 
> OK, I actually didn't notice that these Linux bots were on different
> Ubuntu versions--gee!
> 
>> We could move the builds to a node with 14.04 so that adding
>> dependencies would be you forking the listed repo and then adding the
>> required dependencies
>> here: 
>> https://github.com/apache/infrastructure-puppet/blob/deployment/data/ubuntu/1404.yaml#L316
> 
> hmmm...let me confer with others and I'll get back to you on this. Can
> you get me a pack list for 14.04 as well?
> 
>>
>> Let me know if you have any other questions,
>> -Pono
> 
> Not right now. Thank you SO much for helping with this. Let's keep in touch!
> 
>>
>> On Mon, Aug 22, 2016 at 9:32 PM, Kay sch...@apache.org
>>  > > wrote:
>>
>> Hello Infra--
>> Apache OpenOffice uses the following buildbots:
>> Linux32 : bb-vm2_ubuntu_32bit
>> Linux64: tethys_ubuntu
>> Windows 7: bb-win7
>>
>> Q1: Short of writing a command line entry into our buildbot
>> scripts, is
>> there any way to get a listing of what packs are installed on
>> these systems?
>>
>> Q2: We need the following packs installed on all three of these for
>> automated testing:
>> junit-4.12.jar
>> hamcrest-core-1.3.jar
>>
>> Maybe maven2 also? But I just ran the tests I needed with "ant"
>> which is
>> part of our build requirements.
>>
>> Through private message,  I was sent a link to:
>>  
>> https://github.com/apache/infrastructure-puppet/tree/deployment/modules/build_slaves
>> 
>> 
>>
>> as a way of explanation to self-servicing the buildbots, but, not
>> being
>> a puppet guru, I am lost looking at this. Can you describe a basic
>> procedure for me? What type of karma does anyone need? And to what?
>> What's required to upload a new template? Instructions on what
>> should be
>> in the template. How do we initiate pull requests based on the
>> templates, etc?
>>
>> Thanks.
>>
>>
>>   
> 
> 

-- 

Kay Schenk
Apache OpenOffice

"Things work out best for those who make
 the best of the way things work out."
 -- John Wooden

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [DISCUSS] Release 4.2: General Topics

[Kay Schenk]

On Wed, Aug 24, 2016 at 8:34 AM, Pedro Giffuni  wrote:

> Hello;
>
> Here is my list:
>>
>>   * Update bundled redland / rasqal / raptor to fix a CVE.  This is
>> currently in progress.  The FreeBSD port has been using the system
>> versions of the latest and greatest.
>>
>>
>
> This is difficult because of dependencies between the three and the way
> the configure scripts are tied together :(.
>
>
>   * Updated bundled serf to fix a CVE and a WebDAV issue.  The FreeBSD
>> port has been using the system version of the latest and greatest.
>>
>>
> Agreed, this is important.
>

​check: This one would be OK.
​


>
>   * [low priority] Update bundled vigra.  This version is no longer
>> available upstream.  It is used by the basebmp module, but I don't
>> know what it is used for or how to test it.  I believe only the
>> headers are used.  The FreeBSD port uses the latest and greatest
>> version and I haven't heard of any problems.
>>
>>
> We are using the latest version that does NOT use CMake. TBH, the
> update is probably not worth it.
>
>
>   * [low priority] Updated bundled CoinMP.  There has been an API
>> change, which prevents the FreeBSD port from using the system
>> version.  Difficulty unknown ...
>>
>>
> This is important, I was unaware of it. Sadly, I don't think I will
> have time for it before the release.
>

​Not sure about this one ​

​ Maybe not?​



> While here ... In Kay's list there is BZ 123975, an update to Python 3.
> As stated in the BZ issue, this is not convenient at this time: we
> have tried hard to keep compatibility with OpenOffice.org and updating
> further would put that at risk.
>
> Also the new Python versions upgraded the build scripts for Windows,
> which may require more work for our build system.
>

​Let's skip this one for now. Well this is why I said the list needed to be
evaluated. I think we're at Python 2.7 now and maybe just keep this. If we
stay with CentOS5 for production, Python 3.0 might not be easy to safely
install.

​


>
> Somewhere in the distant future... we should also update ICU.
>
> Pedro.
>
> Pedro.


​Thanks Pedro and Don for checking this out!

​




-- 

Kay Schenk@Apache OpenOffice

“Things work out best for those who make the best of how things work out.”

-- John Wooden

RE: [DISCUSS] Release 4.2: General Topics

[Dennis E. Hamilton]

The problem of incomplete shutdown is very serious.  It can result in damaged 
and completely lost in-progress work, even though apparently saved, and other 
damage.  The whole problem of shutdown, Quickstarter, and failed auto-recovery 
is a big ball of snakes that is worthy of a maintenance release all on its own.

With regard to spell-checking, the usual symptom is that suddenly all words are 
redlined.  Having it stop checking probably goes unnoticed more often, as it 
did for Don.

With regard to spell-checking, there is a promise to provide a profile-fix tool 
for Windows, 
.  That is a bit buried 
(but look at the issue it is tied to). 

I will open a separate task for this now.

At some point, installation of such a tool should at least be part of the built 
distribution.

So there are three steps:

 1. Get the tool out there as something users can install and use.

 2. Incorporate the tool in our binary distributions.

 3. Fix the shut-down problems we have that are so overwhelming and so damaging 
to the work of our users.

Steps (1) will require QA work and L10N work in order to reach the greatest 
number of users.  English will only work for 45% of our users.  It should work 
better for end users than the instructions that are being provided repetitively 
each time someone stumbles on this and manages to report it.   

This is clearly a triage situation.  We need something now, we need something 
about best practices, such as having Quickstarter OFF by default at least on 
Windows, and also doing something about auto-recovery failures.  And we can't 
wait for laborious software fixes for which there is no foreseeable developer 
availability and then production of subsequent full-binary distributions.

Speaking of triage, the targeting of Windows reaches 87% of our users based on 
platform downloads.  Remedies there are assisted by the fact that cmd.exe (the 
console processor) and command-line utilities are available on all versions of 
Windows that AOO supports.  In addition, every install of AOO includes a 
functional version of Python in the OpenOffice 4 code.  Accomplishing the 
provision of side-car utilities for other platforms will depend on committers 
who are devoted to those platforms stepping forward.

 - Dennis

PS: The 4.1.2-patch1 Hotfix will roll to general distribution in the next 24-48 
hours.  We have English language covered and there is provision for more L10N 
localization.  However, the only one completed at this time is Nederland (nl, 
Dutch) for the Windows version.  A Deutsch (de, German) one is in the works.  
To get better coverage, the priority additional L10N-s should be French, 
Italian, and Spanish.  That gets us to 75% of the users by downloaded 
languages.  To get to 90% add Japanese, Russian, Polish, (Dutch), and 
Portuguese.  Chinese would be a great bonus and, of course, we would appreciate 
any other localizations that AOO enthusiasts and committers provide. 

> -Original Message-
> From: Don Lewis [mailto:truck...@apache.org]
> Sent: Wednesday, August 24, 2016 00:38
> To: ofarr...@iol.ie
> Cc: dev@openoffice.apache.org; q...@openoffice.apache.org;
> l...@openoffice.apache.org
> Subject: Re: [DISCUSS] Release 4.2: General Topics
> 
> On 24 Aug, Rory O'Farrell wrote:
> > On Wed, 24 Aug 2016 00:01:22 -0700 (PDT)
> > Don Lewis  wrote:
> 
> >> Someone should fix the broken spellcheck problem.  It generates a lot
> of
> >> complaints from our users.
> >>
> >
> > The "broken spellcheck problem" seems largely to be caused by over
> hasty close-down of the computer before cached files (both hardware and
> software caches) are properly written to disk.  User education is the
> answer - educate them to be patient in closedown and wait for disk
> activity to finish before power-off.
> 
> Maybe using fsync() to flush things out faster when shutting down the
> app and keeping a backup copy of the config would help avoid the
> problem.   We shouldn't just silently fail when something is corrupt.
> 
> I've even experienced this myself on my FreeBSD desktop which stays on
> 24x7 and has an UPS.  It took me quite a while to notice spellcheck
> wasn't working.  I just thought my spelling was unusually good ;-)
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [DISCUSS] Release 4.2: General Topics

[Pedro Giffuni]

Hello;


Here is my list:

  * Update bundled redland / rasqal / raptor to fix a CVE.  This is
currently in progress.  The FreeBSD port has been using the system
versions of the latest and greatest.




This is difficult because of dependencies between the three and the way
the configure scripts are tied together :(.



  * Updated bundled serf to fix a CVE and a WebDAV issue.  The FreeBSD
port has been using the system version of the latest and greatest.



Agreed, this is important.


  * [low priority] Update bundled vigra.  This version is no longer
available upstream.  It is used by the basebmp module, but I don't
know what it is used for or how to test it.  I believe only the
headers are used.  The FreeBSD port uses the latest and greatest
version and I haven't heard of any problems.



We are using the latest version that does NOT use CMake. TBH, the
update is probably not worth it.



  * [low priority] Updated bundled CoinMP.  There has been an API
change, which prevents the FreeBSD port from using the system
version.  Difficulty unknown ...



This is important, I was unaware of it. Sadly, I don't think I will
have time for it before the release.

While here ... In Kay's list there is BZ 123975, an update to Python 3.
As stated in the BZ issue, this is not convenient at this time: we
have tried hard to keep compatibility with OpenOffice.org and updating
further would put that at risk.

Also the new Python versions upgraded the build scripts for Windows,
which may require more work for our build system.

Somewhere in the distant future... we should also update ICU.

Pedro.

Pedro.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [DISCUSS] Release 4.2: General Topics

[Don Lewis]

On 24 Aug, Rory O'Farrell wrote:
> On Wed, 24 Aug 2016 00:01:22 -0700 (PDT)
> Don Lewis  wrote:

>> Someone should fix the broken spellcheck problem.  It generates a lot of
>> complaints from our users.
>> 
> 
> The "broken spellcheck problem" seems largely to be caused by over hasty 
> close-down of the computer before cached files (both hardware and software 
> caches) are properly written to disk.  User education is the answer - educate 
> them to be patient in closedown and wait for disk activity to finish before 
> power-off.

Maybe using fsync() to flush things out faster when shutting down the
app and keeping a backup copy of the config would help avoid the
problem.   We shouldn't just silently fail when something is corrupt.

I've even experienced this myself on my FreeBSD desktop which stays on
24x7 and has an UPS.  It took me quite a while to notice spellcheck
wasn't working.  I just thought my spelling was unusually good ;-)


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [DISCUSS] Release 4.2: General Topics

[Rory O'Farrell]

On Wed, 24 Aug 2016 00:01:22 -0700 (PDT)
Don Lewis  wrote:

> Here is my list:
> 
>   * Update bundled redland / rasqal / raptor to fix a CVE.  This is
> currently in progress.  The FreeBSD port has been using the system
> versions of the latest and greatest.
> 
>   * Updated bundled serf to fix a CVE and a WebDAV issue.  The FreeBSD
> port has been using the system version of the latest and greatest.
> 
>   * [low priority] Update bundled vigra.  This version is no longer
> available upstream.  It is used by the basebmp module, but I don't
> know what it is used for or how to test it.  I believe only the
> headers are used.  The FreeBSD port uses the latest and greatest
> version and I haven't heard of any problems.
> 
>   * [low priority] Updated bundled CoinMP.  There has been an API
> change, which prevents the FreeBSD port from using the system
> version.  Difficulty unknown ...
> 
>   * Fix the easy to fix compiler warnings.  In the case of unused
> private class member variables, deleting them would cause an ABI
> change because the object size would shrink.  If that is a problem
> the alternate would be to mark them unused.  I think there are only
> a small number of these, but they get reported many times.
> 
>   * Handle the Wiki Publisher and PDF Import extensions as integrated
> extensions:
> 
> I've done some work on this in the FreeBSD port, but I haven't
> tackled the installer part for other platforms.
> 
>   * Fix a problem that I stumbled across involving extensions that can
> cause an infinite crash / recover loop.  I think I can generate an
> alert when I detect the problem.  I'm not sure if I can use an
> existing alert message or will need a new one.  If the latter, then
> there will be some translation work required.
> 
>   * Give network connection failures a more informative error message.
> I stumbled across this when tracking down a problem that was
> confined to FreeBSD.
> 
> 
> Someone should fix the broken spellcheck problem.  It generates a lot of
> complaints from our users.
> 

The "broken spellcheck problem" seems largely to be caused by over hasty 
close-down of the computer before cached files (both hardware and software 
caches) are properly written to disk.  User education is the answer - educate 
them to be patient in closedown and wait for disk activity to finish before 
power-off.

-- 
Rory O'Farrell 

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Open Office Error messages

[Rory O'Farrell]

On Tue, 23 Aug 2016 15:24:23 -0500
Greg Hennen  wrote:

> The last time you opened OpenOffice, it unexpectedly quit while reopening 
> windows. Do you want to try to reopen its windows again? It says click to 
> reopen, nothing happens, or don’t reopen and nothing happens.
> We have shut down our computer, hoping it would take care of the problem it 
> did not take care of it.
>  Instead of the blue circle, it is a big question mark. And when we click on 
> it again the error message comes back on. 
> What can be done… ?
> 
> 
> 
> 
> Greg Hennen
> 763-442-3051
> hennen12...@msn.com
> www.generalcontractorandovermn.com
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
> 

This thread in the User Forum offers a solution to the "restore windows" 
problem on a Mac.
https://forum.openoffice.org/en/forum/viewtopic.php?f=17=53884=392123

-- 
Rory O'Farrell 

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [DISCUSS] Release 4.2: General Topics

[Don Lewis]

Here is my list:

  * Update bundled redland / rasqal / raptor to fix a CVE.  This is
currently in progress.  The FreeBSD port has been using the system
versions of the latest and greatest.

  * Updated bundled serf to fix a CVE and a WebDAV issue.  The FreeBSD
port has been using the system version of the latest and greatest.

  * [low priority] Update bundled vigra.  This version is no longer
available upstream.  It is used by the basebmp module, but I don't
know what it is used for or how to test it.  I believe only the
headers are used.  The FreeBSD port uses the latest and greatest
version and I haven't heard of any problems.

  * [low priority] Updated bundled CoinMP.  There has been an API
change, which prevents the FreeBSD port from using the system
version.  Difficulty unknown ...

  * Fix the easy to fix compiler warnings.  In the case of unused
private class member variables, deleting them would cause an ABI
change because the object size would shrink.  If that is a problem
the alternate would be to mark them unused.  I think there are only
a small number of these, but they get reported many times.

  * Handle the Wiki Publisher and PDF Import extensions as integrated
extensions:

I've done some work on this in the FreeBSD port, but I haven't
tackled the installer part for other platforms.

  * Fix a problem that I stumbled across involving extensions that can
cause an infinite crash / recover loop.  I think I can generate an
alert when I detect the problem.  I'm not sure if I can use an
existing alert message or will need a new one.  If the latter, then
there will be some translation work required.

  * Give network connection failures a more informative error message.
I stumbled across this when tracking down a problem that was
confined to FreeBSD.


Someone should fix the broken spellcheck problem.  It generates a lot of
complaints from our users.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

[CWiki] Account Whitelisting

[Mitul Patel]

Username: mitulf10
Real Name: Mitul Patel

Open Office Error messages

[Greg Hennen]

The last time you opened OpenOffice, it unexpectedly quit while reopening 
windows. Do you want to try to reopen its windows again? It says click to 
reopen, nothing happens, or don’t reopen and nothing happens.
We have shut down our computer, hoping it would take care of the problem it did 
not take care of it.
 Instead of the blue circle, it is a big question mark. And when we click on it 
again the error message comes back on. 
What can be done… ?




Greg Hennen
763-442-3051
hennen12...@msn.com
www.generalcontractorandovermn.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org