Re: 4.2.0 release blockers

[Matthias Seidel]

Hi Jim,

Am 05.10.23 um 21:42 schrieb Jim Jagielski:



On Oct 5, 2023, at 3:20 PM, Jim Jagielski  wrote:




On Oct 4, 2023, at 2:12 PM, Damjan Jovanovic mailto:dam...@apache.org>> wrote:

On Wed, Oct 4, 2023 at 4:52 PM Jim Jagielski mailto:j...@jagunet.com> 
> wrote:




On Oct 1, 2023, at 7:44 AM, Damjan Jovanovic  wrote:

127154 and 127966 need to be looked at by a Mac developer.


Those look pretty old. I should create a quick macOS 4.2.0 dev build for
testing



Thank you Jim. While you are here, can you please look at bug
https://bz.apache.org/ooo/show_bug.cgi?id=127861 where one of your commits
created a regression?

Regards
Damjan

It does look like it's a back port. It's possible that it's not needed in 4.2.0

My suggestion is we revert the back port in AOO42X and Trunk... Comments?


I think these commits are there "for a reason".

Could it be that they are a backport of

https://github.com/apache/openoffice/commit/cf914f842e0d4f6546c2c6edefa5660411c62b42

and

https://github.com/apache/openoffice/commit/611fcdab0900c77ff92ad579f9da6d63d2aca818

?

And thinking about it, this is an annoying issue, but I don't think it 
is a real Release Blocker.


Regards,

   Matthias



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: 4.2.0 release blockers

[Jim Jagielski]

> On Oct 5, 2023, at 3:20 PM, Jim Jagielski  wrote:
> 
> 
> 
>> On Oct 4, 2023, at 2:12 PM, Damjan Jovanovic > > wrote:
>> 
>> On Wed, Oct 4, 2023 at 4:52 PM Jim Jagielski >  > wrote:
>> 
>>> 
>>> 
 On Oct 1, 2023, at 7:44 AM, Damjan Jovanovic  wrote:
 
 127154 and 127966 need to be looked at by a Mac developer.
 
>>> 
>>> Those look pretty old. I should create a quick macOS 4.2.0 dev build for
>>> testing
>>> 
>>> 
>> Thank you Jim. While you are here, can you please look at bug
>> https://bz.apache.org/ooo/show_bug.cgi?id=127861 where one of your commits
>> created a regression?
>> 
>> Regards
>> Damjan
> 
> It does look like it's a back port. It's possible that it's not needed in 
> 4.2.0

My suggestion is we revert the back port in AOO42X and Trunk... Comments?

Re: 4.2.0 release blockers

[Jim Jagielski]

> On Oct 4, 2023, at 2:12 PM, Damjan Jovanovic  wrote:
> 
> On Wed, Oct 4, 2023 at 4:52 PM Jim Jagielski  > wrote:
> 
>> 
>> 
>>> On Oct 1, 2023, at 7:44 AM, Damjan Jovanovic  wrote:
>>> 
>>> 127154 and 127966 need to be looked at by a Mac developer.
>>> 
>> 
>> Those look pretty old. I should create a quick macOS 4.2.0 dev build for
>> testing
>> 
>> 
> Thank you Jim. While you are here, can you please look at bug
> https://bz.apache.org/ooo/show_bug.cgi?id=127861 where one of your commits
> created a regression?
> 
> Regards
> Damjan

It does look like it's a back port. It's possible that it's not needed in 4.2.0

Re: 4.2.0 release blockers

[Arrigo Marchiori]

Hello Dave, All,

On Sun, Oct 01, 2023 at 09:11:14PM -0700, Dave Fisher wrote:

> > On Oct 1, 2023, at 12:04 PM, Peter Kovacs  wrote:
> > 
> >> Am 01.10.23 um 13:44 schrieb Damjan Jovanovic:
> >> Hi
> >> 
> >> So for 4.2.0, presumably we need to fix the bugs with 4.2.0_release_blocker
> >> flags:
> >> https://bz.apache.org/ooo/buglist.cgi?f1=flagtypes.name_id=251353=substring_format=advanced=---=4.2.0_release_blocker
> >> of which there is 6:
> >> 
> >> For 127731, I found the problem yesterday (Microsoft's damned side-by-side
> >> assemblies), and am building AOO with my fix now, if all goes well it
> >> should be committed later today or tomorrow.
> >> 127783 needs testing on several platforms to isolate the bug, now that
> >> Arrigo's ppt branch was merged.
> >> 127861 will probably need bisecting.
> >> 128094 is probably a packaging bug and needs testing and might need
> >> bisecting.
> > sadly I suck with c++ debuggers.
> >> 127154 and 127966 need to be looked at by a Mac developer.
> > 
> > please note we have 2 project MacMinis. A intel and a m1 based system.
> > 
> > they are based in the US, the plan has been to set them up as build bots. 
> > (still on this topic)
> > 
> > However in meanwhile i found out that you are not able to build on the new 
> > processors for intel.
> 
> On that machine we should see if we can build for the new chips …
> 
> When you access those Macs do you get a desktop or is it ssh?

