Re: Documenting our source code structure

[Arrigo Marchiori]

Hello All,

On Thu, May 16, 2024 at 03:19:23PM +, Damjan Jovanovic wrote:

> On Thu, May 16, 2024 at 2:41 PM Matthias Seidel 
> wrote:
> 
> > Hi All,
> >
> > Some time ago I added some rudimentary Readme to some directories in our
> > code, e.g.:
> >
> > https://github.com/apache/openoffice/edit/trunk/main/sw/README.md
> >
> > Please feel encouraged to add more information to describe what a
> > specific directory is meant for.
> >
> > Of course, this is a work in progress, but it would help volunteers to
> > understand our code better.
> >
> > In this case, who should know, that "sw" stands for "StarWriter" and
> > contains the code for the "Writer" part of our software?
> >
> > Opinions?
> >
>
> Please note we already have other sources of info that could be used for
> these files,

Until now, I have used this wiki page:
https://wiki.openoffice.org/wiki/Source_code_directories
to get a first idea of what is inside the directories.

> eg. in the  tag of some modules' xml files, such
> as main/sw/xml/writer.xml

Nice! Is that information used anywhere?

Best regards,
-- 
Arrigo

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

Re: Dynamic OpenSSL causes Curl regression on *nix

[Arrigo Marchiori]

Hello All,

TL;DR: I think that keeping distinct branches for trunk and AOO42X is
good practice, and we shall work on stabilizing AOO42X. More below.

On Wed, May 01, 2024 at 03:52:19PM +0200, Matthias Seidel wrote:

> Hi Pedro,
> 
> Am 01.05.24 um 15:39 schrieb Pedro Lino:
> > Hi Matthias
> > 
> > > On 05/01/2024 1:30 PM WEST Matthias Seidel  
> > > wrote:
> > > > > Maybe it is easier to delete the current 42x branch and start a new 
> > > > > 42X
> > > > > branch? If any patches were added to 42X only (and they are still
> > > > > relevant), then these should be cherry picked to trunk before 
> > > > > splitting...
> > > > > 
> > > > > 
> > > > +1.
> > > > 
> > > > The AOO42X branch is quite old. Development only really happens on 
> > > > trunk.
> > > > The best maintained branch is trunk, and any branches should be as 
> > > > close to
> > > > trunk as possible.
> > >
> > > Trunk is an unstable branch.
> >
> > That is the nature of Trunk ;)

Yes! And should not be the nature of AOO42X, IMHO.

> > > Everything we want to have in AOO42X (which was branched from trunk some
> > > years ago) should have been cherry-picked early.
> >
> > Do you mean that all patches/fixes in 42X are in Trunk also?
>
> Trunk has all patches, AOO42X only those that were cherry-picked from trunk.

I confirm this. I personally made some patch ``backwards'' (first in
another branch, and then cherry-picked into trunk) but it was my
mistake: our best practice shall be as Matthias described above.

> > Therefore there would not be a problem in deleting the current branch 42X 
> > and start a new one?
> > This would make sense because Damjan mentioned that many relevant fixes in 
> > trunk are not included in 42X
> 
> If he didn't cherry-pick them (for a reason?) they are not included.

...and if no one else did ;-)

I personally cherry-picked the SSL- and curl-related commits because
of some tests I am doing on AOO42X. I think that it makes sense to
cherry-pick also his latest change of 16-bit into 32-bit indices.

> > > > Also why is the next release 4.2.x? Haven't we made enough changes for
> > > > 5.0.x? If not, what should be in 5.0.x?
> > >
> > > It is quite hypothetical to discuss about versions we are NOT capable to
> > > release.
> >
> > It is. But Damjan's question is still valid? What would be the change 
> > needed to consider this 5.0? I would say that having a Winx64 would be such 
> > a condition. As it is, I still see this as 42X
> 
> For AOO 5.0 I would expect at least that we support ODF 1.3.
> 
> A Win64 build would be great for AOO 4.5.0.

I personally would see both these improvements good for AOO 4.2.0, but
I think it's only a matter of... marketing and promotion. This topic
is worth another thread.

> But again, we are not able to do a release, we should work on that problem
> first.

If we are talking about ``technical'' issues, then I agree that AOO42X
is unstable and for this reason it cannot be released.

> > > The next version we CAN release is 4.1.16 (AOO41X).
> >
> > That is true!
> > 
> > > If we become able to do a release for a newer branch (AOO42X), we should
> > > simply release what we have...
> >
> > Exactly, but including all valid updates that have been added to trunk but 
> > not cherry picked to 42X

+1

> If they were not cherry-picked I would expect there was a reason for it?

I think that we have to discuss the meaning of the ``valid'' word as
used above by Pedro.

Almost all commits I saw to trunk would be IMHO applicable to
AOO42X. I do not think there is anything so ``revolutionary'' or
``experimental'', that I would rather delay to 4.3.0, 4.5.0, 5.0.0 or
whatever future AOO version.

However, the author of each commit has IMHO the right to the first
opinion about the opportunity of cherry-picking into AOO42X, AOO41X
etc.

_My_ latest commits to trunk were all targeted to AOO42X. If I did not
cherry-pick them is just because... I forgot to. And Matthias,
sometimes, kindly reminded me about them.

Only trunk should be allowed to be blatantly unstable. The reason for
AOO42X also being unstable is because we inherited it this way. This
is what I understood, at least, and I believe we have to fix this.

I hope I could explain myself clearly.

Best regards,
-- 
Arrigo

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

Re: Dynamic OpenSSL causes Curl regression on *nix

[Arrigo Marchiori]

Dear All,

On Sat, Apr 27, 2024 at 06:36:29PM +0200, Arrigo Marchiori wrote:

> Dear All,
> 
> On Tue, Apr 23, 2024 at 04:48:13PM +, Damjan Jovanovic wrote:
> 
> [...]
> > I've now verified it works on Windows too, and have pushed the commits to
> > trunk.
> > 
> > Here they are, in case you want to cherry-pick:
> > 
> > commit f7b97bf7d9139c8b602d3da3aadbeef0631e39c1 (HEAD -> trunk,
> > origin/trunk, origin/HEAD)
> [...]
> > commit e469ab6aed23a1b38f105a944997af16e61071d0
> 
> I cherry-picked the commits into AOO42X. I built that branch with our
> Docker image and it seems to work fine, too!
> 
> The build can be downloaded from here:
> https://home.apache.org/~ardovm/openoffice/linux/openoffice4-2024-04-27-x86_64-installed.tar.bz2

Windows build available here:
https://home.apache.org/~ardovm/openoffice/windows/Apache_OpenOffice-2024-04-28_4.2.0_Win_x86_install_en-US.exe

Best regards,
-- 
Arrigo

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

Re: (openoffice) 01/12: Port our WebDAV content provider from serf/apr/apr-util, to curl.

[Arrigo Marchiori]

Hello Dave,

On Sat, Apr 27, 2024 at 09:45:46AM -0700, Dave Fisher wrote:

> Hi Arrigo,
> 
> With this change do we eliminate all dependencies on Apache APR?

Yes, for AOO42X.

This is a cherry-pick of Damjan's work on trunk, so he may elaborate
further.

Apache APR and Serf remain a requirement of our AOO41X branch.

> > On Apr 27, 2024, at 9:32 AM, ard...@apache.org wrote:
> > 
> > This is an automated email from the ASF dual-hosted git repository.
> > 
> > ardovm pushed a commit to branch AOO42X
> > in repository https://gitbox.apache.org/repos/asf/openoffice.git
> > 
> > commit 9646dec509b481cb88dbe1130c2f325ed13af748
> > Author: Damjan Jovanovic 
> > AuthorDate: Mon Apr 4 03:06:47 2022 +0200
> > 
> >Port our WebDAV content provider from serf/apr/apr-util, to curl.
> > 
> >    Patch by: me
> > 
> >(adapted from commit 51ba086bf122dbb5b50fd813e5b9a81c051aa16b by Arrigo
> >Marchiori)
> > ---
> > ext_libraries/apr-util/apr-util-1.6.1.apu.hw.patch |   13 -
> > ext_libraries/apr-util/apr-util-1.6.1.expat.patch  |   17 -
> > .../apr-util/apr-util-1.6.1.makewin32.patch|  199 --
> > ext_libraries/apr-util/aprutil_version.mk  |   24 -
> > ext_libraries/apr-util/makefile.mk |  139 --
> > ext_libraries/apr-util/prj/build.lst   |5 -
> > ext_libraries/apr-util/prj/d.lst   |   15 -
> > ext_libraries/apr/apr-1.6.5-no-devenv.patch|   16 -
> > ext_libraries/apr/apr-1.6.5-windows.patch  |   11 -
> > ext_libraries/apr/apr_version.mk   |   24 -
> > ext_libraries/apr/makefile.mk  |  128 --
> > ext_libraries/apr/prj/build.lst|3 -
> > ext_libraries/apr/prj/d.lst|   24 -
> > ext_libraries/serf/NULbytes.patch  |  313 
> > ext_libraries/serf/makefile.mk |  134 --
> > ext_libraries/serf/prj/build.lst   |3 -
> > ext_libraries/serf/prj/d.lst   |   12 -
> > ext_libraries/serf/serf-1.2.1.ldl.patch|   11 -
> > ext_libraries/serf/serf-1.2.1.libs.patch   |   11 -
> > ext_libraries/serf/serf-1.2.1.logging.patch|   27 -
> > ext_libraries/serf/serf_version.mk |   24 -
> > ext_libraries/serf/win/Library_serf.mk |   89 -
> > ext_libraries/serf/win/Makefile|   30 -
> > ext_libraries/serf/win/Module_serf.mk  |   27 -
> > ext_libraries/serf/win/Package_inc.mk  |   27 -
[...]

-- 
Arrigo

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

Re: Dynamic OpenSSL causes Curl regression on *nix

[Arrigo Marchiori]

Dear All,

On Tue, Apr 23, 2024 at 04:48:13PM +, Damjan Jovanovic wrote:

[...]
> I've now verified it works on Windows too, and have pushed the commits to
> trunk.
> 
> Here they are, in case you want to cherry-pick:
> 
> commit f7b97bf7d9139c8b602d3da3aadbeef0631e39c1 (HEAD -> trunk,
> origin/trunk, origin/HEAD)
[...]
> commit e469ab6aed23a1b38f105a944997af16e61071d0

I cherry-picked the commits into AOO42X. I built that branch with our
Docker image and it seems to work fine, too!

The build can be downloaded from here:
https://home.apache.org/~ardovm/openoffice/linux/openoffice4-2024-04-27-x86_64-installed.tar.bz2

Cherry-picking was not a trivial task, because AOO42X was quite
behind. It still is, WRT Damjan's last work on 32 bit indices. One
step at a time... :-)

Best regards,
-- 
Arrigo

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

Re: Dynamic OpenSSL causes Curl regression on *nix

[Arrigo Marchiori]

Dear All,

On Tue, Apr 23, 2024 at 04:48:13PM +, Damjan Jovanovic wrote:

[...]
> I've now verified it works on Windows too, and have pushed the commits to
> trunk.
> 
> Here they are, in case you want to cherry-pick:
> 
> commit f7b97bf7d9139c8b602d3da3aadbeef0631e39c1 (HEAD -> trunk,
> origin/trunk, origin/HEAD)
[...]
> commit e469ab6aed23a1b38f105a944997af16e61071d0

I built trunk with our Docker image and it seems to work fine!
Good work, Damjan!

The build can be downloaded from here:
https://home.apache.org/~ardovm/openoffice/linux/openoffice4-2024-04-26-x86_64-installed.tar.bz2

Best regards,
-- 
Arrigo

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

Re: Dynamic OpenSSL causes Curl regression on *nix

[Arrigo Marchiori]

Hello Damjan, All,

replying to this other message.

On Mon, Apr 08, 2024 at 02:42:01PM +, Damjan Jovanovic wrote:

[...]
> Here's how you set RPATH in Curl:
> 
> ---snip---
> diff --git a/main/curl/makefile.mk b/main/curl/makefile.mk
> index 044bf4d8c9..ecef11820a 100644
> --- a/main/curl/makefile.mk
> +++ b/main/curl/makefile.mk
> @@ -59,6 +59,7 @@ curl_LDFLAGS+:=$(ARCH_FLAGS)
>  ssl_param=--with-ssl
>  .ELSE
>  ssl_param=--with-ssl=$(OUTDIR)
> +curl_LDFLAGS+=-Wl,-z,origin -Wl,-rpath,\\\$$\$$ORIGIN
>  PATCH_FILES+= curl-bundled_openssl.patch
>  .ENDIF
> 
> ---snip---
> 
> which gets libcurl.so to search for the OpenSSL dynamic libraries in its
> own directory before the system directories:
> 
> $ ldd solver/450/unxfbsdx.pro/lib/libcurl.so
> ...
> libssl.so.3 => /path/to/openoffice-git/main/solver/450/
> unxfbsdx.pro/lib/libssl.so.3 (0x299f766bc000)
> libcrypto.so.3 => /path/to/openoffice/openoffice-git/main/solver/450/
> unxfbsdx.pro/lib/libcrypto.so.3 (0x299f77747000)

It works under Linux too!

If we want to use the dynamically linked OpenSSL, then, we have to
amend 0ca5b4b7b8e66fbc937f89173ce45fcc179e72b3 and have
main/scp2/source/ooo/file_library_ooo.scp include "libssl.so.3" and
"libcrypto.so.3" instead of "libssl.so" and "libcrypto.so".

I think the same should happen under FreeBSD, so you may want to
commit all these edits together after testing them?

Next step will be asking p11-kit for the CA certificates, as you
proposed here:
https://lists.apache.org/thread/3rb1t9jf5fnp4nfxr2z9dxmzt9l61tjq
otherwise Linux builds may be unable to validate certificate chains,
unfortunately.

Best regards,
-- 
Arrigo

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

Re: Dynamic OpenSSL causes Curl regression on *nix

[Arrigo Marchiori]

Hello Damjan, All,

On Sun, Apr 07, 2024 at 05:22:43PM +, Damjan Jovanovic wrote:

> On Sun, Apr 7, 2024 at 2:26 PM Arrigo Marchiori  wrote:
> 
> > Hello Damjan, All,
> >
> > On Sun, Apr 07, 2024 at 01:53:08PM +, Damjan Jovanovic wrote:
> >
> > > Hi
> > >
> > > With Pedro Lino's help, I've discovered a serious regression, where Curl
> > > (and libraries that use Curl) can fail to load, because they've been
> > > dynamically linked to OpenSSL but cannot find the copy of OpenSSL shipped
> > > with OpenOffice.
> >
> > [big snip]
> >
> > [...]
> >
> > > When main/oox linked to internal OpenSSL, it did dynamically on Windows,
> > > and on *nix, dynamically to system OpenSSL, and statically to internal
> > > OpenSSL.
> >
> > I might have missed the end of this sentence: "statically to internal
> > OpenSSL".
> >
> > >
> > ---
> > > 2022-05-06, commit 0ca5b4b7b8e66fbc937f89173ce45fcc179e72b3
> > >
> > ---
> > > "Fix including OpenSSL dynamic libraries on Unix (#147)" by Arrigo.
> > >
> > > OpenSSL, on *nix, now starts delivering static and dynamic libraries, and
> > > packaging dynamic libraries at the end of the build.
> > > Curl continues using OpenSSL, but now since both static and dynamic
> > OpenSSL
> > > libraries are available, it favours the dynamic.
> > > main/oox still links to OpenSSL statically outside Windows.
> > > main/ucb still links to OpenSSL statically outside Windows.
> >
> > [...]
> >
> > > 
> > > CURL LOADS WRONG OPENSSL
> > > 
> > >
> > > Now the combination of these last 2 commits broke Curl (and possibly
> > python
> > > and redland as well) as follows:
> > > - Internal modules have their RPATH set to $ORIGIN (among others), and
> > thus
> > > always search for dependencies in the same directory as themselves at
> > > runtime.
> > > - Third-party modules usually do not set their RPATH. In libcurl.so, it's
> > > unset.
> > > - When only static libraries are present at link-time, the binary being
> > > linked, is linked to them statically. So before
> > > 0ca5b4b7b8e66fbc937f89173ce45fcc179e72b3, Curl was linking statically to
> > > OpenSSL.
> >
> > Apparently not. My purpose, with that commit, was to include the
> > OpenSSL libraries _linked by the AOO executable_, that were: dynamic.
> >
> > In other words, the SSL libraries were not linked statically when
> > building on my system. They were linked dynamically instead.
> >
> >
> What happens currently, with OpenSSL 3, if you revert most of
> 0ca5b4b7b8e66fbc937f89173ce45fcc179e72b3 (I think the makefile.mk change is
> still correct)? Does Curl still link to OpenSSL dynamically, or does it
> start linking statically? For me, on FreeBSD, it links statically.

Apparently, this is also happening on Linux.
After reverting 0ca5b4b7b8e66fbc937f89173ce45fcc179e72b3:

$ ldd solver/450/unxlngx6.pro/lib/libcurl.so
linux-vdso.so.1 (0x7ffe59dab000)
libidn2.so.0 => /usr/lib64/libidn2.so.0 (0x7f123640)
libzstd.so.1 => /usr/lib64/libzstd.so.1 (0x7f12362cf000)
libbrotlidec.so.1 => /usr/lib64/libbrotlidec.so.1 (0x7f123600)
libz.so.1 => /usr/lib64/libz.so.1 (0x7f12366f)
libdl.so.2 => /lib64/libdl.so.2 (0x7f12366eb000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x7f12366c5000)
libc.so.6 => /lib64/libc.so.6 (0x7f1235e09000)
libunistring.so.2 => /usr/lib64/libunistring.so.2 (0x7f1235a0)
libbrotlicommon.so.1 => /usr/lib64/libbrotlicommon.so.1 
(0x7f123560)
/lib64/ld-linux-x86-64.so.2 (0x7f1236c2e000)

OpenSSL libraries are not listed! They must be linked statically!

> > I think this thread excerpt explains it:
> > https://lists.apache.org/thread/3rvvgxnws9867krk75rw6bvhmds1t2co
> >
> >
> Is that horrible bug fixed now, or does Curl/OpenSSL still crash AOO in
> certain setups?

Now when I check for update I see a dialog box with the following
error message:

Status
  Checking for an update failed.
Description
  Error reading data from the Internet.
  Server error message: Problem with the SSL CA cert (path? access rights?).

I think that on trunk we had solved the crash, but automatic updates

Re: Dynamic OpenSSL causes Curl regression on *nix

[Arrigo Marchiori]

Hello Damjan, All,

On Sun, Apr 07, 2024 at 01:53:08PM +, Damjan Jovanovic wrote:

> Hi
> 
> With Pedro Lino's help, I've discovered a serious regression, where Curl
> (and libraries that use Curl) can fail to load, because they've been
> dynamically linked to OpenSSL but cannot find the copy of OpenSSL shipped
> with OpenOffice.

[big snip]

[...]

> When main/oox linked to internal OpenSSL, it did dynamically on Windows,
> and on *nix, dynamically to system OpenSSL, and statically to internal
> OpenSSL.

I might have missed the end of this sentence: "statically to internal
OpenSSL".

