Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

AND WE HAVE A WINNER!! With the below changes to the redland build setup, I get no errors when opening on Ubuntu 18.04. > On Oct 29, 2020, at 7:28 AM, Jim Jagielski wrote: > > I'm trying with this: > > diff --git a/main/redland/raptor/makefile.mk b/main/redland/raptor/makefile.mk > index

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

I'm trying with this: diff --git a/main/redland/raptor/makefile.mk b/main/redland/raptor/makefile.mk index 51b78762c3..0c8b6a4d7b 100644 --- a/main/redland/raptor/makefile.mk +++ b/main/redland/raptor/makefile.mk @@ -128,7 +128,7 @@ XSLTLIB!:=$(XSLTLIB) # expand dmake variables for xslt-config

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

I did try specifically forcing --with-curl-config=no, because I saw that too, but that wasn't it.I also add 'with-threads' which was in the old CONFIGURE_FLAGS but that this one and again no luck. But I think we're on the right track. > On Oct 28, 2020, at 7:59 PM, Don Lewis wrote: > > On 27

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

On 28 Oct, Don Lewis wrote: > On 28 Oct, Don Lewis wrote: >> On 27 Oct, Don Lewis wrote: >>> On 27 Oct, Jim Jagielski wrote: Maybe... but it DID WORK before. That is, before the mega patch, configure did the "right thing". So if something is causing configure to make a different

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

On 28 Oct, Don Lewis wrote: > On 27 Oct, Don Lewis wrote: >> On 27 Oct, Jim Jagielski wrote: >>> Maybe... but it DID WORK before. That is, before the mega patch, >>> configure did the "right thing". So if something is causing configure >>> to make a different decision, it is due to the interaction

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

Hi Jim, On 10/28/20 2:08 PM, Jim Jagielski wrote: Thanks... in the meantime, please test the '-jj1' builds available. General Errors on opening using Ubuntu 18.04 VM. Best regards, Carl On Oct 28, 2020, at 1:28 PM, Pedro Lino wrote: Hi Jim Find attached an odt and an ods that I just

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

On 27 Oct, Don Lewis wrote: > On 27 Oct, Jim Jagielski wrote: >> Maybe... but it DID WORK before. That is, before the mega patch, >> configure did the "right thing". So if something is causing configure >> to make a different decision, it is due to the interaction w/ the new >> stuff that the RDF

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

Top posting: Confirmed under Ubuntu 18.04.5 x64 > On 10/28/2020 8:10 PM Matthias Seidel wrote: > > > Hi Jim, > > "General Error" when opening files on Ubuntu 16.04. > > Am 28.10.20 um 19:08 schrieb Jim Jagielski: > > Thanks... in the meantime, please test the '-jj1' builds available. > > >

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

Hi Jim, "General Error" when opening files on Ubuntu 16.04. Am 28.10.20 um 19:08 schrieb Jim Jagielski: > Thanks... in the meantime, please test the '-jj1' builds available. > >> On Oct 28, 2020, at 1:28 PM, Pedro Lino wrote: >> >> Hi Jim >> >> Find attached an odt and an ods that I just

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

