Re: Fwd: E-mail address for publishing extensions is wrong

2023-03-13 Thread Matthias Seidel
FYI:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  nore...@extensions.openoffice.org
retry timeout exceeded

Am 11.03.23 um 19:07 schrieb Matthias Seidel:
>
> Hi All,
>
> The extension site gets more and more broken...
>
> I don't have the time to spend hours on every new extension that
> someone wants to publish.
>
> Maybe we should get the problems fixed?
>
> Regards,
>
>    Matthias
>
> Am 09.03.23 um 17:46 schrieb Matthias Seidel:
>>
>> Hello All,
>>
>> FYI:
>>
>> While I can publish the extension page, the downloadable files are
>> (again) not to be found in the SourceForge database.
>>
>> Apart from that, we need a working mail address for users to contact us.
>>
>> Regards,
>>
>>    Matthias
>>
>>
>>  Weitergeleitete Nachricht 
>> Betreff: E-mail address for publishing extensions is wrong
>> Datum:   Thu, 9 Mar 2023 17:24:20 +0100
>> Von: Bogdan 
>> Antwort an:  us...@openoffice.apache.org
>> An:  us...@openoffice.apache.org
>>
>>
>>
>> Hello.
>>
>> After I created my extension, I wanted to publish it, but instead I
>> saw the message:
>>
>> "
>> This extension is currently not published. Please contact the system
>> administrator at nore...@extensions.openoffice.org to have it
>> published, including a link to this page.
>> "
>>
>> What would be the actual address to write to? Because it isn't
>> "noreply", right?
>>
>> The extension is:
>> https://extensions.openoffice.org/en/project/keyparastocx
>>
>> Thank you!
>>
>> -- 
>> Regards - Bogdan ('bogdro') D. (GNU/Linux & FreeDOS)
>> X86 assembly (DOS, GNU/Linux):http://bogdro.evai.pl/index-en.php
>> Soft(EN): http://bogdro.evai.pl/soft  http://bogdro.evai.pl/soft4asm
>> www.Xiph.org  www.TorProject.org  www.LibreOffice.org  www.GnuPG.org
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: users-h...@openoffice.apache.org
>>


smime.p7s
Description: S/MIME Cryptographic Signature


Problème avec Open office

2023-03-13 Thread martinevoyeux
Bonjour,

J’ai un Mac OS 13.1 Ventura  acheté le 02/04/2022 

J’ai voulu télécharger Apache Open office 4.1.13. Et il est Impossible d’ouvrir 
cette application .

J’ai vu sur le forum que c’était le même problème d’autres utilisateurs de 
cette dernière version de Mac .

Pouvez-vous m’aider s’il vous plait ?

C’est urgent, merci d’avance .

Cordialement

Martine VOYEUX



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



Re: Problème avec Open office

2023-03-13 Thread Rory O'Farrell
On Mon, 13 Mar 2023 18:57:36 +0100
martinevoyeux  wrote:

> Bonjour,
> 
> J’ai un Mac OS 13.1 Ventura  acheté le 02/04/2022 
> 
> J’ai voulu télécharger Apache Open office 4.1.13. Et il est Impossible 
> d’ouvrir cette application .
> 
> J’ai vu sur le forum que c’était le même problème d’autres utilisateurs de 
> cette dernière version de Mac .
> 
> Pouvez-vous m’aider s’il vous plait ?
> 
> C’est urgent, merci d’avance .
> 
> Cordialement
> 
> Martine VOYEUX


Probable solution given in 
https://forum.openoffice.org/en/forum/viewtopic.php?t=89283]Mac FAQ Q05/A05: 
The Gatekeeper won't let me run OpenOffice. How do I proceed?

This is caused by Apple Gatekeeper.
-- 
Rory O'Farrell 

-
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

2023-03-13 Thread Matthias Seidel
Hi Arrigo,

Am 12.03.23 um 21:10 schrieb 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.

Just FYI:

I could successfully build AOO41X using make 4.4.1 *without* this patch.

AOO42X did not build, so there must be a difference (gbuild?)...

Regards,

   Matthias

>
>> 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,



smime.p7s
Description: S/MIME Cryptographic Signature