> ---
> 2022-05-06, commit 0ca5b4b7b8e66fbc937f89173ce45fcc179e72b3
> ---
> "Fix including OpenSSL dynamic libraries on Unix (#147)" by Arrigo.
> 
> OpenSSL, on *nix, now starts delivering static and dynamic libraries, and
> packaging dynamic libraries at the end of the build.
> Curl continues using OpenSSL, but now since both static and dynamic OpenSSL
> libraries are available, it favours the dynamic.
> main/oox still links to OpenSSL statically outside Windows.
> main/ucb still links to OpenSSL statically outside Windows.

[...]

> 
> CURL LOADS WRONG OPENSSL
> 
> 
> Now the combination of these last 2 commits broke Curl (and possibly python
> and redland as well) as follows:
> - Internal modules have their RPATH set to $ORIGIN (among others), and thus
> always search for dependencies in the same directory as themselves at
> runtime.
> - Third-party modules usually do not set their RPATH. In libcurl.so, it's
> unset.
> - When only static libraries are present at link-time, the binary being
> linked, is linked to them statically. So before
> 0ca5b4b7b8e66fbc937f89173ce45fcc179e72b3, Curl was linking statically to
> OpenSSL.

Apparently not. My purpose, with that commit, was to include the
OpenSSL libraries _linked by the AOO executable_, that were: dynamic.

In other words, the SSL libraries were not linked statically when
building on my system. They were linked dynamically instead.

I think this thread excerpt explains it:
https://lists.apache.org/thread/3rvvgxnws9867krk75rw6bvhmds1t2co

[...]

> ==
> LINK STATICALLY OR SET RPATH?
> ==
> 
> There are 2 ways to fix this:
> 1. Provide only static OpenSSL libraries at build and run time, to force
> Curl to link to OpenSSL statically.
> 2. Provide OpenSSL dynamically, but set RPATH to $ORIGIN in all binaries
> that use it (including Curl), so they can find the local OpenSSL copy that
> ships with OpenOffice.
> 
> Arrigo: why did you ever make OpenSSL deliver dynamic libraries? Were you
> planning to implement option 2?

Not at all. I just wanted to fix the problem of the (required) OpenSSL
libraries missing from the AOO distribution.

I now agree that 1. is the best solution, and that my commit including
the .so files was sort of a wrong solution to the problem.

Honestly, I don't know in detail what RPATH is and how to change it,
and I would like to adopt the simplest approach to the problem.

> Why was OpenOffice ever using option 1, always linking statically to
> OpenSSL on *nix? We can't tell from our Git log, because it was done before
> we got the code, and we don't have history going that far back. But if I
> had to guess, I would say that the OpenSSL API is unstable, and yet OpenSSL
> is widely used, and when different versions of OpenSSL (eg. one internal,
> one system) were loaded into memory by different dependencies, it led to
> conflicts.

That seems reasonable to me.

> Maybe it's safe to link to OpenSSL dynamically now?

I think that our ``official'' Linux build machines are quite outdated,
and for this reason it makes sense not to rely on their system
libraries.

I hope this helps making my intentions at the time more clear now.
Thank you for the efforts you are putting into this issue!

Best regards,
-- 
Arrigo

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

Re: Next blog post

[Arrigo Marchiori]

Dear All,

On Mon, Apr 01, 2024 at 09:18:07AM +0200, Arrigo Marchiori wrote:

[...]
> > I prepared a draft on our wiki at [1], so anyone can contribute to the
> > text.  I am no native English speaker, nor marketing expert... feel
> > free to correct it!
> > 
> > Can we sort out something in this weekend? It would be great to
> > publish, say, on April 2nd!
> 
> There is now a pull request at [2]. Merging it will cause the post to
> be published. As the post is dated 2 April, let us wait until tomorrow.
> 
> References:
>  
>  1: https://cwiki.apache.org/confluence/x/1gniEQ
>  2: https://github.com/apache/openoffice-project/pull/11

I pushed commit 6316c11 to the "main" branch of "openoffice-project"
but, apparently, the web site was not published.

Can someone please look into it?

Best regards,
-- 
Arrigo

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

Re: Next blog post

[Arrigo Marchiori]

Dear All,

On Fri, Mar 29, 2024 at 07:25:44PM +0100, Arrigo Marchiori wrote:

> Dear All,
> 
> trunk has seen quite a lot of work recently, and because it's trunk,
> it is proceeding in a somewhat hidden way.
> 
> Due to the fact that the last post on our blog is already 3 months
> old, I suggest we make a new post to just tell what it is going on
> behind the scenes.

[...]

> I prepared a draft on our wiki at [1], so anyone can contribute to the
> text.  I am no native English speaker, nor marketing expert... feel
> free to correct it!
> 
> Can we sort out something in this weekend? It would be great to
> publish, say, on April 2nd!

There is now a pull request at [2]. Merging it will cause the post to
be published. As the post is dated 2 April, let us wait until tomorrow.

References:
 
 1: https://cwiki.apache.org/confluence/x/1gniEQ
 2: https://github.com/apache/openoffice-project/pull/11

Best regards,
-- 
Arrigo

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

Back to the Future Initiative

[Arrigo Marchiori]

Dear All,

The Apache OpenOffice Development Team is proud to announce that the
next releases will introduce an important change: a text-only user
interface.

Read more:
https://openoffice.apache.org/blog/back-to-the-future-initiative.html

:-)
-- 
Arrigo

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

Re: Next blog post

[Arrigo Marchiori]

Hello Matthias, All,

On Sun, Mar 31, 2024 at 03:29:19PM +0200, Matthias Seidel wrote:

> Hi Arrigo,
> 
> Am 29.03.24 um 19:25 schrieb Arrigo Marchiori:
> > Dear All,
> > 
> > trunk has seen quite a lot of work recently, and because it's trunk,
> > it is proceeding in a somewhat hidden way.
> > 
> > Due to the fact that the last post on our blog is already 3 months
> > old, I suggest we make a new post to just tell what it is going on
> > behind the scenes.
> > 
> > The most relevant things that we I could list are the following:
> > 
> >   - OpenSSL upgrade (this is related to security, encryption
> > and digital signatures);
> > 
> >   - implementation of OOXML encryption (this helps compatibility with
> > other office suites);
> > 
> >   - fix of compilation errors under the latest Ubuntu (this helps
> > contributors build and test AOO on their systems)
> > 
> >   - allow pasting of vector graphics (this helps making prettier documents)
> > 
> >   - various fixes in documentation, help files and interface (this
> > makes the overall user experience smoother)
> > 
> >   - various spelling fixes in the source code and documentation (this
> > helps developers)
> > 
> >   - various code fixes and cleanups (this helps developers focus on
> > interesting things)
> > 
> > Some other commits look ``important'' but I cannot explain them and
> > need some help:
> > 
> >   * 00ab6c3f8bc46b7dee5058d1206cc64de18809de
> > Removing all High Contrast icons from 'Classic' icon set.
> 
> This is just a cleanup.
> 
> Preparation for the (planned) separation of icon sets.

Ok, do you think it is worth mentioning on the article at [1]?

> > I prepared a draft on our wiki at [1], so anyone can contribute to the
> > text.  I am no native English speaker, nor marketing expert... feel
> > free to correct it!
> > 
> > Can we sort out something in this weekend? It would be great to
> > publish, say, on April 2nd!
> > 
> > Comments and suggestions welcome.
> > 
> > Best regards.
> > 
> > References:
> > 
> >   1: https://cwiki.apache.org/confluence/x/1gniEQ
-- 
Arrigo

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

Next blog post

[Arrigo Marchiori]

Dear All,

trunk has seen quite a lot of work recently, and because it's trunk,
it is proceeding in a somewhat hidden way.

Due to the fact that the last post on our blog is already 3 months
old, I suggest we make a new post to just tell what it is going on
behind the scenes.

The most relevant things that we I could list are the following:

 - OpenSSL upgrade (this is related to security, encryption
   and digital signatures);

 - implementation of OOXML encryption (this helps compatibility with
   other office suites);

 - fix of compilation errors under the latest Ubuntu (this helps
   contributors build and test AOO on their systems)

 - allow pasting of vector graphics (this helps making prettier documents)

 - various fixes in documentation, help files and interface (this
   makes the overall user experience smoother)

 - various spelling fixes in the source code and documentation (this
   helps developers)

 - various code fixes and cleanups (this helps developers focus on
   interesting things)

Some other commits look ``important'' but I cannot explain them and
need some help:

 * 00ab6c3f8bc46b7dee5058d1206cc64de18809de
   Removing all High Contrast icons from 'Classic' icon set.

I prepared a draft on our wiki at [1], so anyone can contribute to the
text.  I am no native English speaker, nor marketing expert... feel
free to correct it!

Can we sort out something in this weekend? It would be great to
publish, say, on April 2nd!

Comments and suggestions welcome.

Best regards.

References:

 1: https://cwiki.apache.org/confluence/x/1gniEQ
-- 
Arrigo

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

Re: Bugzilla Improvement to fix confusion Fwd: New Open Office account?

[Arrigo Marchiori]

Hello All,

On Thu, Mar 28, 2024 at 11:48:03AM +1030, David wrote:

> I believe self service registration to Bugzilla has been disabled for
> several years - see for example
> https://www.mail-archive.com/dev@openoffice.apache.org/msg39684.html

Yes, and I agree that registration should be advertised in a clear way
on the homepage.

The current BZ entry page [1] is full of information (including the
wrong email address reported by John Silver).

> Dave Fisher wrote:
[...]
> > I think that at a minimum we should:
> > 
> > 1. Change the footer text on our bugzilla [...]
> > To
> > 
> > “For additional information about this Bugzilla instance including 
> > requesting an account please see [about Bug 
> > Tracking](https://openoffice.apache.org/bug-tracking.html 
> > }’

+1

I suggest this link should also be added below the search box,
before the "Apache OpenOffice (AOO) Bugzilla User's Guide" link.

> > 2. We can then add improvements to the bug-tracking page at any time.

+1

Best regards,
-- 
Arrigo

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

Re: sot module build failures with recent gcc

[Arrigo Marchiori]

Dear All,

just to close this thread: all major branches (AOO41X, AOO42X and
trunk) should now build with GCC 11.

For Linux users: this includes Ubuntu 22.04 LTS.

Best regards.

On Wed, Jan 17, 2024 at 08:08:05AM +0100, Arrigo Marchiori wrote:

> Dear All,
> 
> On Tue, Aug 01, 2023 at 11:57:09AM +0200, Peter Kovacs wrote:
> 
> > hello Don,
> > 
> > were you able to look into this, or the freeBsd volunteer.
> > 
> > I can try to put together a report for gcc if you still like that to be
> > done.
> 
> If you can carve out the necessary bits, and only them, and reproduce
> the problem, then it would be great IMHO.
> 
> Don, do we know if clang compiles correctly?
> 
> For what it's worth, I tried to work around this bug in this PR for AOO41X:
> https://github.com/apache/openoffice/pull/198
> 
> > Am 01.04.23 um 20:12 schrieb Arrigo Marchiori:
> > > Hello Don, All,
> > > 
> > > On Wed, Mar 29, 2023 at 11:58:06PM -0700, Don Lewis wrote:
> > > 
> > > > A FreeBSD user is trying to unbreak the ppc64 build and ran into an
> > > > issue with the sot module.  I dig into it pretty deeply and it looks to
> > > > me like a gcc bug.  It's reproducable in amd64.  It seems to affect
> > > > gcc10, gcc11, and gcc12 builds.  The build failure does not happen with
> > > > gcc9.
> > > > 
> > > > It is not limited to FreeBSD.  I get the same failure on Debian
> > > > bullseye:
> > > >   cc --version
> > > > cc (Debian 10.2.1-6) 10.2.1 20210110
> > > > Copyright (C) 2020 Free Software Foundation, Inc.
> > > > This is free software; see the source for copying conditions.  There is 
> > > > NO
> > > > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR 
> > > > PURPOSE.
> > > > 
> > > > [ build LNK ] Library/libsot.so
> > > > /usr/bin/ld: 
> > > > /home/dl/aoo/openoffice/main/solver/4111/unxlngx6.pro/workdir/CxxObject/sot/source/sdstor/ucbstorage.o:
> > > >  in function `UCBStorage_Impl::Init()':
> > > > ucbstorage.cxx:(.text+0x72b4): undefined reference to `non-virtual 
> > > > thunk to 
> > > > cppu::WeakImplHelper1::acquire()'
> > > > collect2: error: ld returned 1 exit status
> > > > 
> > > > 
> > > > The problem appears to be that gcc is getting confused when compiling
> > > > line 1884 of ucbstorage.cxx.  It ends up trying to call the thunk to the
> > > > acquire() method of a non-existent class.  That thunk isn't defined, so
> > > > the linker bombs on the undefined symbol.
> > > I reproduced it with OpenSUSE Linux Leap 15.4, using the provided gcc-10.
> > > 
> > > However, the problem seems to be at line 1879:
> > > 
> > > > > com::sun::star::uno::Reference < ::com::sun::star::io::XInputStream > 
> > > > > xInputStream( pHelper );
> > > It seems to compile if we split it as follows:
> > > 
> > > > > com::sun::star::uno::Reference < ::com::sun::star::io::XInputStream > 
> > > > > xInputStream;
> > > > > xInputStream = pHelper;
> > > This _should_ work as it is how method
> > > Reference UCBStorageStream_Impl::GetXInputStream()
> > > does: it returns an instance of Reference on which
> > > it calls calls operator= with a OInputStreamWrapper
> > > 
> > > I have no idea how to test this, though.
> > > 
> > > Can you please verify if the above restores compilation?
> > > 
> > > Best regards,
-- 
Arrigo

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

Re: MS Office 2010+ "Agile" encrypted OOXML documents are working now!

[Arrigo Marchiori]

Hello Damjan, all,

On Mon, Mar 18, 2024 at 06:10:01AM +, Damjan Jovanovic wrote:

> That's great. Thank you for testing.
> 
> My own tests also show it no longer crashes, both the Standard and Agile
> encryption are working now :).

Great job!

-- 
Arrigo

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

Re: MIME types for WMF/EMF

[Arrigo Marchiori]

Dear All,

On Sat, Feb 24, 2024 at 02:08:24PM +0100, Marcus wrote:

> Am 22.02.24 um 20:41 schrieb Pedro Lino:
> > > On 02/22/2024 4:01 PM WET Damjan Jovanovic  wrote:
> > 
> > > Should we change the MIME types to "image/wmf" and "image/emf"? We would
> > > presumably also keep aliases like "image/x-wmf" and "image/x-emf". 
> > > Inkscape
> > > can paste "image/x-emf". Should we keep the existing MIME types as aliases
> > > too, so we can copy and paste to and from LibreOffice?
> > 
> > +1 on changing  the MIME types to improve compatibility with Inkscape and 
> > other programs.
> > I'm not sure LO still uses the same types. In my experience copying from LO 
> > to AOO usually doesn't work that well (at least under Windows)
> 
> +1 to change MIME types and keep the aliases.

+1 for me too.

Best regards,
-- 
Arrigo

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

Re: Article in "The Register" on CUA

[Arrigo Marchiori]

Hello,

On Thu, Jan 25, 2024 at 01:17:13PM +0100, Matthias Seidel wrote:

> Hi All,
> 
> interesting article on CUA:
> 
> https://www.theregister.com/2024/01/24/rise_and_fall_of_cua/

Very informative IMHO. Thank you for sharing!

Another important, related concept is the Principle of Least
Astonishment:
https://en.wikipedia.org/wiki/Principle_of_least_astonishment

Best regarsd,
-- 
Arrigo

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

Re: sot module build failures with recent gcc

[Arrigo Marchiori]

Dear All,

On Tue, Aug 01, 2023 at 11:57:09AM +0200, Peter Kovacs wrote:

> hello Don,
> 
> were you able to look into this, or the freeBsd volunteer.
> 
> I can try to put together a report for gcc if you still like that to be
> done.

If you can carve out the necessary bits, and only them, and reproduce
the problem, then it would be great IMHO.

Don, do we know if clang compiles correctly?

For what it's worth, I tried to work around this bug in this PR for AOO41X:
https://github.com/apache/openoffice/pull/198

> Am 01.04.23 um 20:12 schrieb Arrigo Marchiori:
> > Hello Don, All,
> > 
> > On Wed, Mar 29, 2023 at 11:58:06PM -0700, Don Lewis wrote:
> > 
> > > A FreeBSD user is trying to unbreak the ppc64 build and ran into an
> > > issue with the sot module.  I dig into it pretty deeply and it looks to
> > > me like a gcc bug.  It's reproducable in amd64.  It seems to affect
> > > gcc10, gcc11, and gcc12 builds.  The build failure does not happen with
> > > gcc9.
> > > 
> > > It is not limited to FreeBSD.  I get the same failure on Debian
> > > bullseye:
> > >   cc --version
> > > cc (Debian 10.2.1-6) 10.2.1 20210110
> > > Copyright (C) 2020 Free Software Foundation, Inc.
> > > This is free software; see the source for copying conditions.  There is NO
> > > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR 
> > > PURPOSE.
> > > 
> > > [ build LNK ] Library/libsot.so
> > > /usr/bin/ld: 
> > > /home/dl/aoo/openoffice/main/solver/4111/unxlngx6.pro/workdir/CxxObject/sot/source/sdstor/ucbstorage.o:
> > >  in function `UCBStorage_Impl::Init()':
> > > ucbstorage.cxx:(.text+0x72b4): undefined reference to `non-virtual thunk 
> > > to cppu::WeakImplHelper1::acquire()'
> > > collect2: error: ld returned 1 exit status
> > > 
> > > 
> > > The problem appears to be that gcc is getting confused when compiling
> > > line 1884 of ucbstorage.cxx.  It ends up trying to call the thunk to the
> > > acquire() method of a non-existent class.  That thunk isn't defined, so
> > > the linker bombs on the undefined symbol.
> > I reproduced it with OpenSUSE Linux Leap 15.4, using the provided gcc-10.
> > 
> > However, the problem seems to be at line 1879:
> > 
> > > > com::sun::star::uno::Reference < ::com::sun::star::io::XInputStream > 
> > > > xInputStream( pHelper );
> > It seems to compile if we split it as follows:
> > 
> > > > com::sun::star::uno::Reference < ::com::sun::star::io::XInputStream > 
> > > > xInputStream;
> > > > xInputStream = pHelper;
> > This _should_ work as it is how method
> > Reference UCBStorageStream_Impl::GetXInputStream()
> > does: it returns an instance of Reference on which
> > it calls calls operator= with a OInputStreamWrapper
> > 
> > I have no idea how to test this, though.
> > 
> > Can you please verify if the above restores compilation?
> > 
> > Best regards,

-- 
Arrigo

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

Re: AOO crashes at start if Sitka*.ttc font

[Arrigo Marchiori]

Hello Matthias, All,

On Sat, Jan 13, 2024 at 09:46:57PM +0100, Matthias Seidel wrote:

> Hi Arrigo,
> 
> Am 13.01.24 um 21:36 schrieb Arrigo Marchiori:
> > Hello All,
> > 
> > Bug 128583 opened [1].
> > 
> > On Sat, Jan 13, 2024 at 11:58:59AM +0100, Matthias Seidel wrote:
> > 
> > > Am 13.01.24 um 11:55 schrieb Dick Groskamp:
> > > > Works for me on Windows 11. AOO 4.1.15 (Dutch)
> > > Yes, that ttc is distributed with Windows...
> > > 
> > > Seems to be Linux only? We might cross-check on macOS.
> > That would be a good idea.