Thanks... in the meantime, please test the '-jj1' builds available. > On Oct 28, 2020, at 1:28 PM, Pedro Lino wrote: > > Hi Jim > > Find attached an odt and an ods that I just confirmed that cause the error > messages with test12 > > Regards, > Pedro > > (the attachments will not be

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

Hi Jim Find attached an odt and an ods that I just confirmed that cause the error messages with test12 Regards, Pedro (the attachments will not be available to the mailing list) > On 10/28/2020 3:02 PM Jim Jagielski wrote: > > > Can someone send me a file or 2 that is known to cause the

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

Can someone send me a file or 2 that is known to cause the error? TIA > On Oct 28, 2020, at 9:34 AM, Pedro Lino > wrote: > > Hi Jim > > Top posting. > The most commonly used Ubuntu version should be 18.04 (but Canonical still > supports as far back as 14.04) but many of us are already

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

Hi Jim Top posting. The most commonly used Ubuntu version should be 18.04 (but Canonical still supports as far back as 14.04) but many of us are already testing that version. If this is just a test VM, I would say it could be useful if you installed 20.04.1 LTS which none of us is using but

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

Hi Jim, On 10/28/20 7:20 AM, Jim Jagielski wrote: I have some Ubuntu VMs that I can use to try to test... can someone share which one is the more-than-likely one to show the bug and is there any particular file(s) I should use to test?

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

I have some Ubuntu VMs that I can use to try to test... can someone share which one is the more-than-likely one to show the bug and is there any particular file(s) I should use to test? - To unsubscribe, e-mail:

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

Possible... esp w/ raptor that saw a huge bump from 1.x to 2.x... > On Oct 27, 2020, at 6:47 PM, Don Lewis wrote: > > On 27 Oct, Jim Jagielski wrote: >> Maybe... but it DID WORK before. That is, before the mega patch, >> configure did the "right thing". So if something is causing configure >>

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

On 27 Oct, Jim Jagielski wrote: > Maybe... but it DID WORK before. That is, before the mega patch, > configure did the "right thing". So if something is causing configure > to make a different decision, it is due to the interaction w/ the new > stuff that the RDF stuff does. The problem is with

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

Maybe... but it DID WORK before. That is, before the mega patch, configure did the "right thing". So if something is causing configure to make a different decision, it is due to the interaction w/ the new stuff that the RDF stuff does. The problem is with the patch or how it is working... In

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

On 27 Oct, Jim Jagielski wrote: > For completeness, and especially for those not following the thread, > what we have conclusively shown is that it is NOT an issue w/ the > build server, which is the same we've been using for several 4.1.x > releases, nor with the configure and build parameters

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

For completeness, and especially for those not following the thread, what we have conclusively shown is that it is NOT an issue w/ the build server, which is the same we've been using for several 4.1.x releases, nor with the configure and build parameters (also unchanged from previous). It is

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

> On Oct 27, 2020, at 2:34 PM, Don Lewis wrote: > > On 27 Oct, Jim Jagielski wrote: >> Thanks all... I am now building the final 'git bisect' test, based on >> >> >> https://github.com/apache/openoffice/commit/f7070ae3689d0d34bf9dab3d31f56744d0df4784 >> >> assuming that this is good, it

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

On 27 Oct, Jim Jagielski wrote: > Thanks all... I am now building the final 'git bisect' test, based on > > > https://github.com/apache/openoffice/commit/f7070ae3689d0d34bf9dab3d31f56744d0df4784 > > assuming that this is good, it seems like 99% likely that the problem arose > with > >

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

As expected: e9fab906a0063dca04a52bfc5270c9d70ccbbb27 is the first bad commit commit e9fab906a0063dca04a52bfc5270c9d70ccbbb27 Author: truckman Date: Fri Aug 26 07:13:14 2016 + Upgrade bundled raptor from raptor-1.4.18 to raptor2-2.0.15 to get the fix for CVE-2012-0037. It is not

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

No problems in test15 for me! Matthias Am 27.10.20 um 17:16 schrieb Jim Jagielski: > test15, likely the final test of the git bisect series, is now available. > >> On Oct 27, 2020, at 10:19 AM, Jim Jagielski wrote: >> >> Thanks all... I am now building the final 'git bisect' test, based on >>

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

test15 Debian 10 64bits No error messages to open or save odt and ods files

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

test15, likely the final test of the git bisect series, is now available. > On Oct 27, 2020, at 10:19 AM, Jim Jagielski wrote: > > Thanks all... I am now building the final 'git bisect' test, based on > > >

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

Thanks all... I am now building the final 'git bisect' test, based on https://github.com/apache/openoffice/commit/f7070ae3689d0d34bf9dab3d31f56744d0df4784 assuming that this is good, it seems like 99% likely that the problem arose with

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

Hi Jim, No error messages on opening and saving on Ubuntu 16.04. Am 27.10.20 um 14:01 schrieb Jim Jagielski: > test14 is ready for testing! > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

test14 Debian 10 64bits No error messages to open or save odt and ods files On Tue, Oct 27, 2020 at 10:02 AM Jim Jagielski wrote: > test14 is ready for testing! > > - > To unsubscribe, e-mail:

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

test14 is ready for testing! - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

Hi Jim, On 10/26/20 4:32 PM, Jim Jagielski wrote: Thx... I'll wait for a few more tests before I mark test13 as bad On Ubuntu 18.04 x86-64 VM General error saving a new Writer doc. Gereral Error opening an existing doc. Saving existing document is okay. Thanks, Carl On Oct 26, 2020, at

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

the same one that I just created, AOO_4.8.1 show an error messages. More later I will test with Debian 9. Regards, Delio. - Mensaje original - De: "André Pereira" Para: "dev" Enviados: Lunes, 26 de Octubre 2020 17:17:49 Asunto: Re: test12 (Was: Re: test11 (Was: Re: t

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

Does it help if I myself test it in another machine too? Is there anything else I can do to help to spot this bug? (I don't know much code though :-/ On Mon, Oct 26, 2020 at 5:33 PM Jim Jagielski wrote: > Thx... I'll wait for a few more tests before I mark test13 as bad > > > On Oct 26, 2020,

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

Thx... I'll wait for a few more tests before I mark test13 as bad > On Oct 26, 2020, at 3:59 PM, André Pereira wrote: > > teste13 > Here with Debian 10 64bits I have "General Error" message when opening odt > file and "Not all attributes could be read" when opening ods file. Saving > gives no

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

teste13 Here with Debian 10 64bits I have "General Error" message when opening odt file and "Not all attributes could be read" when opening ods file. Saving gives no error. The terminal gives "Failed to load module "atk-bridge"". On Mon, Oct 26, 2020 at 4:34 PM Jim Jagielski wrote: > test13 is

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

test13 is now available for test and review. thx again! > On Oct 26, 2020, at 12:06 PM, Jim Jagielski wrote: > > Thanks... we *seem* to be narrowing down to raptor2 as the possible cause. > >> On Oct 26, 2020, at 11:44 AM, Matthias Seidel >> wrote: >> >> Hi Jim, >> >> Confirming the error

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

Hi Jim, Confirming the error messages with test12. Matthias Am 26.10.20 um 16:18 schrieb Jim Jagielski: > Thanks... I'll wait for at least one additional confirmation that this one is > bad before I kick off #13 > >> On Oct 26, 2020, at 11:11 AM, Pedro Lino >> wrote: >> >> Hi Jim >> >> Still

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

Thanks... I'll wait for at least one additional confirmation that this one is bad before I kick off #13 > On Oct 26, 2020, at 11:11 AM, Pedro Lino > wrote: > > Hi Jim > > Still the same errors on Ubuntu 18.04.5 x64 > > Pedro > >> On 10/26/2020 1:56 PM Jim Jagielski wrote: >> >> >>

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

Hi Jim Still the same errors on Ubuntu 18.04.5 x64 Pedro > On 10/26/2020 1:56 PM Jim Jagielski wrote: > > > test12 is now available... you know where :) > > > On Oct 26, 2020, at 7:12 AM, André Pereira wrote: > > > > teste11 > > Here with Debian 10 64bits I have "General Error" message

Re: test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

Sorry I can't test until this evening. On Mon, Oct 26, 2020 at 9:57 AM Jim Jagielski wrote: > test12 is now available... you know where :) > > > On Oct 26, 2020, at 7:12 AM, André Pereira wrote: > > > > teste11 > > Here with Debian 10 64bits I have "General Error" message when opening > odt >

test12 (Was: Re: test11 (Was: Re: test2 is ready to run))

test12 is now available... you know where :) > On Oct 26, 2020, at 7:12 AM, André Pereira wrote: > > teste11 > Here with Debian 10 64bits I have "General Error" message when opening odt > file and "Not all attributes could be read" when opening ods file. Saving > gives no error. The terminal

Re: test11 (Was: Re: test2 is ready to run)

teste11 Here with Debian 10 64bits I have "General Error" message when opening odt file and "Not all attributes could be read" when opening ods file. Saving gives no error. The terminal gives "Failed to load module "atk-bridge"". On Sun, Oct 25, 2020 at 10:40 PM Carl Marcum wrote: > Hi Jim,

Re: test11 (Was: Re: test2 is ready to run)

Hi Jim, On 10/25/20 8:16 PM, Jim Jagielski wrote: And test11 is now available for test Getting the General Error opening Writer documents and when saving a new document. I don't get the error again when saving after opening an existing document and saving it. I get the Not all attributes

test11 (Was: Re: test2 is ready to run)

And test11 is now available for test > On Oct 25, 2020, at 2:11 PM, Carl Marcum wrote: > > > > On 10/25/20 1:04 PM, Matthias Seidel wrote: >> Am 25.10.20 um 17:46 schrieb Jim Jagielski: >>> test10 builds are now available... >> I still get "General Error" >> > > I also get the Error on

Re: test2 is ready to run

On 10/25/20 1:04 PM, Matthias Seidel wrote: Am 25.10.20 um 17:46 schrieb Jim Jagielski: test10 builds are now available... I still get "General Error" I also get the Error on Ubuntu 18.04 x86-64 on test 10. Thanks, Carl

Re: test2 is ready to run

Am 25.10.20 um 17:46 schrieb Jim Jagielski: > test10 builds are now available... I still get "General Error" > >> On Oct 25, 2020, at 5:28 AM, Matthias Seidel >> wrote: >> >> Confirmed, error message is back on Ubuntu 16.04 with test9. >> >> Matthias >>

Re: test2 is ready to run

test10 builds are now available... > On Oct 25, 2020, at 5:28 AM, Matthias Seidel > wrote: > > Confirmed, error message is back on Ubuntu 16.04 with test9. > > Matthias > >>> >>> http://home.apache.org/~jim/AOO-builds/ <

Re: test2 is ready to run

Confirmed, error message is back on Ubuntu 16.04 with test9. Matthias Am 25.10.20 um 03:36 schrieb Carl Marcum: > Hi Jim, > > On 10/24/20 8:22 PM, Jim Jagielski wrote: >> And with that, test9 are now available... > > Test 9 gives me the General error on opening and saving on Ubuntu > 18.04

Re: test2 is ready to run

Hi Jim, On 10/24/20 8:22 PM, Jim Jagielski wrote: And with that, test9 are now available... Test 9 gives me the General error on opening and saving on Ubuntu 18.04 x86-64. Best regards, Carl On Oct 24, 2020, at 12:36 PM, Pedro Lino wrote: No problems on Ubuntu 18.04.5 x64 Would it

Re: test2 is ready to run

And with that, test9 are now available... > On Oct 24, 2020, at 12:36 PM, Pedro Lino > wrote: > > No problems on Ubuntu 18.04.5 x64 > > Would it be useful to test on an older (or newer) distro like Ubuntu 14.04 or > 20.10? > > I have an old laptop (Intel Classmate aka Magalhães) running

Re: test2 is ready to run

Hi Matthias, all > On 10/24/2020 5:39 PM Matthias Seidel wrote: > > I have an old laptop (Intel Classmate aka Magalhães) running Ubuntu 12.04 > > x86 which I can give a spin if/when a 32bit build is available. > > We would definitely need someone to test the RC on 32bit Linux. Ok. I can do

Re: test2 is ready to run

Hi, On Sat, Oct 24, 2020 at 6:50 PM Dave Fisher wrote: > Hi Gavin, > > These tests are not RCs. We had a bug in the RCs and now Jim is trying to > find the commit that introduced it. > Ok yeah I've been following. So the only thing Jim is interested in during these tests is open a file and

Re: test2 is ready to run

Hi Gavin, These tests are not RCs. We had a bug in the RCs and now Jim is trying to find the commit that introduced it. Regards, Dave > On Oct 24, 2020, at 9:43 AM, Gavin McDonald wrote: > > What is the full suite of tests that needs to be done for a release > candidate? > > Open, and Save

Re: test2 is ready to run

What is the full suite of tests that needs to be done for a release candidate? Open, and Save a file seems a bit limited On Sat, Oct 24, 2020 at 6:39 PM Matthias Seidel wrote: > Hi Pedro, > > Am 24.10.20 um 18:36 schrieb Pedro Lino: > > No problems on Ubuntu 18.04.5 x64 > > > > Would it be

Re: test2 is ready to run

Hi Pedro, Am 24.10.20 um 18:36 schrieb Pedro Lino: > No problems on Ubuntu 18.04.5 x64 > > Would it be useful to test on an older (or newer) distro like Ubuntu 14.04 or > 20.10? > > I have an old laptop (Intel Classmate aka Magalhães) running Ubuntu 12.04 x86 > which I can give a spin if/when a

Re: test2 is ready to run

No problems on Ubuntu 18.04.5 x64 Would it be useful to test on an older (or newer) distro like Ubuntu 14.04 or 20.10? I have an old laptop (Intel Classmate aka Magalhães) running Ubuntu 12.04 x86 which I can give a spin if/when a 32bit build is available. Regards, Pedro > On 10/24/2020 4:56

Re: test2 is ready to run

Hi Jim, Test 8 works without errors on Ubuntu 18.04 Thanks Carl On 10/24/20 11:24 AM, Jim Jagielski wrote: And test8 is now available... http://home.apache.org/~jim/AOO-builds/

Re: test2 is ready to run

No problems on Ubuntu 16.04 64-bit. Am 24.10.20 um 17:53 schrieb André Pereira: > test8 opens and saves files with no error messages here. > Debian 10 > > > On Sat, Oct 24, 2020 at 12:25 PM Jim Jagielski wrote: > >> And test8 is now available... >> >> http://home.apache.org/~jim/AOO-builds/

Re: test2 is ready to run

test8 opens and saves files with no error messages here. Debian 10 On Sat, Oct 24, 2020 at 12:25 PM Jim Jagielski wrote: > And test8 is now available... > > http://home.apache.org/~jim/AOO-builds/ < > http://home.apache.org/~jim/AOO-builds/>

Re: test2 is ready to run

And test8 is now available... http://home.apache.org/~jim/AOO-builds/

Re: test2 is ready to run

Getting closer! Yeah. Starting build for test8. Thx > On Oct 24, 2020, at 8:29 AM, André Pereira wrote: > > test7 opens and saves files with no error messages for me too. > Debian 10 > > On Sat, Oct 24, 2020 at 9:09 AM Matthias Seidel > wrote: > >> Hi Jim, >> >> Opens documents without

Re: test2 is ready to run

test7 opens and saves files with no error messages for me too. Debian 10 On Sat, Oct 24, 2020 at 9:09 AM Matthias Seidel wrote: > Hi Jim, > > Opens documents without error message on Ubuntu 16.04 for me. > > Am 24.10.20 um 13:32 schrieb Jim Jagielski: > > And test7 is uploaded and ready to be

Re: test2 is ready to run

Test 7 works for me on Ubuntu 18.04! Thanks, Carl On 10/24/20 7:32 AM, Jim Jagielski wrote: And test7 is uploaded and ready to be tested. Thx! On Oct 23, 2020, at 6:51 PM, Jim Jagielski wrote: Thanks you all... test7 is getting kicked off On Oct 23, 2020, at 5:51 PM, Carl Marcum

Re: test2 is ready to run

Hi Jim, Opens documents without error message on Ubuntu 16.04 for me. Am 24.10.20 um 13:32 schrieb Jim Jagielski: > And test7 is uploaded and ready to be tested. Thx! > >> On Oct 23, 2020, at 6:51 PM, Jim Jagielski wrote: >> >> Thanks you all... test7 is getting kicked off >> >>> On Oct 23,

Re: test2 is ready to run

And test7 is uploaded and ready to be tested. Thx! > On Oct 23, 2020, at 6:51 PM, Jim Jagielski wrote: > > Thanks you all... test7 is getting kicked off > >> On Oct 23, 2020, at 5:51 PM, Carl Marcum > > wrote: >> >> Hi Jim, >> >> On 10/23/20 5:09 PM, Jim Jagielski

Re: test2 is ready to run

Thanks you all... test7 is getting kicked off > On Oct 23, 2020, at 5:51 PM, Carl Marcum wrote: > > Hi Jim, > > On 10/23/20 5:09 PM, Jim Jagielski wrote: >> test6 is ready!! Thx everyone for their patience and for their testing. > > Test 6 is also good for me as well on Ubuntu 18.04 !! > >

Re: test2 is ready to run

Hi Jim, On 10/23/20 5:09 PM, Jim Jagielski wrote: test6 is ready!! Thx everyone for their patience and for their testing. Test 6 is also good for me as well on Ubuntu 18.04 !! Best regards, Carl On Oct 23, 2020, at 2:21 PM, Jim Jagielski wrote: Status update ... still working on this...

Re: test2 is ready to run

test6 opens and saves odt file without any error message on Debian 10 On Fri, Oct 23, 2020 at 6:29 PM Matthias Seidel wrote: > Hi Jim, > > Am 23.10.20 um 23:09 schrieb Jim Jagielski: > > test6 is ready!! Thx everyone for their patience and for their testing. > > Works for me! ;-) > > Matthias >

Re: test2 is ready to run

Hi Jim, Am 23.10.20 um 23:09 schrieb Jim Jagielski: > test6 is ready!! Thx everyone for their patience and for their testing. Works for me! ;-) Matthias > >> On Oct 23, 2020, at 2:21 PM, Jim Jagielski wrote: >> >> Status update >> ... still working on this... the issue is that the random

