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

2020-10-29 Thread Jim Jagielski
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))

2020-10-29 Thread Jim Jagielski
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))

2020-10-29 Thread Jim Jagielski
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))

2020-10-29 Thread Don Lewis
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))

2020-10-28 Thread Don Lewis
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))

2020-10-28 Thread Carl Marcum
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))

2020-10-28 Thread Don Lewis
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))

2020-10-28 Thread Pedro Lino
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))

2020-10-28 Thread Matthias Seidel
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))

2020-10-28 Thread 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 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))

2020-10-28 Thread Pedro Lino
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))

2020-10-28 Thread Jim Jagielski
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))

2020-10-28 Thread Pedro Lino
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))

2020-10-28 Thread Carl Marcum
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))

2020-10-28 Thread Jim Jagielski
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))

2020-10-27 Thread Jim Jagielski
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))

2020-10-27 Thread Don Lewis
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))

2020-10-27 Thread Jim Jagielski
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))

2020-10-27 Thread Don Lewis
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))

2020-10-27 Thread Jim Jagielski
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))

2020-10-27 Thread Jim Jagielski
> 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))

2020-10-27 Thread Don Lewis
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))

2020-10-27 Thread Jim Jagielski
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))

2020-10-27 Thread Matthias Seidel
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))

2020-10-27 Thread André Pereira
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))

2020-10-27 Thread 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))

2020-10-27 Thread Jim Jagielski
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))

2020-10-27 Thread Matthias Seidel
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))

2020-10-27 Thread André Pereira
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))

2020-10-27 Thread Jim Jagielski
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))

2020-10-26 Thread Carl Marcum
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))

2020-10-26 Thread Delio Orozco Gonzalez
Hello to alll: Test with AOO_4.1.8_test13 PC: Intel Core 2 Quad Q8400 (4) @ 2.669GHz OS: Debian GNU/Linux 10 (buster) x86_64 Kernel: 4.19.0-10-amd64 DE: IceWm and Budgie 1.-At saving a odt document first time, AOO_4.1.8_test13 show an error messages 2.-When I open and odt document, even the

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

2020-10-26 Thread André Pereira
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))

2020-10-26 Thread Jim Jagielski
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))

2020-10-26 Thread André Pereira
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))

2020-10-26 Thread Jim Jagielski
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))

2020-10-26 Thread Matthias Seidel
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))

2020-10-26 Thread 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 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))

2020-10-26 Thread Pedro Lino
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))

2020-10-26 Thread Carl Marcum
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))

2020-10-26 Thread Jim Jagielski
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