I verified my last config.log on macOS. It says that fontconfig is not
used by that build. This means that the macOS builds are not affected
by this bug.

> > However, we are blatantly not following the suggestions from the
> > Fontconfig documentation [2], and we should fix that nevertheless.
> > 
> > The fix seems as easy as adding a single line:
> >FcDefaultSubstitute( pTestPattern );
> > after the instantiation of pTestPattern.
> > 
> > That seems to fix the crash. But then, the "Sitka" font does not seem
> > to show up in the selectors.
> 
> A ttc is not a single font but a font collection.
> 
> Maybe we have to add logic for that...

Fontconfig is used to _find_ installed fonts.  If the font does not
show up in the list, it is either not found (that would be
Fontconfig's problem) or not supported (and that's another library's
problem).

> > Let's fix this crash first.
> 
> Great!

It should be fixed in trunk, AOO41X and AOO42X now.

> A good candidate for AOO 4.1.16 I guess... ;-)

Heh, sure!

According to Murphy's law, important bugs are found shortly _after_
release, not before... ;-)

Best regards,
-- 
Arrigo

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

Re: AOO crashes at start if Sitka*.ttc font

[Arrigo Marchiori]

Hello All,

Bug 128583 opened [1].

On Sat, Jan 13, 2024 at 11:58:59AM +0100, Matthias Seidel wrote:

> Am 13.01.24 um 11:55 schrieb Dick Groskamp:
> > Works for me on Windows 11. AOO 4.1.15 (Dutch)
> 
> Yes, that ttc is distributed with Windows...
> 
> Seems to be Linux only? We might cross-check on macOS.

That would be a good idea.

However, we are blatantly not following the suggestions from the
Fontconfig documentation [2], and we should fix that nevertheless.

The fix seems as easy as adding a single line:
  FcDefaultSubstitute( pTestPattern );
after the instantiation of pTestPattern.

That seems to fix the crash. But then, the "Sitka" font does not seem
to show up in the selectors.

Let's fix this crash first.

References:
 1: https://bz.apache.org/ooo/show_bug.cgi?id=128583
 2: 
https://www.freedesktop.org/software/fontconfig/fontconfig-devel/fcfontmatch.html

Best regards,
-- 
Arrigo

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

Re: AOO crashes at start if Sitka*.ttc font

[Arrigo Marchiori]

Hello All,

On Sat, Jan 13, 2024 at 10:55:10AM -, Dick Groskamp wrote:

> Works for me on Windows 11. AOO 4.1.15 (Dutch)
> 
> On 2024/01/13 08:07:58 "Paweł (Tomasz)" wrote:
> > Hello
> > 
> > If there is any Sitka.ttc font in .fonts folder AOO crashes at start.
> > 
> > guest@me:~$ openoffice4
> > Application Error
> > 
> > Fatal exception: Signal 6

Confirmed on trunk on openSUSE Linux. Thank you for your report!

We will have to open a bug report with detailed information.

In fact, the crash is in fontconfig's FcFontMatch() function, called
from method FontCfgWrapper::addFontSet() in file
main/vcl/unx/generic/fontmanager/fontconfig.cxx

Best regards,
-- 
Arrigo

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

Re: [VOTE] Release AOO 4.1.15-RC2 as GA

[Arrigo Marchiori]

Hello All,

On Tue, Nov 28, 2023 at 10:45:34AM -0500, Jim Jagielski wrote:

> I am calling a VOTE on releasing the source and complimentary community 
> builds of Apache OpenOffice 4.1.15-RC2 as GA.
> 
> These artifacts can be found at:
> 
>https://dist.apache.org/repos/dist/dev/openoffice/4.1.15-RC2/
> 
> Please cast your vote:

The Release Candidate is good for production/GA:

[X] yes / +1
[ ] no / -1

My vote is based on:

[X] binding (member of PMC)
[ ] I have built and tested the RC from source on platforms
[ Linux x86-64, Windows ]
[X] I have tested the binary RC on platform [ Linux x86-64, Windows ]
 
Best regards,
-- 
Arrigo


signature.asc
Description: PGP signature

Re: [DISCUSS][VOTE] Release AOO 4.1.15-RC1 as GA

[Arrigo Marchiori]

Hello Jim, All,

On Sun, Nov 19, 2023 at 08:59:46AM -0500, Jim Jagielski wrote:

> Are there any patches or additions anyone thinks would be
> appropriate to add in for a RC2 or is RC1 "good enough"?

I suggest we build a -RC2 from the current head of AOO41X.

We would include the solution for bug 126680 [1], a long-standing
problem involving builds for non-latin Alphabets.

Best regards.

1: https://bz.apache.org/ooo/show_bug.cgi?id=126680
-- 
Arrigo

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

Re: [DISCUSS][VOTE] Release AOO 4.1.15-RC1 as GA

[Arrigo Marchiori]

Dear Matthias, All,

On Sat, Nov 11, 2023 at 09:51:42AM +0100, Matthias Seidel wrote:

[...]
> @All: There are still a lot of tasks open in our Release Schedule:
> 
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.15
> 
> If you want to participate, please volunteer!

I subscribed myself for CVE related stuff.

I added a missing task: after the announcement email, send
announcement emails for each new CVE.

I am not sure if I there is a template I should edit, so that this new
task will also be listed in next release schedule pages? There is a
"template" link but it leads to a non-existent page.

Best regards,
-- 
Arrigo

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

Re: Ugly UI [Was: "Roadmap"]

[Arrigo Marchiori]

Hello,

On Fri, Oct 06, 2023 at 11:14:41PM +0200, Marcus wrote:

[...]
> @All:
> Please have a look if that psart of text is OK or what should be written in
> another way.

Fixed on the wiki:
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.15+Release+Notes

Best regards,
-- 
Arrigo

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

Re: Ugly UI [Was: "Roadmap"]

[Arrigo Marchiori]

Hello All,

On Fri, Oct 06, 2023 at 07:18:37PM +0200, Marcus wrote:

> Am 06.10.23 um 18:39 schrieb Rory O'Farrell:
> > On Fri, 6 Oct 2023 18:31:01 +0200
> > Marcus  wrote:
> > 
> > > Am 06.10.23 um 18:02 schrieb Pedro Lino:
> > > > Hi Matthias
> > > > 
> > > > > On 10/06/2023 3:44 PM WEST Matthias Seidel 
> > > > >  wrote:
> > > > 
> > > > > > Does it mean we need to include this library in the installer?
> > > > > 
> > > > > Either bundle it (when possible) or include instructions in the 
> > > > > Release
> > > > > Notes.
> > > > 
> > > > If it's not possible to bundle it (due to the *Open* Source license!) 
> > > > would it be possible to create a library dependency (or something 
> > > > similar) so that it is automatically installed after?
> > > 
> > > I hope so, as this is a good way to get it installed when necessary.
> > > 
> > > > Adding manual instructions is a further complication. OpenOffice has 
> > > > mostly been abandoned by Linux users, adding further separate 
> > > > requirements is adding another reason not to install it...
> > > 
> > > Nevertheless is a hint is helpful. ;-)
> > > Therefore I've create new release notes for 4.1.15 and add a text at the
> > > end "For Linux Users":
> > > 
> > > https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.15+Release+Notes

+1 for mentioning it in the release notes.

> > > Help needed:
> > > I know how to check and install the library via RPM. But how to do it
> > > with the DEB package system?
> > 
> > Typically in a deb system the install command for package.deb is
> > 
> > sudo dpkg -i package.deb

I'd rather suggest:

sudo apt install libgdk-pixbuf-xlib-2.0-0

On Debian-based systems, apt fetches the package from the
distribution's archives, together with any missing dependencies, and
then install it.  It's more like the dnf comand.

dpkg only works on packages you already downloaded.
It's like the rpm command.

Best regards,
-- 
Arrigo

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

Ugly UI [Was: "Roadmap"]

[Arrigo Marchiori]

Hello All,

On Thu, Oct 05, 2023 at 11:49:34PM +0200, Matthias Seidel wrote:

> Am 05.10.23 um 23:25 schrieb Matthias Seidel:
> > Hi Marcus,
> > 
> > Am 05.10.23 um 23:17 schrieb Marcus:
> > > Am 05.10.23 um 21:25 schrieb Matthias Seidel:
> > > > Am 05.10.23 um 21:06 schrieb Marcus:
> > > > > Am 05.10.23 um 15:23 schrieb Matthias Seidel:
> > > > > > I would like to collect ideas for some kind of roadmap for AOO:
> > > > > > 
> > > > > >   - Release AOO 4.1.15 before the end of 2023. Branch
> > > > > > AOO41X is in good condition, but personally I would like
> > > > > > to have the "ugly UI" fixed on some Linux distribution.
> > > > > 
> > > > > I've no discussions about this in mind. Do you have the BZ
> > > > > issue(s) at hand?
> > > > 
> > > > No, I think it was discussed on a user list but more or less ignored.
> > > > 
> > > > I only recently moved from Ubuntu 16.04 to 22.04 and discovered
> > > > the "ugly UI". But everyone using a newer distribution with
> > > > Gnome should probably see it.
> > > 
> > > I've Fedora 36 with Gnome 43.1.
> > > How / where can I see what you mean?
> 
> Found a screenshot...
> 
> https://home.apache.org/~mseidel/bildschirmfoto_vom_2023-08-05_13-16-38.png

According to:
https://forum.openoffice.org/en/forum/viewtopic.php?t=103671
the solution is: install the libgdk-pixbuf-xlib package.

On Ubuntu Jammy, it is named libgdk-pixbuf-xlib-2.0-0

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

[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: facebook

[Arrigo Marchiori]

Hello All,

I am sorry for chiming in very late.

On Tue, Jul 04, 2023 at 02:36:21PM +0200, Matthias Seidel wrote:

> Hi Peter, All,
> 
> Am 02.07.23 um 17:35 schrieb Peter Kovacs:
> >
> > Am 02.07.23 um 16:03 schrieb Matthias Seidel:
> >> Hi Peter,
> >>
> >> Am 19.06.23 um 22:57 schrieb Peter Kovacs:
> >>> Hello all,
> >>>
> >>>
> >>> I have not logged into Facebook for quite some time. Can someone take
> >>> over?

Can it be shared?

I am no Facebook expert, but I was pulled into a sort of ``business''
account and now I can choose whether to impersonate myself or that
business.

This sort of sharing allows many people to cooperate in managing a
Facebook account.

Is it already so? Could we just share this burden instead of moving it
from a single person to another?

> >> If we have no volunteer for Facebook, we should shut that profile down
> >> sooner or later...
> > +1
> 
> That said, we should not remove the account, but simply state that it is
> not maintained actively.
> 
> Plus we should redirect users that look for help to our other resources...

+1

Sending ``canned'' replies to Facebook queries such as ``Write to the
dev@ mailing lists or to the forums'' could be a group effort.

What do you think?

Best regards,
-- 
Arrigo

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

Re: [Discussion] ODF 1.3 filter implementation strategy

[Arrigo Marchiori]

Dear All,

On Tue, Aug 22, 2023 at 05:23:50PM +0200, Matthias Seidel wrote:

> Hi Pedro,
> 
> Good find!
> 
> "OpenOffice" (exactly written like that) is a registered trademark of the
> ASF.
> 
> I think we need to add that to our list of trademark violations?

+1

If we wanted to follow this way, we should probably establish a
"Friends of OpenOffice" collective as Groovy did.

[...]
> > > [1] https://opencollective.com/friends-of-groovy#category-ABOUT

-- 
Arrigo

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

Re: blog migration

[Arrigo Marchiori]

Dear All,

the "Blog" link at the top-right corner of the homepage links to:
https://blogs.apache.org/ooo/
that is not valid.

I think that the correct URL should rather be:
https://openoffice.apache.org/blogpage.html

I made a "git grep blogs.apache.org" and this URL appears in a _lot_
of files; for this reason I refrained to try fixing this myself.

I also suggest to make:
https://openoffice.apache.org/blog/
redirect to the above, correct URL
(or maybe, make _this_ the correct URL, as it looks easier to type).

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: Install AOO via winget on Windows 10/11

[Arrigo Marchiori]

Hello,

adding volunteer@ mailing list because... we need a volunteer. Please
read below.

On Sat, Jun 03, 2023 at 08:32:10PM +0200, Matthias Seidel wrote:

> Hi,
> 
> FYI, I recently learned about using "winget".
> 
> This is Microsofts commandline package manager for Windows 10/11.

Nice!

> While the OpenOffice package information is still showing 4.1.13 [1]
[...]

I see anyone can open a pull request to update the package repository.

While I am glad this has happened since March 2021, I suggest we could
coordinate here further efforts.

Are there any volunteers for submitting the 4.1.14 release to
winget-pkgs ?

Once we learn how to do this, we could add a "task" in the release
planning document.

Best regards,
-- 
Arrigo

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

Re: blog migration

[Arrigo Marchiori]

Hello Peter, All,

On Mon, Jun 05, 2023 at 12:14:12AM +0200, Peter Kovacs wrote:

> I have merged the migration.

Well done!

Best regards,
-- 
Arrigo

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

Re: Executable flag

[Arrigo Marchiori]

Hello Matthias, All,

On Thu, Jun 01, 2023 at 04:57:39PM +0200, Matthias Seidel wrote:

> Hi All,
> 
> How about all those .java files in
> 
> main/ooxml/source/framework/OOXMLViewer/src/org/apache/openoffice/ooxml/viewer/
> 
> ?

I think they shall _not_ be executable as well.

Best regards.
-- 
Arrigo

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

Re: [discussion] looking for Contributor "campaign"

[Arrigo Marchiori]

Hello Matthias, All,

On Sun, May 28, 2023 at 01:34:56PM +0200, Matthias Seidel wrote:

> Hi All,
> 
> Apart from the major task to write a Readme... ;-)
> 
>  - We had some files encoded with CRLF, maybe there are still others?
>  - We have a lot of mixed indentation (spaces+tabs) that produce
> warnings with newer compilers.
>  - We still have a big amount of German comments that need to be translated.
>  - We have a vim modeline in some files, shouldn't we use them more?
>  - ...
> 
> I really don't know where to stop here!
> 
> Before we talk about a timeline, let's do the basic tasks...  A
> "cleaner" source code may also attract volunteers/developers.
> 
> What do others think?

IMHO, the highest hurdle for new contributors, today, is our build
system, especially under Windows.

That is why I tried to put some efforts into the scons-build branch
some time ago.

The ``task difficulty'' is very high, though.

Best regards,
-- 
Arrigo

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

Re: Executable flag

[Arrigo Marchiori]

Hello Matthias, All,

On Thu, May 25, 2023 at 04:08:59PM +0200, Matthias Seidel wrote:

> Hi all,
> 
> By accident I found two cxx files that had the executable flag set. I
> think that does not make sense.

+1

> But there were lot more and I removed their flags now with 2 commits.
> 
> Some are still left, do the files in /extras/source/gallery need to be
> executable?

All .jpg, .bmp, .mk, .svg, .thm, .sdg, .sdv files should IMHO not be
executable. And also .cxx and .hxx as you already noted.

> Our source really needs more maintenance...

Sure.

Best regards,
-- 
Arrigo

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

Re: [discussion] looking for Contributor "campaign"

[Arrigo Marchiori]

Hello Matthias, All,

On Sat, May 20, 2023 at 05:01:36PM +0200, Matthias Seidel wrote:

> Hi all,
> 
> Am 20.05.23 um 12:17 schrieb Peter Kovacs:
> >
> > Am 20.05.23 um 10:10 schrieb Arrigo Marchiori:
> >> Hello All,
> >>
> >> On Thu, Apr 27, 2023 at 10:49:53PM +0200, Matthias Seidel wrote:
> >>
> >>> Hi Peter,
> > [...]
> >>>
> >>> After all, we are here to maintain and develop OpenOffice...
> >> Isn't the "Help Wanted" page already a good list?
> >> https://cwiki.apache.org/confluence/display/OOOUSERS/Help+Wanted
> >>
> >> It is not in the form of a roadmap, but it already contains a lot of
> >> content, well structured.
> >
> > I did not have this page on my mind. I have various points not noted,
> > and I would not rate the difficulties of those.

The difficulty rating is a way to help newcomers understand what kind
of task they should start with.

Tasks whose difficulty is hardly estimated could go into an "Undecided
difficulty" list... ;-)

> > For example Damjan has written a patch, for getting rid of expat. but
> > we need to implement a small part. However
> >
> > the patch is on the list but not as PR or in code.

This sounds ``very challenging'' to me ;-)

[...]
> >> ...and just because we are discussing README.md I would appreciate if
> >> someone added it to the AOO41X and AOO42X branches! They are worth at
> >> least a minimal description...
> > also +1
> 
> I added a short description at least for AOO41X now.

Thank you!

While re-reading my own paragraph above, I think it sounded
polemical. This was not my intention, I apologize. My intention was to
ask for something I did not think I could do very well.

Best regards,
-- 
Arrigo

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

Re: Wizard for Letter / Fax — unexpected security warning

[Arrigo Marchiori]

Hello Czesław, All,

On Fri, May 12, 2023 at 08:23:17AM +0200, Czesław Wolański wrote:

> Hi All,
> 
> Version 4.1.14 seems to have gone a bit too far in terms of security
> measures.
> 
> Prerequisite: "Macro security" set to "Low".
> 
> 1. Choose File ⟶  Wizards ⟶ Letter (or ⟶ Fax).
> 2. In the dialog press "Finish".
> 
> AOO creates a Writer document and displays a security warning about the
> template.

Thank you for this report.

In fact, those templates request certain macros to be run when the
document is loaded.

I could find for example:
 - Template.Correspondence.Database
 - Template.Correspondence.Placeholder
but there may be more.

XML-wise, they are loaded by means of "event listeners"; I am not sure
it is possible to see/edit them using the OpenOffice dialogs.

Best regards,
-- 
Arrigo

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

Re: Updated graphics for AOO

[Arrigo Marchiori]

Hello Matthias, All,

On Sat, Apr 22, 2023 at 08:01:07PM +0200, Matthias Seidel wrote:

> Hi All,
> 
> During the last weeks I did some work on the handles
> (markers/cropmarkers) for AOO.
[...]

Please forgive my ignorance... how can we see these new cropmarkers?
When are they displayed?

Best regards,
-- 
Arrigo

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

Re: [discussion] looking for Contributor "campaign"

[Arrigo Marchiori]

Hello All,

On Thu, Apr 27, 2023 at 10:49:53PM +0200, Matthias Seidel wrote:

> Hi Peter,
> 
> Am 22.04.23 um 09:22 schrieb Peter Kovacs:
> > Hi all,
> >
> > I came across
> >
> > https://dev.to/opensauced/whos-looking-for-open-source-contributors-week-38-16e9
> >
> >
> > And it got me thinking. I would like to advertise for help. But so far
> > our on boarding quota is really bad, since we relay on the volunteers
> > long term motivation.

+1, because it takes a very long time to be able to actually work on
AOO, IMHO.

> > so i would like to call for help on specific tasks. These tasks are
> > promoted in a contribute.md file. I would like to break down tasks in
> > small steps so volunteer engagement is quickly achieved.
> >
> > And i would like to build feature roadmaps. So we can promote them,
> > and become more structured. Of course this approach is to be seen as
> > an addition on how we engage today.
> 
> Yes, something like a roadmap would be great!
> 
> After all, we are here to maintain and develop OpenOffice...

