Re: Issue for 4.1.4 and MacOS

2017-11-06 Thread Larry Gusaas 

I got the same result as Dave.
Larry

On 2017-11-06, 4:12 PM Dave Fisher wrote:

Good news is that the Base issue is fixed.

Bad news is that the Charts saving issue has returned.

Sorry.

Regards,
Dave


On Nov 6, 2017, at 12:27 PM, Jim Jagielski  wrote:

Okey dokey... I *think* that having xml2 built w/ iconv was,
in fact, the issue. Double checking as we speak.

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


__




--
_

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: Issue for 4.1.4 and MacOS

2017-11-06 Thread Dave Fisher 
Hi Jim,

I’m not seeing an improvement in the latest build you are now pushing to dist.

Base works. I still get the two system.log messages.

Charts are not saved even if I just do a save as.

I wonder if we also need the redland/raptor update that is in trunk. I can 
spare a few hours tomorrow to try building on my side if we can confirm a few 
things. Up to you. We can webex or something ..

Regards,
Dave

> On Nov 6, 2017, at 6:20 PM, Patricia Shanahan  wrote:
> 
> There is something I've seen in the OpenOffice code that may be involved in 
> the silent failures to do something. For example, 
> main\xmloff\source\core\xmlexp.cxx, line 759:
> 
>   catch( com::sun::star::uno::Exception& )
>   {
>   }
> 
> This will hide any and all UNO exceptions thrown in anything called from the 
> corresponding try block, even with assertions enabled. I assume the intent is 
> that the problem has already been reported, but I don't think it is really 
> safe to relay on that.
> 
> Maybe scatter some breakpoints at places like that?
> 
> On 11/6/2017 2:12 PM, Dave Fisher wrote:
>> Good news is that the Base issue is fixed.
>> Bad news is that the Charts saving issue has returned.
>> Sorry.
>> Regards,
>> Dave
>>> On Nov 6, 2017, at 12:27 PM, Jim Jagielski  wrote:
>>> 
>>> Okey dokey... I *think* that having xml2 built w/ iconv was,
>>> in fact, the issue. Double checking as we speak.
>>> 
>>> -
>>> 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
> 



signature.asc
Description: Message signed with OpenPGP

Re: Issue for 4.1.4 and MacOS

2017-11-06 Thread Patricia Shanahan 
There is something I've seen in the OpenOffice code that may be involved 
in the silent failures to do something. For example, 
main\xmloff\source\core\xmlexp.cxx, line 759:


catch( com::sun::star::uno::Exception& )
{
}

This will hide any and all UNO exceptions thrown in anything called from 
the corresponding try block, even with assertions enabled. I assume the 
intent is that the problem has already been reported, but I don't think 
it is really safe to relay on that.


Maybe scatter some breakpoints at places like that?

On 11/6/2017 2:12 PM, Dave Fisher wrote:

Good news is that the Base issue is fixed.

Bad news is that the Charts saving issue has returned.

Sorry.

Regards,
Dave


On Nov 6, 2017, at 12:27 PM, Jim Jagielski  wrote:

Okey dokey... I *think* that having xml2 built w/ iconv was,
in fact, the issue. Double checking as we speak.

-
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: Issue for 4.1.4 and MacOS

2017-11-06 Thread Dave Fisher 
Good news is that the Base issue is fixed.

Bad news is that the Charts saving issue has returned.

Sorry.

Regards,
Dave

> On Nov 6, 2017, at 12:27 PM, Jim Jagielski  wrote:
> 
> Okey dokey... I *think* that having xml2 built w/ iconv was,
> in fact, the issue. Double checking as we speak.
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 



signature.asc
Description: Message signed with OpenPGP

Re: Issue for 4.1.4 and MacOS

2017-11-06 Thread Jim Jagielski 
Okey dokey... I *think* that having xml2 built w/ iconv was,
in fact, the issue. Double checking as we speak.

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

Re: Issue for 4.1.4 and MacOS

2017-11-06 Thread Jim Jagielski 
A reminder of what I'm talking about:

< LIBXML_CFLAGS='-I/usr/local/include/libxml2'
---
> 
LIBXML_CFLAGS='-I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/libxml2'
1289,1291c1326,1328
< LIBXML_LIBS='-L/usr/local/lib -lxml2 -lz -lpthread -liconv -lm'
< LIBXSLT_CFLAGS='-I/usr/local/include -I/usr/local/include/libxml2'
< LIBXSLT_LIBS='-L/usr/local/lib -lxslt -lxml2'
---
> 
LIBXML_LIBS='-L/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/lib
 -lxml2 -lz -lpthread -licucore -lm'
> 
LIBXSLT_CFLAGS='-I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include
 
-I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/libxml2'
> 
LIBXSLT_LIBS='-L/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/lib
 -lxslt -lxml2 -lz -lpthread -licucore -lm'


> On Nov 6, 2017, at 12:43 PM, Jim Jagielski  wrote:
> 
> Considering that it was the xml2/xslt libs that changed
> between the version, I am focusing my attention on that.
> The pervious version, that broke embedded charts but worked
> with the table used/linked macOS's libs. This latest
> version uses local libs; which looks to have fixed the
> embedded chart but broke the table/sql.
> 
> I *think* that the macOS versions did not incorporate iconv,
> whereas the local libs do. So I'm rebuilding xml2 with
> '--without-iconv' to see if that resolve it.
> 
> -
> 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: Issue for 4.1.4 and MacOS

2017-11-06 Thread Jim Jagielski 
Considering that it was the xml2/xslt libs that changed
between the version, I am focusing my attention on that.
The pervious version, that broke embedded charts but worked
with the table used/linked macOS's libs. This latest
version uses local libs; which looks to have fixed the
embedded chart but broke the table/sql.

I *think* that the macOS versions did not incorporate iconv,
whereas the local libs do. So I'm rebuilding xml2 with
'--without-iconv' to see if that resolve it.

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

Re: Issue for 4.1.4 and MacOS

2017-11-06 Thread Jim Jagielski 
yep
> On Nov 5, 2017, at 5:49 PM, Andrea Pescetti  wrote:
> 
> Jim Jagielski wrote:
>> I am wondering if this means/requires that the build machine
>> MUST be running 10.12 (Sierra).
> 
> The original report https://bz.apache.org/ooo/show_bug.cgi?id=127580 says 
> that the Base bug happens with the new (20171101) builds but not with the 
> 4.1.4 builds released in October.
> 
> Both builds were done on the same system, right? Just with different 
> configuration options.
> 
> Regards,
>  Andrea.
> 
> -
> 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: Issue for 4.1.4 and MacOS

2017-11-05 Thread Andrea Pescetti 

Jim Jagielski wrote:

I am wondering if this means/requires that the build machine
MUST be running 10.12 (Sierra).


The original report https://bz.apache.org/ooo/show_bug.cgi?id=127580 
says that the Base bug happens with the new (20171101) builds but not 
with the 4.1.4 builds released in October.


Both builds were done on the same system, right? Just with different 
configuration options.


Regards,
  Andrea.

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

Re: Issue for 4.1.4 and MacOS

2017-11-05 Thread Jim Jagielski 
Another possible useful link:

  o 
http://support.cocoatech.com/discussions/problems/43623-crashes-under-the-new-sierra-10122-update/page/3
 


I am wondering if this means/requires that the build machine
MUST be running 10.12 (Sierra).

Re: Issue for 4.1.4 and MacOS

2017-11-05 Thread Dave Fisher 
Hi Jim,

I did some googling of the error message. On this page may be a clue: 
https://discussions.apple.com/thread/7677685

I wonder if there is something with the internal SQL setup. I know we have 
developers who are working on variations and Base can handle alternatives.

I am going to try a few things like rebooting, etc, but I don’t have much time 
today. So I thought I’d share my suspicions…

Here is another link with an idea from a similar error in VMWare Fusion: 
https://www.reddit.com/r/vmware/comments/5n5723/internal_error_with_fusion_is_there_a_logfile_to/?st=j9n1owd1=4eeb46f7

Regards,
Dave

> On Nov 4, 2017, at 2:02 PM, Jim Jagielski  wrote:
> 
> I can't even imagine what in the build system would cause this situation
> or how changes in the build system would do this.
> 
> Does someone know, off the top of their head, the process/code
> flow which is being performed? I guess I could try to attach to
> the soffice process and step through, but it would be nice to
> have at least some prelim basic idea of where some useful
> breakpoints should be set.
> 
>> On Nov 3, 2017, at 5:21 PM, Jim Jagielski  wrote:
>> 
>> Copying here:
>> 
>> This is interesting...
>> 
>> When opening the Base file I get the following in /var/log/system.log:
>> 
>> 596:Nov  3 10:29:19 Daves-MacBook-Pro soffice[70777]: assertion failed: 
>> 16G29: libxpc.dylib + 74307 [BF896DF0-D8E9-31A8-A4B3-01120BFEEE52]: 0x89
>> 597:Nov  3 10:29:22 Daves-MacBook-Pro soffice[70777]: BUG in libdispatch 
>> client: kevent[EVFILT_MACHPORT] monitored resource vanished before the 
>> source cancel handler was invoked
>> 
>> When I open the Base file with the original 4.1.4 from October 17 I only see:
>> 
>> 598:Nov  3 10:31:40 Daves-MacBook-Pro soffice[70791]: assertion failed: 
>> 16G29: libxpc.dylib + 74307 [BF896DF0-D8E9-31A8-A4B3-01120BFEEE52]: 0x89
>> 
>> 
>> 
>> -
>> 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
> 



signature.asc
Description: Message signed with OpenPGP

Re: Issue for 4.1.4 and MacOS

2017-11-04 Thread Jim Jagielski 
I can't even imagine what in the build system would cause this situation
or how changes in the build system would do this.

Does someone know, off the top of their head, the process/code
flow which is being performed? I guess I could try to attach to
the soffice process and step through, but it would be nice to
have at least some prelim basic idea of where some useful
breakpoints should be set.

> On Nov 3, 2017, at 5:21 PM, Jim Jagielski  wrote:
> 
> Copying here:
> 
> This is interesting...
> 
> When opening the Base file I get the following in /var/log/system.log:
> 
> 596:Nov  3 10:29:19 Daves-MacBook-Pro soffice[70777]: assertion failed: 
> 16G29: libxpc.dylib + 74307 [BF896DF0-D8E9-31A8-A4B3-01120BFEEE52]: 0x89
> 597:Nov  3 10:29:22 Daves-MacBook-Pro soffice[70777]: BUG in libdispatch 
> client: kevent[EVFILT_MACHPORT] monitored resource vanished before the source 
> cancel handler was invoked
> 
> When I open the Base file with the original 4.1.4 from October 17 I only see:
> 
> 598:Nov  3 10:31:40 Daves-MacBook-Pro soffice[70791]: assertion failed: 
> 16G29: libxpc.dylib + 74307 [BF896DF0-D8E9-31A8-A4B3-01120BFEEE52]: 0x89
> 
> 
> 
> -
> 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: Issue for 4.1.4 and MacOS

2017-11-03 Thread Jim Jagielski 
Copying here:

This is interesting...

When opening the Base file I get the following in /var/log/system.log:

596:Nov  3 10:29:19 Daves-MacBook-Pro soffice[70777]: assertion failed: 16G29: 
libxpc.dylib + 74307 [BF896DF0-D8E9-31A8-A4B3-01120BFEEE52]: 0x89
597:Nov  3 10:29:22 Daves-MacBook-Pro soffice[70777]: BUG in libdispatch 
client: kevent[EVFILT_MACHPORT] monitored resource vanished before the source 
cancel handler was invoked

When I open the Base file with the original 4.1.4 from October 17 I only see:

598:Nov  3 10:31:40 Daves-MacBook-Pro soffice[70791]: assertion failed: 16G29: 
libxpc.dylib + 74307 [BF896DF0-D8E9-31A8-A4B3-01120BFEEE52]: 0x89



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

Re: Issue for 4.1.4 and MacOS

2017-11-03 Thread Dave Fisher 
I confirmed that I have Larry’s bug. I commented in BZ. I noticed an error in 
/var/log/system.log


> On Nov 3, 2017, at 5:48 AM, Larry Gusaas <larry.gus...@gmail.com> wrote:
> 
> commented in Bugzilla
> 
> On 2017-11-03, 6:03 AM Jim Jagielski wrote concerning "Re: Issue for 4.1.4 
> and MacOS":
>> Following up in Bugz... cannot recreate.
>> 
>>> On Nov 3, 2017, at 7:45 AM, Larry Gusaas<larry.gus...@gmail.com>  wrote:
>>> 
>>> Created an issue in Bugzillahttps://bz.apache.org/ooo/show_bug.cgi?id=127580
>>> *Issue 127580*<https://bz.apache.org/ooo/show_bug.cgi?id=127580>-Fix 
>>> forIssue 127568<https://bz.apache.org/ooo/show_bug.cgi?id=127568>created a 
>>> new bug in Base
>> 
>> __
>> 
> 
> 
> --
> _
> 
> 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
> 



signature.asc
Description: Message signed with OpenPGP

Re: Issue for 4.1.4 and MacOS

2017-11-03 Thread Larry Gusaas 

commented in Bugzilla

On 2017-11-03, 6:03 AM Jim Jagielski wrote concerning "Re: Issue for 4.1.4 and 
MacOS":

Following up in Bugz... cannot recreate.


On Nov 3, 2017, at 7:45 AM, Larry Gusaas<larry.gus...@gmail.com>  wrote:

Created an issue in Bugzillahttps://bz.apache.org/ooo/show_bug.cgi?id=127580
*Issue 127580*<https://bz.apache.org/ooo/show_bug.cgi?id=127580>-Fix forIssue 
127568<https://bz.apache.org/ooo/show_bug.cgi?id=127568>created a new bug in Base


__




--
_

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: Issue for 4.1.4 and MacOS

2017-11-03 Thread Jim Jagielski 
Following up in Bugz... cannot recreate.