Re: test2 is ready to run

Test6 works perfectly under Ubuntu 18.04 x64! > On 10/23/2020 10:09 PM Jim Jagielski wrote: > > > test6 is ready!! Thx everyone for their patience and for their testing. > > > On Oct 23, 2020, at 2:21 PM, Jim Jagielski wrote: > > > > Status update > > ... still working on this... the

Re: test2 is ready to run

test6 is ready!! Thx everyone for their patience and for their testing. > On Oct 23, 2020, at 2:21 PM, Jim Jagielski wrote: > > Status update > ... still working on this... the issue is that the random selected picks end > up with snapshots that can't be built as-is, so I need to cherry-pick

Re: test2 is ready to run

Status update ... still working on this... the issue is that the random selected picks end up with snapshots that can't be built as-is, so I need to cherry-pick stuff (like the nss and HW acceleration stuff) and so it's taking a lot longer than a regular build would. > On Oct 23, 2020, at

Re: test2 is ready to run

w00t! Kicking off test6 > On Oct 23, 2020, at 10:55 AM, Carl Marcum wrote: > > Hi Jim, > > On 10/23/20 10:28 AM, Jim Jagielski wrote: >> test5 is now available... > > Getting closer. > No errors on Ubuntu 18.04 opening or saving .odt and .ods with test5. > > Best regards, > Carl >> >>> On