Isn't the "Help Wanted" page already a good list?
https://cwiki.apache.org/confluence/display/OOOUSERS/Help+Wanted

It is not in the form of a roadmap, but it already contains a lot of
content, well structured.

> > What do you think?

A "Contributing" paragraph in README.md with a link to the above page
could already be a step forward.

Then, we could focus on making that page better, more up to date, in
tabular form etc.

...and just because we are discussing README.md I would appreciate if
someone added it to the AOO41X and AOO42X branches! They are worth at
least a minimal description...

Best regards,
-- 
Arrigo

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

Re: Changes proposal for the future AOO 5.0.0

[Arrigo Marchiori]

Hello All,

replying mid-thread.

On Sat, Apr 22, 2023 at 04:41:37PM +0200, Corentin Verbrèghe wrote:

> Hello,
> I think that making my proposal an extension of AOO is a bad idea, I rather
> thought that it should be part of the software because the problem of an
> extension is that it does not install automatically. Moreover, this could
> improve the gallery to make it much more interesting and complete, with an
> almost infinite choice of images, illustrations, icons and even audio files
> available for everyone. The fact that it is not an extension will make AOO
> more interesting and useful compared to before and other software such as
> LibreOffice.

Let's not forget that extensions could be embedded within the official
installer.

Choosing between an extension and "something else" (a module?) is IMHO
a choice about how to _develop_ this.

By keeping a separate code base from the AOO main trunk, we could have
more focused development.

By using an extension, we would have the possibility to update that
``part of AOO'' without recompiling the full AOO distribution, during
the development.

I also expect that developing an extension will be easier than
learning how the AOO code is organized, what classes do what etc.  And
maybe we may not even need C++, but rather Basic, Python or other more
accessible programming languages.

I hope this makes sense, and I encourage anyone interested to start
reading this:
https://wiki.openoffice.org/wiki/Extensions_development

Best regards,
-- 
Arrigo

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

Re: Compile Linux x86

[Arrigo Marchiori]

Hello Pedro,

On Sun, Apr 16, 2023 at 10:32:03AM +0100, Pedro Lino wrote:

> Hi all
>  
> This is very a basic question for a programmer but as "developer" I could not 
> find any clear documentation: how do I compile an x86 build in Linux?
>  
> I have managed to build an x64 Linux installer following the steps in
> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
> but
>  
> 1) When compiling on a physical PC (aka metal) do I need an x86 CPU to build 
> an x86 build?
>  
> if the answer to 1) is no then
>  
> 2) Do I need and x86 Linux OS?

For what it's worth, I am using a virtual machine, in which I
installed 32 bit Linux, for testing 32 bit builds. Our release builds
are done in VM's as well.

> if not then, how do I get shell script to setup an x86 environment? I can't 
> understand the instructions to create the LinuxX86Env.Set.sh script needed 
> for the unxlngi6 platform...

If you have an x86_64 Linux system (either bare metal or virtual,
should make no difference) you should be able to build for 32 bit by
forcing parameter "-m32" to the compiler.

It should be enough to instruct the configure script to use proper
CFLAGS and CXXFLAGS:

$ CFLAGS="-m32" CXXFLAGS="-m32" ./configure [other parameters]

I cannot confirm this will work, because the build system is very
complex, but that is how I would do for other software projects.

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: scons-build branch

[Arrigo Marchiori]

Hello Peter, Yury, All,

replying to both messages inline.

On Tue, Apr 18, 2023 at 05:24:58AM +, Peter kovacs wrote:

> Hello Yury
> 
> You can build more or less every module on its own. If there is a dependency 
> module then you need the inc header files and the module binary to link 
> against.
> At least this is my understanding on the build architecture.

Yes, that is how it works.

[...]

> Am 18. April 2023 06:49:03 MESZ schrieb Yury Tarasievich:
> >On 16/04/2023 16:21, Arrigo Marchiori wrote:
> >> I just pushed some commits to the scons-build branch, in which I am
> >> attempting to write _from scratch_ the SConscripts to build some
> >> modules.
> >...
> >> The only module that _seems_ to build is xml2cmp, but only under Linux
> >> so far.
> >
> >Is it because of modules dependencies, would you say, or because toolchain 
> >and codebase are out of sync w/r to language features used and similar 
> >issues?

The xml2cmp does not need other modules.

In practice, I took the list of modules, in the order they are built,
and started with the first ones.

I am working on a system (Linux openSUSE Leap 15.4) that is able to
build trunk and AOO41X (with minor edits), so I can exclude
toolchain-related problems.

> > Last time I looked at that branch, the transition of build descriptions to 
> > scons hadn't been completed. 

This thread is about bringing the transition forward ;-)

> > Can you even build AOO modules one by one, aren't they all inter-dependent?

I must add to my reply above, that the current scripts isolate SCons'
build artifacts, installing them all into a subdirectory named
"scons". This avoids mixing Scons and GBuild output, and IMHO it is a
good idea.

The current structure of the ``solver'' is... complex, and I hope this
migration could become and occasion to make it simpler and/or more
efficient.

Best regards,
-- 
Arrigo

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

scons-build branch

[Arrigo Marchiori]

Dear All,

I just pushed some commits to the scons-build branch, in which I am
attempting to write _from scratch_ the SConscripts to build some
modules.

>From a ``didactical'' point of view, I thought that this way could be
better for newbies like me, to get a grasp on SCons' internals, rather
than working on Gotoscons or other automatic converters.

Moreover, I thought that some steps _have_ to be done, if we want to
get anywhere... ;-)

The only module that _seems_ to build is xml2cmp, but only under Linux
so far.

Any comments (or also just corrections) to the commits are
appreciated.

Best regards,
-- 
Arrigo

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

Re: sot module build failures with recent gcc

[Arrigo Marchiori]

Hello Don, All,

On Wed, Mar 29, 2023 at 11:58:06PM -0700, Don Lewis wrote:

> A FreeBSD user is trying to unbreak the ppc64 build and ran into an
> issue with the sot module.  I dig into it pretty deeply and it looks to
> me like a gcc bug.  It's reproducable in amd64.  It seems to affect
> gcc10, gcc11, and gcc12 builds.  The build failure does not happen with
> gcc9.
> 
> It is not limited to FreeBSD.  I get the same failure on Debian
> bullseye:
>  cc --version
> cc (Debian 10.2.1-6) 10.2.1 20210110
> Copyright (C) 2020 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> [ build LNK ] Library/libsot.so
> /usr/bin/ld: 
> /home/dl/aoo/openoffice/main/solver/4111/unxlngx6.pro/workdir/CxxObject/sot/source/sdstor/ucbstorage.o:
>  in function `UCBStorage_Impl::Init()':
> ucbstorage.cxx:(.text+0x72b4): undefined reference to `non-virtual thunk to 
> cppu::WeakImplHelper1::acquire()'
> collect2: error: ld returned 1 exit status
> 
> 
> The problem appears to be that gcc is getting confused when compiling
> line 1884 of ucbstorage.cxx.  It ends up trying to call the thunk to the
> acquire() method of a non-existent class.  That thunk isn't defined, so
> the linker bombs on the undefined symbol.

I reproduced it with OpenSUSE Linux Leap 15.4, using the provided gcc-10.

However, the problem seems to be at line 1879:

> > com::sun::star::uno::Reference < ::com::sun::star::io::XInputStream > 
> > xInputStream( pHelper );

It seems to compile if we split it as follows:

> > com::sun::star::uno::Reference < ::com::sun::star::io::XInputStream > 
> > xInputStream;
> > xInputStream = pHelper;

This _should_ work as it is how method
Reference UCBStorageStream_Impl::GetXInputStream()
does: it returns an instance of Reference on which
it calls calls operator= with a OInputStreamWrapper

I have no idea how to test this, though.

Can you please verify if the above restores compilation?

Best regards,
-- 
Arrigo

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

Re: GNU make 4.4 under Cygwin64

[Arrigo Marchiori]

Dear All,

On Sun, Mar 12, 2023 at 12:01:01AM +0100, Arrigo Marchiori wrote:

> Hello Matthias, All,
> 
> apparently, compatibility with the latest GNU Make is not yet ensured.
> 
> On Tue, Dec 06, 2022 at 01:20:17PM +0100, Matthias Seidel wrote:
> 
> > And in the end it doesn't build:
> > 
> > ---
> > 
> > =
> > Building module slideshow
> > =
> > 
> > Entering /cygdrive/c/Source/openoffice/main/slideshow/prj
> > 
> > cd .. && make -s -r -j1   && make -s -r deliverlog
> > [ build CXX ] slideshow/source/engine/slideshowimpl
> > slideshowimpl.cxx
> > c:/Source/openoffice/main/slideshow/source/engine/slideshowimpl.cxx(25)
> > : fatal error C1083: Cannot open include file:
> > 'precompiled_slideshow.hxx': No such file or directory
> > make: *** No rule to make target
> > '/cygdrive/c/Source/openoffice/main/solver/420/wntmsci12.pro/workdir/CxxObject/slideshow/source/engine/slideshowimpl.o',
> > needed by
> > '/cygdrive/c/Source/openoffice/main/solver/420/wntmsci12.pro/workdir/LinkTarget/StaticLibrary/sldshw_s.lib'.
> >  
> > Stop.
> > dmake:  Error code 2, while making 'all'
> [...]
> 
> This seems to be a different problem than addressed with PR #175.
> 
> The slideshow module seems to fail because the slideshowimpl.cxx file
> is not provided the correct include path.
> 
> There are two Makefiles, inside module slideshow, where the
> slideshowimpl "object" is listed:
> 
>  - StaticLibrary_sldshw_s.mk: that contains the proper build
>parameters passed to:
>  * gb_StaticLibrary_add_api,
>  * gb_StaticLibrary_set_include.
> 
>  - Library_slideshow.mk that does not list any of the above.
> 
> If I add to the second file the calls to gb_Library_add_api and
> gb_Library_set_include, with the same parameters as the static library
> counterparts, then the compilation seems to be successful.
> 
> If the above is not clear, I can open a PR proposing the above edits.

PR just opened:
https://github.com/apache/openoffice/pull/176

It builds now, but I am not sure this is the correct solution for this
problem.

> But the question is: why is the same "object" "slideshowimpl" listed
> in two files? The second has a comment stating:
> 
>   # List this file again, even though it's in the static lib, so that
>   # component_getFactory and component_getImplementationEnvironment are 
> exported:
>
[...]

Best regards,
-- 
Arrigo

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

Re: GNU make 4.4 under Cygwin64

[Arrigo Marchiori]

Hello Matthias, All,

apparently, compatibility with the latest GNU Make is not yet ensured.

On Tue, Dec 06, 2022 at 01:20:17PM +0100, Matthias Seidel wrote:

> And in the end it doesn't build:
> 
> ---
> 
> =
> Building module slideshow
> =
> 
> Entering /cygdrive/c/Source/openoffice/main/slideshow/prj
> 
> cd .. && make -s -r -j1   && make -s -r deliverlog
> [ build CXX ] slideshow/source/engine/slideshowimpl
> slideshowimpl.cxx
> c:/Source/openoffice/main/slideshow/source/engine/slideshowimpl.cxx(25)
> : fatal error C1083: Cannot open include file:
> 'precompiled_slideshow.hxx': No such file or directory
> make: *** No rule to make target
> '/cygdrive/c/Source/openoffice/main/solver/420/wntmsci12.pro/workdir/CxxObject/slideshow/source/engine/slideshowimpl.o',
> needed by
> '/cygdrive/c/Source/openoffice/main/solver/420/wntmsci12.pro/workdir/LinkTarget/StaticLibrary/sldshw_s.lib'.
>  
> Stop.
> dmake:  Error code 2, while making 'all'
[...]

This seems to be a different problem than addressed with PR #175.

The slideshow module seems to fail because the slideshowimpl.cxx file
is not provided the correct include path.

There are two Makefiles, inside module slideshow, where the
slideshowimpl "object" is listed:

 - StaticLibrary_sldshw_s.mk: that contains the proper build
   parameters passed to:
 * gb_StaticLibrary_add_api,
 * gb_StaticLibrary_set_include.

 - Library_slideshow.mk that does not list any of the above.

If I add to the second file the calls to gb_Library_add_api and
gb_Library_set_include, with the same parameters as the static library
counterparts, then the compilation seems to be successful.

If the above is not clear, I can open a PR proposing the above edits.

But the question is: why is the same "object" "slideshowimpl" listed
in two files? The second has a comment stating:

  # List this file again, even though it's in the static lib, so that
  # component_getFactory and component_getImplementationEnvironment are 
exported:

This seems to be broken now, with the latest GNU Make.

I hope this makes sense.

Best regards,
-- 
Arrigo

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

Re: Review from Microsoft Store

[Arrigo Marchiori]

Hello Matthias, All,

On Thu, Mar 09, 2023 at 02:34:22PM +0100, Matthias Seidel wrote:

> Just FYI:
> 
> This user is not willing to give more details...
> 
> I am pretty sure the problem is that his AntiVirus program blocked
> OpenOffice and that his files are NOT password protected.
> 
> Maybe a future update of his AntiVirus program will "solve" the problem...
> 
> Case closed! ;-)

Thank you for taking care of this!

Best regards,
-- 
Arrigo

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

Re: GNU make 4.4 under Cygwin64

[Arrigo Marchiori]

Hello Matthias, All,

On Thu, Feb 23, 2023 at 04:42:26PM +0100, Matthias Seidel wrote:

> Hi Arrigo, All,
> 
> Am 23.02.23 um 16:29 schrieb Arrigo Marchiori:
> > Hello Matthias, All,
> >
> > On Sat, Dec 17, 2022 at 01:51:43PM +0100, Matthias Seidel wrote:
> >
> >> Hi all,
> >>
> >> It would be great if someone could have an eye on the precompiled
> >> headers in module slideshow that are a "problem" for make 4.4.
> > Apparently, Make 4.4 is the only version available now.
> > We have to tackle this.
> 
> Oh, back-level now only possible to 4.4.0.91-Test. Luckily I am still on
> 4.3.1.
> 
> With make 4.4.0.90 the same problem occurred.
> 
> >
> > Did you encounter this problem with trunk or with AOO41X?
> 
> Both (I think...)!

I have been working on trunk and found a possible fix.
See the "make44" branch.

A similar fix should work for AOO41X.

I will report the results of my tests. When ready, I will open a PR.

Best regards,
-- 
Arrigo

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

Re: Fwd: Updated: make-4.4.1-1 & -2

[Arrigo Marchiori]

Hello Matthias,

On Thu, Mar 02, 2023 at 05:43:22PM +0100, Matthias Seidel wrote:

> Hi All,
> 
> Can anyone test if we can build with the updated make on Windows?
> 
> I don't want to risk it! If not there is no way back... ;-)

We seem to have the same problems with GNU Make 4.4.1 as with GNU Make
4.4.

I'll discuss my proposed fix in the other thread.

Best regards,
-- 
Arrigo

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

Re: GNU make 4.4 under Cygwin64

[Arrigo Marchiori]

Hello Matthias, All,

On Sat, Dec 17, 2022 at 01:51:43PM +0100, Matthias Seidel wrote:

> Hi all,
> 
> It would be great if someone could have an eye on the precompiled
> headers in module slideshow that are a "problem" for make 4.4.

Apparently, Make 4.4 is the only version available now.
We have to tackle this.

Did you encounter this problem with trunk or with AOO41X?

> Am 06.12.22 um 13:20 schrieb Matthias Seidel:
> > And in the end it doesn't build:
> >
> > ---
> >
> > =
> > Building module slideshow
> > =
> >
> > Entering /cygdrive/c/Source/openoffice/main/slideshow/prj
> >
> > cd .. && make -s -r -j1   && make -s -r deliverlog
> > [ build CXX ] slideshow/source/engine/slideshowimpl
> > slideshowimpl.cxx
> > c:/Source/openoffice/main/slideshow/source/engine/slideshowimpl.cxx(25)
> > : fatal error C1083: Cannot open include file:
> > 'precompiled_slideshow.hxx': No such file or directory
> > make: *** No rule to make target
> > '/cygdrive/c/Source/openoffice/main/solver/420/wntmsci12.pro/workdir/CxxObject/slideshow/source/engine/slideshowimpl.o',
> > needed by
> > '/cygdrive/c/Source/openoffice/main/solver/420/wntmsci12.pro/workdir/LinkTarget/StaticLibrary/sldshw_s.lib'.
> >  
> > Stop.
> > dmake:  Error code 2, while making 'all'
> >
> > 1 module(s):
> >     slideshow
> > need(s) to be rebuilt
> >
> > Reason(s):
> >
> > ERROR: error 65280 occurred while making
> > /cygdrive/c/Source/openoffice/main/slideshow/prj
> >
> > When you have fixed the errors in that module you can resume the build
> > by running:
> >
> >     build --from slideshow
> >
> > ---
[...]
-- 
Arrigo

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

Testing AOO on macOS

[Arrigo Marchiori]

Dear All,

for some reason, our Catalina-based macMini shared instance is giving
me problems when testing AOO.

Buttons do not seem to behave properly.

For example: once AOO opens, I cannot click on "Text document" to open
a new document. My clicks seem to be ignored.

The menus work: I can click File -> New and have a new document.

I believe that these problems are given by the remote control program
I am using. I would be grateful if anyone with a ``physical'' mac in
their hands -- or other users of our shared macMini as well -- could
confirm that the UI of the current RC is working as expected.

Thank you in advance and best regards,
-- 
Arrigo


signature.asc
Description: PGP signature

Re: [VOTE] Release AOO 4.1.14-RC1 as GA

[Arrigo Marchiori]

On Mon, Feb 13, 2023 at 07:38:51AM -0500, Jim Jagielski wrote:

> I am calling a VOTE on releasing the source and complimentary community 
> builds of
> Apache OpenOffice 4.1.14-RC1 as GA.
> 
> These artifacts can be found at:
> 
>https://dist.apache.org/repos/dist/dev/openoffice/4.1.14-RC1/
> 
> Please cast your vote:

The Release Candidate is good for production/GA:

   [X] yes / +1

   [ ] no / -1
 
My vote is based on

   [X] binding (member of PMC)

   [X] I have built and tested the RC from source on platforms:
   [ Linux (x86_64 and x86), Windows, macOS ]

   [X] I have tested the binary RC on platform [ Linux x86_64 ]

SHA sums and GPG signatures were verified for sources and Linux binaries.

Linux binaries were built using the build scripts from SVN (Linux x86
required a small modification due to libgio not present on Centos 5
x86).

macOS build was conducted on macOS Catalina system.

Best regards,
-- 
Arrigo

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

Re: 41X fails to build in Ubuntu 18.04 (was Re: Fails to build on Pop!_OS 18.04)

[Arrigo Marchiori]

Dear All,

On Tue, Jan 24, 2023 at 11:10:21PM +, Pedro Lino wrote:

> > On 01/24/2023 9:59 PM WET Peter Kovacs  wrote:
> 
> > strange. I have:
> > 
> > /usr/lib/jvm/java-8-openjdk-amd64/lib/amd64/libjawt.so
> > /usr/lib/jvm/java-8-openjdk-amd64/include/jawt.h
> > /usr/lib/jvm/java-8-openjdk-amd64/include/linux/jawt_md.h
> > /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/libjawt.so
> 
> I also have them on my "old" disk with Ubuntu 18.04 (installed in April 
> 2018). This one was installed last week.
>

