[call for help] libreoffice 6.2 update

[Greg Veldman]

Is there anything else that needs to be done to get the LO
updates currently on GitHub into a state where they can be
committed?  Should I open a PR?

On Thu, Mar 14, 2019 at 10:17:45AM -0400, Greg Veldman wrote:
> On Wed, Mar 13, 2019 at 02:46:41PM -0400, Greg Veldman wrote:
> > On Tue, Mar 12, 2019 at 07:45:49PM -0400, Greg Veldman wrote:
> > > I was able to reproduce the segfault.  From the limited amount
> > > of debugging I've been able to do, it looks like it may trace
> > > back to the cpp_uno libs.  Will try to look into it more tomorrow.
> > 
> > I was able to spend a bit of quality time with gdb and UBSan
> > this morning, and got it tracked down.  It was indeed the cpp_uno
> > bridge, specifically the exception processing code as triggered
> > by the FileExists() function in svx/source/gallery2/galmisc.cxx.
> > 
> > I'm running an i386 test build again now, if it finishes
> > successfully I'll push the patch.
> 
> With the most recent two commits, I've now gotten clean builds
> on 11.2-amd64, 11.2-i386, and 12.0-i386.  I'll try to run a
> test build on 12.0-amd64 later today if I can.  I've also done
> some basic functionality tests (e.g. can I open, edit, save
> documents, use internal LO dialogs, etc).
> 
> I think the current repo seems to be in a fairly stable state
> at this point.  Li-Wen, if you agree do you want to issue a
> broader call for testing?  With all the work that's been done
> on this, I'd kind of like to see it make it into the ports
> tree for 2019Q2 if possible, so the broader community can
> actually use it... ;-)
> 
> -- 
> Greg Veldman

-- 
Greg Veldman