Re: [openoffice] branch AOO41X updated: Create 'tmp' directory into solver

2022-02-11 Thread Matthias Seidel
Hi Arrigo,

Should this be "backported" to the other branches or is it already there?

Regards,

   Matthias

Am 10.02.22 um 14:53 schrieb ard...@apache.org:
> This is an automated email from the ASF dual-hosted git repository.
>
> ardovm pushed a commit to branch AOO41X
> in repository https://gitbox.apache.org/repos/asf/openoffice.git
>
>
> The following commit(s) were added to refs/heads/AOO41X by this push:
>  new f76c880  Create 'tmp' directory into solver
> f76c880 is described below
>
> commit f76c88023642e2d81093a0f72c05e19cda1f23f3
> Author: Arrigo Marchiori 
> AuthorDate: Thu Feb 10 14:51:57 2022 +0100
>
> Create 'tmp' directory into solver
> 
> Completes f110f2132c033266ae9e2e1ff7ec2f29347b01ab
> ---
>  main/solenv/bin/deliver.pl | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/main/solenv/bin/deliver.pl b/main/solenv/bin/deliver.pl
> index 425cbf0..f20a803 100755
> --- a/main/solenv/bin/deliver.pl
> +++ b/main/solenv/bin/deliver.pl
> @@ -1002,6 +1002,7 @@ sub push_default_actions
>  'pck',
>  'rdb',
>  'res',
> +'tmp',
>  'xml'
>  );
>  push(@subdirs, 'zip') if $opt_zip;



smime.p7s
Description: S/MIME Cryptographic Signature


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

2022-02-11 Thread Matthias Seidel
Hi Arrigo,

Same here: Would this also be wanted in trunk and AOO42X?

Regards,

   Matthias

Am 11.02.22 um 09:47 schrieb ard...@apache.org:
> This is an automated email from the ASF dual-hosted git repository.
>
> ardovm pushed a commit to branch AOO41X
> in repository https://gitbox.apache.org/repos/asf/openoffice.git
>
>
> The following commit(s) were added to refs/heads/AOO41X by this push:
>  new 5a5de59  Add support for Azul JDK's
> 5a5de59 is described below
>
> commit 5a5de594da9b5e283ddf91696613752c382591ca
> Author: Arrigo Marchiori 
> AuthorDate: Fri Feb 11 09:45:16 2022 +0100
>
> Add support for Azul JDK's
> ---
>  main/scripting/java/build.xml | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/main/scripting/java/build.xml b/main/scripting/java/build.xml
> index 176db83..017913d 100644
> --- a/main/scripting/java/build.xml
> +++ b/main/scripting/java/build.xml
> @@ -97,6 +97,7 @@
>
>   casesensitive="false" />
>   casesensitive="false" />
> + casesensitive="false" />
>
>  
>



smime.p7s
Description: S/MIME Cryptographic Signature


Re: Check for English spelling extension updates broken?

2022-02-11 Thread Pedro Lino
Hi Andrea

Do you have time for this issue during this weekend?

Regards,
Pedro

> On 02/03/2022 11:01 PM Andrea Pescetti  wrote:
> 
>  
> Pedro Lino wrote:
> > I found some odd results. If the user has an older than 2017 version of the 
> > dictionary, the Extension Update dialog will report that version 2017.05.01 
> > is available. If the user has the 2017.05.01 version or newer it will 
> > always report that "No new updates are available."
> 
> This is not odd actually, it is quite easily explained.
> 
> The update feed, much like the one we use for OpenOffice itself, has 
> information on the latest available version. If you don't update it (I 
> mean, "updating the update feed") for a while it will still advertise 
> the old version as "latest", and the logic is that if you have a newer 
> version than what the feed believes is the "latest" then you are 
> considered to not need the update.
> 
> I'm surely available to show you all details, just please let FOSDEM 
> pass... but it is just round the corner, links coming in a separate mail.
> 
> Regards,
>Andrea.
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org

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