Wild guess: did you install the "jdk" package?
You may have installed the "jre" only.

On Ubuntu 18.04 the package containing the libraries (.so files) is
"openjdk-8-jdk-headless", whereas the package containing the header
files is "openjdk-8-jdk".

I hope this helps. If not... sorry for the noise!

Best regards,
-- 
Arrigo

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

Re: Happy...

[Arrigo Marchiori]

On Sun, Jan 01, 2023 at 07:39:47PM +0100, Matthias Seidel wrote:

> ...new year! ;-)

+1

(I know I am sort of late, but... we are still in 2023, aren't we? :-)

Best regards,
-- 
Arrigo

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

Re: No OpenOffice Devroom at FOSDEM 2023

[Arrigo Marchiori]

On Fri, Dec 30, 2022 at 03:13:20PM -0500, Carl Marcum wrote:

> Hi Andrea,
> 
> On 12/30/22 12:52 PM, Andrea Pescetti wrote:
> > You've often seen me spamming this list in the last week of the year in
> > recent years calling for FOSDEM submissions, but I am not doing it this
> > time... since there will be no OpenOffice devroom at FOSDEM 2023.
> > 
> > With the return to physical events, rooms are limited and FOSDEM tries
> > to rotate projects, so OpenOffice, despite the request we filed, didn't
> > make the list this year but it might find space again in future.
> > 
> > We should be grateful to the FOSDEM organizers for having offered us a
> > room for several years, without requesting (or receiving, for that
> > matter) any money or financial benefit from the Apache OpenOffice
> > project.
> > 
> > Still, there will be other ASF projects represented in different
> > devrooms and possibly an ASF booth too... so there are still reasons to
> > consider attending FOSDEM
> > 
> Thanks for the information and for all that you have done for the project 
> with FOSDEM.
> The remote format worked good for me for a couple years and I'm glad I had 
> the opportunity to participate with talks where I wouldn't have been able to 
> otherwise.

Me too! Thank you!

-- 
Arrigo

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

Re: Hyperlink Warning Message for mp4 file

[Arrigo Marchiori]

Hello,

On Mon, Aug 01, 2022 at 11:08:33PM +0200, Matthias Seidel wrote:

> Hi,
> 
> Am 01.08.22 um 20:20 schrieb Czesław Wolański:
> > Hi,
> >
> > The topic "Macro warning - sometimes" on the English forum, started
> > yesterday. [1]
> > An user annoyed by the fact that a hyperlink pointing to an mp4 file (as
> > opposed to an mp3 file)
> > raises a warning.
> >
> > As you all remember, the list of safe extensions was one of the issues
> > discussed
> > in the "Hyperlink Warning Message" thread on dev@.
> >
> > Shouldn't the mp4 extension be allowed?
> 
> We already allowed m4a. I don't think mp4 should be a problem?

PR open: https://github.com/apache/openoffice/pull/157

-- 
Arrigo

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

Re: [codehealth] casting int to a pointer

[Arrigo Marchiori]

Hello,

On Fri, Sep 23, 2022 at 07:08:26AM +0200, Peter Kovacs wrote:

> Hi all,
> 
> We cast int to (void*) -> (example in main/sw/source/ui/fldui/changedb.cxx 
> line 234)
> 
> In general this sounds like not a sane idea to me, see discussions [1] [2]
> [3]. The solution that the c++ community found is the use of intptr_t, which
> is defined in C99.
> 
> In general I would like to get rid of these casts. However as a quick fix it
> would make sense to use intptr_t as a first measure.

IMHO casting int to void* is not as bad as it seems.

Your cited sources explains that there would be problems with
_round-tripping_ i.e. using an int type to pass a pointer.

The reason is that on some architectures pointers (void*) are
represented with more bits than integers. Notable example: Linux on
x86_64.

As long as we are using pointers as ``general purpose integers'' we
should have no problems because they are ``big enough'' to contain any
integer value _and_ any pointer.

> Is there any reason that would block the move to C99? I guess C99 should be
> supported by all the compilers we require . (c11 is currently not available
> on all Plattforms we support.)

Unfortunately, Visual Studio 2008 does not support C99.  Specifically
for this case, it is missing the definition of the intptr_t type.

Wikipedia [4] gives more information about C99 support in Visual Studio.

I hope this helps.

> [1] 
> https://stackoverflow.com/questions/26805461/why-do-i-get-cast-from-pointer-to-integer-of-different-size-error
> 
> [2] 
> https://stackoverflow.com/questions/25381610/cast-int-to-pointer-why-cast-to-long-first-as-in-p-void-42
> 
> [3] 
> https://stackoverflow.com/questions/6326338/why-when-to-use-intptr-t-for-type-casting-in-c

[4] https://en.wikipedia.org/wiki/Microsoft_Visual_C%2B%2B#C

-- 
Arrigo

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

Re: WebDAV module ported from serf to curl; curl using openssl and zlib

[Arrigo Marchiori]

Hello Damjan, All,

I had a hard time restoring all the proper line breaks... this thread
is getting long! :-)

On Tue, Aug 23, 2022 at 03:22:07AM +0200, Damjan Jovanovic wrote:

> On Sat, May 28, 2022 at 6:54 PM Arrigo Marchiori 
> wrote:
> 
> > Hello Damjan, All,
> >
> > On Sat, May 28, 2022 at 03:22:53PM +0200, Damjan Jovanovic wrote:
> >
> > > On Sat, May 28, 2022 at 11:48 AM Arrigo Marchiori
> > 
> > > wrote:
> > >
> > > > Hello Damjan,
> > > >
> > > > On Sat, May 28, 2022 at 11:12:45AM +0200, Damjan Jovanovic wrote:
> > > >
> > > > > On Sat, May 28, 2022 at 9:20 AM Arrigo Marchiori 
> > > > >  wrote:
> > > > >
> > > > > > Hello Damjan, all,
> > > > > >
> > > > > > On Fri, May 27, 2022 at 11:27:11PM +0200, Arrigo Marchiori wrote:
> > > > > >
> > > > > > > Hello,
> > > > > > >
> > > > > > > On Fri, May 27, 2022 at 09:46:51PM +0200, Arrigo Marchiori wrote:
> > > > > > >
> > > > > > > > Hello Damjan,
> > > > > > > >
> > > > > > > > On Sun, May 22, 2022 at 06:10:46PM +0200, Damjan Jovanovic 
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > On Sun, May 22, 2022 at 2:43 PM Arrigo Marchiori 
> > > > > > > > >  wrote:
> > > > > > > > >
> > > > > > > > > > Hello Damjan, all,
> > > > > > > > > >
> > > > > > > > > > On Tue, Apr 26, 2022 at 07:56:22PM +0200, Damjan Jovanovic 
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > On Mon, Nov 15, 2021 at 9:57 PM Jim Jagielski 
> > > > > > > > > > >  wrote:
> > > > > > > > > > >
> > > > > > > > > > > > I'm gonna look into the serf->(lib)curl option... Since 
> > > > > > > > > > > > we don't use any
> > > > > > > > > > > > of the fancy features of serf, I'm thinking that the 
> > > > > > > > > > > > easy option might be
> > > > > > > > > > > > best
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Hi
> > > > > > > > > > >
> > > > > > > > > > > I've ported our WebDAV content provider module from Serf 
> > > > > > > > > > > to Curl.
> > > > > > > > > >
> > > > > > > > > > I just enhanced the error reporting a bit; I am finding a 
> > > > > > > > > > problem
> > > > > > > > > > under Linux and I do not really know how to assess it.
> > > > > > > > > >
> > > > > > > > > > The problem: if we build AOO on CentOS (that is our 
> > > > > > > > > > reference
> > > > > > > > > > platform) then Curl will look for CA certificates in
> > > > > > > > > > /etc/pki/tls/certs/ca-bundle.crt
> > > > > > > > > >
> > > > > > > > > > This will fail on openSUSE and probably on Ubuntu as well.
> > > > > > > > > >
> > > > > > > > > > It seems that the above path is set at configure time and 
> > > > > > > > > > embedded
> > > > > > > > > > into Curl's code as #define macros.
> > > > > > > > > >
> > > > > > > > > > Is there an ``official'' way to assess this? Like, can we 
> > > > > > > > > > depend on
> > > > > > > > > > NSS' certificate store as you wrote (quoted below)?
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > Curl/OpenSSL have an enormous number of options and I am 
> > > > > > > > > pretty sure it can
> > > > > > > > > be fixed, but first I n

Re: Can't find boostrap when building

[Arrigo Marchiori]

Hello,

On Sat, Aug 06, 2022 at 12:24:21AM +, Hao Wang wrote:

> I'm following the installation guide on the following page :
> 
> https://github.com/apache/openoffice

[...]

> and I ran the following commands
> 
> 
> cd aoo/main
> autoconf
> ./configure
> 
> But then I discovered there was no bootstrap file - there was only a 
> bootstrap.1 file, which after removal of .1 extension, still not working.
> 
> Can anyone help me fix this problem ?

Please send us the last 10-15 lines output by the "configure" command.

Best regards,
-- 
Arrigo

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

Re: strange error message during build on docker image

[Arrigo Marchiori]

Hello Peter,

On Thu, Jul 21, 2022 at 10:47:38AM +0200, Peter Kovacs wrote:

> Hi all,
> 
> I started to build AOO again. (finally found some time)
> 
> I run into a strange issue.
> 
> =
> Building module gtest
> =
> 
> Entering /workspace/AOO/gitbox/ext_libraries/gtest
> 
> if [ -d ./unxlngx6/misc/build/gtest-1.7.0 ] ; then echo "moving" && mv
> ./unxlngx6/misc/build/gtest-1.7.0 ./unxlngx6/misc/build/gtest-1.7.0_removeme
> ; fi
> moving
> unzip:  cannot find or open 
> /home/legine/AOO/ext_sources/2d6ec8ccdf5c46b05ba54a9fd1d130d7-gtest-1.7.0.zip,
>  
> /home/legine/AOO/ext_sources/2d6ec8ccdf5c46b05ba54a9fd1d130d7-gtest-1.7.0.zip.zip
> or 
> /home/legine/AOO/ext_sources/2d6ec8ccdf5c46b05ba54a9fd1d130d7-gtest-1.7.0.zip.Z
> IP.
> dmake:  Error code 9, while making
> './unxlngx6/misc/build/so_unpacked_oo_gtest'
> 
> here is the content of my ext source:
> 
> 
> [root@1b6f44d92128 main]# ll /workspace/AOO/gitbox/ext_sources/*gtest*
> -rw-rw-r-- 1 1001 1001 1164254 Jan  7  2020 
> /workspace/AOO/gitbox/ext_sources/2d6ec8ccdf5c46b05ba54a9fd1d130d7-gtest-1.7.0.zip
> 
> I think it is strange that the build is searching in /home/legine/ which
> does not exist on the docker image, plus it will not find the sources there
> in general.
> 
> Anyone had this issue before? I think we should search realtive to main
> folder if we are not able to find it.

I think I encounter similar issues when I build under Docker and then
again on bare metal, or vice versa, on the same source tree.

"dmake clean" is necessary at every switch (Docker - bare metal) and I
often forget about it.

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: [DISCUSS] 4.1.13 release user profile warning

[Arrigo Marchiori]

Dear All,

On Mon, Jul 18, 2022 at 07:03:09PM +0200, Marcus wrote:

> Am 16.07.22 um 15:38 schrieb Carl Marcum:
> > 
[...Carl's version]
> > 
> > For the blog post I propose adding this text after the second paragraph.
> > 
> > If you reference the 4.1.12 release blog post [1] this would replace the
> > sentence about the dedication to Jörg in 4.1.12.
> > 
> > ---
> > It is always a good idea to backup your OpenOffice user profile before
> > an upgrade. It is especially important during this upgrade for users who
> > use the Master Password functionality and may decide to use an older
> > version later. There is a change in the encoding of stored passwords in
> > this 4.1.13 release that may make your user profile unusable for
> > previous versions.

[... Marcus' version ]
> thanks for the text. IMHO The priority #1 should be the hint why this time a
> backup is recommended. Therefore I suggest to switch the order:
> 
> 1. Backup due to this release
> 2. Backup is always a good idea.
> 
> What do you think about this?
> 
> 
> 
> It is recommended to make a backup of the Apache OpenOffice users profile
> before installing AOO 4.1.13. It is especially important for users who use
> the Master Password functionality and may decide to use an older version
> later. There is a change in the encoding of stored passwords in this 4.1.13
> release that may make your user profile unusable for previous versions.
> 
> In general, it is always a good idea to do a backup of important and
> personal data, so we recommend to always backup your OpenOffice user profile
> before doing an upgrade to a newer release.

I personally like Carl's version best, but both are good IMHO.

I would like to suggest we only put these paragraphs (either Marcus'
or Carl's version) on the blog post and emails.

More details on the user profile (the list of directories for
different OSes) IMHO do not fit a blog post or an email for ``general
users''. I would rather only expect to see them on the release notes,
that can ``get more technical''.

I.e. this text:

> Users can backup their profile by copying these directories:
> 
> Linux: /home//.openoffice
> Windows 10: C:\Users\\AppData\Roaming\OpenOffice
> Earlier Windows: \Documents and Settings\\Application
> Data\OpenOffice
> macOS: /Users//Library/Application Support/OpenOffice
> 
> More information about the users profile is in the support forum:
> https://forum.openoffice.org/en/forum/viewtopic.php?t=12426

Is very good (thank you Marcus) but I would like to see it only in the
release notes.

Just my two cents.

Best regards,
-- 
Arrigo

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

Re: [VOTE] Release AOO 4.1.13-RC1 as GA

[Arrigo Marchiori]

Dear All,

On Tue, Jul 05, 2022 at 07:58:49AM -0400, Jim Jagielski wrote:

> I am calling a VOTE on releasing the source and complimentary community 
> builds of
> Apache OpenOffice 4.1.13-RC1 as GA.
> 
> These artifacts can be found at:
> 
> https://dist.apache.org/repos/dist/dev/openoffice/4.1.13-RC1/
> 
> Please cast your vote:
 
The Release Candidate is good for production/GA:

[X] yes / +1

[ ] no / -1

My vote is based on

[X] binding (member of PMC)

[X] I have built and tested the RC from source on platform [ Linux x86_64 
(CentOS 5) ]

[X] I have tested the binary RC on platform [ Linux x86_64 (Ubuntu 18.04) ]

I used the RC for daily work -- mostly Writer, seldom Calc.

Best regards,
-- 
Arrigo

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

Re: Windows Visual Studio version for building on Windows 10

[Arrigo Marchiori]

Hello,

On Wed, Jul 13, 2022 at 08:32:29AM +0200, Peter Kovacs wrote:

> Hello Kelly,
> 
> Am 12.07.22 um 04:23 schrieb Kelly Hodis:
> > Hello,
> > 
> > The oowintool Perl script inside of /openoffice/main is looking for early 
> > Visual Studio versions not present on my machine. I have Visual Studio 10, 
> > 12, and 14. For those of you building on Windows without the earlier Visual 
> > Studio versions, what did you do for this step? What is the reason the 
> > script doesn't look for newer versions?
> 
> We still support Windows XP as a target. I am not sure which SDK is the
> latest one that does this. But I remember that Arrigo run into trouble
> trying to build with a newer SDK. Something with Linker path is user
> differently in the perl scripts. But I am not sure anymore.

Yes, oowintool looks for the only supported versions of Visual Studio.

Newer versions are not compatible with our build system. There is a
conflict of environment variables.

FWIW, Windows 10 remains capable of running all the necessary software
to build OpenOffice.

I hope this helps.
-- 
Arrigo

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

Re: PR 141 - Only addes empty lines

[Arrigo Marchiori]

Hello All,

On Mon, Jun 13, 2022 at 08:46:06AM +0200, Peter Kovacs wrote:

> Hi all,
> 
> see  https://github.com/apache/openoffice/pull/141
> 
> 
> I do not see any value in this Request. It does not make the code more
> readable, since there are already empty lines.
> 
> I would like to close it with the same reason. Any insights?

+1

We have a lot of whitespace-fixing commits (thanks, Matthias!) but
this is not the same. I do not think that it makes the code better
adhere to our coding standards, or solves any compiler warnings.

All the above is IMHO, of course.

Best regards,
-- 
Arrigo

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

Re: [Discussion] Pootle Migration - Git Connection

[Arrigo Marchiori]

Hello All,

On Sun, May 29, 2022 at 11:41:09PM +0200, Peter Kovacs wrote:

> Hello all,
> 
> I am still working myself into Pootle.
> 
> Pootle stores the translation at default on the filesystem. There is a
> backend which can utilize git. Pootle commit changes on the translation
> towards the git repository.
> 
> It would give us maybe the opportunity to maintain different Iteration of
> OpenOffice Translation texts.

Storing any development effort into a version control system is IMHO a
good idea.

I think that the best way to do it, would be the easiest, technically
speaking.

For example: if you want to configure Pootle to use Git, you will have
to let it authenticate in some ways. If it's easy, then go ahead!

The alternative would be having someone manually pushing changes from
the filesystem into the repository. This could be done on a periodic
basis; say every two weeks.

To summarize: +1 for Git, in whatever way it is easiest to configure
and to maintain.

> For example. 4.1.x and 4.2.x Translation sets do not match. Maybe we could
> use Git to have a 4.2.x branch,another branch will contain 4.1.x Translation
> files.

I agree that branches would be most useful.

> We could then think of a Version Mapping and a back push translation system.
> This is just a crazy Idea at this moment, to manage the string changes
> between Versions.

What do you mean exactly?

I would expect l10n-savy developers to push changes from the Pootle
development repository into AOO41X or other branches, at appropriate
times (for example, before a beta release).

> What do you think? Is this an Idea to look into? Please write me your
> opinion. Thanks.

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: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)

[Arrigo Marchiori]

Hello Damjan, All,

On Sat, May 28, 2022 at 03:22:53PM +0200, Damjan Jovanovic wrote:

> On Sat, May 28, 2022 at 11:48 AM Arrigo Marchiori 
> wrote:
> 
> > Hello Damjan,
> >
> > On Sat, May 28, 2022 at 11:12:45AM +0200, Damjan Jovanovic wrote:
> >
> > > On Sat, May 28, 2022 at 9:20 AM Arrigo Marchiori  > >
> > > wrote:
> > >
> > > > Hello Damjan, all,
> > > >
> > > > On Fri, May 27, 2022 at 11:27:11PM +0200, Arrigo Marchiori wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > On Fri, May 27, 2022 at 09:46:51PM +0200, Arrigo Marchiori wrote:
> > > > >
> > > > > > Hello Damjan,
> > > > > >
> > > > > > On Sun, May 22, 2022 at 06:10:46PM +0200, Damjan Jovanovic wrote:
> > > > > >
> > > > > > > On Sun, May 22, 2022 at 2:43 PM Arrigo Marchiori
> > > > 
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hello Damjan, all,
> > > > > > > >
> > > > > > > > On Tue, Apr 26, 2022 at 07:56:22PM +0200, Damjan Jovanovic
> > wrote:
> > > > > > > >
> > > > > > > > > On Mon, Nov 15, 2021 at 9:57 PM Jim Jagielski <
> > j...@jagunet.com>
> > > > wrote:
> > > > > > > > >
> > > > > > > > > > I'm gonna look into the serf->(lib)curl option... Since we
> > > > don't use
> > > > > > > > any
> > > > > > > > > > of the fancy features of serf, I'm thinking that the easy
> > > > option might
> > > > > > > > be
> > > > > > > > > > best
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Hi
> > > > > > > > >
> > > > > > > > > I've ported our WebDAV content provider module from Serf to
> > Curl.
> > > > > > > >
> > > > > > > > I just enhanced the error reporting a bit; I am finding a
> > problem
> > > > > > > > under Linux and I do not really know how to assess it.
> > > > > > > >
> > > > > > > > The problem: if we build AOO on CentOS (that is our reference
> > > > > > > > platform) then Curl will look for CA certificates in
> > > > > > > > /etc/pki/tls/certs/ca-bundle.crt
> > > > > > > >
> > > > > > > > This will fail on openSUSE and probably on Ubuntu as well.
> > > > > > > >
> > > > > > > > It seems that the above path is set at configure time and
> > embedded
> > > > > > > > into Curl's code as #define macros.
> > > > > > > >
> > > > > > > > Is there an ``official'' way to assess this? Like, can we
> > depend on
> > > > > > > > NSS' certificate store as you wrote (quoted below)?
> > > > > > > >
> > > > > > >
> > > > > > > Curl/OpenSSL have an enormous number of options and I am pretty
> > sure
> > > > it can
> > > > > > > be fixed, but first I need to understand where and how it's
> > failing.
> > > > > > >
> > > > > > > We currently allow it to run with the default CA certificate
> > path, do
> > > > > > > pre-verification on the server's certificate using those CA
> > > > certificates,
> > > > > > > then call our SSL_VERIFY_PEER function where we override the
> > > > verification
> > > > > > > result with the certificates from NSS.
> > > > > >
> > > > > > Apparently, it is failing before calling our SSL_VERIFY_PEER
> > function.
> > > > > >
> > > > > > > If it's failing before reaching our SSL_VERIFY_PEER function, we
> > > > should be
> > > > > > > able to use Curl's CURLOPT_CAINFO or CURLOPT_CAINFO_BLOB
> > functions
> > > > to set a
> > > > > > > custom CA certificate path (or in-memory buffer), maybe even an
> > empty
> > > > > > > buffer, so that it proceeds further. 

Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)

[Arrigo Marchiori]

Hello Damjan,

On Sat, May 28, 2022 at 11:12:45AM +0200, Damjan Jovanovic wrote:

> On Sat, May 28, 2022 at 9:20 AM Arrigo Marchiori 
> wrote:
> 
> > Hello Damjan, all,
> >
> > On Fri, May 27, 2022 at 11:27:11PM +0200, Arrigo Marchiori wrote:
> >
> > > Hello,
> > >
> > > On Fri, May 27, 2022 at 09:46:51PM +0200, Arrigo Marchiori wrote:
> > >
> > > > Hello Damjan,
> > > >
> > > > On Sun, May 22, 2022 at 06:10:46PM +0200, Damjan Jovanovic wrote:
> > > >
> > > > > On Sun, May 22, 2022 at 2:43 PM Arrigo Marchiori
> > 
> > > > > wrote:
> > > > >
> > > > > > Hello Damjan, all,
> > > > > >
> > > > > > On Tue, Apr 26, 2022 at 07:56:22PM +0200, Damjan Jovanovic wrote:
> > > > > >
> > > > > > > On Mon, Nov 15, 2021 at 9:57 PM Jim Jagielski 
> > wrote:
> > > > > > >
> > > > > > > > I'm gonna look into the serf->(lib)curl option... Since we
> > don't use
> > > > > > any
> > > > > > > > of the fancy features of serf, I'm thinking that the easy
> > option might
> > > > > > be
> > > > > > > > best
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Hi
> > > > > > >
> > > > > > > I've ported our WebDAV content provider module from Serf to Curl.
> > > > > >
> > > > > > I just enhanced the error reporting a bit; I am finding a problem
> > > > > > under Linux and I do not really know how to assess it.
> > > > > >
> > > > > > The problem: if we build AOO on CentOS (that is our reference
> > > > > > platform) then Curl will look for CA certificates in
> > > > > > /etc/pki/tls/certs/ca-bundle.crt
> > > > > >
> > > > > > This will fail on openSUSE and probably on Ubuntu as well.
> > > > > >
> > > > > > It seems that the above path is set at configure time and embedded
> > > > > > into Curl's code as #define macros.
> > > > > >
> > > > > > Is there an ``official'' way to assess this? Like, can we depend on
> > > > > > NSS' certificate store as you wrote (quoted below)?
> > > > > >
> > > > >
> > > > > Curl/OpenSSL have an enormous number of options and I am pretty sure
> > it can
> > > > > be fixed, but first I need to understand where and how it's failing.
> > > > >
> > > > > We currently allow it to run with the default CA certificate path, do
> > > > > pre-verification on the server's certificate using those CA
> > certificates,
> > > > > then call our SSL_VERIFY_PEER function where we override the
> > verification
> > > > > result with the certificates from NSS.
> > > >
> > > > Apparently, it is failing before calling our SSL_VERIFY_PEER function.
> > > >
> > > > > If it's failing before reaching our SSL_VERIFY_PEER function, we
> > should be
> > > > > able to use Curl's CURLOPT_CAINFO or CURLOPT_CAINFO_BLOB functions
> > to set a
> > > > > custom CA certificate path (or in-memory buffer), maybe even an empty
> > > > > buffer, so that it proceeds further. ("man CURLOPT_CAINFO", "man
> > > > > CURLOPT_CAINFO_BLOB", or "man curl_easy_setopt" and read under the
> > "SSL and
> > > > > SECURITY OPTIONS" section.)
> > > >
> > > > So we would need to hard-code and try all possible paths to the CA
> > > > bundle on Unix systems?
> > > >
> > > > > With the CURLOPT_CAINFO_BLOB option it might even be possible to
> > skip the
> > > > > custom certificate verification we do later, and pre-populate
> > Curl/OpenSSL
> > > > > with NSS certificates from the beginning, I just don't know enough
> > about
> > > > > NSS to rely on that (eg. if you are using a cryptographic device or
> > smart
> > > > > card in NSS, how does that work?). If that option is ok, then we
> > might not
> > > > > even need the NSS libraries: recent versions of NSS store all the
> > > > > certificates in an SQLite database, which can be accessed with
> >

Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)

[Arrigo Marchiori]

Hello Damjan, all,

On Fri, May 27, 2022 at 11:27:11PM +0200, Arrigo Marchiori wrote:

> Hello,
> 
> On Fri, May 27, 2022 at 09:46:51PM +0200, Arrigo Marchiori wrote:
> 
> > Hello Damjan,
> > 
> > On Sun, May 22, 2022 at 06:10:46PM +0200, Damjan Jovanovic wrote:
> > 
> > > On Sun, May 22, 2022 at 2:43 PM Arrigo Marchiori 
> > > wrote:
> > > 
> > > > Hello Damjan, all,
> > > >
> > > > On Tue, Apr 26, 2022 at 07:56:22PM +0200, Damjan Jovanovic wrote:
> > > >
> > > > > On Mon, Nov 15, 2021 at 9:57 PM Jim Jagielski  
> > > > > wrote:
> > > > >
> > > > > > I'm gonna look into the serf->(lib)curl option... Since we don't use
> > > > any
> > > > > > of the fancy features of serf, I'm thinking that the easy option 
> > > > > > might
> > > > be
> > > > > > best
> > > > >
> > > > >
> > > > >
> > > > > Hi
> > > > >
> > > > > I've ported our WebDAV content provider module from Serf to Curl.
> > > >
> > > > I just enhanced the error reporting a bit; I am finding a problem
> > > > under Linux and I do not really know how to assess it.
> > > >
> > > > The problem: if we build AOO on CentOS (that is our reference
> > > > platform) then Curl will look for CA certificates in
> > > > /etc/pki/tls/certs/ca-bundle.crt
> > > >
> > > > This will fail on openSUSE and probably on Ubuntu as well.
> > > >
> > > > It seems that the above path is set at configure time and embedded
> > > > into Curl's code as #define macros.
> > > >
> > > > Is there an ``official'' way to assess this? Like, can we depend on
> > > > NSS' certificate store as you wrote (quoted below)?
> > > >
> > > 
> > > Curl/OpenSSL have an enormous number of options and I am pretty sure it 
> > > can
> > > be fixed, but first I need to understand where and how it's failing.
> > > 
> > > We currently allow it to run with the default CA certificate path, do
> > > pre-verification on the server's certificate using those CA certificates,
> > > then call our SSL_VERIFY_PEER function where we override the verification
> > > result with the certificates from NSS.
> > 
> > Apparently, it is failing before calling our SSL_VERIFY_PEER function.
> > 
> > > If it's failing before reaching our SSL_VERIFY_PEER function, we should be
> > > able to use Curl's CURLOPT_CAINFO or CURLOPT_CAINFO_BLOB functions to set 
> > > a
> > > custom CA certificate path (or in-memory buffer), maybe even an empty
> > > buffer, so that it proceeds further. ("man CURLOPT_CAINFO", "man
> > > CURLOPT_CAINFO_BLOB", or "man curl_easy_setopt" and read under the "SSL 
> > > and
> > > SECURITY OPTIONS" section.)
> > 
> > So we would need to hard-code and try all possible paths to the CA
> > bundle on Unix systems?
> >  
> > > With the CURLOPT_CAINFO_BLOB option it might even be possible to skip the
> > > custom certificate verification we do later, and pre-populate Curl/OpenSSL
> > > with NSS certificates from the beginning, I just don't know enough about
> > > NSS to rely on that (eg. if you are using a cryptographic device or smart
> > > card in NSS, how does that work?). If that option is ok, then we might not
> > > even need the NSS libraries: recent versions of NSS store all the
> > > certificates in an SQLite database, which can be accessed with SQLite APIs
> > > directly, no need to build with or ship the NSS libraries at all.
> > 
> > If I understood correctly [1], a NSS-linked Curl would query NSS by
> > itself... are we not in this condition?
[...]
>   1: https://curl.se/libcurl/c/CURLOPT_CAINFO.html

Apparently, we are not. If we force CURLOPT_CAINFO and CURLOPT_CAPATH
to be NULL, we get a bit further but eventually Curl aborts because
validateServerX509Certificate fails.

Here is the log for checking AOO updates (please excuse the long
lines).  I added an extra bit of logging when entering and leaving
OPENSSL_ValidateServerCertificate, that is ``our SSL_VERIFY_PEER
function''.

8<8<8<8<8<8<8<-

 19 2022-05-28 07:13:52.61 CurlSession::CurlSession with URL 
https://ooo-updates.apache.org/aoonext/check.Update?pkgfmt=install

Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)

[Arrigo Marchiori]

Hello,

On Fri, May 27, 2022 at 09:46:51PM +0200, Arrigo Marchiori wrote:

> Hello Damjan,
> 
> On Sun, May 22, 2022 at 06:10:46PM +0200, Damjan Jovanovic wrote:
> 
> > On Sun, May 22, 2022 at 2:43 PM Arrigo Marchiori 
> > wrote:
> > 
> > > Hello Damjan, all,
> > >
> > > On Tue, Apr 26, 2022 at 07:56:22PM +0200, Damjan Jovanovic wrote:
> > >
> > > > On Mon, Nov 15, 2021 at 9:57 PM Jim Jagielski  wrote:
> > > >
> > > > > I'm gonna look into the serf->(lib)curl option... Since we don't use
> > > any
> > > > > of the fancy features of serf, I'm thinking that the easy option might
> > > be
> > > > > best
> > > >
> > > >
> > > >
> > > > Hi
> > > >
> > > > I've ported our WebDAV content provider module from Serf to Curl.
> > >
> > > I just enhanced the error reporting a bit; I am finding a problem
> > > under Linux and I do not really know how to assess it.
> > >
> > > The problem: if we build AOO on CentOS (that is our reference
> > > platform) then Curl will look for CA certificates in
> > > /etc/pki/tls/certs/ca-bundle.crt
> > >
> > > This will fail on openSUSE and probably on Ubuntu as well.
> > >
> > > It seems that the above path is set at configure time and embedded
> > > into Curl's code as #define macros.
> > >
> > > Is there an ``official'' way to assess this? Like, can we depend on
> > > NSS' certificate store as you wrote (quoted below)?
> > >
> > 
> > Curl/OpenSSL have an enormous number of options and I am pretty sure it can
> > be fixed, but first I need to understand where and how it's failing.
> > 
> > We currently allow it to run with the default CA certificate path, do
> > pre-verification on the server's certificate using those CA certificates,
> > then call our SSL_VERIFY_PEER function where we override the verification
> > result with the certificates from NSS.
> 
> Apparently, it is failing before calling our SSL_VERIFY_PEER function.
> 
> > If it's failing before reaching our SSL_VERIFY_PEER function, we should be
> > able to use Curl's CURLOPT_CAINFO or CURLOPT_CAINFO_BLOB functions to set a
> > custom CA certificate path (or in-memory buffer), maybe even an empty
> > buffer, so that it proceeds further. ("man CURLOPT_CAINFO", "man
> > CURLOPT_CAINFO_BLOB", or "man curl_easy_setopt" and read under the "SSL and
> > SECURITY OPTIONS" section.)
> 
> So we would need to hard-code and try all possible paths to the CA
> bundle on Unix systems?
>  
> > With the CURLOPT_CAINFO_BLOB option it might even be possible to skip the
> > custom certificate verification we do later, and pre-populate Curl/OpenSSL
> > with NSS certificates from the beginning, I just don't know enough about
> > NSS to rely on that (eg. if you are using a cryptographic device or smart
> > card in NSS, how does that work?). If that option is ok, then we might not
> > even need the NSS libraries: recent versions of NSS store all the
> > certificates in an SQLite database, which can be accessed with SQLite APIs
> > directly, no need to build with or ship the NSS libraries at all.
> 
> If I understood correctly [1], a NSS-linked Curl would query NSS by
> itself... are we not in this condition?

Sorry, I forgot the link!
Here it is:

  1: https://curl.se/libcurl/c/CURLOPT_CAINFO.html

> Thank you in advance and best regards,

-- 
Arrigo

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

Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)

[Arrigo Marchiori]

Hello Damjan,

On Sun, May 22, 2022 at 06:10:46PM +0200, Damjan Jovanovic wrote:

> On Sun, May 22, 2022 at 2:43 PM Arrigo Marchiori 
> wrote:
> 
> > Hello Damjan, all,
> >
> > On Tue, Apr 26, 2022 at 07:56:22PM +0200, Damjan Jovanovic wrote:
> >
> > > On Mon, Nov 15, 2021 at 9:57 PM Jim Jagielski  wrote:
> > >
> > > > I'm gonna look into the serf->(lib)curl option... Since we don't use
> > any
> > > > of the fancy features of serf, I'm thinking that the easy option might
> > be
> > > > best
> > >
> > >
> > >
> > > Hi
> > >
> > > I've ported our WebDAV content provider module from Serf to Curl.
> >
> > I just enhanced the error reporting a bit; I am finding a problem
> > under Linux and I do not really know how to assess it.
> >
> > The problem: if we build AOO on CentOS (that is our reference
> > platform) then Curl will look for CA certificates in
> > /etc/pki/tls/certs/ca-bundle.crt
> >
> > This will fail on openSUSE and probably on Ubuntu as well.
> >
> > It seems that the above path is set at configure time and embedded
> > into Curl's code as #define macros.
> >
> > Is there an ``official'' way to assess this? Like, can we depend on
> > NSS' certificate store as you wrote (quoted below)?
> >
> 
> Curl/OpenSSL have an enormous number of options and I am pretty sure it can
> be fixed, but first I need to understand where and how it's failing.
> 
> We currently allow it to run with the default CA certificate path, do
> pre-verification on the server's certificate using those CA certificates,
> then call our SSL_VERIFY_PEER function where we override the verification
> result with the certificates from NSS.

Apparently, it is failing before calling our SSL_VERIFY_PEER function.

> If it's failing before reaching our SSL_VERIFY_PEER function, we should be
> able to use Curl's CURLOPT_CAINFO or CURLOPT_CAINFO_BLOB functions to set a
> custom CA certificate path (or in-memory buffer), maybe even an empty
> buffer, so that it proceeds further. ("man CURLOPT_CAINFO", "man
> CURLOPT_CAINFO_BLOB", or "man curl_easy_setopt" and read under the "SSL and
> SECURITY OPTIONS" section.)

So we would need to hard-code and try all possible paths to the CA
bundle on Unix systems?
 
> With the CURLOPT_CAINFO_BLOB option it might even be possible to skip the
> custom certificate verification we do later, and pre-populate Curl/OpenSSL
> with NSS certificates from the beginning, I just don't know enough about
> NSS to rely on that (eg. if you are using a cryptographic device or smart
> card in NSS, how does that work?). If that option is ok, then we might not
> even need the NSS libraries: recent versions of NSS store all the
> certificates in an SQLite database, which can be accessed with SQLite APIs
> directly, no need to build with or ship the NSS libraries at all.

If I understood correctly [1], a NSS-linked Curl would query NSS by
itself... are we not in this condition?

Thank you in advance and best regards,
-- 
Arrigo

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

Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)

[Arrigo Marchiori]

Hello Damjan, all,

On Tue, Apr 26, 2022 at 07:56:22PM +0200, Damjan Jovanovic wrote:

> On Mon, Nov 15, 2021 at 9:57 PM Jim Jagielski  wrote:
> 
> > I'm gonna look into the serf->(lib)curl option... Since we don't use any
> > of the fancy features of serf, I'm thinking that the easy option might be
> > best
> 
> 
> 
> Hi
> 
> I've ported our WebDAV content provider module from Serf to Curl.

I just enhanced the error reporting a bit; I am finding a problem
under Linux and I do not really know how to assess it.

The problem: if we build AOO on CentOS (that is our reference
platform) then Curl will look for CA certificates in
/etc/pki/tls/certs/ca-bundle.crt

This will fail on openSUSE and probably on Ubuntu as well.

It seems that the above path is set at configure time and embedded
into Curl's code as #define macros.

Is there an ``official'' way to assess this? Like, can we depend on
NSS' certificate store as you wrote (quoted below)?

[...]

> HTTPS works, with a custom certificate verification function, using our own
> certificate store from NSS and its API (like the Serf code used). A bug was
> discovered (which is in the Serf implementation too) where self-signed
> certificates were being unconditionally rejected; apparently NSS wants to
> see that a copy of that certificate  in its certificate chain parameter
> too. Now they work, and the user gets prompted to allow access.

Thank you in advance and best regards,
-- 
Arrigo

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

Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)

[Arrigo Marchiori]

Hello Damjan, all,

On Sun, May 15, 2022 at 04:12:14PM +0200, Damjan Jovanovic wrote:

> On Sun, May 15, 2022 at 3:57 PM Arrigo Marchiori 
> wrote:
> 
> > Dear All,
> >
> > On Thu, May 12, 2022 at 07:36:49PM +0200, Arrigo Marchiori wrote:
> >
> > > Dear all,
> > >
> > > if nobody objects, I will merge this PR during the week-end.
> > >
> > > Reference: https://github.com/apache/openoffice/pull/146
> >
> > Done.
> >
> > Thank you again, Damjan!
> >
> 
> It's a pleasure :).
> 
> The next library to update could be zlib, because this version of curl
> > does _not_ compile with the bundled zlib.
> >
> 
> I distinctly recall that zlib and curl compiled for me on Windows. Where
> and how is it failing for you?

