Issue for 4.1.4 and MacOS

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

Re: Issue for 4.1.4 and MacOS

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 <[hidden email]> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>


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

Reply | Threaded
Open this post in threaded view
|

Re: Issue for 4.1.4 and MacOS

Jim Jagielski
In reply to this post by Patricia Shanahan

> On Oct 28, 2017, at 1:30 PM, Patricia Shanahan <[hidden email]> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Issue for 4.1.4 and MacOS

Larry Gusaas-4
On 2017-10-29, 8:05 AM Jim Jagielski wrote:
>> On Oct 28, 2017, at 1:30 PM, Patricia Shanahan <[hidden email]> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Issue for 4.1.4 and MacOS

Jim Jagielski
Thx!

> On Oct 29, 2017, at 2:07 PM, Larry Gusaas <[hidden email]> wrote:
>
> On 2017-10-29, 8:05 AM Jim Jagielski wrote:
>>> On Oct 28, 2017, at 1:30 PM, Patricia Shanahan <[hidden email]> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>


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

Reply | Threaded
Open this post in threaded view
|

Re: Issue for 4.1.4 and MacOS

Jim Jagielski
Building from AOO413 (tag) as we speak...

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

Reply | Threaded
Open this post in threaded view
|

Re: Issue for 4.1.4 and MacOS

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 <[hidden email]> wrote:
>
> Building from AOO413 (tag) as we speak...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


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

Reply | Threaded
Open this post in threaded view
|

Re: Issue for 4.1.4 and MacOS

Don Lewis-2
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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Issue for 4.1.4 and MacOS

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 <[hidden email]> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>


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

Reply | Threaded
Open this post in threaded view
|

Re: Issue for 4.1.4 and MacOS

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 <[hidden email]> 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 <[hidden email]> 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: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


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

Reply | Threaded
Open this post in threaded view
|

Re: Issue for 4.1.4 and MacOS

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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Issue for 4.1.4 and MacOS

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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Issue for 4.1.4 and MacOS

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: [hidden email]
> For additional commands, e-mail: [hidden email]
>

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

Reply | Threaded
Open this post in threaded view
|

Re: Issue for 4.1.4 and MacOS

Dave Fisher
In reply to this post by Jim Jagielski
Hi Jim,

Any use of XcodeLegacy in your Xcode7 setup?

Regards,
Dave

> On Oct 31, 2017, at 8:53 AM, Jim Jagielski <[hidden email]> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>


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

Re: Issue for 4.1.4 and MacOS

Jim Jagielski
In reply to this post by Patricia Shanahan
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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Issue for 4.1.4 and MacOS

Jim Jagielski
In reply to this post by Dave Fisher
Nope. This is virgin Xcode7

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

> On Oct 31, 2017, at 12:02 PM, Dave Fisher <[hidden email]> wrote:
>
> Hi Jim,
>
> Any use of XcodeLegacy in your Xcode7 setup?
>
> Regards,
> Dave
>
>> On Oct 31, 2017, at 8:53 AM, Jim Jagielski <[hidden email]> 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: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>


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

Reply | Threaded
Open this post in threaded view
|

Re: Issue for 4.1.4 and MacOS

Jim Jagielski
In reply to this post by Jim Jagielski
Question: Assuming we have "correction" builds available,
what do we do? Simply replace the online version with
these?

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

Reply | Threaded
Open this post in threaded view
|

Re: Issue for 4.1.4 and MacOS

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 <[hidden email]> wrote:
>
> Question: Assuming we have "correction" builds available,
> what do we do? Simply replace the online version with
> these?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


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

Re: Issue for 4.1.4 and MacOS

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 <[hidden email]> wrote:
>>
>> Question: Assuming we have "correction" builds available,
>> what do we do? Simply replace the online version with
>> these?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>

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

Reply | Threaded
Open this post in threaded view
|

Re: Issue for 4.1.4 and MacOS

Matthias Seidel
In reply to this post by Dave Fisher
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 <[hidden email]> wrote:
>>
>> Question: Assuming we have "correction" builds available,
>> what do we do? Simply replace the online version with
>> these?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>


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

Re: Issue for 4.1.4 and MacOS

Dave Fisher
In reply to this post by Patricia Shanahan

> On Oct 31, 2017, at 9:51 AM, Patricia Shanahan <[hidden email]> 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 <[hidden email]> wrote:
>>>
>>> Question: Assuming we have "correction" builds available,
>>> what do we do? Simply replace the online version with
>>> these?
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


signature.asc (817 bytes) Download Attachment
12345