> On Nov 3, 2017, at 7:45 AM, Larry Gusaas  wrote:
> 
> Created an issue in Bugzilla https://bz.apache.org/ooo/show_bug.cgi?id=127580
> *Issue 127580* -Fix 
> forIssue 127568 created a 
> new bug in Base
> 
> On 2017-11-02, 5:32 PM Larry Gusaas wrote:
>> On 2017-11-02, 4:21 PM Dave Fisher wrote:
>> 
>>> Hi Larry,
>>> 
>>> Thanks. Are you able to share the Base document and steps to reproduce?
>> 
>> I will have to make a new document. The one I have is a community list with 
>> names, addresses, phone numbers, etc. I'll make a copy and xxx out the 
>> personal information. Won't get to it till late tonight.
>> 
>>> Are you pulling from your local address book?
>> 
>> No. Created from scratch with complete personal information
>> 
>>>   What version of Mac OS are you on?
>> 
>> macOS ver. 10.13.1 High Sierra.
>>> Would you put this information into BZ?
>> 
>> Yes.
>>> 
>>> Regards,
>>> Dave
>>> 
>>> Sent from my iPhone
>>> 
 On Nov 2, 2017, at 1:17 PM, Larry Gusaas  wrote:
 
 Found problem in Base. I only have one Base document. When I select Tables 
 under Database and then Addresses under Tables it does not open.
 
 Forms/Query Addresses opens.
 
 Works properly in 4.1.3 and in the released version of 4.1.4.
 
> On 2017-11-02, 12:56 PM Dave Fisher wrote:
> Larry can you check for any regressions?
> 
> Regards,
> Dave
> 
> __
> 
 
> 
> 
> -- 
> _
> 
> 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
> 


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

Re: Issue for 4.1.4 and MacOS

2017-11-03 Thread Larry Gusaas 

Created an issue in Bugzilla https://bz.apache.org/ooo/show_bug.cgi?id=127580
*Issue 127580* -Fix forIssue 127568 
created a new bug in Base


On 2017-11-02, 5:32 PM Larry Gusaas wrote:

On 2017-11-02, 4:21 PM Dave Fisher wrote:


Hi Larry,

Thanks. Are you able to share the Base document and steps to reproduce?


I will have to make a new document. The one I have is a community list with names, addresses, 
phone numbers, etc. I'll make a copy and xxx out the personal information. Won't get to it 
till late tonight.



Are you pulling from your local address book?


No. Created from scratch with complete personal information


  What version of Mac OS are you on?


macOS ver. 10.13.1 High Sierra.

Would you put this information into BZ?


Yes.


Regards,
Dave

Sent from my iPhone


On Nov 2, 2017, at 1:17 PM, Larry Gusaas  wrote:

Found problem in Base. I only have one Base document. When I select Tables under Database 
and then Addresses under Tables it does not open.


Forms/Query Addresses opens.

Works properly in 4.1.3 and in the released version of 4.1.4.


On 2017-11-02, 12:56 PM Dave Fisher wrote:
Larry can you check for any regressions?

Regards,
Dave

__






--
_

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: Issue for 4.1.4 and MacOS

2017-11-02 Thread Larry Gusaas 

On 2017-11-02, 4:21 PM Dave Fisher wrote:


Hi Larry,

Thanks. Are you able to share the Base document and steps to reproduce?


I will have to make a new document. The one I have is a community list with names, addresses, 
phone numbers, etc. I'll make a copy and xxx out the personal information. Won't get to it till 
late tonight.



Are you pulling from your local address book?


No. Created from scratch with complete personal information


  What version of Mac OS are you on?


macOS ver. 10.13.1 High Sierra.

Would you put this information into BZ?


Yes.


Regards,
Dave

Sent from my iPhone


On Nov 2, 2017, at 1:17 PM, Larry Gusaas  wrote:

Found problem in Base. I only have one Base document. When I select Tables 
under Database and then Addresses under Tables it does not open.

Forms/Query Addresses opens.

Works properly in 4.1.3 and in the released version of 4.1.4.


On 2017-11-02, 12:56 PM Dave Fisher wrote:
Larry can you check for any regressions?

Regards,
Dave

__



--
_

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


__




--
_

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: Issue for 4.1.4 and MacOS

2017-11-02 Thread Dave Fisher 
Hi Larry,

Thanks. Are you able to share the Base document and steps to reproduce? Are you 
pulling from your local address book? What version of Mac OS are you on?

Would you put this information into BZ?

Regards,
Dave

Sent from my iPhone

> On Nov 2, 2017, at 1:17 PM, Larry Gusaas  wrote:
> 
> Found problem in Base. I only have one Base document. When I select Tables 
> under Database and then Addresses under Tables it does not open.
> 
> Forms/Query Addresses opens.
> 
> Works properly in 4.1.3 and in the released version of 4.1.4.
> 
>> On 2017-11-02, 12:56 PM Dave Fisher wrote:
>> Larry can you check for any regressions?
>> 
>> Regards,
>> Dave
>> 
>> __
>> 
> 
> 
> -- 
> _
> 
> 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
> 


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

Re: Issue for 4.1.4 and MacOS

2017-11-02 Thread Marcus 

Am 01.11.2017 um 22:41 schrieb Marcus:

Am 01.11.2017 um 00:29 schrieb Matthias Seidel:

Am 01.11.2017 um 00:22 schrieb Andrea Pescetti:

Matthias Seidel wrote:

Am 31.10.2017 um 23:39 schrieb Andrea Pescetti:

Andrea Pescetti wrote:

In terms of the update feed, we can keep on hold the update feeds for
the 4.1.3 (and earlier) to 4.1.4 upgrade for Mac users; and once 
4.1.5

is out, we will push the update as usual.

I could temporarily exchange all update feeds with versions without
macOS?


This is overkill. Those users have ignored update notifications for at
least one year anyway, so the impact would be minimal. 4.1.3 users and
new users are the primary target.


It is not so much work for me to do...

And you would be surprised how many updates there are every day from
older versions via update feed.
I can see it in real time with "Google Analytics". ;-)




download page would suggest 4.1.4 for other platforms and 4.1.3 for
Mac, with a short explanation saying that OS X binary builds will be
provided soon (then whether this happens with "new" 4.1.4 builds or
with 4.1.5 is a detail that doesn't concern users at this time).


We could do that in a similar way as we tell people that 4.1.4 is not
available for OS X <= 10.6.
The logic is in
http://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/content/download/download.js 





I thought we had some easier way to just "cap" OS X to 4.1.3, but
Marcus probably knows best how we could do it - provided we want to,
of course; it's just a proposal for the time being, and I can't even
verify the issue directly.


Yes, Marcus knows best. But I think this would be the best way to
implement it.


fix is ready and working locally.

Text in the red error box:

Problem: Apache OpenOffice 4.1.4 is not available for OS X (version >= 
10.7) (DMG).

Solution: Please select version 4.1.0 or newer.


I haven't seen any feedback. So, should I commit the change to block the 
Mac downloads? Or is it no longer necessary?


Thanks

Marcus


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

Re: Issue for 4.1.4 and MacOS

2017-11-02 Thread Larry Gusaas 
Found problem in Base. I only have one Base document. When I select Tables under Database and 
then Addresses under Tables it does not open.


Forms/Query Addresses opens.

Works properly in 4.1.3 and in the released version of 4.1.4.

On 2017-11-02, 12:56 PM Dave Fisher wrote:

Larry can you check for any regressions?

Regards,
Dave

__




--
_

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: Issue for 4.1.4 and MacOS

2017-11-02 Thread Rory O'Farrell 
On Thu, 2 Nov 2017 11:56:39 -0700
Dave Fisher  wrote:

> I confirmed the same yesterday.

Remember The Hunting of the Snark "What I tell you three times is true"!


Rory


> 
> Larry can you check for any regressions?
> 
> Regards,
> Dave
> 
> Sent from my iPhone
> 
> > On Nov 2, 2017, at 11:40 AM, Marcus  wrote:
> > 
> >> Am 02.11.2017 um 19:36 schrieb Larry Gusaas:
> >> Tested calc in the repaired version. Charts are saving properly.
> > 
> > and the 2nd confirmation. That's great. :-)
> > 
> > Marcus
> > 
> > 
> > 
> >>> On 2017-11-02, 4:48 AM Jim Jagielski wrote:
> >>> https://dist.apache.org/repos/dist/dev/openoffice/macOS-4.1.4-20171101/ 
> >>>  
> >>> 
>  On Nov 1, 2017, at 6:15 PM, Rory O'Farrell  wrote:
>  
>  May I have a URL for the repaired Mac version of 4.1.4 (or a copy of the 
>  repaired Mac file) which I can pass to the Forum user who has posted on 
>  this problem; he uses charts daily and can be relied upon to report any 
>  other problems.
>  
>  Rory
> > 
> > 
> > -
> > 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
> 
> 


-- 
Rory O'Farrell 

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

Re: Issue for 4.1.4 and MacOS

2017-11-02 Thread Dave Fisher 
I confirmed the same yesterday.

Larry can you check for any regressions?

Regards,
Dave

Sent from my iPhone

> On Nov 2, 2017, at 11:40 AM, Marcus  wrote:
> 
>> Am 02.11.2017 um 19:36 schrieb Larry Gusaas:
>> Tested calc in the repaired version. Charts are saving properly.
> 
> and the 2nd confirmation. That's great. :-)
> 
> Marcus
> 
> 
> 
>>> On 2017-11-02, 4:48 AM Jim Jagielski wrote:
>>> https://dist.apache.org/repos/dist/dev/openoffice/macOS-4.1.4-20171101/ 
>>>  
>>> 
 On Nov 1, 2017, at 6:15 PM, Rory O'Farrell  wrote:
 
 May I have a URL for the repaired Mac version of 4.1.4 (or a copy of the 
 repaired Mac file) which I can pass to the Forum user who has posted on 
 this problem; he uses charts daily and can be relied upon to report any 
 other problems.
 
 Rory
> 
> 
> -
> 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: Issue for 4.1.4 and MacOS

2017-11-02 Thread Marcus 

Am 02.11.2017 um 19:36 schrieb Larry Gusaas:

Tested calc in the repaired version. Charts are saving properly.


and the 2nd confirmation. That's great. :-)

Marcus




On 2017-11-02, 4:48 AM Jim Jagielski wrote:
https://dist.apache.org/repos/dist/dev/openoffice/macOS-4.1.4-20171101/  




On Nov 1, 2017, at 6:15 PM, Rory O'Farrell  wrote:

May I have a URL for the repaired Mac version of 4.1.4 (or a copy of 
the repaired Mac file) which I can pass to the Forum user who has 
posted on this problem; he uses charts daily and can be relied upon 
to report any other problems.


Rory



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

Re: Issue for 4.1.4 and MacOS

2017-11-02 Thread Larry Gusaas 

Tested calc in the repaired version. Charts are saving properly.

On 2017-11-02, 4:48 AM Jim Jagielski wrote:

https://dist.apache.org/repos/dist/dev/openoffice/macOS-4.1.4-20171101/ 



On Nov 1, 2017, at 6:15 PM, Rory O'Farrell  wrote:

May I have a URL for the repaired Mac version of 4.1.4 (or a copy of the 
repaired Mac file) which I can pass to the Forum user who has posted on this 
problem; he uses charts daily and can be relied upon to report any other 
problems.

Rory

--
Rory O'Farrell 

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



__




--
_

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: Issue for 4.1.4 and MacOS

2017-11-02 Thread Kay Schenk 


On 11/02/2017 08:20 AM, Rory O'Farrell wrote:

Reports from the affected user are that old files (pre 4.1.4) with charts are 
opening correctly.  Files made and/or saved with the faulty 4.1.4 release are 
not showing charts, as we would expect, as the charts were not stored in the 
files.  When these files are remade with the new version and the charts 
inserted, they then work as expected.



Good news!!

--
--
MzK

"Only the truth will save you now."
  -- Ensei Tankado, "Digital Fortress"

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

Re: Issue for 4.1.4 and MacOS

2017-11-02 Thread Rory O'Farrell 
Reports from the affected user are that old files (pre 4.1.4) with charts are 
opening correctly.  Files made and/or saved with the faulty 4.1.4 release are 
not showing charts, as we would expect, as the charts were not stored in the 
files.  When these files are remade with the new version and the charts 
inserted, they then work as expected.

-- 
Rory O'Farrell 

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

Re: Issue for 4.1.4 and MacOS

2017-11-02 Thread Rory O'Farrell 
On Thu, 2 Nov 2017 06:48:03 -0400
Jim Jagielski  wrote:

> https://dist.apache.org/repos/dist/dev/openoffice/macOS-4.1.4-20171101/ 
> 
> 
> > On Nov 1, 2017, at 6:15 PM, Rory O'Farrell  wrote:
> > 
> > May I have a URL for the repaired Mac version of 4.1.4 (or a copy of the 
> > repaired Mac file) which I can pass to the Forum user who has posted on 
> > this problem; he uses charts daily and can be relied upon to report any 
> > other problems.
> > 
> > Rory
> > 
> > -- 
> > Rory O'Farrell 
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> > 
> 

Thank you - I asked for a URL to be certain I got a correct one with the latest 
revision.

-- 
Rory O'Farrell 

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

Re: Issue for 4.1.4 and MacOS

2017-11-02 Thread Jim Jagielski 
https://dist.apache.org/repos/dist/dev/openoffice/macOS-4.1.4-20171101/ 


> On Nov 1, 2017, at 6:15 PM, Rory O'Farrell  wrote:
> 
> May I have a URL for the repaired Mac version of 4.1.4 (or a copy of the 
> repaired Mac file) which I can pass to the Forum user who has posted on this 
> problem; he uses charts daily and can be relied upon to report any other 
> problems.
> 
> Rory
> 
> -- 
> Rory O'Farrell 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>

Re: Issue for 4.1.4 and MacOS

2017-11-01 Thread Marcus 

Am 01.11.2017 um 23:09 schrieb Rory O'Farrell:

On Wed, 1 Nov 2017 22:41:38 +0100
Marcus  wrote:


Am 01.11.2017 um 00:29 schrieb Matthias Seidel:

Am 01.11.2017 um 00:22 schrieb Andrea Pescetti:

Matthias Seidel wrote:

Am 31.10.2017 um 23:39 schrieb Andrea Pescetti:

Andrea Pescetti wrote:

In terms of the update feed, we can keep on hold the update feeds for
the 4.1.3 (and earlier) to 4.1.4 upgrade for Mac users; and once 4.1.5
is out, we will push the update as usual.

I could temporarily exchange all update feeds with versions without
macOS?


This is overkill. Those users have ignored update notifications for at
least one year anyway, so the impact would be minimal. 4.1.3 users and
new users are the primary target.


It is not so much work for me to do...

And you would be surprised how many updates there are every day from
older versions via update feed.
I can see it in real time with "Google Analytics". ;-)