It's failing on Linux.

If we want to use the bundled zlib, we have to tell the configure
script --with-zlib=$(OUTDIR) .

The configure script would look for:
 1- the header file in $(OUTDIR)/include
 2- the library in $(OUTDIR)/lib/
But the bundled zlib module installs:
 1a- the header file into $(OUTDIR)/inc
 2a- the static library as file $(OUTDIR)/lib/libzlib.a

So we have to patch it in a similar way as we did for the openssl paths
(i.e. replicate bb956dfd85428dd08d991a01ee6a6c4e966bf431)

Even in that case, it is not easy to understand if we are using the
bundled zlib or the system-level one. The main cause, IMHO, is that
system-level zlib is surely installed (because of other build
dependencies) and is auto-detected by configure scripts and default
Makefile settings.

To a quick glance, also the "openssl" module seems to link to the
system zlib on Linux.

As the bundled zlib is linked statically, I wonder if invoking ldd on
the built executables and .so files is the only way to check for
proper linking.

I am sorry I do not have more time to get into details by now. I hope
the above makes sense.

Best regards,
-- 
Arrigo

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

Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)

[Arrigo Marchiori]

Dear All,

On Thu, May 12, 2022 at 07:36:49PM +0200, Arrigo Marchiori wrote:

> Dear all,
> 
> if nobody objects, I will merge this PR during the week-end.
> 
> Reference: https://github.com/apache/openoffice/pull/146

Done.

Thank you again, Damjan!

The next library to update could be zlib, because this version of curl
does _not_ compile with the bundled zlib.

But I guess it is only one more... among many.

Best regards,
-- 
Arrigo

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

Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)

[Arrigo Marchiori]

Dear all,

if nobody objects, I will merge this PR during the week-end.

Reference: https://github.com/apache/openoffice/pull/146

Best regards,
-- 
Arrigo

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

Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)

[Arrigo Marchiori]

Hello All,

replying to myself now...

On Mon, May 02, 2022 at 10:28:51PM +0200, Arrigo Marchiori wrote:

> > > > On Fri, Apr 29, 2022 at 04:53:59AM +0200, Damjan Jovanovic wrote:
> > > [...]
> > > > > When I run your Linux binaries, I also get that error.
> > > > > 
> > > > > One problem is libcurl -> openssl.
[...]
> I suggest:

[...]

>  2- we patch curl's configure script to use the bundled OpenSSL
>  library, when requested.

PR here: https://github.com/DamjanJovanovic/openoffice/pull/1

This should fix the crash.

Best regards,
-- 
Arrigo

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

Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)

[Arrigo Marchiori]

Hello Dave,

On Mon, May 02, 2022 at 05:53:19PM -0700, Dave Fisher wrote:

> Just so that you aren’t the only one here.

I am sure I am not alone... but thank you anyway ;-)

> It will be important to write good release notes about these changes.
> 
> Users will need to understand clearly that updates to cURL and
> OpenSSL for CVEs won’t happen immediately unless they build with 2
> on their own.

I am not sure I understand this. We are just updating/changing bundled
libraries... Can you please explain better what you mean?

Best regards,
-- 
Arrigo

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

Re: [IMPORTANT] Scheduling Maintenance for our Forum

[Arrigo Marchiori]

On Thu, May 05, 2022 at 05:37:40PM +0200, Marcus wrote:

> Also from me a big thank you for this even bigger work.
> It's very much appreciated. :-)

+1

> Am 05.05.22 um 13:02 schrieb Dick Groskamp:
> > Thanks for the update Dave. Much appreceated.
> > 
> > Dutch forum looks good.
> > 
> > On 2022/05/04 23:06:54 Dave Fisher wrote:
> > > Maintenance on the Forums is completed!

[...]
-- 
Arrigo

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

Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)

[Arrigo Marchiori]

Hello All,

On Sat, Apr 30, 2022 at 10:31:33PM +0200, Arrigo Marchiori wrote:

> Replying to myself again...
> 
> On Sat, Apr 30, 2022 at 10:03:54PM +0200, Arrigo Marchiori wrote:
> 
> > Replying to myself...
> > 
> > On Sat, Apr 30, 2022 at 09:41:04PM +0200, Arrigo Marchiori wrote:
> > 
> > > Hello Damjan,
> > > 
> > > On Fri, Apr 29, 2022 at 04:53:59AM +0200, Damjan Jovanovic wrote:
> > [...]
> > > > When I run your Linux binaries, I also get that error.
> > > > 
> > > > One problem is libcurl -> openssl.
> > > > 
> > > > "ldd ./libcurl.so" shows:
> > > > libssl.so.10 => not found
> > > > libcrypto.so.10 => not found
> > [...]
> > > > 
> > > > It connects and seems to begin the SSL negotiations, and then probably
> > > > crashes while doing the verify_callback we set with 
> > > > SSL_CTX_set_verify().
> > > > 
> > > > I suspect the Curl and/or OpenSSL headers used to build AOO, and their
> > > > libraries available at runtime, are incompatible.
> > > > 
> > > > What happens if you run AOO on the same machine it was built on?
> > [...]
> > > As I wrote above, according to your suspects, it may be worthwile to
> > > bundle curl and openssl binaries. I will try to follow this path. It
> > > should be a matter of parameters to the configure script.
> > 
> > Curl and openssl are already bundled.
> > 
> > But Curl is not using the openssl from AOO, but rather from the
> > system. In other words, it does not honor the environment variable
> > SYSTEM_OPENSSL=NO set by the AOO build system.
> > 
> > Curl's configure script looks for the SSL headers and libraries either
> > from pkgconfig or at a path provided with parameter --with-ssl
> > 
> > We do not support pkgconfig inside the solver, so we have to rely on
> > the path.
> > 
> > But Curl's configure script expects to find a directory structure such as:
> >  - $PREFIX/include/openssl
> >  - $PREFIX/lib[64]
> > whereas our $OUTDIR has openssl installed into different paths:
> >  - $OUTDIR/inc/external/openssl
> >  - $OUTDIR/lib
> > 
> > I believe this means we have to patch Curl's configure script.
> 
> Not only. We also have to actually bundle libssl.so and libcrypto.so
> because they are not!
> 
> This means we have to patch:
> 
>  - main/openssl/prj/d.lst to have them included into the solver;
> 
>  - scp2/source/ooo/file_library_ooo.scp to have their Unix names
>  included.
> 
> This is a separate bug and will be worth its own pull request.

Here it is:
https://github.com/apache/openoffice/pull/147

I suggest:

 1- we merge the above PR (I will on Friday, if no one vetoes and no
 issues are raised);

 2- we patch curl's configure script to use the bundled OpenSSL
 library, when requested.

Comments are always welcome.
 
Best regards,
-- 
Arrigo

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

Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)

[Arrigo Marchiori]

Replying to myself again...

On Sat, Apr 30, 2022 at 10:03:54PM +0200, Arrigo Marchiori wrote:

> Replying to myself...
> 
> On Sat, Apr 30, 2022 at 09:41:04PM +0200, Arrigo Marchiori wrote:
> 
> > Hello Damjan,
> > 
> > On Fri, Apr 29, 2022 at 04:53:59AM +0200, Damjan Jovanovic wrote:
> [...]
> > > When I run your Linux binaries, I also get that error.
> > > 
> > > One problem is libcurl -> openssl.
> > > 
> > > "ldd ./libcurl.so" shows:
> > > libssl.so.10 => not found
> > > libcrypto.so.10 => not found
> [...]
> > > 
> > > It connects and seems to begin the SSL negotiations, and then probably
> > > crashes while doing the verify_callback we set with SSL_CTX_set_verify().
> > > 
> > > I suspect the Curl and/or OpenSSL headers used to build AOO, and their
> > > libraries available at runtime, are incompatible.
> > > 
> > > What happens if you run AOO on the same machine it was built on?
> [...]
> > As I wrote above, according to your suspects, it may be worthwile to
> > bundle curl and openssl binaries. I will try to follow this path. It
> > should be a matter of parameters to the configure script.
> 
> Curl and openssl are already bundled.
> 
> But Curl is not using the openssl from AOO, but rather from the
> system. In other words, it does not honor the environment variable
> SYSTEM_OPENSSL=NO set by the AOO build system.
> 
> Curl's configure script looks for the SSL headers and libraries either
> from pkgconfig or at a path provided with parameter --with-ssl
> 
> We do not support pkgconfig inside the solver, so we have to rely on
> the path.
> 
> But Curl's configure script expects to find a directory structure such as:
>  - $PREFIX/include/openssl
>  - $PREFIX/lib[64]
> whereas our $OUTDIR has openssl installed into different paths:
>  - $OUTDIR/inc/external/openssl
>  - $OUTDIR/lib
> 
> I believe this means we have to patch Curl's configure script.

Not only. We also have to actually bundle libssl.so and libcrypto.so
because they are not!

This means we have to patch:

 - main/openssl/prj/d.lst to have them included into the solver;

 - scp2/source/ooo/file_library_ooo.scp to have their Unix names
 included.

This is a separate bug and will be worth its own pull request.

Comments are welcome.

Best regards,
-- 
Arrigo

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

Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)

[Arrigo Marchiori]

Replying to myself...

On Sat, Apr 30, 2022 at 09:41:04PM +0200, Arrigo Marchiori wrote:

> Hello Damjan,
> 
> On Fri, Apr 29, 2022 at 04:53:59AM +0200, Damjan Jovanovic wrote:
[...]
> > When I run your Linux binaries, I also get that error.
> > 
> > One problem is libcurl -> openssl.
> > 
> > "ldd ./libcurl.so" shows:
> > libssl.so.10 => not found
> > libcrypto.so.10 => not found
[...]
> > 
> > It connects and seems to begin the SSL negotiations, and then probably
> > crashes while doing the verify_callback we set with SSL_CTX_set_verify().
> > 
> > I suspect the Curl and/or OpenSSL headers used to build AOO, and their
> > libraries available at runtime, are incompatible.
> > 
> > What happens if you run AOO on the same machine it was built on?
[...]
> As I wrote above, according to your suspects, it may be worthwile to
> bundle curl and openssl binaries. I will try to follow this path. It
> should be a matter of parameters to the configure script.

Curl and openssl are already bundled.

But Curl is not using the openssl from AOO, but rather from the
system. In other words, it does not honor the environment variable
SYSTEM_OPENSSL=NO set by the AOO build system.

Curl's configure script looks for the SSL headers and libraries either
from pkgconfig or at a path provided with parameter --with-ssl

We do not support pkgconfig inside the solver, so we have to rely on
the path.

But Curl's configure script expects to find a directory structure such as:
 - $PREFIX/include/openssl
 - $PREFIX/lib[64]
whereas our $OUTDIR has openssl installed into different paths:
 - $OUTDIR/inc/external/openssl
 - $OUTDIR/lib

I believe this means we have to patch Curl's configure script.

Best regards,
-- 
Arrigo

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

Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)

[Arrigo Marchiori]

Hello Damjan,

On Fri, Apr 29, 2022 at 04:53:59AM +0200, Damjan Jovanovic wrote:

> On Thu, Apr 28, 2022 at 8:46 PM Arrigo Marchiori 
> wrote:
> 
> > Hello Damjan,
> >
> > On Thu, Apr 28, 2022 at 06:53:43PM +0200, Damjan Jovanovic wrote:
> >
> > > On Thu, Apr 28, 2022 at 6:12 PM Arrigo Marchiori  > >
> > > wrote:
> > >
> > > > Dear Damjan, All,
> > > >
> > > > On Tue, Apr 26, 2022 at 07:56:22PM +0200, Damjan Jovanovic wrote:
> > > >
> > > > > On Mon, Nov 15, 2021 at 9:57 PM Jim Jagielski 
> > wrote:
> > > > >
> > > > > > I'm gonna look into the serf->(lib)curl option... Since we don't
> > use
> > > > any
> > > > > > of the fancy features of serf, I'm thinking that the easy option
> > might
> > > > be
> > > > > > best
> > > > >
> > > > >
> > > > >
> > > > > Hi
> > > > >
> > > > > I've ported our WebDAV content provider module from Serf to Curl.
> > > >
> > > > Binary for Linux available here for download:
> > > >
> > > >
> > https://home.apache.org/~ardovm/openoffice/linux/openoffice4-serf2curl-2022-04-28-installed.tar.bz2
> > > >
> > > > I understand from your previous message that you don't really like
> > > > GitHub, so I am writing here.
> > > >
> > > > [...]
> > > > > STATUS
> > > > >
> > > > > It builds and works well on FreeBSD and Windows.
> > > > >
> > > > > Most of the code was reused, and all the operations and semantics
> > > > > previously present with Serf, should have been preserved.
> > > > >
> > > > > Browsing WebDAV files and directories, loading files, overwriting
> > them
> > > > > ("Save"), creating them ("Save As"), renaming and deleting them, all
> > > > works.
> > > >
> > > > I am testing the binary for Linux linked above.
> > > >
> > > > I tried "Open" and entered a https address, that I know is password
> > > > protected.
> > > >
> > > > The current trunk would ask for the password. I got an error message
> > > > instead:
> > > >
> > > > > > Nonexistent object.
> > > > > > Nonexistent file.
> > > >
> > > > The address I tried to open is in the form https://host.domain:port/
> > > >
> > > > I tried to substitute "https" with "davs" and I got the same error.
> > > >
> > > > Maybe something is going wrong in the Linux build?
> > > >
> > > > I will now begin recompiling with debugging symbols enabled. Please
> > > > let me know how I can help.
> > > >
> > >
> > > That's not good :(.
> > >
> > > Set your macro security to "Medium", open the spreadsheet I've attached,
> > > and run the "RunMe" Basic macro. That should enable logging to the
> > console
> > > at the finest level of detail. Then exit and re-run AOO like this:
> > > soffice 2>&1 | tee /tmp/log.txt
> > > and examine the console output interactively as you use AOO, and/or check
> > > the log file afterwards. It should have everything, our logging, HTTP
> > > request and response headers and bodies, Curl's internal logging.
> >
> > I can't get to that point.
> >
> > I fired gdb and it seems that I end up into the blind
> >   catch (Exception const &)
> > block in file ucb/source/core/provprox.cxx:361
> >
> > Method UcbContentProviderProxy::getContentProvider() in fact is called
> > many times, but it only fails when I enter the https url in the "Open"
> > dialog box and press ENTER.
> >
> > Sorry this is all the debugging I can do for today. I hope it helps.
> >
> >
> When I run your Linux binaries, I also get that error.
> 
> One problem is libcurl -> openssl.
> 
> "ldd ./libcurl.so" shows:
> libssl.so.10 => not found
> libcrypto.so.10 => not found

This probably means that we have to ship our own binaries of openssl
on Linux.

> When I rename AOO's libcurl.so so that it's forced to use my system libcurl
> instead, it proceeds further, but runs into another problem:
> 
> Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation 

Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)

[Arrigo Marchiori]

Hello Damjan,

On Thu, Apr 28, 2022 at 06:53:43PM +0200, Damjan Jovanovic wrote:

> On Thu, Apr 28, 2022 at 6:12 PM Arrigo Marchiori 
> wrote:
> 
> > Dear Damjan, All,
> >
> > On Tue, Apr 26, 2022 at 07:56:22PM +0200, Damjan Jovanovic wrote:
> >
> > > On Mon, Nov 15, 2021 at 9:57 PM Jim Jagielski  wrote:
> > >
> > > > I'm gonna look into the serf->(lib)curl option... Since we don't use
> > any
> > > > of the fancy features of serf, I'm thinking that the easy option might
> > be
> > > > best
> > >
> > >
> > >
> > > Hi
> > >
> > > I've ported our WebDAV content provider module from Serf to Curl.
> >
> > Binary for Linux available here for download:
> >
> > https://home.apache.org/~ardovm/openoffice/linux/openoffice4-serf2curl-2022-04-28-installed.tar.bz2
> >
> > I understand from your previous message that you don't really like
> > GitHub, so I am writing here.
> >
> > [...]
> > > STATUS
> > >
> > > It builds and works well on FreeBSD and Windows.
> > >
> > > Most of the code was reused, and all the operations and semantics
> > > previously present with Serf, should have been preserved.
> > >
> > > Browsing WebDAV files and directories, loading files, overwriting them
> > > ("Save"), creating them ("Save As"), renaming and deleting them, all
> > works.
> >
> > I am testing the binary for Linux linked above.
> >
> > I tried "Open" and entered a https address, that I know is password
> > protected.
> >
> > The current trunk would ask for the password. I got an error message
> > instead:
> >
> > > > Nonexistent object.
> > > > Nonexistent file.
> >
> > The address I tried to open is in the form https://host.domain:port/
> >
> > I tried to substitute "https" with "davs" and I got the same error.
> >
> > Maybe something is going wrong in the Linux build?
> >
> > I will now begin recompiling with debugging symbols enabled. Please
> > let me know how I can help.
> >
> 
> That's not good :(.
> 
> Set your macro security to "Medium", open the spreadsheet I've attached,
> and run the "RunMe" Basic macro. That should enable logging to the console
> at the finest level of detail. Then exit and re-run AOO like this:
> soffice 2>&1 | tee /tmp/log.txt
> and examine the console output interactively as you use AOO, and/or check
> the log file afterwards. It should have everything, our logging, HTTP
> request and response headers and bodies, Curl's internal logging.

I can't get to that point.

I fired gdb and it seems that I end up into the blind
  catch (Exception const &)
block in file ucb/source/core/provprox.cxx:361

Method UcbContentProviderProxy::getContentProvider() in fact is called
many times, but it only fails when I enter the https url in the "Open"
dialog box and press ENTER.

Sorry this is all the debugging I can do for today. I hope it helps.

Best regards,
-- 
Arrigo

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

Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)

[Arrigo Marchiori]

Dear Damjan, All,

On Tue, Apr 26, 2022 at 07:56:22PM +0200, Damjan Jovanovic wrote:

> On Mon, Nov 15, 2021 at 9:57 PM Jim Jagielski  wrote:
> 
> > I'm gonna look into the serf->(lib)curl option... Since we don't use any
> > of the fancy features of serf, I'm thinking that the easy option might be
> > best
> 
> 
> 
> Hi
> 
> I've ported our WebDAV content provider module from Serf to Curl.

Binary for Linux available here for download:
https://home.apache.org/~ardovm/openoffice/linux/openoffice4-serf2curl-2022-04-28-installed.tar.bz2

I understand from your previous message that you don't really like
GitHub, so I am writing here.

[...]
> STATUS
> 
> It builds and works well on FreeBSD and Windows.
> 
> Most of the code was reused, and all the operations and semantics
> previously present with Serf, should have been preserved.
> 
> Browsing WebDAV files and directories, loading files, overwriting them
> ("Save"), creating them ("Save As"), renaming and deleting them, all works.

I am testing the binary for Linux linked above.

I tried "Open" and entered a https address, that I know is password
protected.

The current trunk would ask for the password. I got an error message
instead:

> > Nonexistent object.
> > Nonexistent file.

The address I tried to open is in the form https://host.domain:port/

I tried to substitute "https" with "davs" and I got the same error.

Maybe something is going wrong in the Linux build?

I will now begin recompiling with debugging symbols enabled. Please
let me know how I can help.

[...]
> P.S. APACHE 2.4 SETUP FOR TESTING
[...]

I still have to try this. Thank you for this tutorial!!

Best regards,
-- 
Arrigo

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

Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)