Re: test2 is ready to run

Hi Jim, On 10/23/20 10:28 AM, Jim Jagielski wrote: test5 is now available... Getting closer. No errors on Ubuntu 18.04 opening or saving .odt and .ods with test5. Best regards, Carl On Oct 23, 2020, at 10:16 AM, Matthias Seidel wrote: Hi Jim, Am 23.10.20 um 13:54 schrieb Jim

Re: test2 is ready to run

Debian 10 No error messages on test5

Re: test2 is ready to run

test5 is now available... > On Oct 23, 2020, at 10:16 AM, Matthias Seidel > wrote: > > Hi Jim, > > Am 23.10.20 um 13:54 schrieb Jim Jagielski: >> OK, so we have narrowed things down... somewhere between >> >> >>

Re: test2 is ready to run

Hi Jim, Am 23.10.20 um 13:54 schrieb Jim Jagielski: > OK, so we have narrowed things down... somewhere between > > > https://github.com/apache/openoffice/commit/21aebe28dbe5d985add2fadc46e6217b148303bb > > and > > >

Re: test2 is ready to run

OK, so we have narrowed things down... somewhere between https://github.com/apache/openoffice/commit/21aebe28dbe5d985add2fadc46e6217b148303bb and https://github.com/apache/openoffice/commit/27aafff9ac690db20ff7d9edf69a595216b2386e things broke for CentOS5. Starting git bisect with