Both. The desktop connection is via VNC.

> Is there a step by step how to build AOO on these? Knowing the steps
> would allow someone who is interested to try on their own Mac.
> 
> Remind what version of macOS should be the minimum? My 11 year old iMac can 
> only be on 10.11.6 (I’m not saying I can build on it, but I could test a 
> build). Our minimum for 4.1.x is currently 10.7.
> 
> > 
> > But the intel one is available to all who do not own a apple device but 
> > need to test or develop something for AOO.
> 
> If multiple will be trying on these we’ll need to agree on the environment 
> and make sure they are setup.

I worked on the oldest one for some time. I tested my commits on that
machine.

I can build AOO41X there, but not trunk or AOO42X. It should be set up
already, and the build can be done through SSH only (VNC is not
necessary).

AOO42X/trunk require a very different setup in terms of libraries etc.
I tried but failed to get a full build.

I hope this helps.

Best regards,
-- 
Arrigo

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

Re: 4.2.0 release blockers

[Matthias Seidel]

Hi All,

Am 01.10.23 um 21:04 schrieb Peter Kovacs:


Am 01.10.23 um 13:44 schrieb Damjan Jovanovic:

Hi

So for 4.2.0, presumably we need to fix the bugs with 
4.2.0_release_blocker

flags:
https://bz.apache.org/ooo/buglist.cgi?f1=flagtypes.name_id=251353=substring_format=advanced=---=4.2.0_release_blocker 


of which there is 6:

For 127731, I found the problem yesterday (Microsoft's damned 
side-by-side

assemblies), and am building AOO with my fix now, if all goes well it
should be committed later today or tomorrow.
127783 needs testing on several platforms to isolate the bug, now that
Arrigo's ppt branch was merged.
127861 will probably need bisecting.
128094 is probably a packaging bug and needs testing and might need
bisecting.

sadly I suck with c++ debuggers.

127154 and 127966 need to be looked at by a Mac developer.


please note we have 2 project MacMinis. A intel and a m1 based system.


FYI: I just updated the M1 machine to macOS 14 (Sonoma).

Happy testing!

Regards,

   Matthias



they are based in the US, the plan has been to set them up as build 
bots. (still on this topic)


However in meanwhile i found out that you are not able to build on the 
new processors for intel.


But the intel one is available to all who do not own a apple device 
but need to test or develop something for AOO.



All the best.



Regards
Damjan



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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: 4.2.0 release blockers

[Damjan Jovanovic]

On Wed, Oct 4, 2023 at 4:52 PM Jim Jagielski  wrote:

>
>
> > On Oct 1, 2023, at 7:44 AM, Damjan Jovanovic  wrote:
> >
> > 127154 and 127966 need to be looked at by a Mac developer.
> >
>
> Those look pretty old. I should create a quick macOS 4.2.0 dev build for
> testing
>
>
Thank you Jim. While you are here, can you please look at bug
https://bz.apache.org/ooo/show_bug.cgi?id=127861 where one of your commits
created a regression?

Regards
Damjan

Re: 4.2.0 release blockers

[Jim Jagielski]

> On Oct 2, 2023, at 12:11 AM, Dave Fisher  wrote:
> 
> 
> Is there a step by step how to build AOO on these? Knowing the steps would 
> allow someone who is interested to try on their own Mac. 
> 
> Remind what version of macOS should be the minimum? My 11 year old iMac can 
> only be on 10.11.6 (I’m not saying I can build on it, but I could test a 
> build). Our minimum for 4.1.x is currently 10.7.
> 

https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Building_on_MacOsX

Re: 4.2.0 release blockers

[Jim Jagielski]

> On Oct 1, 2023, at 7:44 AM, Damjan Jovanovic  wrote:
> 
> 127154 and 127966 need to be looked at by a Mac developer.
> 

Those look pretty old. I should create a quick macOS 4.2.0 dev build for testing


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

Re: 4.2.0 release blockers

[Matthias Seidel]

Hi Keith,

Am 03.10.23 um 21:48 schrieb Keith N. McKenna:

Matthias Seidel wrote:
Apart from the release blocker we need to get the translation process 
running again...


At the moment we would only be able to release en-US. ;-)

Regards,

    Matthias

Matthias;

Where is the disconnect in the translation process currently? Is it 
lack of translators, something in the linking of Poodle with the code, 
or some other disconnect?


At the moment it is the linking of Pootle with our code (and vice versa).

The lack of translations is because we made no progress there. I am sure 
we will see activity again once we have done our part and update our 
test builds.


Peter is working on the server, because we need a newer version of the 
Translate Toolkit.


Regards,

   Matthias