[Arrigo Marchiori]

Dear All,

first of all thank you Damjan, for this huge work!
It looks... wonderful.

On Wed, Apr 27, 2022 at 07:11:14PM +0200, Damjan Jovanovic wrote:

> Thank you Matthias.
> 
> Not too happy to use Github, but here is the pull request:
> https://github.com/apache/openoffice/pull/146

This is much helpful, thanks.

I see that my review was requested. I need a couple of days to check
it builds fine under Linux. Matthias, will you please check under
Windows?

Jim, could you please check MacOS? I cannot build trunk on that
platform yet.

I am not asking because I don't trust Damjan, but just to suggest we
honestly hunt for ``works on my machine'' effects ;-)
The commit is... big and IMHO we shall not hurry.

Best regards.

> > On Mon, Nov 15, 2021 at 9:57 PM Jim Jagielski  wrote:
> >
> >> I'm gonna look into the serf->(lib)curl option... Since we don't use any
> >> of the fancy features of serf, I'm thinking that the easy option might be
> >> best
> >
> >
> >
> > Hi
> >
> > I've ported our WebDAV content provider module from Serf to Curl.

[...]

-- 
Arrigo

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

Re: [VOTE] Release AOO 4.1.12-RC1 as GA

[Arrigo Marchiori]

Dear All,

On Wed, Apr 13, 2022 at 09:54:53AM -0400, Jim Jagielski wrote:

> I am calling a VOTE on releasing the source and complimentary community 
> builds of
> Apache OpenOffice 4.1.12-RC1 as GA.
> 
> These artifacts can be found at:
> 
> https://dist.apache.org/repos/dist/dev/openoffice/4.1.12-RC1/
> 
> Please cast your vote:

The Release Candidate is good for production/GA:
 
 [X] yes / +1
 
 [ ] no / -1
 
My vote is based on
 
 [X] binding (member of PMC)
 
 [X] I have built the RC from source on platform [ Linux x86, Linux x86_64 ]
 
 [X] I have tested the binary RC on platform [ Linux x86_64 ]
 
Best regards,
-- 
Arrigo


signature.asc
Description: PGP signature

Re: Building 4.1.12-RC1 Linux x86

[Arrigo Marchiori]

Hello Jim, All,

On Mon, Apr 18, 2022 at 07:21:49AM -0400, Jim Jagielski wrote:

> The source of truth on how we build the community packages are the build
> script and the config.log file, which shows exactly what packages, features,
> and libraries are included. Have you ensured that all the packages from
> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step_Linux
>  
> <https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step_Linux>
> are installed on your VM?

I double-checked and everything seems in order in my VM.

The build script from SVN only works when I overwrite file
configure.ac with its version before commit 16f572b

Please note I am trying with a ``fresh unpack'' of the source archive.
The configure script is not present there, so it's generated by the
build script, invoking autoconf.

Everything works if I patch the build script adding parameters
--enable-gnome-vfs and --disable-gio

But I understand it's just my problem... so let's move forward.

Best regards.

> > On Apr 17, 2022, at 9:25 AM, Arrigo Marchiori  
> > wrote:
> > 
> > Dear Jim, All,
> > 
> > I cannot build the current RC on my CentOS 5 VM (x86, 32 bit) using
> > the build script from Subversion.
> > 
> > The configure script aborts because it cannot find the gio library:
> > 
> > 8<8<8<8<8<8<8<-
> > checking whether to enable GIO support... yes
> > checking for GIO... no
> > configure: error: Package requirements (gio-2.0 ) were not met:
> > 
> > No package 'gio-2.0' found
> > 8<8<8<8<8<8<8<-
> > 
> > Maybe we should add the parameters --enable-gnome-vfs and --disable-gio
> > to the script, because of commit 16f572b ?
> > 
> > Please let me know if there are any better solutions.
> > 
> > Best regards,
-- 
Arrigo

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

Building 4.1.12-RC1 Linux x86

[Arrigo Marchiori]

Dear Jim, All,

I cannot build the current RC on my CentOS 5 VM (x86, 32 bit) using
the build script from Subversion.

The configure script aborts because it cannot find the gio library:

8<8<8<8<8<8<8<-
checking whether to enable GIO support... yes
checking for GIO... no
configure: error: Package requirements (gio-2.0 ) were not met:

No package 'gio-2.0' found
8<8<8<8<8<8<8<-

Maybe we should add the parameters --enable-gnome-vfs and --disable-gio
to the script, because of commit 16f572b ?

Please let me know if there are any better solutions.

Best regards,
-- 
Arrigo

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

Re: Help building in Ubuntu 20.04.4?

[Arrigo Marchiori]

Hello Matthias, all,

On Mon, Mar 21, 2022 at 05:34:32PM +0100, Matthias Seidel wrote:

> Hi Pedro,
> 
> I cherry-picked the second patch, so AOO41X should build now.
> 
> Can you test, please?

Current AOO41X builds under CentOS 5, 64 bit.

Best regards,
-- 
Arrigo

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

Re: AOO 4.1.12?

[Arrigo Marchiori]

Hello Jim, All,

On Wed, Mar 16, 2022 at 11:40:23AM -0400, Jim Jagielski wrote:

> Thanks! I volunteer to RM. Is that OK?

+1 with thanks!

Best regards,
-- 
Arrigo

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

Re: problem reading old XML formats with trunk

[Arrigo Marchiori]

Hello Carl, All,

On Fri, Jan 07, 2022 at 04:57:20PM +0100, Arrigo Marchiori wrote:

> Hello Carl, All,
> 
> I am branching the thread from here in order to prune less
> interesting parts.
> 
> On Sun, Nov 14, 2021 at 10:12:05PM -0500, Carl Marcum wrote:
> 
> > Hi All,
> > 
> > On 11/14/21 5:05 PM, Matthias Seidel wrote:
> > > Hi Carl,
> > > 
> > > Am 14.11.21 um 22:45 schrieb Carl Marcum:
> > > > Hi Matthias,
> > > > 
> > > > 
> > > > On 11/14/21 11:44 AM, Matthias Seidel wrote:
> > > > > Hi Carl,
> > > > > 
> > > > > Am 14.11.21 um 17:36 schrieb Matthias Seidel:
> > > > > > Hi Carl,
> > > > > > 
> > > > > > Am 14.11.21 um 17:31 schrieb Carl Marcum:
> > > > > > > Hi Matthias and All,
> > > > > > > 
> > > > > > > On 11/14/21 9:10 AM, Matthias Seidel wrote:
> > > > > > > > Hi Carl,
> > > > > > > > 
> > > > > > > > I only have a VM available with Xubuntu 18.04.6 and AOO42X, but
> > > > > > > > have no
> > > > > > > > problems opening and saving *.STW.
> > > > > > > Okay I'll build AOO42X and see if I have same issues as trunk.
> > > > > > > 
> > > > > > > I recompiled trunk with
> > > > > > > --enable-crashdump=yes \
> > > > > > > --enable-dbgutil \
> > > > > > > 
> > > > > > > and now I get a better error dialog for opening these file types:
> > > > > > > testSaveNewSTC.stc
> > > > > > > testSaveNewSXC.sxc
> > > > > > > --
> > > > > > > Error: uno exception caught while importing:
> > > > > > > attempt to insert duplicate XML tag attribute: xmlns:svg
> > > > > > >   From File
> > > > > > > /openoffice/main/sc/source/filter/xml/xmlwrap.cxx 
> > > > > > > at
> > > > > > > Line 365
> > > > > > > Abort ? (Yes=abort / No=ignore / Cancel=core dump)
> > > > > > I remember that we have a commit in trunk but not in AOO42X:
> > > > > > 
> > > > > > https://github.com/apache/openoffice/pull/122
> > > > > > 
> > > > > > Until now it has not been tested... Maybe that is the problem?
> > > > > I can confirm Read-Errors with AOO450 (trunk) on Windows with STW and
> > > > > SXW.
> > > > > No problems with AOO420 (AOO42X).
> > > > > 
> > > > > This merge may need to be reverted...
> > > > 
> > > > Thanks for checking.
> > > > 
> > > > It might be better at this point to fix the code.
> > > That's why I asked for testing... ;-)
> > > > I'll do some bisecting and try to narrow it down.
> > > I am not sure if the code was ready, Arrigo might know better.
> > 
> > I bisected it down to this one where it starts giving me the error which
> > makes sense according the the commit message:
> > 
> > ebd28ad3a7fedadb378ee1596803008e8c6b383b is the first bad commit
> > commit ebd28ad3a7fedadb378ee1596803008e8c6b383b
> > 
> >     Raise an exception when attempting to add duplicate attributes
> 
> The error is raised during parsing of file styles.xml, initial tag
> , attribute
> xmlns:svg="http://openoffice.org/2000/svg;
> 
> Method XMLDocumentTransformerContext_Impl::StartElement() considers
> individual XML attributes and, at the end, it adds the ones it
> considers missing.
> 
> The xmlns:svg is considered missing because it does not have the
> expected _content_. Yes, the check is made on attribute contents,
> rather than attribute names.
> 
> That attributs's content _should_ be the one indicated above, but the
> caller method XMLTransformerBase::startElement() has _just changed its
> content_ into
> "urn:oasis:names:tc:opendocument:xmlns:svg-compatible:1.0"
> 
> For this reason, method
> XMLDocumentTransformerContext_Impl::StartElement() tries to re-add the
> "xmlns:svg" element.
> 
> The first solutions that come into my mind are:
> 
>  1- have XMLDocumentTransformerContext_Impl::StartElement() consider
>  element _names_ rather than values, or
> 
>  2- have XMLDocumentTransformerContext_Impl::StartElement() look for
>  the ``changed'' content (urn:etcetera) instead of the ``original''
>  one (http://Etcetera)
> 
> What is the best way to go?

I went for 2-

This problem should be fixed in trunk with commit
7462b7435704d287da295f8819ee4fd4bffded77

I could not run the tests, though, I think because they cannot
``type'' the string "@AOO" correctly.

My PC has an Italian keyboard, and I am seeing the tests type
 "AOO 
instead of 
 @AOO
maybe because the Italian layout has the quotes " above the 2 key?

Best regards,
-- 
Arrigo

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

[DISCUSS] The Public Service Mission of Apache OpenOffice

[Arrigo Marchiori]

The Apache OpenOffice PMC is calling all developers and users to
prepare the "Mission Statement" for the project.

A project’s mission statement is crucially important for defining both
the identity of the project and of the community that makes that
project a reality.

Our mission statement must outline the current state of the project
and its near and distant goals.

The "Apache Way" emphasizes that the community is more valued than the
software source code itself.

The current draft of the mission statement is here:
https://cwiki.apache.org/confluence/x/KALFAQ

The purpose of this [DISCUSS] thread is to get community feedback
before publishing the mission statement. We expect this discussion to
take not more than one week. This means that the mission statement
will be officially released on 22 February 2022 -- unless we find a
broad consensus on delaying it.

The discussion will take place on the development mailing list.
The list archives are public and anyone can subscribe to contribute:
https://openoffice.apache.org/mailing-lists.html#development-mailing-list-public

We look forward to your feedback!
-- 
Arrigo Marchiori
On behalf of the OpenOffice PMC

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

Re: [openoffice] branch AOO41X updated: Add support for Azul JDK's

[Arrigo Marchiori]

Hello Matthias,

On Sun, Feb 13, 2022 at 05:43:25PM +0100, Matthias Seidel wrote:

> Hi Arrigo,
> 
> Am 13.02.22 um 17:22 schrieb Arrigo Marchiori:
> > Hello Matthias, All,
> >
> > On Fri, Feb 11, 2022 at 08:15:32PM +0100, Matthias Seidel wrote:
> >
> >> Hi Arrigo,
> >>
> >> Same here: Would this also be wanted in trunk and AOO42X?
> > I think so. This commit had to be adjusted because AOO42X and trunk do
> > not seem to support Java 1.7, whereas AOO41X did.
> >
> > I merged the other one about the `tmp' folder.
> >
> > Thank you for pointing this out! My bad; I should not work on trunk
> > directly...
> 
> No problem, I just want to have the branches in sync as much as possible.

Sure!

[...]

> The fix for "Azul" is just for building?
> 
> I ask, because on Windows the Azul JDK is already detected. But it is
> listed as "OpenJDK" like the one from Adoptium. Maybe we can make that
> list a bit more clear?

The commit changes the logic that selects whether "mac.java.path"
shall be set to "mac.oracle.java.path" or "mac.apple.java.path".

Apparently, there are two ``families'' of JDK's under macOS, and each
family keeps its base classes in a different path.

This edit only affects building under macOS.

Do you suggest that an explanation like the above shall be integrated
into the file as a comment?

Best regards,
-- 
Arrigo

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

Re: [openoffice] branch AOO41X updated: Add support for Azul JDK's

[Arrigo Marchiori]

Hello Matthias, All,

On Fri, Feb 11, 2022 at 08:15:32PM +0100, Matthias Seidel wrote:

> Hi Arrigo,
> 
> Same here: Would this also be wanted in trunk and AOO42X?

I think so. This commit had to be adjusted because AOO42X and trunk do
not seem to support Java 1.7, whereas AOO41X did.

I merged the other one about the `tmp' folder.

Thank you for pointing this out! My bad; I should not work on trunk
directly...

Best regards,
-- 
Arrigo

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

Building AOO41X on macOS Catalina [Was: Openssl, serf and curl... and NSS]

[Arrigo Marchiori]

Hello Marcus, All,

On Thu, Feb 10, 2022 at 11:01:10PM +0100, Marcus wrote:

[huge snip about official build scripts on macOS]

> For the AOO41X release branch we really should try as best and long as
> possible to keep the setup the same like the past releases to give a (kind
> of) guarantee that a new release would run also in the same PC environment.
> 
> So, the next step is to see if the build is also successful with Java 7. But
> as I see this already in progress . :-)

The official build script cannot work as-is, because it expects the
only XCode to be version 7.

On Catalina, we rather have to install XCode 12.0.1 and then the SDK
only from XCode 7.3.1, using the XCodeLegacy script.

The following lines have to be commented out:

8<8<8<8<8<8<8<-
$(xcode-select -p | grep "Xcode7" -q)
if [ $? != 0 ]; then 
echo "xcode-select must point to Xcode7."
exit 1 
fi
8<8<8<8<8<8<8<-

This should not be a big problem IMHO.

I hope this helps,
-- 
Arrigo

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

Re: Openssl, serf and curl... and NSS

[Arrigo Marchiori]

Just a quick, small update:

On Thu, Feb 10, 2022 at 08:12:02PM +0100, Arrigo Marchiori wrote:

> Hello Carl,
> 
> On Thu, Feb 10, 2022 at 11:32:57AM -0500, Carl Marcum wrote:

[...]
> > Asul has x86-64 JDK's available for Java 7 but that's all.
> > 
> > https://www.azul.com/downloads/?version=java-7-lts=macos=jdk
> 
> I will try that!

Installed, detected, new build of AOO41X in progress! :-)

Thank you!

Best regards,
-- 
Arrigo

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

Re: Openssl, serf and curl... and NSS

[Arrigo Marchiori]

Hello Carl,

On Thu, Feb 10, 2022 at 11:32:57AM -0500, Carl Marcum wrote:

> Hi Arrigo,
> 
> On 2/10/22 11:00 AM, Arrigo Marchiori wrote:
> > Hello Matthias,
> > 
> > On Thu, Feb 10, 2022 at 03:42:16PM +0100, Matthias Seidel wrote:
> > 
> > > Hi Arrigo,
> > > 
> > > Am 10.02.22 um 15:21 schrieb Arrigo Marchiori:
> > > > Dear Jim, Matthias, All,
> > > > 
> > > > On Wed, Feb 09, 2022 at 12:12:09PM -0500, Jim Jagielski wrote:
> > > > 
> > > > > That's right... I'll wait to even try compiling until things settle
> > > > > down and we have some slowly moving target I can compile and build
> > > > > against.
> > > > > 
> > > > > > On Feb 8, 2022, at 6:06 AM, Matthias Seidel 
> > > > > >  wrote:
> > > > > > 
> > > > > > Hi Arrigo,
> > > > > > 
> > > > > > No need to apologize. ;-)
> > > > > > 
> > > > > > But I think, before we begin to think about upgrading serf we need 
> > > > > > to
> > > > > > make sure that AOO41X is able to build successfully on all 
> > > > > > platforms.
> > > > > > 
> > > > > > Windows and Linux are OK, I think. macOS is still pending?
> > > > AOO41X now builds under Catalina, with a single edit to the official
> > > > build script: AOO_JAVA_VERSION=1.8
> > > So you build with Java 8?
> > The official build script contains the setting:
> > AOO_JAVA_VERSION=1.7
> > 
> > On our Mac mini, the script fails because Java 1.7 is not installed,
> > and it does not seem to be available on-line for download.
> 
> What is the architecture of the Mac Mini?

% uname -a
Darwin administrators-Mac-mini.local 19.6.0 Darwin Kernel Version 19.6.0: Sun 
Nov 14 19:58:51 PST 2021; root:xnu-6153.141.50~1/RELEASE_X86_64 x86_64

> Asul has x86-64 JDK's available for Java 7 but that's all.
> 
> https://www.azul.com/downloads/?version=java-7-lts=macos=jdk

I will try that!

Please allow me to state I had no intention to ``subvert'' current
versions of Java or whatever. For what I understand, Catalina and the
XCode versions installed in our Mac mini do not match the reference
macOS version and tools for our AOO41X builds, and this is absolutely
fine for me, as long as there is someone else who has a system with
the ``official'' architecture and is able to use it.

I am just trying to have a (whatever version of) macOS building AOO,
so that when I commit something, I can test on that architecture as
well. And possibly lower the barriers to entry for others.

So if any of my edits break the builds on ``official machines'',
please let us just revert them.

The Java version change was not even committed anywhere. ;-)

Thank you for reading through my disclaimer. ;-)

Best regards,
-- 
Arrigo

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

Re: Openssl, serf and curl... and NSS

[Arrigo Marchiori]

Hello Matthias,

On Thu, Feb 10, 2022 at 03:42:16PM +0100, Matthias Seidel wrote:

> Hi Arrigo,
> 
> Am 10.02.22 um 15:21 schrieb Arrigo Marchiori:
> > Dear Jim, Matthias, All,
> >
> > On Wed, Feb 09, 2022 at 12:12:09PM -0500, Jim Jagielski wrote:
> >
> >> That's right... I'll wait to even try compiling until things settle
> >> down and we have some slowly moving target I can compile and build
> >> against.
> >>
> >>> On Feb 8, 2022, at 6:06 AM, Matthias Seidel  
> >>> wrote:
> >>>
> >>> Hi Arrigo,
> >>>
> >>> No need to apologize. ;-)
> >>>
> >>> But I think, before we begin to think about upgrading serf we need to
> >>> make sure that AOO41X is able to build successfully on all platforms.
> >>>
> >>> Windows and Linux are OK, I think. macOS is still pending?
> > AOO41X now builds under Catalina, with a single edit to the official
> > build script: AOO_JAVA_VERSION=1.8
> 
> So you build with Java 8?

The official build script contains the setting:
AOO_JAVA_VERSION=1.7

On our Mac mini, the script fails because Java 1.7 is not installed,
and it does not seem to be available on-line for download.

I found Java 8 installed, and that's why I changed the setting.

I hope it makes sense.

Best regards,
-- 
Arrigo

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