Re: test2 is ready to run

> > Opening a document with test4 On Debian 10 I get the "General Error" > message and the terminal displays "tk-Message: 08:47:39.634: Failed to load > module "atk-bridge""

Re: test2 is ready to run

Hi Jim, On 10/23/20 6:53 AM, Jim Jagielski wrote: test4 is uploaded and ready to be tested. Thx again! - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail:

Re: test2 is ready to run

This build has the same errors when opening ods and odt > On 10/23/2020 11:53 AM Jim Jagielski wrote: > > > test4 is uploaded and ready to be tested. Thx again! > > - > To unsubscribe, e-mail:

Re: test2 is ready to run

test4 is uploaded and ready to be tested. Thx again! - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: test2 is ready to run

I've had some things pop up so I'm just starting the test4 build now... this will be on 27aafff9ac690db20ff7d9edf69a595216b2386e (right before the libxml updates) > On Oct 22, 2020, at 5:51 PM, André Pereira wrote: > > I can confirm test3 open documents without any error messages on Debian

Re: test2 is ready to run

I can confirm test3 open documents without any error messages on Debian 10. On Thu, Oct 22, 2020 at 4:22 PM Jim Jagielski wrote: > Yep! > > > On Oct 22, 2020, at 3:11 PM, Matthias Seidel > wrote: > > > > Confirmed! > > > > So we are now at August 22nd? > > > > Am 22.10.20 um 21:04 schrieb Jim