Regards
Keith



-
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: 4.2.0 release blockers

[Keith N. McKenna]

Matthias Seidel wrote:
Apart from the release blocker we need to get the translation process 
running again...


At the moment we would only be able to release en-US. ;-)

Regards,

    Matthias

Matthias;

Where is the disconnect in the translation process currently? Is it lack 
of translators, something in the linking of Poodle with the code, or 
some other disconnect?


Regards
Keith



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

Re: 4.2.0 release blockers

[Dave Fisher]

Sent from my iPhone

> On Oct 1, 2023, at 12:04 PM, Peter Kovacs  wrote:
> 
> 
>> Am 01.10.23 um 13:44 schrieb Damjan Jovanovic:
>> Hi
>> 
>> So for 4.2.0, presumably we need to fix the bugs with 4.2.0_release_blocker
>> flags:
>> https://bz.apache.org/ooo/buglist.cgi?f1=flagtypes.name_id=251353=substring_format=advanced=---=4.2.0_release_blocker
>> of which there is 6:
>> 
>> For 127731, I found the problem yesterday (Microsoft's damned side-by-side
>> assemblies), and am building AOO with my fix now, if all goes well it
>> should be committed later today or tomorrow.
>> 127783 needs testing on several platforms to isolate the bug, now that
>> Arrigo's ppt branch was merged.
>> 127861 will probably need bisecting.
>> 128094 is probably a packaging bug and needs testing and might need
>> bisecting.
> sadly I suck with c++ debuggers.
>> 127154 and 127966 need to be looked at by a Mac developer.
> 
> please note we have 2 project MacMinis. A intel and a m1 based system.
> 
> they are based in the US, the plan has been to set them up as build bots. 
> (still on this topic)
> 
> However in meanwhile i found out that you are not able to build on the new 
> processors for intel.

On that machine we should see if we can build for the new chips …

When you access those Macs do you get a desktop or is it ssh?

Is there a step by step how to build AOO on these? Knowing the steps would 
allow someone who is interested to try on their own Mac. 

Remind what version of macOS should be the minimum? My 11 year old iMac can 
only be on 10.11.6 (I’m not saying I can build on it, but I could test a 
build). Our minimum for 4.1.x is currently 10.7.

> 
> But the intel one is available to all who do not own a apple device but need 
> to test or develop something for AOO.

If multiple will be trying on these we’ll need to agree on the environment and 
make sure they are setup.

Best,
Dave
> 
> 
> All the best.
> 
>> 
>> Regards
>> Damjan
>> 
> 
> -
> 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: 4.2.0 release blockers

[Matthias Seidel]

Hi All,

Am 01.10.23 um 13:44 schrieb Damjan Jovanovic:

Hi

So for 4.2.0, presumably we need to fix the bugs with 4.2.0_release_blocker
flags:
https://bz.apache.org/ooo/buglist.cgi?f1=flagtypes.name_id=251353=substring_format=advanced=---=4.2.0_release_blocker
of which there is 6:

For 127731, I found the problem yesterday (Microsoft's damned side-by-side
assemblies), and am building AOO with my fix now, if all goes well it
should be committed later today or tomorrow.

Sounds great!

127783 needs testing on several platforms to isolate the bug, now that
Arrigo's ppt branch was merged.
127861 will probably need bisecting.
128094 is probably a packaging bug and needs testing and might need
bisecting.
127154 and 127966 need to be looked at by a Mac developer.


Apart from the release blocker we need to get the translation process 
running again...


At the moment we would only be able to release en-US. ;-)

Regards,

   Matthias



Regards
Damjan



smime.p7s
Description: S/MIME Cryptographic Signature

Re: 4.2.0 release blockers

[Peter Kovacs]

Am 01.10.23 um 13:44 schrieb Damjan Jovanovic:

Hi

So for 4.2.0, presumably we need to fix the bugs with 4.2.0_release_blocker
flags:
https://bz.apache.org/ooo/buglist.cgi?f1=flagtypes.name_id=251353=substring_format=advanced=---=4.2.0_release_blocker
of which there is 6:

For 127731, I found the problem yesterday (Microsoft's damned side-by-side
assemblies), and am building AOO with my fix now, if all goes well it
should be committed later today or tomorrow.
127783 needs testing on several platforms to isolate the bug, now that
Arrigo's ppt branch was merged.
127861 will probably need bisecting.
128094 is probably a packaging bug and needs testing and might need
bisecting.

sadly I suck with c++ debuggers.

127154 and 127966 need to be looked at by a Mac developer.


please note we have 2 project MacMinis. A intel and a m1 based system.

they are based in the US, the plan has been to set them up as build 
bots. (still on this topic)


However in meanwhile i found out that you are not able to build on the 
new processors for intel.


But the intel one is available to all who do not own a apple device but 
need to test or develop something for AOO.



All the best.



Regards
Damjan



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