download page would suggest 4.1.4 for other platforms and 4.1.3 for
Mac, with a short explanation saying that OS X binary builds will be
provided soon (then whether this happens with "new" 4.1.4 builds or
with 4.1.5 is a detail that doesn't concern users at this time).


We could do that in a similar way as we tell people that 4.1.4 is not
available for OS X <= 10.6.
The logic is in
http://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/content/download/download.js



I thought we had some easier way to just "cap" OS X to 4.1.3, but
Marcus probably knows best how we could do it - provided we want to,
of course; it's just a proposal for the time being, and I can't even
verify the issue directly.


Yes, Marcus knows best. But I think this would be the best way to
implement it.


fix is ready and working locally.

Text in the red error box:

Problem: Apache OpenOffice 4.1.4 is not available for OS X (version >=
10.7) (DMG).
Solution: Please select version 4.1.0 or newer.

Marcus




I suggest a small change: "Apache OpenOffice 4.1.4 is not YET available..." 
(remove the emphasis, oif course)
and
"Please select version 4.1.0 - 4.1.3"


I really would like. However, text changes are not really possible as 
I'm "abusing" an existing exception to put another one into it. This is 
only possible when also re-using the already existing error texts.


Creating new texts is not possible without breaking the scripting. And 
not for all languages within a few hours.


I'm really sorry but we should see this as it is: just a dirty-hack 
until we have the real solution. ;-(


Marcus


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

Re: Issue for 4.1.4 and MacOS

2017-11-01 Thread Rory O'Farrell 
May I have a URL for the repaired Mac version of 4.1.4 (or a copy of the 
repaired Mac file) which I can pass to the Forum user who has posted on this 
problem; he uses charts daily and can be relied upon to report any other 
problems.

Rory

-- 
Rory O'Farrell 

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

Re: Issue for 4.1.4 and MacOS

2017-11-01 Thread Rory O'Farrell 
On Wed, 1 Nov 2017 22:41:38 +0100
Marcus  wrote:

> Am 01.11.2017 um 00:29 schrieb Matthias Seidel:
> > Am 01.11.2017 um 00:22 schrieb Andrea Pescetti:
> >> Matthias Seidel wrote:
> >>> Am 31.10.2017 um 23:39 schrieb Andrea Pescetti:
>  Andrea Pescetti wrote:
> > In terms of the update feed, we can keep on hold the update feeds for
> > the 4.1.3 (and earlier) to 4.1.4 upgrade for Mac users; and once 4.1.5
> > is out, we will push the update as usual.
> >>> I could temporarily exchange all update feeds with versions without
> >>> macOS?
> >>
> >> This is overkill. Those users have ignored update notifications for at
> >> least one year anyway, so the impact would be minimal. 4.1.3 users and
> >> new users are the primary target.
> > 
> > It is not so much work for me to do...
> > 
> > And you would be surprised how many updates there are every day from
> > older versions via update feed.
> > I can see it in real time with "Google Analytics". ;-)
> > 
> >>
>  download page would suggest 4.1.4 for other platforms and 4.1.3 for
>  Mac, with a short explanation saying that OS X binary builds will be
>  provided soon (then whether this happens with "new" 4.1.4 builds or
>  with 4.1.5 is a detail that doesn't concern users at this time).
> >>>
> >>> We could do that in a similar way as we tell people that 4.1.4 is not
> >>> available for OS X <= 10.6.
> >>> The logic is in
> >>> http://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/content/download/download.js
> >>>
> >>
> >> I thought we had some easier way to just "cap" OS X to 4.1.3, but
> >> Marcus probably knows best how we could do it - provided we want to,
> >> of course; it's just a proposal for the time being, and I can't even
> >> verify the issue directly.
> > 
> > Yes, Marcus knows best. But I think this would be the best way to
> > implement it.
> 
> fix is ready and working locally.
> 
> Text in the red error box:
> 
> Problem: Apache OpenOffice 4.1.4 is not available for OS X (version >= 
> 10.7) (DMG).
> Solution: Please select version 4.1.0 or newer.
> 
> Marcus
> 
>

I suggest a small change: "Apache OpenOffice 4.1.4 is not YET available..." 
(remove the emphasis, oif course)
and 
"Please select version 4.1.0 - 4.1.3"

Rory


-- 
Rory O'Farrell 

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

Re: Issue for 4.1.4 and MacOS

2017-11-01 Thread Marcus 

Am 01.11.2017 um 00:29 schrieb Matthias Seidel:

Am 01.11.2017 um 00:22 schrieb Andrea Pescetti:

Matthias Seidel wrote:

Am 31.10.2017 um 23:39 schrieb Andrea Pescetti:

Andrea Pescetti wrote:

In terms of the update feed, we can keep on hold the update feeds for
the 4.1.3 (and earlier) to 4.1.4 upgrade for Mac users; and once 4.1.5
is out, we will push the update as usual.

I could temporarily exchange all update feeds with versions without
macOS?


This is overkill. Those users have ignored update notifications for at
least one year anyway, so the impact would be minimal. 4.1.3 users and
new users are the primary target.


It is not so much work for me to do...

And you would be surprised how many updates there are every day from
older versions via update feed.
I can see it in real time with "Google Analytics". ;-)




download page would suggest 4.1.4 for other platforms and 4.1.3 for
Mac, with a short explanation saying that OS X binary builds will be
provided soon (then whether this happens with "new" 4.1.4 builds or
with 4.1.5 is a detail that doesn't concern users at this time).


We could do that in a similar way as we tell people that 4.1.4 is not
available for OS X <= 10.6.
The logic is in
http://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/content/download/download.js



I thought we had some easier way to just "cap" OS X to 4.1.3, but
Marcus probably knows best how we could do it - provided we want to,
of course; it's just a proposal for the time being, and I can't even
verify the issue directly.


Yes, Marcus knows best. But I think this would be the best way to
implement it.


fix is ready and working locally.

Text in the red error box:

Problem: Apache OpenOffice 4.1.4 is not available for OS X (version >= 
10.7) (DMG).

Solution: Please select version 4.1.0 or newer.

Marcus


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

Re: Issue for 4.1.4 and MacOS

2017-11-01 Thread Kay Schenk 

On 10/31/2017 11:03 AM, Jim Jagielski wrote:

It would be easy to bump the build number 414m6 just for macOS.
Of course, the date is also changed, even if we keep the same
build number.


This makes more sense to me than a complete 4.1.5 (for all?) when this 
build issue just applies to MacOS.  But the update feed script would 
need some tweaking.




I am up for whatever makes sense. The issue is that it's
not a code "problem" at all.


On Oct 31, 2017, at 1:52 PM, Dave Fisher  wrote:



On Oct 31, 2017, at 9:51 AM, Patricia Shanahan  wrote:

I do not know if this is the right choice, but we should include doing both in 
our thinking. Rebuild 4.1.4 for Mac only, test, and upload as soon as possible. 
Meanwhile, create, test, and vote on 4.1.5, to pick up the upgrade service.

I agree this what we need to think about. With the new 4.1.4 route we should 
make sure that we can tell the difference between the bad original and the 
repaired build. Is the date sufficient or would build number be better? I 
really don’t like the idea of people being confused about what they need to do 
to fix issues. Right now the message is to downgrade to 4.1.3.

I would like to know what Andrea and Matthias think since they have been 
working with the upgrade system.

Regards,
Dave


On 10/31/2017 9:30 AM, Dave Fisher wrote:

There have been over 1,000,000 downloads of 4.1.4.  How many were of the bad 
Mac version?
If we replace then how would those people know to upgrade?
This issue makes me think we need to have this be a new version so that we can 
setup the upgrade service correctly.
Regards,
Dave

On Oct 31, 2017, at 9:21 AM, Jim Jagielski  wrote:

Question: Assuming we have "correction" builds available,
what do we do? Simply replace the online version with
these?

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


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



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



--
--
MzK

"Only the truth will save you now."
  -- Ensei Tankado, "Digital Fortress"


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

Re: Issue for 4.1.4 and MacOS

2017-11-01 Thread Dave Fisher 

> On Nov 1, 2017, at 8:04 AM, Jim Jagielski  wrote:
> 
> I have replacement macOS builds available which solve this problem.
> 
> There were no source code changes required: it was simply an issue
> with the build environment itself. As such, these new builds have
> the same version numbers, just different build dates.
> 
> I'd like to propose that we open up these builds for additional
> macOS/OSX testing before we "replace" the current builds.

+1 - I’ve done a smoke test and can confirm that the particular bug with saving 
links is fixed.

> 
> Comments? Feedback? Suggestions?

I am for disclosing the url so that the new build can be tested quickly. We 
should put the link on dev@, users@ and qa@ - any others?

I think we wait on the forums until we confirm the replacement.

How long should we allow for testing?

Regards,
Dave

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



signature.asc
Description: Message signed with OpenPGP

Re: Issue for 4.1.4 and MacOS

2017-11-01 Thread Jim Jagielski 
I have replacement macOS builds available which solve this problem.

There were no source code changes required: it was simply an issue
with the build environment itself. As such, these new builds have
the same version numbers, just different build dates.

I'd like to propose that we open up these builds for additional
macOS/OSX testing before we "replace" the current builds.

Comments? Feedback? Suggestions?

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

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Matthias Seidel 
Am 01.11.2017 um 00:22 schrieb Andrea Pescetti:
> Matthias Seidel wrote:
>> Am 31.10.2017 um 23:39 schrieb Andrea Pescetti:
>>> Andrea Pescetti wrote:
 In terms of the update feed, we can keep on hold the update feeds for
 the 4.1.3 (and earlier) to 4.1.4 upgrade for Mac users; and once 4.1.5
 is out, we will push the update as usual.
>> I could temporarily exchange all update feeds with versions without
>> macOS?
>
> This is overkill. Those users have ignored update notifications for at
> least one year anyway, so the impact would be minimal. 4.1.3 users and
> new users are the primary target.

It is not so much work for me to do...

And you would be surprised how many updates there are every day from
older versions via update feed.
I can see it in real time with "Google Analytics". ;-)

>
>>> download page would suggest 4.1.4 for other platforms and 4.1.3 for
>>> Mac, with a short explanation saying that OS X binary builds will be
>>> provided soon (then whether this happens with "new" 4.1.4 builds or
>>> with 4.1.5 is a detail that doesn't concern users at this time).
>>
>> We could do that in a similar way as we tell people that 4.1.4 is not
>> available for OS X <= 10.6.
>> The logic is in
>> http://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/content/download/download.js
>>
>
> I thought we had some easier way to just "cap" OS X to 4.1.3, but
> Marcus probably knows best how we could do it - provided we want to,
> of course; it's just a proposal for the time being, and I can't even
> verify the issue directly.

Yes, Marcus knows best. But I think this would be the best way to
implement it.

Regards, Matthias

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




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Andrea Pescetti 

Matthias Seidel wrote:

Am 31.10.2017 um 23:39 schrieb Andrea Pescetti:

Andrea Pescetti wrote:

In terms of the update feed, we can keep on hold the update feeds for
the 4.1.3 (and earlier) to 4.1.4 upgrade for Mac users; and once 4.1.5
is out, we will push the update as usual.

I could temporarily exchange all update feeds with versions without macOS?


This is overkill. Those users have ignored update notifications for at 
least one year anyway, so the impact would be minimal. 4.1.3 users and 
new users are the primary target.



download page would suggest 4.1.4 for other platforms and 4.1.3 for
Mac, with a short explanation saying that OS X binary builds will be
provided soon (then whether this happens with "new" 4.1.4 builds or
with 4.1.5 is a detail that doesn't concern users at this time).


We could do that in a similar way as we tell people that 4.1.4 is not
available for OS X <= 10.6.
The logic is in
http://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/content/download/download.js


I thought we had some easier way to just "cap" OS X to 4.1.3, but Marcus 
probably knows best how we could do it - provided we want to, of course; 
it's just a proposal for the time being, and I can't even verify the 
issue directly.


Regards,
  Andrea.

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

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Matthias Seidel 
Am 31.10.2017 um 23:39 schrieb Andrea Pescetti:
> Andrea Pescetti wrote:
>> In terms of the update feed, we can keep on hold the update feeds for
>> the 4.1.3 (and earlier) to 4.1.4 upgrade for Mac users; and once 4.1.5
>> is out, we will push the update as usual.

I could temporarily exchange all update feeds with versions without macOS?
Since the old ones will always lead people to the download page, even if
they only say e.g. 4.1.2 is available...

>
> Another obvious thing we can do (if we are really sure that 4.1.4 for
> Mac contains a dataloss bug) is to simply retire the Mac build. The
> download page would suggest 4.1.4 for other platforms and 4.1.3 for
> Mac, with a short explanation saying that OS X binary builds will be
> provided soon (then whether this happens with "new" 4.1.4 builds or
> with 4.1.5 is a detail that doesn't concern users at this time).

We could do that in a similar way as we tell people that 4.1.4 is not
available for OS X <= 10.6.
The logic is in
http://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/content/download/download.js

Regards, Matthias

>
> Files would still be on SourceForge for those who really want to
> download 4.1.4, but this would still guarantee that Mac users do not
> download a build known to have issues.
>
> Regards,
>   Andrea.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Andrea Pescetti 

Andrea Pescetti wrote:

In terms of the update feed, we can keep on hold the update feeds for
the 4.1.3 (and earlier) to 4.1.4 upgrade for Mac users; and once 4.1.5
is out, we will push the update as usual.


Another obvious thing we can do (if we are really sure that 4.1.4 for 
Mac contains a dataloss bug) is to simply retire the Mac build. The 
download page would suggest 4.1.4 for other platforms and 4.1.3 for Mac, 
with a short explanation saying that OS X binary builds will be provided 
soon (then whether this happens with "new" 4.1.4 builds or with 4.1.5 is 
a detail that doesn't concern users at this time).


Files would still be on SourceForge for those who really want to 
download 4.1.4, but this would still guarantee that Mac users do not 
download a build known to have issues.


Regards,
  Andrea.

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

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Andrea Pescetti 

Dave Fisher wrote:

I would like to know what Andrea and Matthias think since they have been 
working with the upgrade system.


This is just a bug. A bad bug, that teaches us that (let alone the 
source code) we should document not only the configure switches but also 
key details of the environment.


As for the resolution, I would follow our standard practices, nothing 
special:


1. We make sure the bug is fixed, and document in all detail what 
happened on https://bz.apache.org/ooo/show_bug.cgi?id=127568 - note that 
we are still at this stage at the moment, and we can't be sure whether 
this is a build-only issue (as it seems to be) or it requires code 
changes or at least Makefile changes.


2. We seriously test the new builds since it's clear that Mac is the 
most problematic platform, starting with the bug reported by Roberto for 
RC4, then the inability to save documents in the first attempt of RC5, 
then this dataloss issue in the released 4.1.4.


3. We simply release 4.1.5. There is nothing preventing us from doing 
so. It will take a couple weeks, maybe we will find another couple 
regressions and fix them in the meantime. For example (this is not a 
regression but a UX problem) we'll want to include the latest English 
dictionary. There's nothing wrong in making a new release one month 
after 4.1.4 rather than one year after it!


In terms of the update feed, we can keep on hold the update feeds for 
the 4.1.3 (and earlier) to 4.1.4 upgrade for Mac users; and once 4.1.5 
is out, we will push the update as usual.


Regards,
  Andrea.

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

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Marcus 

Am 31.10.2017 um 19:46 schrieb Dave Fisher:

The implication is that build id, milestone, binaries and svn version must be 
in sync across all of OpenOffice.


which is the case already. ;-)


Jim should leave the values the same as the prior release.

So 75,000 plus users of Mac may be in limbo not knowing about the update until 
4.2 comes out. We will need to announce the situation when we are ready.

We won’t do 4.1.5, but then should try to get 4.2 done pretty soon.

We can look into the download pages to see about changes for 4.2 allowing 
different builds for different platforms?

This seems the most pragmatic approach given current constraints. Do we all 
agree?


sure, we can split up things. But this would createa nightmare for the 
support/forums guys when every platform (language aloso ;-) ) will/can 
have different metadata.


So, the problem is not the download script. I'm sure that this can be 
enhanced. But do we really want to go this step? I'm not so sure.


Marcus




On Oct 31, 2017, at 11:29 AM, Marcus  wrote:

Am 31.10.2017 um 19:09 schrieb Jim Jagielski:

Actually, it looks like buildid (9788) is likely
should also be bumped, looking at the way downloads
are done... Do linux and Windows would be m5(9788)
and mac would be m5(9789) or m6(9789)
I am *guessing* that the m# is SVN related
and the buildid number is courtesy build # related??

On Oct 31, 2017, at 2:03 PM, Jim Jagielski  wrote:


the new builds would be downloadable as long as they have the same version 
number (4.1.4) inside the filenames.

It's just that the new build ID or milestone number cannot be displayed on the 
download webpage as it has to be the same for every platform.

But I think that this shouldn't be a problem. When the Mac users download the 
files, they get the new files and should be happy.

Marcus




It would be easy to bump the build number 414m6 just for macOS.
Of course, the date is also changed, even if we keep the same
build number.

I am up for whatever makes sense. The issue is that it's
not a code "problem" at all.


On Oct 31, 2017, at 1:52 PM, Dave Fisher  wrote:



On Oct 31, 2017, at 9:51 AM, Patricia Shanahan  wrote:

I do not know if this is the right choice, but we should include doing both in 
our thinking. Rebuild 4.1.4 for Mac only, test, and upload as soon as possible. 
Meanwhile, create, test, and vote on 4.1.5, to pick up the upgrade service.


I agree this what we need to think about. With the new 4.1.4 route we should 
make sure that we can tell the difference between the bad original and the 
repaired build. Is the date sufficient or would build number be better? I 
really don’t like the idea of people being confused about what they need to do 
to fix issues. Right now the message is to downgrade to 4.1.3.

I would like to know what Andrea and Matthias think since they have been 
working with the upgrade system.

Regards,
Dave



On 10/31/2017 9:30 AM, Dave Fisher wrote:

There have been over 1,000,000 downloads of 4.1.4.  How many were of the bad 
Mac version?
If we replace then how would those people know to upgrade?
This issue makes me think we need to have this be a new version so that we can 
setup the upgrade service correctly.
Regards,
Dave

On Oct 31, 2017, at 9:21 AM, Jim Jagielski  wrote:

Question: Assuming we have "correction" builds available,
what do we do? Simply replace the online version with
these?



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

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Dave Fisher 
Hi Marcus,

The implication is that build id, milestone, binaries and svn version must be 
in sync across all of OpenOffice.

Jim should leave the values the same as the prior release.

So 75,000 plus users of Mac may be in limbo not knowing about the update until 
4.2 comes out. We will need to announce the situation when we are ready.

We won’t do 4.1.5, but then should try to get 4.2 done pretty soon.

We can look into the download pages to see about changes for 4.2 allowing 
different builds for different platforms?

This seems the most pragmatic approach given current constraints. Do we all 
agree?

Regards,
Dave

> On Oct 31, 2017, at 11:29 AM, Marcus  wrote:
> 
> Am 31.10.2017 um 19:09 schrieb Jim Jagielski:
>> Actually, it looks like buildid (9788) is likely
>> should also be bumped, looking at the way downloads
>> are done... Do linux and Windows would be m5(9788)
>> and mac would be m5(9789) or m6(9789)
>> I am *guessing* that the m# is SVN related
>> and the buildid number is courtesy build # related??
>>> On Oct 31, 2017, at 2:03 PM, Jim Jagielski  wrote:
> 
> the new builds would be downloadable as long as they have the same version 
> number (4.1.4) inside the filenames.
> 
> It's just that the new build ID or milestone number cannot be displayed on 
> the download webpage as it has to be the same for every platform.
> 
> But I think that this shouldn't be a problem. When the Mac users download the 
> files, they get the new files and should be happy.
> 
> Marcus
> 
> 
> 
>>> It would be easy to bump the build number 414m6 just for macOS.
>>> Of course, the date is also changed, even if we keep the same
>>> build number.
>>> 
>>> I am up for whatever makes sense. The issue is that it's
>>> not a code "problem" at all.
>>> 
 On Oct 31, 2017, at 1:52 PM, Dave Fisher  wrote:
 
 
> On Oct 31, 2017, at 9:51 AM, Patricia Shanahan  wrote:
> 
> I do not know if this is the right choice, but we should include doing 
> both in our thinking. Rebuild 4.1.4 for Mac only, test, and upload as 
> soon as possible. Meanwhile, create, test, and vote on 4.1.5, to pick up 
> the upgrade service.
 
 I agree this what we need to think about. With the new 4.1.4 route we 
 should make sure that we can tell the difference between the bad original 
 and the repaired build. Is the date sufficient or would build number be 
 better? I really don’t like the idea of people being confused about what 
 they need to do to fix issues. Right now the message is to downgrade to 
 4.1.3.
 
 I would like to know what Andrea and Matthias think since they have been 
 working with the upgrade system.
 
 Regards,
 Dave
 
> 
> On 10/31/2017 9:30 AM, Dave Fisher wrote:
>> There have been over 1,000,000 downloads of 4.1.4.  How many were of the 
>> bad Mac version?
>> If we replace then how would those people know to upgrade?
>> This issue makes me think we need to have this be a new version so that 
>> we can setup the upgrade service correctly.
>> Regards,
>> Dave
>>> On Oct 31, 2017, at 9:21 AM, Jim Jagielski  wrote:
>>> 
>>> Question: Assuming we have "correction" builds available,
>>> what do we do? Simply replace the online version with
>>> these?
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 



signature.asc
Description: Message signed with OpenPGP

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Marcus 

Am 31.10.2017 um 19:09 schrieb Jim Jagielski:

Actually, it looks like buildid (9788) is likely
should also be bumped, looking at the way downloads
are done... Do linux and Windows would be m5(9788)
and mac would be m5(9789) or m6(9789)

I am *guessing* that the m# is SVN related
and the buildid number is courtesy build # related??

On Oct 31, 2017, at 2:03 PM, Jim Jagielski  wrote:


the new builds would be downloadable as long as they have the same 
version number (4.1.4) inside the filenames.


It's just that the new build ID or milestone number cannot be displayed 
on the download webpage as it has to be the same for every platform.


But I think that this shouldn't be a problem. When the Mac users 
download the files, they get the new files and should be happy.


Marcus




It would be easy to bump the build number 414m6 just for macOS.
Of course, the date is also changed, even if we keep the same
build number.

I am up for whatever makes sense. The issue is that it's
not a code "problem" at all.


On Oct 31, 2017, at 1:52 PM, Dave Fisher  wrote:



On Oct 31, 2017, at 9:51 AM, Patricia Shanahan  wrote:

I do not know if this is the right choice, but we should include doing both in 
our thinking. Rebuild 4.1.4 for Mac only, test, and upload as soon as possible. 
Meanwhile, create, test, and vote on 4.1.5, to pick up the upgrade service.


I agree this what we need to think about. With the new 4.1.4 route we should 
make sure that we can tell the difference between the bad original and the 
repaired build. Is the date sufficient or would build number be better? I 
really don’t like the idea of people being confused about what they need to do 
to fix issues. Right now the message is to downgrade to 4.1.3.

I would like to know what Andrea and Matthias think since they have been 
working with the upgrade system.

Regards,
Dave



On 10/31/2017 9:30 AM, Dave Fisher wrote:

There have been over 1,000,000 downloads of 4.1.4.  How many were of the bad 
Mac version?
If we replace then how would those people know to upgrade?
This issue makes me think we need to have this be a new version so that we can 
setup the upgrade service correctly.
Regards,
Dave

On Oct 31, 2017, at 9:21 AM, Jim Jagielski  wrote:

Question: Assuming we have "correction" builds available,
what do we do? Simply replace the online version with
these?



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

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Dave Fisher 
Hi Jim,

Have a look at 
http://svn.apache.org/viewvc/openoffice/devtools/genUpdateFeed/generate-update-feed.sh?view=markup

80 

 elif [ $idx -eq 2 ]; then
81 

 productbuildid[$version]=$data

It looks like a version can only have one build id.

It would be safe to bump to m6(9788) but it is not so safe to do m6(9789). 
Unless generate-update-feed.sh is updated.

Regards,
Dave

> On Oct 31, 2017, at 11:09 AM, Jim Jagielski  wrote:
> 
> Actually, it looks like buildid (9788) is likely
> should also be bumped, looking at the way downloads
> are done... Do linux and Windows would be m5(9788)
> and mac would be m5(9789) or m6(9789)
> 
> I am *guessing* that the m# is SVN related
> and the buildid number is courtesy build # related??
>> On Oct 31, 2017, at 2:03 PM, Jim Jagielski  wrote:
>> 
>> It would be easy to bump the build number 414m6 just for macOS.
>> Of course, the date is also changed, even if we keep the same
>> build number.
>> 
>> I am up for whatever makes sense. The issue is that it's
>> not a code "problem" at all.
>> 
>>> On Oct 31, 2017, at 1:52 PM, Dave Fisher  wrote:
>>> 
>>> 
 On Oct 31, 2017, at 9:51 AM, Patricia Shanahan  wrote:
 
 I do not know if this is the right choice, but we should include doing 
 both in our thinking. Rebuild 4.1.4 for Mac only, test, and upload as soon 
 as possible. Meanwhile, create, test, and vote on 4.1.5, to pick up the 
 upgrade service.
>>> 
>>> I agree this what we need to think about. With the new 4.1.4 route we 
>>> should make sure that we can tell the difference between the bad original 
>>> and the repaired build. Is the date sufficient or would build number be 
>>> better? I really don’t like the idea of people being confused about what 
>>> they need to do to fix issues. Right now the message is to downgrade to 
>>> 4.1.3.
>>> 
>>> I would like to know what Andrea and Matthias think since they have been 
>>> working with the upgrade system.
>>> 
>>> Regards,
>>> Dave
>>> 
 
 On 10/31/2017 9:30 AM, Dave Fisher wrote:
> There have been over 1,000,000 downloads of 4.1.4.  How many were of the 
> bad Mac version?
> If we replace then how would those people know to upgrade?
> This issue makes me think we need to have this be a new version so that 
> we can setup the upgrade service correctly.
> Regards,
> Dave
>> On Oct 31, 2017, at 9:21 AM, Jim Jagielski  wrote:
>> 
>> Question: Assuming we have "correction" builds available,
>> what do we do? Simply replace the online version with
>> these?
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: dev-h...@openoffice.apache.org
 
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 



signature.asc
Description: Message signed with OpenPGP

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Jim Jagielski 
So the only thing that will indicate the new version will
be an updated date in the About page?

> On Oct 31, 2017, at 2:19 PM, Rory O'Farrell  wrote:
> 
> On Tue, 31 Oct 2017 14:09:46 -0400
> Jim Jagielski > wrote:
> 
>> Actually, it looks like buildid (9788) is likely
>> should also be bumped, looking at the way downloads
>> are done... Do linux and Windows would be m5(9788)
>> and mac would be m5(9789) or m6(9789)
> 
> When a decision is reached and the new Mac version is ready for download, I 
> will post a notice on the Forum advising Mac owners to install the corrected 
> version
> 
> Rory
> 
>> 
>> I am *guessing* that the m# is SVN related
>> and the buildid number is courtesy build # related??
>>> On Oct 31, 2017, at 2:03 PM, Jim Jagielski  wrote:
>>> 
>>> It would be easy to bump the build number 414m6 just for macOS.
>>> Of course, the date is also changed, even if we keep the same
>>> build number.
>>> 
>>> I am up for whatever makes sense. The issue is that it's
>>> not a code "problem" at all.
>>> 
 On Oct 31, 2017, at 1:52 PM, Dave Fisher  wrote:
 
 
> On Oct 31, 2017, at 9:51 AM, Patricia Shanahan  wrote:
> 
> I do not know if this is the right choice, but we should include doing 
> both in our thinking. Rebuild 4.1.4 for Mac only, test, and upload as 
> soon as possible. Meanwhile, create, test, and vote on 4.1.5, to pick up 
> the upgrade service.
 
 I agree this what we need to think about. With the new 4.1.4 route we 
 should make sure that we can tell the difference between the bad original 
 and the repaired build. Is the date sufficient or would build number be 
 better? I really don’t like the idea of people being confused about what 
 they need to do to fix issues. Right now the message is to downgrade to 
 4.1.3.
 
 I would like to know what Andrea and Matthias think since they have been 
 working with the upgrade system.
 
 Regards,
 Dave
 
> 
> On 10/31/2017 9:30 AM, Dave Fisher wrote:
>> There have been over 1,000,000 downloads of 4.1.4.  How many were of the 
>> bad Mac version?
>> If we replace then how would those people know to upgrade?
>> This issue makes me think we need to have this be a new version so that 
>> we can setup the upgrade service correctly.
>> Regards,
>> Dave
>>> On Oct 31, 2017, at 9:21 AM, Jim Jagielski  wrote:
>>> 
>>> Question: Assuming we have "correction" builds available,
>>> what do we do? Simply replace the online version with
>>> these?
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> 
>> 
> 
> 
> -- 
> Rory O'Farrell >
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org 
> 
> For additional commands, e-mail: dev-h...@openoffice.apache.org 
>

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Rory O'Farrell 
On Tue, 31 Oct 2017 14:09:46 -0400
Jim Jagielski  wrote:

> Actually, it looks like buildid (9788) is likely
> should also be bumped, looking at the way downloads
> are done... Do linux and Windows would be m5(9788)
> and mac would be m5(9789) or m6(9789)

When a decision is reached and the new Mac version is ready for download, I 
will post a notice on the Forum advising Mac owners to install the corrected 
version

Rory

> 
> I am *guessing* that the m# is SVN related
> and the buildid number is courtesy build # related??
> > On Oct 31, 2017, at 2:03 PM, Jim Jagielski  wrote:
> > 
> > It would be easy to bump the build number 414m6 just for macOS.
> > Of course, the date is also changed, even if we keep the same
> > build number.
> > 
> > I am up for whatever makes sense. The issue is that it's
> > not a code "problem" at all.
> > 
> >> On Oct 31, 2017, at 1:52 PM, Dave Fisher  wrote:
> >> 
> >> 
> >>> On Oct 31, 2017, at 9:51 AM, Patricia Shanahan  wrote:
> >>> 
> >>> I do not know if this is the right choice, but we should include doing 
> >>> both in our thinking. Rebuild 4.1.4 for Mac only, test, and upload as 
> >>> soon as possible. Meanwhile, create, test, and vote on 4.1.5, to pick up 
> >>> the upgrade service.
> >> 
> >> I agree this what we need to think about. With the new 4.1.4 route we 
> >> should make sure that we can tell the difference between the bad original 
> >> and the repaired build. Is the date sufficient or would build number be 
> >> better? I really don’t like the idea of people being confused about what 
> >> they need to do to fix issues. Right now the message is to downgrade to 
> >> 4.1.3.
> >> 
> >> I would like to know what Andrea and Matthias think since they have been 
> >> working with the upgrade system.
> >> 
> >> Regards,
> >> Dave
> >> 
> >>> 
> >>> On 10/31/2017 9:30 AM, Dave Fisher wrote:
>  There have been over 1,000,000 downloads of 4.1.4.  How many were of the 
>  bad Mac version?
>  If we replace then how would those people know to upgrade?
>  This issue makes me think we need to have this be a new version so that 
>  we can setup the upgrade service correctly.
>  Regards,
>  Dave
> > On Oct 31, 2017, at 9:21 AM, Jim Jagielski  wrote:
> > 
> > Question: Assuming we have "correction" builds available,
> > what do we do? Simply replace the online version with
> > these?
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> > 
> >>> 
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >>> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>> 
> >> 
> > 
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> > 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
> 


-- 
Rory O'Farrell 

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

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Dave Fisher 
Sorry hit the command key and track pad at the same time and sent before done.

> On Oct 31, 2017, at 11:10 AM, Dave Fisher  wrote:
> 
> 
>> On Oct 31, 2017, at 11:05 AM, Matthias Seidel > > wrote:
>> 
>> Am 31.10.2017 um 18:52 schrieb Dave Fisher:
 On Oct 31, 2017, at 9:51 AM, Patricia Shanahan > wrote:
 
 I do not know if this is the right choice, but we should include doing 
 both in our thinking. Rebuild 4.1.4 for Mac only, test, and upload as soon 
 as possible. Meanwhile, create, test, and vote on 4.1.5, to pick up the 
 upgrade service.
>>> I agree this what we need to think about. With the new 4.1.4 route we 
>>> should make sure that we can tell the difference between the bad original 
>>> and the repaired build. Is the date sufficient or would build number be 
>>> better? I really don’t like the idea of people being confused about what 
>>> they need to do to fix issues. Right now the message is to downgrade to 
>>> 4.1.3.
>> 
>> My $ 0.02:
>> The date would be sufficient.
>> A new build number means a new build and I don't like the idea to
>> confuse 95% of our users (Windows and Linux) with a "new" version, where
>> not a single line of code was changed.
>> Rebuild the mac version and make an announcement/press release to let
>> the people know about it.
> 
> Jim is mentioning a different id for the build from the one that drives the 
> upgrade:
> 
> http://svn.apache.org/viewvc/openoffice/devtools/genUpdateFeed/ProductInfos.txt?view=markup
>  
> 
> 
> 4.1.4 OpenOffice_4 9788 https://www.openoffice.org/download 
>  en-US ast bg ca ca-XR ca-XV cs da de el 
> en-GB es eu fi fr gd gl he hi hu it ja km ko lt nb nl pl pt pt-BR ru sk sl sr 
> sv ta th tr vi zh-CN zh-TW
> 
> 
> 9788 is different from 414m5 or 414m6.
> 
> Jim - I think that 414

I think that changing to 414m6 would be helpful.

Regards,
Dave

> 
>> 
>>> 
>>> I would like to know what Andrea and Matthias think since they have been 
>>> working with the upgrade system.
>> 
>> macOS update notification (4.1.3 -> 4.1.4) is on hold until this issue
>> is fixed.
>> But people can always download directly from our download page, maybe we
>> should put a notice there?
>> 
>> Regards, Matthias
>> 
>>> 
>>> Regards,
>>> Dave
>>> 
 On 10/31/2017 9:30 AM, Dave Fisher wrote:
> There have been over 1,000,000 downloads of 4.1.4.  How many were of the 
> bad Mac version?
> If we replace then how would those people know to upgrade?
> This issue makes me think we need to have this be a new version so that 
> we can setup the upgrade service correctly.
> Regards,
> Dave
>> On Oct 31, 2017, at 9:21 AM, Jim Jagielski > > wrote:
>> 
>> Question: Assuming we have "correction" builds available,
>> what do we do? Simply replace the online version with
>> these?
>> 
>> -
>> 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 
 
 
>> 
>> 
> 



signature.asc
Description: Message signed with OpenPGP

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Dave Fisher 

> On Oct 31, 2017, at 11:05 AM, Matthias Seidel  
> wrote:
> 
> Am 31.10.2017 um 18:52 schrieb Dave Fisher:
>>> On Oct 31, 2017, at 9:51 AM, Patricia Shanahan  wrote:
>>> 
>>> I do not know if this is the right choice, but we should include doing both 
>>> in our thinking. Rebuild 4.1.4 for Mac only, test, and upload as soon as 
>>> possible. Meanwhile, create, test, and vote on 4.1.5, to pick up the 
>>> upgrade service.
>> I agree this what we need to think about. With the new 4.1.4 route we should 
>> make sure that we can tell the difference between the bad original and the 
>> repaired build. Is the date sufficient or would build number be better? I 
>> really don’t like the idea of people being confused about what they need to 
>> do to fix issues. Right now the message is to downgrade to 4.1.3.
> 
> My $ 0.02:
> The date would be sufficient.
> A new build number means a new build and I don't like the idea to
> confuse 95% of our users (Windows and Linux) with a "new" version, where
> not a single line of code was changed.
> Rebuild the mac version and make an announcement/press release to let
> the people know about it.

Jim is mentioning a different id for the build from the one that drives the 
upgrade:

http://svn.apache.org/viewvc/openoffice/devtools/genUpdateFeed/ProductInfos.txt?view=markup

4.1.4 OpenOffice_4 9788 https://www.openoffice.org/download 
 en-US ast bg ca ca-XR ca-XV cs da de el 
en-GB es eu fi fr gd gl he hi hu it ja km ko lt nb nl pl pt pt-BR ru sk sl sr 
sv ta th tr vi zh-CN zh-TW


9788 is different from 414m5 or 414m6.

Jim - I think that 414

> 
>> 
>> I would like to know what Andrea and Matthias think since they have been 
>> working with the upgrade system.
> 
> macOS update notification (4.1.3 -> 4.1.4) is on hold until this issue
> is fixed.
> But people can always download directly from our download page, maybe we
> should put a notice there?
> 
> Regards, Matthias
> 
>> 
>> Regards,
>> Dave
>> 
>>> On 10/31/2017 9:30 AM, Dave Fisher wrote:
 There have been over 1,000,000 downloads of 4.1.4.  How many were of the 
 bad Mac version?
 If we replace then how would those people know to upgrade?
 This issue makes me think we need to have this be a new version so that we 
 can setup the upgrade service correctly.
 Regards,
 Dave
> On Oct 31, 2017, at 9:21 AM, Jim Jagielski  wrote:
> 
> Question: Assuming we have "correction" builds available,
> what do we do? Simply replace the online version with
> these?
> 
> -
> 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
>>> 
> 
> 



signature.asc
Description: Message signed with OpenPGP

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Jim Jagielski 
Actually, it looks like buildid (9788) is likely
should also be bumped, looking at the way downloads
are done... Do linux and Windows would be m5(9788)
and mac would be m5(9789) or m6(9789)

I am *guessing* that the m# is SVN related
and the buildid number is courtesy build # related??
> On Oct 31, 2017, at 2:03 PM, Jim Jagielski  wrote:
> 
> It would be easy to bump the build number 414m6 just for macOS.
> Of course, the date is also changed, even if we keep the same
> build number.
> 
> I am up for whatever makes sense. The issue is that it's
> not a code "problem" at all.
> 
>> On Oct 31, 2017, at 1:52 PM, Dave Fisher  wrote:
>> 
>> 
>>> On Oct 31, 2017, at 9:51 AM, Patricia Shanahan  wrote:
>>> 
>>> I do not know if this is the right choice, but we should include doing both 
>>> in our thinking. Rebuild 4.1.4 for Mac only, test, and upload as soon as 
>>> possible. Meanwhile, create, test, and vote on 4.1.5, to pick up the 
>>> upgrade service.
>> 
>> I agree this what we need to think about. With the new 4.1.4 route we should 
>> make sure that we can tell the difference between the bad original and the 
>> repaired build. Is the date sufficient or would build number be better? I 
>> really don’t like the idea of people being confused about what they need to 
>> do to fix issues. Right now the message is to downgrade to 4.1.3.
>> 
>> I would like to know what Andrea and Matthias think since they have been 
>> working with the upgrade system.
>> 
>> Regards,
>> Dave
>> 
>>> 
>>> On 10/31/2017 9:30 AM, Dave Fisher wrote:
 There have been over 1,000,000 downloads of 4.1.4.  How many were of the 
 bad Mac version?
 If we replace then how would those people know to upgrade?
 This issue makes me think we need to have this be a new version so that we 
 can setup the upgrade service correctly.
 Regards,
 Dave
> On Oct 31, 2017, at 9:21 AM, Jim Jagielski  wrote:
> 
> Question: Assuming we have "correction" builds available,
> what do we do? Simply replace the online version with
> these?
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>> 
>> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 


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

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Matthias Seidel 
Am 31.10.2017 um 18:52 schrieb Dave Fisher:
>> On Oct 31, 2017, at 9:51 AM, Patricia Shanahan  wrote:
>>
>> I do not know if this is the right choice, but we should include doing both 
>> in our thinking. Rebuild 4.1.4 for Mac only, test, and upload as soon as 
>> possible. Meanwhile, create, test, and vote on 4.1.5, to pick up the upgrade 
>> service.
> I agree this what we need to think about. With the new 4.1.4 route we should 
> make sure that we can tell the difference between the bad original and the 
> repaired build. Is the date sufficient or would build number be better? I 
> really don’t like the idea of people being confused about what they need to 
> do to fix issues. Right now the message is to downgrade to 4.1.3.

My $ 0.02:
The date would be sufficient.
A new build number means a new build and I don't like the idea to
confuse 95% of our users (Windows and Linux) with a "new" version, where
not a single line of code was changed.
Rebuild the mac version and make an announcement/press release to let
the people know about it.

>
> I would like to know what Andrea and Matthias think since they have been 
> working with the upgrade system.

macOS update notification (4.1.3 -> 4.1.4) is on hold until this issue
is fixed.
But people can always download directly from our download page, maybe we
should put a notice there?

Regards, Matthias

>
> Regards,
> Dave
>
>> On 10/31/2017 9:30 AM, Dave Fisher wrote:
>>> There have been over 1,000,000 downloads of 4.1.4.  How many were of the 
>>> bad Mac version?
>>> If we replace then how would those people know to upgrade?
>>> This issue makes me think we need to have this be a new version so that we 
>>> can setup the upgrade service correctly.
>>> Regards,
>>> Dave
 On Oct 31, 2017, at 9:21 AM, Jim Jagielski  wrote:

 Question: Assuming we have "correction" builds available,
 what do we do? Simply replace the online version with
 these?

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

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




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Jim Jagielski 
It would be easy to bump the build number 414m6 just for macOS.
Of course, the date is also changed, even if we keep the same
build number.

I am up for whatever makes sense. The issue is that it's
not a code "problem" at all.

> On Oct 31, 2017, at 1:52 PM, Dave Fisher  wrote:
> 
> 
>> On Oct 31, 2017, at 9:51 AM, Patricia Shanahan  wrote:
>> 
>> I do not know if this is the right choice, but we should include doing both 
>> in our thinking. Rebuild 4.1.4 for Mac only, test, and upload as soon as 
>> possible. Meanwhile, create, test, and vote on 4.1.5, to pick up the upgrade 
>> service.
> 
> I agree this what we need to think about. With the new 4.1.4 route we should 
> make sure that we can tell the difference between the bad original and the 
> repaired build. Is the date sufficient or would build number be better? I 
> really don’t like the idea of people being confused about what they need to 
> do to fix issues. Right now the message is to downgrade to 4.1.3.
> 
> I would like to know what Andrea and Matthias think since they have been 
> working with the upgrade system.
> 
> Regards,
> Dave
> 
>> 
>> On 10/31/2017 9:30 AM, Dave Fisher wrote:
>>> There have been over 1,000,000 downloads of 4.1.4.  How many were of the 
>>> bad Mac version?
>>> If we replace then how would those people know to upgrade?
>>> This issue makes me think we need to have this be a new version so that we 
>>> can setup the upgrade service correctly.
>>> Regards,
>>> Dave
 On Oct 31, 2017, at 9:21 AM, Jim Jagielski  wrote:
 
 Question: Assuming we have "correction" builds available,
 what do we do? Simply replace the online version with
 these?
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: dev-h...@openoffice.apache.org
 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> 
> 


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

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Dave Fisher 

> On Oct 31, 2017, at 9:51 AM, Patricia Shanahan  wrote:
> 
> I do not know if this is the right choice, but we should include doing both 
> in our thinking. Rebuild 4.1.4 for Mac only, test, and upload as soon as 
> possible. Meanwhile, create, test, and vote on 4.1.5, to pick up the upgrade 
> service.

I agree this what we need to think about. With the new 4.1.4 route we should 
make sure that we can tell the difference between the bad original and the 
repaired build. Is the date sufficient or would build number be better? I 
really don’t like the idea of people being confused about what they need to do 
to fix issues. Right now the message is to downgrade to 4.1.3.

I would like to know what Andrea and Matthias think since they have been 
working with the upgrade system.

Regards,
Dave

> 
> On 10/31/2017 9:30 AM, Dave Fisher wrote:
>> There have been over 1,000,000 downloads of 4.1.4.  How many were of the bad 
>> Mac version?
>> If we replace then how would those people know to upgrade?
>> This issue makes me think we need to have this be a new version so that we 
>> can setup the upgrade service correctly.
>> Regards,
>> Dave
>>> On Oct 31, 2017, at 9:21 AM, Jim Jagielski  wrote:
>>> 
>>> Question: Assuming we have "correction" builds available,
>>> what do we do? Simply replace the online version with
>>> these?
>>> 
>>> -
>>> 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
> 



signature.asc
Description: Message signed with OpenPGP

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Matthias Seidel 
Am 31.10.2017 um 17:30 schrieb Dave Fisher:
> There have been over 1,000,000 downloads of 4.1.4.  How many were of the bad 
> Mac version?

About 75,000:
https://sourceforge.net/projects/openofficeorg.mirror/files/4.1.4/binaries/stats/os?dates=2017-10-19%20to%202017-10-31

Regards, Matthias

>
> If we replace then how would those people know to upgrade?
>
> This issue makes me think we need to have this be a new version so that we 
> can setup the upgrade service correctly.
>
> Regards,
> Dave
>
>> On Oct 31, 2017, at 9:21 AM, Jim Jagielski  wrote:
>>
>> Question: Assuming we have "correction" builds available,
>> what do we do? Simply replace the online version with
>> these?
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Patricia Shanahan 
I do not know if this is the right choice, but we should include doing 
both in our thinking. Rebuild 4.1.4 for Mac only, test, and upload as 
soon as possible. Meanwhile, create, test, and vote on 4.1.5, to pick up 
the upgrade service.


On 10/31/2017 9:30 AM, Dave Fisher wrote:

There have been over 1,000,000 downloads of 4.1.4.  How many were of the bad 
Mac version?

If we replace then how would those people know to upgrade?

This issue makes me think we need to have this be a new version so that we can 
setup the upgrade service correctly.

Regards,
Dave


On Oct 31, 2017, at 9:21 AM, Jim Jagielski  wrote:

Question: Assuming we have "correction" builds available,
what do we do? Simply replace the online version with
these?

-
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: Issue for 4.1.4 and MacOS

2017-10-31 Thread Dave Fisher 
There have been over 1,000,000 downloads of 4.1.4.  How many were of the bad 
Mac version?

If we replace then how would those people know to upgrade?

This issue makes me think we need to have this be a new version so that we can 
setup the upgrade service correctly.

Regards,
Dave

> On Oct 31, 2017, at 9:21 AM, Jim Jagielski  wrote:
> 
> Question: Assuming we have "correction" builds available,
> what do we do? Simply replace the online version with
> these?
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 



signature.asc
Description: Message signed with OpenPGP

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Jim Jagielski 
Question: Assuming we have "correction" builds available,
what do we do? Simply replace the online version with
these? 

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

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Jim Jagielski 
Nope. This is virgin Xcode7

$ sudo xcode-select -s /Applications/Xcode7.app

> On Oct 31, 2017, at 12:02 PM, Dave Fisher  wrote:
> 
> Hi Jim,
> 
> Any use of XcodeLegacy in your Xcode7 setup?
> 
> Regards,
> Dave
> 
>> On Oct 31, 2017, at 8:53 AM, Jim Jagielski  wrote:
>> 
>> OK, I *think* I found it... it looks like it is a XML/xslt issue
>> where the 10.12 SDK, even though it is not used, the
>> XML libs from it are.
>> 
>> Downgrading from Xcode8 to Xcode7 looks to resolve that.
>> Build 4.1.3 using Xcode7 worked (no corrupt).
>> 
>> -
>> 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: Issue for 4.1.4 and MacOS

2017-10-31 Thread Jim Jagielski 
This is what I'm thinking... by using the system xml/xslt, instead of
bundling it, we are getting some weird interactions.

< LIBXML_CFLAGS='-I/usr/local/include/libxml2'
---
> LIBXML_CFLAGS='-I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/libxml2'
1289,1291c1326,1328
< LIBXML_LIBS='-L/usr/local/lib -lxml2 -lz -lpthread -liconv -lm'
< LIBXSLT_CFLAGS='-I/usr/local/include -I/usr/local/include/libxml2'
< LIBXSLT_LIBS='-L/usr/local/lib -lxslt -lxml2'
---
> LIBXML_LIBS='-L/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/lib
>  -lxml2 -lz -lpthread -licucore -lm'
> LIBXSLT_CFLAGS='-I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include
>  
> -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/libxml2'
> LIBXSLT_LIBS='-L/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/lib
>  -lxslt -lxml2 -lz -lpthread -licucore -lm'


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

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Dave Fisher 
Hi Jim,

Any use of XcodeLegacy in your Xcode7 setup?

Regards,
Dave

> On Oct 31, 2017, at 8:53 AM, Jim Jagielski  wrote:
> 
> OK, I *think* I found it... it looks like it is a XML/xslt issue
> where the 10.12 SDK, even though it is not used, the
> XML libs from it are.
> 
> Downgrading from Xcode8 to Xcode7 looks to resolve that.
> Build 4.1.3 using Xcode7 worked (no corrupt).
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 



signature.asc
Description: Message signed with OpenPGP

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Patricia Shanahan 
I bow to empirical facts, but I am still confused. There are several xml 
files in the .ods, most of which are written correctly. Why just the 
ones under 'Object 1'?


On 10/31/2017 8:53 AM, Jim Jagielski wrote:

OK, I *think* I found it... it looks like it is a XML/xslt issue
where the 10.12 SDK, even though it is not used, the
XML libs from it are.

Downgrading from Xcode8 to Xcode7 looks to resolve that.
Build 4.1.3 using Xcode7 worked (no corrupt).

-
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: Issue for 4.1.4 and MacOS

2017-10-31 Thread Jim Jagielski 
OK, I *think* I found it... it looks like it is a XML/xslt issue
where the 10.12 SDK, even though it is not used, the
XML libs from it are.

Downgrading from Xcode8 to Xcode7 looks to resolve that.
Build 4.1.3 using Xcode7 worked (no corrupt).

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

Re: Issue for 4.1.4 and MacOS

2017-10-31 Thread Jim Jagielski 
Looking over how 4.1.2 was built I will admit that I am
totally confused. According to the config.out file it was
built on an 8-core MacBook, running Mavericks (10.9) but
with an Xcode that supported the 10.10 SDK... which is
basically impossible. Xcode6, which is the 1st one
to support the 10.10 SDK does not RUN on Mavericks.
And Xcode5 does not provide the 10.10 SDK.

Anyway, I am playing around with installing Yosemite
(10.10) and Xcode6 on a VM.

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

Re: Issue for 4.1.4 and MacOS

2017-10-30 Thread Jim Jagielski 
Hmmm... the default memory allocator seems to have changed
between 4.1.2 and 4.1.4 from internal to system. Checking...

> On Oct 30, 2017, at 9:51 PM, Jim Jagielski  wrote:
> 
> That is what I am thinking... looking at the config.out
> diff between 4.1.2 and 4.1.4...
> 
>> On Oct 30, 2017, at 8:43 PM, Don Lewis  wrote:
>> 
>> On 30 Oct, Jim Jagielski wrote:
>>> So building 4.1.3 also results in the same behavior
>>> as 4.1.4... so it is almost assuredly a build issue.
>>> Assuming it is an SDK issue, I am trying to build
>>> w/ Xcode5... Will keep everyone posted.
>> 
>> It could also be different configuration settings for bundled vs. system
>> libraries.
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 


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

Re: Issue for 4.1.4 and MacOS

2017-10-30 Thread Jim Jagielski 
That is what I am thinking... looking at the config.out
diff between 4.1.2 and 4.1.4...

> On Oct 30, 2017, at 8:43 PM, Don Lewis  wrote:
> 
> On 30 Oct, Jim Jagielski wrote:
>> So building 4.1.3 also results in the same behavior
>> as 4.1.4... so it is almost assuredly a build issue.
>> Assuming it is an SDK issue, I am trying to build
>> w/ Xcode5... Will keep everyone posted.
> 
> It could also be different configuration settings for bundled vs. system
> libraries.
> 
> 
> -
> 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: Issue for 4.1.4 and MacOS

2017-10-30 Thread Don Lewis 
On 30 Oct, Jim Jagielski wrote:
> So building 4.1.3 also results in the same behavior
> as 4.1.4... so it is almost assuredly a build issue.
> Assuming it is an SDK issue, I am trying to build
> w/ Xcode5... Will keep everyone posted.

It could also be different configuration settings for bundled vs. system
libraries.


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

Re: Issue for 4.1.4 and MacOS

2017-10-30 Thread Jim Jagielski 
So building 4.1.3 also results in the same behavior
as 4.1.4... so it is almost assuredly a build issue.
Assuming it is an SDK issue, I am trying to build
w/ Xcode5... Will keep everyone posted.


> On Oct 30, 2017, at 4:29 PM, Jim Jagielski  wrote:
> 
> Building from AOO413 (tag) as we speak...
> 
> -
> 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: Issue for 4.1.4 and MacOS

2017-10-30 Thread Jim Jagielski 
Building from AOO413 (tag) as we speak...

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

Re: Issue for 4.1.4 and MacOS

2017-10-29 Thread Jim Jagielski 
Thx!

> On Oct 29, 2017, at 2:07 PM, Larry Gusaas  wrote:
> 
> On 2017-10-29, 8:05 AM Jim Jagielski wrote:
>>> On Oct 28, 2017, at 1:30 PM, Patricia Shanahan  wrote:
>>> 
>>> The original bug report said "This wasn't an issue of AOO 4.1.3, but is an 
>>> issue of AOO 4.1.4" so we are looking for something that changed.
>> Can someone download 4.1.3 for macOS and confirm that? I'm out-of-pocket
>> for a coupla days.
> 
> Downloaded 4.1.3. Inserted a graph in a spreadsheet worked. It was still 
> there when I reopened it after saving.
> 
> 
> -- 
> _
> 
> 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
> 


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

Re: Issue for 4.1.4 and MacOS

2017-10-29 Thread Larry Gusaas 

On 2017-10-29, 8:05 AM Jim Jagielski wrote:

On Oct 28, 2017, at 1:30 PM, Patricia Shanahan  wrote:

The original bug report said "This wasn't an issue of AOO 4.1.3, but is an issue of 
AOO 4.1.4" so we are looking for something that changed.

Can someone download 4.1.3 for macOS and confirm that? I'm out-of-pocket
for a coupla days.


Downloaded 4.1.3. Inserted a graph in a spreadsheet worked. It was still there when I reopened 
it after saving.



--
_

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: Issue for 4.1.4 and MacOS

2017-10-29 Thread Jim Jagielski 

> On Oct 28, 2017, at 1:30 PM, Patricia Shanahan  wrote:
> 
> The original bug report said "This wasn't an issue of AOO 4.1.3, but is an 
> issue of AOO 4.1.4" so we are looking for something that changed.
> 

Can someone download 4.1.3 for macOS and confirm that? I'm out-of-pocket
for a coupla days.


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

Re: Issue for 4.1.4 and MacOS

2017-10-29 Thread Jim Jagielski 
That is a good idea... Also, IIRC, we don't have any real record of
the build params used for 4.1.3 macOS. What's in there is what
I uploaded, but, as mentioned, I didn't build the 4.1.3 macOS release.

> On Oct 28, 2017, at 3:11 PM, Andrea Pescetti  wrote:
> 
> Dave Fisher wrote:
>> We ought to factor out the build tooling by comparing a build based on 4.1.3 
>> with the bug to rule out a tooling regression.
> 
> Very good suggestion. Building 4.1.3 on exactly the same system and with 
> exactly the same config used for 4.1.4 will tell us whether this is related 
> to the code or to the build options or the build machine.
> 
> Regards,
>  Andrea.
> 
> -
> 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: Issue for 4.1.4 and MacOS

2017-10-28 Thread Patricia Shanahan 

On 10/28/2017 12:11 PM, Andrea Pescetti wrote:

Dave Fisher wrote:
We ought to factor out the build tooling by comparing a build based on 
4.1.3 with the bug to rule out a tooling regression.


Very good suggestion. Building 4.1.3 on exactly the same system and with 
exactly the same config used for 4.1.4 will tell us whether this is 
related to the code or to the build options or the build machine.


+1

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

Re: Issue for 4.1.4 and MacOS

2017-10-28 Thread Dave Fisher 

> On Oct 28, 2017, at 12:11 PM, Andrea Pescetti  wrote:
> 
> Dave Fisher wrote:
>> We ought to factor out the build tooling by comparing a build based on 4.1.3 
>> with the bug to rule out a tooling regression.
> 
> Very good suggestion. Building 4.1.3 on exactly the same system and with 
> exactly the same config used for 4.1.4 will tell us whether this is related 
> to the code or to the build options or the build machine.

A reminder from the 4.1.x is frozen and no updates thread. Macs builds are not 
done on VMs.

Regards,
Dave

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



signature.asc
Description: Message signed with OpenPGP

Re: Issue for 4.1.4 and MacOS

2017-10-28 Thread Andrea Pescetti 

Dave Fisher wrote:

We ought to factor out the build tooling by comparing a build based on 4.1.3 
with the bug to rule out a tooling regression.


Very good suggestion. Building 4.1.3 on exactly the same system and with 
exactly the same config used for 4.1.4 will tell us whether this is 
related to the code or to the build options or the build machine.


Regards,
  Andrea.

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

Re: Issue for 4.1.4 and MacOS

2017-10-28 Thread Dave Fisher 
Hi -

> On Oct 28, 2017, at 10:30 AM, Patricia Shanahan  wrote:
> 
> The original bug report said "This wasn't an issue of AOO 4.1.3, but is an 
> issue of AOO 4.1.4" so we are looking for something that changed.
> 
> I would have assumed that the same libraries would be used in writing the 
> main content.xml and the one in the 'Object 1' subdirectory. The main 
> content.xml is fine. The one in the 'Object 1' subdirectory is empty, so I am 
> confused and puzzled.
> 
> Can someone with Mac building and testing capability do the search for the 
> change that made it fail? In another project, I used binary search on the SVN 
> revision number to locate exactly when a regression appeared.

I think that only Jim can build 4.1.4 on Mac. I am blocked waiting for a friend 
to give me a Mac JDK7. Or, I’ll apply Damjan’s javadoc JDK8 patches and see.

Keep in mind that 4.1.3 was built over a year ago. AFIAK it was not built by 
Jim. Apple has updated Xcode and switched MacOSX to macOS since then. We ought 
to factor out the build tooling by comparing a build based on 4.1.3 with the 
bug to rule out a tooling regression.

> 
> (For anyone who is not already familiar with the structure of the files, it 
> may be useful to look at an unzipped .ods file.)

Regards,
Dave


> 
> On 10/28/2017 10:01 AM, Dave Fisher wrote:
>> Hi -
>> I’ve attached a diff of the differences between 4.1.3 and 4.1.4. I hope that 
>> this helps. If I had a working build I would be looking into undoing a 
>> change at a time to see which had the impact on the save of links on Mac.
>> I am also suspicious of tooling and what caused the link xml to be created, 
>> but empty. Is there a system library involved and an impact due to fixes and 
>> updates in Xcode? If aoo413 is built on the same tooling as aoo414 is it 
>> broken too?
>> Regards,
>> Dave
>>> On Oct 28, 2017, at 5:47 AM, Patricia Shanahan  wrote:
>>> 
>>> I at first thought this might be a load problem. It is now clear it is a 
>>> case of file corruption on save, only on Mac.
>>> 
>>> Unfortunately, that means I am out of ideas, other than checking that your 
>>> original test has been done on the file save. The fixes I know about are 
>>> intended to affect file loading, not saving.
>>> 
>>> On 10/26/2017 5:45 AM, Jim Jagielski wrote:
 Yeah, I kinda figured out what your hypothesis was... I'll need
 to think about this some more.
> On Oct 26, 2017, at 8:34 AM, Patricia Shanahan  wrote:
> 
> OK, forget that hypothesis. You have even done the next test I would have 
> asked for if the line 288 breakpoint was not reached.
> 
> I'll need to think up a new hypothesis. I'm planning to go groom a couple 
> of horses this morning, but I'll work on this in the afternoon.
> 
> On 10/26/2017 5:01 AM, Jim Jagielski wrote:
>> I set breakpoints on both:
>>(lldb) breakpoint set --file main/sfx2/source/appl/linkmgr2.cxx 
>> --line 288
>>(lldb) breakpoint set -n LinkManager::GetUserAllowsLinkUpdate
>> Breakpoint 4: where = 
>> libsfx.dylib`sfx2::LinkManager::GetUserAllowsLinkUpdate(Window*), 
>> address = 0x00010070a260
>> and when opening up the corrupted file, neither breakpoint
>> was reached. :/
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
 -
 To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: dev-h...@openoffice.apache.org
>>> 
>>> -
>>> 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
> 



signature.asc
Description: Message signed with OpenPGP

Re: Issue for 4.1.4 and MacOS

2017-10-28 Thread Patricia Shanahan 
The original bug report said "This wasn't an issue of AOO 4.1.3, but is 
an issue of AOO 4.1.4" so we are looking for something that changed.


I would have assumed that the same libraries would be used in writing 
the main content.xml and the one in the 'Object 1' subdirectory. The 
main content.xml is fine. The one in the 'Object 1' subdirectory is 
empty, so I am confused and puzzled.


Can someone with Mac building and testing capability do the search for 
the change that made it fail? In another project, I used binary search 
on the SVN revision number to locate exactly when a regression appeared.


(For anyone who is not already familiar with the structure of the files, 
it may be useful to look at an unzipped .ods file.)


On 10/28/2017 10:01 AM, Dave Fisher wrote:

Hi -

I’ve attached a diff of the differences between 4.1.3 and 4.1.4. I hope that 
this helps. If I had a working build I would be looking into undoing a change 
at a time to see which had the impact on the save of links on Mac.

I am also suspicious of tooling and what caused the link xml to be created, but 
empty. Is there a system library involved and an impact due to fixes and 
updates in Xcode? If aoo413 is built on the same tooling as aoo414 is it broken 
too?

Regards,
Dave


On Oct 28, 2017, at 5:47 AM, Patricia Shanahan  wrote:

I at first thought this might be a load problem. It is now clear it is a case 
of file corruption on save, only on Mac.

Unfortunately, that means I am out of ideas, other than checking that your 
original test has been done on the file save. The fixes I know about are 
intended to affect file loading, not saving.

On 10/26/2017 5:45 AM, Jim Jagielski wrote:

Yeah, I kinda figured out what your hypothesis was... I'll need
to think about this some more.

On Oct 26, 2017, at 8:34 AM, Patricia Shanahan  wrote:

OK, forget that hypothesis. You have even done the next test I would have asked 
for if the line 288 breakpoint was not reached.

I'll need to think up a new hypothesis. I'm planning to go groom a couple of 
horses this morning, but I'll work on this in the afternoon.

On 10/26/2017 5:01 AM, Jim Jagielski wrote:

I set breakpoints on both:
(lldb) breakpoint set --file main/sfx2/source/appl/linkmgr2.cxx --line 288
(lldb) breakpoint set -n LinkManager::GetUserAllowsLinkUpdate
Breakpoint 4: where = 
libsfx.dylib`sfx2::LinkManager::GetUserAllowsLinkUpdate(Window*), address = 
0x00010070a260
and when opening up the corrupted file, neither breakpoint
was reached. :/
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org


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


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


-
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: Issue for 4.1.4 and MacOS

2017-10-28 Thread Dave Fisher 
Hi -

I’ve attached a diff of the differences between 4.1.3 and 4.1.4. I hope that 
this helps. If I had a working build I would be looking into undoing a change 
at a time to see which had the impact on the save of links on Mac.

I am also suspicious of tooling and what caused the link xml to be created, but 
empty. Is there a system library involved and an impact due to fixes and 
updates in Xcode? If aoo413 is built on the same tooling as aoo414 is it broken 
too?

Regards,
Dave

> On Oct 28, 2017, at 5:47 AM, Patricia Shanahan  wrote:
> 
> I at first thought this might be a load problem. It is now clear it is a case 
> of file corruption on save, only on Mac.
> 
> Unfortunately, that means I am out of ideas, other than checking that your 
> original test has been done on the file save. The fixes I know about are 
> intended to affect file loading, not saving.
> 
> On 10/26/2017 5:45 AM, Jim Jagielski wrote:
>> Yeah, I kinda figured out what your hypothesis was... I'll need
>> to think about this some more.
>>> On Oct 26, 2017, at 8:34 AM, Patricia Shanahan  wrote:
>>> 
>>> OK, forget that hypothesis. You have even done the next test I would have 
>>> asked for if the line 288 breakpoint was not reached.
>>> 
>>> I'll need to think up a new hypothesis. I'm planning to go groom a couple 
>>> of horses this morning, but I'll work on this in the afternoon.
>>> 
>>> On 10/26/2017 5:01 AM, Jim Jagielski wrote:
 I set breakpoints on both:
(lldb) breakpoint set --file main/sfx2/source/appl/linkmgr2.cxx --line 
 288
(lldb) breakpoint set -n LinkManager::GetUserAllowsLinkUpdate
 Breakpoint 4: where = 
 libsfx.dylib`sfx2::LinkManager::GetUserAllowsLinkUpdate(Window*), address 
 = 0x00010070a260
 and when opening up the corrupted file, neither breakpoint
 was reached. :/
 -
 To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: dev-h...@openoffice.apache.org
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 



signature.asc
Description: Message signed with OpenPGP

Re: Issue for 4.1.4 and MacOS

2017-10-28 Thread Patricia Shanahan 
I at first thought this might be a load problem. It is now clear it is a 
case of file corruption on save, only on Mac.


Unfortunately, that means I am out of ideas, other than checking that 
your original test has been done on the file save. The fixes I know 
about are intended to affect file loading, not saving.


On 10/26/2017 5:45 AM, Jim Jagielski wrote:

Yeah, I kinda figured out what your hypothesis was... I'll need
to think about this some more.

On Oct 26, 2017, at 8:34 AM, Patricia Shanahan  wrote:

OK, forget that hypothesis. You have even done the next test I would have asked 
for if the line 288 breakpoint was not reached.

I'll need to think up a new hypothesis. I'm planning to go groom a couple of 
horses this morning, but I'll work on this in the afternoon.

On 10/26/2017 5:01 AM, Jim Jagielski wrote:

I set breakpoints on both:
(lldb) breakpoint set --file main/sfx2/source/appl/linkmgr2.cxx --line 288
(lldb) breakpoint set -n LinkManager::GetUserAllowsLinkUpdate
Breakpoint 4: where = 
libsfx.dylib`sfx2::LinkManager::GetUserAllowsLinkUpdate(Window*), address = 
0x00010070a260
and when opening up the corrupted file, neither breakpoint
was reached. :/
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org


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




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



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

Re: Issue for 4.1.4 and MacOS

2017-10-26 Thread Jim Jagielski 
Yeah, I kinda figured out what your hypothesis was... I'll need
to think about this some more.
> On Oct 26, 2017, at 8:34 AM, Patricia Shanahan  wrote:
> 
> OK, forget that hypothesis. You have even done the next test I would have 
> asked for if the line 288 breakpoint was not reached.
> 
> I'll need to think up a new hypothesis. I'm planning to go groom a couple of 
> horses this morning, but I'll work on this in the afternoon.
> 
> On 10/26/2017 5:01 AM, Jim Jagielski wrote:
>> I set breakpoints on both:
>>(lldb) breakpoint set --file main/sfx2/source/appl/linkmgr2.cxx --line 288
>>(lldb) breakpoint set -n LinkManager::GetUserAllowsLinkUpdate
>> Breakpoint 4: where = 
>> libsfx.dylib`sfx2::LinkManager::GetUserAllowsLinkUpdate(Window*), address = 
>> 0x00010070a260
>> and when opening up the corrupted file, neither breakpoint
>> was reached. :/
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 


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

Re: Issue for 4.1.4 and MacOS

2017-10-26 Thread Patricia Shanahan 
OK, forget that hypothesis. You have even done the next test I would 
have asked for if the line 288 breakpoint was not reached.


I'll need to think up a new hypothesis. I'm planning to go groom a 
couple of horses this morning, but I'll work on this in the afternoon.


On 10/26/2017 5:01 AM, Jim Jagielski wrote:

I set breakpoints on both:

(lldb) breakpoint set --file main/sfx2/source/appl/linkmgr2.cxx --line 288
(lldb) breakpoint set -n LinkManager::GetUserAllowsLinkUpdate
Breakpoint 4: where = 
libsfx.dylib`sfx2::LinkManager::GetUserAllowsLinkUpdate(Window*), address = 
0x00010070a260

and when opening up the corrupted file, neither breakpoint
was reached. :/
-
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: Issue for 4.1.4 and MacOS

2017-10-26 Thread Jim Jagielski 
I set breakpoints on both:

   (lldb) breakpoint set --file main/sfx2/source/appl/linkmgr2.cxx --line 288
   (lldb) breakpoint set -n LinkManager::GetUserAllowsLinkUpdate
Breakpoint 4: where = 
libsfx.dylib`sfx2::LinkManager::GetUserAllowsLinkUpdate(Window*), address = 
0x00010070a260

and when opening up the corrupted file, neither breakpoint
was reached. :/
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Issue for 4.1.4 and MacOS

2017-10-25 Thread Jim Jagielski 
I did a quick rebuild but with the '--with-alloc=system'
line removed. No change in behavior.

Will try to track down the question Patricia
raised in the Bugz report.

> On Oct 24, 2017, at 11:36 AM, Jim Jagielski  wrote:
> 
> Will also follow up on the Bugz report, but one change between 4.1.3
> and 4.1.4 regarding macOS *builds* is that 4.1.4 uses '--with-alloc=system'
> but the 4.1.3 build does not.
> 
> I will create a macOS build of AOO414 but adjust the configure script
> to not include that and see what effect that may have.
> 
> 
>> On Oct 24, 2017, at 8:52 AM, Patricia Shanahan  wrote:
>> 
>> 
>> 
>> On 10/24/2017 5:49 AM, Rory O'Farrell wrote:
>>> On Tue, 24 Oct 2017 05:35:34 -0700
>>> Patricia Shanahan  wrote:
 Since the issue appeared in 4.1.4, and involves document links, it might
 be related to my changes.
 
 I do not have a Mac, and do not have any Mac debug experience.
 
 How do people think we should proceed with this? Is there a Mac
 developer who can work with me on it?
>>> I don't have access to a Mac, so cannot help there.
>>> I make one suggestion - a guess - based on loss of images in Writer (and 
>>> Calc/Impress? I'm not certain of this) on other operating systems.
>>> John_Ha has done some work on loss on images in Writer and relates it to 
>>> sometimes occurring at the time of OO saving an Autorecovery image.  See 
>>> his note at
>>> https://forum.openoffice.org/en/forum/viewtopic.php?f=71=86682
>>> As this new bug is occurring at Save time, might it be a manifestation of 
>>> the same problem?
>> 
>> I don't think there are any changes that relate to that bug between 4.1.3 
>> and 4.1.4. This seems to be solid and repeatable with 4.1.4, and not 
>> happening at all with 4.1.3.
>> 
>> -
>> 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: Issue for 4.1.4 and MacOS

2017-10-24 Thread Dave Fisher 
Hi -

I’ve been trying to get Mac builds going today. I am trying right now with 
trunk. I’m still stuck on configure and have an XCodeLegacy question out to Jim 
on another thread.

checking which jpeg to use... internal
checking which expat to use... internal
checking which libxslt to use... external
checking for xsltproc... /usr/bin/xsltproc
checking which libxml to use... external
checking checking SDK compatibility with OSX 10.9... configure: error: No SDK 
with OSX 10.9 compatibility found
../build_aooreleases.sh: line 153: ./bootstrap: No such file or directory

I have time to try tomorrow.

Regards,
Dave


> On Oct 24, 2017, at 4:06 PM, Patricia Shanahan  wrote:
> 
> Even if you can't get a Mac build going in time to help with this bug, we 
> obviously need more people building and testing on Mac.
> 
> On 10/24/2017 4:01 PM, Peter kovacs wrote:
>> I do own a Mac. But its me. ;) I hope that maybe with the actual guide I can 
>> build. So far I failed to install the old code on it. If I can manage to 
>> build, I could dig into the problem. I have a long weekend upcoming. Hope I 
>> can allocate time.
>> Am 24. Oktober 2017 17:36:16 MESZ schrieb Jim Jagielski :
>>> Will also follow up on the Bugz report, but one change between 4.1.3
>>> and 4.1.4 regarding macOS *builds* is that 4.1.4 uses
>>> '--with-alloc=system'
>>> but the 4.1.3 build does not.
>>> 
>>> I will create a macOS build of AOO414 but adjust the configure script
>>> to not include that and see what effect that may have.
>>> 
>>> 
 On Oct 24, 2017, at 8:52 AM, Patricia Shanahan  wrote:
 
 
 
 On 10/24/2017 5:49 AM, Rory O'Farrell wrote:
> On Tue, 24 Oct 2017 05:35:34 -0700
> Patricia Shanahan  wrote:
>> Since the issue appeared in 4.1.4, and involves document links, it
>>> might
>> be related to my changes.
>> 
>> I do not have a Mac, and do not have any Mac debug experience.
>> 
>> How do people think we should proceed with this? Is there a Mac
>> developer who can work with me on it?
> I don't have access to a Mac, so cannot help there.
> I make one suggestion - a guess - based on loss of images in Writer
>>> (and Calc/Impress? I'm not certain of this) on other operating systems.
> John_Ha has done some work on loss on images in Writer and relates
>>> it to sometimes occurring at the time of OO saving an Autorecovery
>>> image.  See his note at
> https://forum.openoffice.org/en/forum/viewtopic.php?f=71=86682
> As this new bug is occurring at Save time, might it be a
>>> manifestation of the same problem?
 
 I don't think there are any changes that relate to that bug between
>>> 4.1.3 and 4.1.4. This seems to be solid and repeatable with 4.1.4, and
>>> not happening at all with 4.1.3.
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> 
 For additional commands, e-mail: dev-h...@openoffice.apache.org
>>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 



signature.asc
Description: Message signed with OpenPGP

Re: Issue for 4.1.4 and MacOS

2017-10-24 Thread Patricia Shanahan 
Even if you can't get a Mac build going in time to help with this bug, 
we obviously need more people building and testing on Mac.


On 10/24/2017 4:01 PM, Peter kovacs wrote:

I do own a Mac. But its me. ;) I hope that maybe with the actual guide I can 
build. So far I failed to install the old code on it. If I can manage to build, 
I could dig into the problem. I have a long weekend upcoming. Hope I can 
allocate time.

Am 24. Oktober 2017 17:36:16 MESZ schrieb Jim Jagielski :

Will also follow up on the Bugz report, but one change between 4.1.3
and 4.1.4 regarding macOS *builds* is that 4.1.4 uses
'--with-alloc=system'
but the 4.1.3 build does not.

I will create a macOS build of AOO414 but adjust the configure script
to not include that and see what effect that may have.



On Oct 24, 2017, at 8:52 AM, Patricia Shanahan  wrote:



On 10/24/2017 5:49 AM, Rory O'Farrell wrote:

On Tue, 24 Oct 2017 05:35:34 -0700
Patricia Shanahan  wrote:

Since the issue appeared in 4.1.4, and involves document links, it

might

be related to my changes.

I do not have a Mac, and do not have any Mac debug experience.

How do people think we should proceed with this? Is there a Mac
developer who can work with me on it?

I don't have access to a Mac, so cannot help there.
I make one suggestion - a guess - based on loss of images in Writer

(and Calc/Impress? I'm not certain of this) on other operating systems.

John_Ha has done some work on loss on images in Writer and relates

it to sometimes occurring at the time of OO saving an Autorecovery
image.  See his note at

https://forum.openoffice.org/en/forum/viewtopic.php?f=71=86682
As this new bug is occurring at Save time, might it be a

manifestation of the same problem?


I don't think there are any changes that relate to that bug between

4.1.3 and 4.1.4. This seems to be solid and repeatable with 4.1.4, and
not happening at all with 4.1.3.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org



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




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



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

Re: Issue for 4.1.4 and MacOS

2017-10-24 Thread Peter kovacs 
I do own a Mac. But its me. ;) I hope that maybe with the actual guide I can 
build. So far I failed to install the old code on it. If I can manage to build, 
I could dig into the problem. I have a long weekend upcoming. Hope I can 
allocate time.

Am 24. Oktober 2017 17:36:16 MESZ schrieb Jim Jagielski :
>Will also follow up on the Bugz report, but one change between 4.1.3
>and 4.1.4 regarding macOS *builds* is that 4.1.4 uses
>'--with-alloc=system'
>but the 4.1.3 build does not.
>
>I will create a macOS build of AOO414 but adjust the configure script
>to not include that and see what effect that may have.
>
>
>> On Oct 24, 2017, at 8:52 AM, Patricia Shanahan  wrote:
>> 
>> 
>> 
>> On 10/24/2017 5:49 AM, Rory O'Farrell wrote:
>>> On Tue, 24 Oct 2017 05:35:34 -0700
>>> Patricia Shanahan  wrote:
 Since the issue appeared in 4.1.4, and involves document links, it
>might
 be related to my changes.
 
 I do not have a Mac, and do not have any Mac debug experience.
 
 How do people think we should proceed with this? Is there a Mac
 developer who can work with me on it?
>>> I don't have access to a Mac, so cannot help there.
>>> I make one suggestion - a guess - based on loss of images in Writer
>(and Calc/Impress? I'm not certain of this) on other operating systems.
>>> John_Ha has done some work on loss on images in Writer and relates
>it to sometimes occurring at the time of OO saving an Autorecovery
>image.  See his note at
>>> https://forum.openoffice.org/en/forum/viewtopic.php?f=71=86682
>>> As this new bug is occurring at Save time, might it be a
>manifestation of the same problem?
>> 
>> I don't think there are any changes that relate to that bug between
>4.1.3 and 4.1.4. This seems to be solid and repeatable with 4.1.4, and
>not happening at all with 4.1.3.
>> 
>> -
>> 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: Issue for 4.1.4 and MacOS

2017-10-24 Thread Jim Jagielski 
Will also follow up on the Bugz report, but one change between 4.1.3
and 4.1.4 regarding macOS *builds* is that 4.1.4 uses '--with-alloc=system'
but the 4.1.3 build does not.

I will create a macOS build of AOO414 but adjust the configure script
to not include that and see what effect that may have.


> On Oct 24, 2017, at 8:52 AM, Patricia Shanahan  wrote:
> 
> 
> 
> On 10/24/2017 5:49 AM, Rory O'Farrell wrote:
>> On Tue, 24 Oct 2017 05:35:34 -0700
>> Patricia Shanahan  wrote:
>>> Since the issue appeared in 4.1.4, and involves document links, it might
>>> be related to my changes.
>>> 
>>> I do not have a Mac, and do not have any Mac debug experience.
>>> 
>>> How do people think we should proceed with this? Is there a Mac
>>> developer who can work with me on it?
>> I don't have access to a Mac, so cannot help there.
>> I make one suggestion - a guess - based on loss of images in Writer (and 
>> Calc/Impress? I'm not certain of this) on other operating systems.
>> John_Ha has done some work on loss on images in Writer and relates it to 
>> sometimes occurring at the time of OO saving an Autorecovery image.  See his 
>> note at
>> https://forum.openoffice.org/en/forum/viewtopic.php?f=71=86682
>> As this new bug is occurring at Save time, might it be a manifestation of 
>> the same problem?
> 
> I don't think there are any changes that relate to that bug between 4.1.3 and 
> 4.1.4. This seems to be solid and repeatable with 4.1.4, and not happening at 
> all with 4.1.3.
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org 
> 
> For additional commands, e-mail: dev-h...@openoffice.apache.org 
>

Re: Issue for 4.1.4 and MacOS

2017-10-24 Thread Patricia Shanahan 



On 10/24/2017 5:49 AM, Rory O'Farrell wrote:

On Tue, 24 Oct 2017 05:35:34 -0700
Patricia Shanahan  wrote:


Since the issue appeared in 4.1.4, and involves document links, it might
be related to my changes.

I do not have a Mac, and do not have any Mac debug experience.

How do people think we should proceed with this? Is there a Mac
developer who can work with me on it?


I don't have access to a Mac, so cannot help there.

I make one suggestion - a guess - based on loss of images in Writer (and 
Calc/Impress? I'm not certain of this) on other operating systems.

John_Ha has done some work on loss on images in Writer and relates it to 
sometimes occurring at the time of OO saving an Autorecovery image.  See his 
note at
https://forum.openoffice.org/en/forum/viewtopic.php?f=71=86682

As this new bug is occurring at Save time, might it be a manifestation of the 
same problem?



I don't think there are any changes that relate to that bug between 
4.1.3 and 4.1.4. This seems to be solid and repeatable with 4.1.4, and 
not happening at all with 4.1.3.


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

Re: Issue for 4.1.4 and MacOS

2017-10-24 Thread Rory O'Farrell 
On Tue, 24 Oct 2017 05:35:34 -0700
Patricia Shanahan  wrote:

> Since the issue appeared in 4.1.4, and involves document links, it might 
> be related to my changes.
> 
> I do not have a Mac, and do not have any Mac debug experience.
> 
> How do people think we should proceed with this? Is there a Mac 
> developer who can work with me on it?

I don't have access to a Mac, so cannot help there.  

I make one suggestion - a guess - based on loss of images in Writer (and 
Calc/Impress? I'm not certain of this) on other operating systems.  

John_Ha has done some work on loss on images in Writer and relates it to 
sometimes occurring at the time of OO saving an Autorecovery image.  See his 
note at
https://forum.openoffice.org/en/forum/viewtopic.php?f=71=86682

As this new bug is occurring at Save time, might it be a manifestation of the 
same problem?

Rory


> 
> On 10/24/2017 4:40 AM, Larry Gusaas wrote:
> > On 2017-10-24, 4:19 AM FR web forum wrote:
> > 
> >> Please have a look on:
> >> https://bz.apache.org/ooo/show_bug.cgi?id=127568
> > 
> > I tested and confirm the problem. Posted my result on the bug report.
> > 
> > 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
> 


-- 
Rory O'Farrell 

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

Re: Issue for 4.1.4 and MacOS

2017-10-24 Thread Patricia Shanahan 
Since the issue appeared in 4.1.4, and involves document links, it might 
be related to my changes.


I do not have a Mac, and do not have any Mac debug experience.

How do people think we should proceed with this? Is there a Mac 
developer who can work with me on it?


On 10/24/2017 4:40 AM, Larry Gusaas wrote:

On 2017-10-24, 4:19 AM FR web forum wrote:


Please have a look on:
https://bz.apache.org/ooo/show_bug.cgi?id=127568


I tested and confirm the problem. Posted my result on the bug report.




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

Re: Issue for 4.1.4 and MacOS

2017-10-24 Thread Larry Gusaas 

On 2017-10-24, 4:19 AM FR web forum wrote:


Please have a look on:
https://bz.apache.org/ooo/show_bug.cgi?id=127568


I tested and confirm the problem. Posted my result on the bug report.


--
_

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

Issue for 4.1.4 and MacOS

2017-10-24 Thread FR web forum 
Please have a look on:
https://bz.apache.org/ooo/show_bug.cgi?id=127568

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