Re: test2 is ready to run

Yep! > On Oct 22, 2020, at 3:11 PM, Matthias Seidel > wrote: > > Confirmed! > > So we are now at August 22nd? > > Am 22.10.20 um 21:04 schrieb Jim Jagielski: >> Wow. I had just uploaded test3 ! :) >> >> >>> On Oct 22, 2020, at 2:53 PM, Pedro Lino >>> wrote: >>> >>> Hi Jim >>> >>> Good

Re: test2 is ready to run

Confirmed! So we are now at August 22nd? Am 22.10.20 um 21:04 schrieb Jim Jagielski: > Wow. I had just uploaded test3 ! :) > > >> On Oct 22, 2020, at 2:53 PM, Pedro Lino >> wrote: >> >> Hi Jim >> >> Good news! >> Test 3 has no problems and check for Update also works (it didn't in test2) >> >>

Re: test2 is ready to run

Wow. I had just uploaded test3 ! :) > On Oct 22, 2020, at 2:53 PM, Pedro Lino > wrote: > > Hi Jim > > Good news! > Test 3 has no problems and check for Update also works (it didn't in test2) > > Apparentely we have a good one! :) > > (Downloading at 500Mbit means 3 seconds to download

Re: test2 is ready to run

Hi Jim Good news! Test 3 has no problems and check for Update also works (it didn't in test2) Apparentely we have a good one! :) (Downloading at 500Mbit means 3 seconds to download 150MB :) ) Regards, Pedro > On 10/22/2020 5:58 PM Jim Jagielski wrote: > > > YEAH! I am now building from

Re: test2 is ready to run

YEAH! I am now building from 21aebe28dbe5d985add2fadc46e6217b148303bb which is right after the OpenSLL upgrade(s). If test3, to be provided ASAP, fails, then we know the problem. If not, I'll start a full git bisect with 21aebe28dbe5d985add2fadc46e6217b148303bb as 'git bisect good' > On Oct

Re: test2 is ready to run

Hi Jim, test2 is OK for me. Am 22.10.20 um 18:33 schrieb Jim Jagielski: > Via > > http://home.apache.org/~jim/AOO-builds/ > >> On Oct 22, 2020, at 10:38 AM, Jim Jagielski wrote: >> >> OK... just did a co of 787546a0bd53c78489200311961fb621d00e1e69. This is >> before the openssl upgrade and