New SDF files for 4.2.0

2018-11-25 Thread Andrea Pescetti 
On 25/11/2018 Mechtilde wrote:> now I'm able to create sdf files based 
on the source code and the files

in Pootle.


(changing subject since I'm not commenting on the build issue, but on 
the other information).


This is good news! Have you experienced/fixed the two issues I had 
found, meaning that you can go through gsicheck successfully and that 
you found a way to move strings to their new place?



So I think we need a branch whre we can work for the next release like 4.2.


We should just use trunk. We branch only for "stabilization", i.e., 
close to a release. But the real active development happens on trunk.



@ Jim: Can you gererate a 4.2 branch up to r 184789. Then I can put the
new sdf files. I did it manually for 6 Languages.
I will do it then for all Languages in Pootle.


Just ask Infra to get shell access to translate.apache.org (this is done 
by opening a JIRA ticket; Pootle is not an OpenOffice-specific service, 
so Infra manages it completely). I admit I haven't tried that way since 
I only exported Italian and a couple other test languages back at the time.



After then I can create new *.po files to import in Pootle.


This will be an especially important step. We haven't imported strings 
into Pootle for a long time. If all the workflow up to and including 
this step can be fixed, we will be able to engage translators and 
preserve their work.



I will also publish the documentation after migration of the wiki.


The "old" https://wiki.openoffice.org is free for editing at any time 
until you see a prominent notice on all pages. Don't worry, content 
published before we put the notice will all be migrated.


Regards,
  Andrea.

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

Re: Please test the new MWiki: https://wikitest.openoffice.org

2018-11-25 Thread Andrea Pescetti 

On 15/07/2018 Andrea Pescetti wrote:

https://wikitest.openoffice.org
Please test it as follows:
- if you don't have an account, just browse the pages and check that 
everything looks good
- if you have an account, please login with the same username/password 
you use for MWiki and check that you can edit pages normally.


All reported bugs have been fixed today. The test instance was 
synchronized with production the wiki a few hours ago, so all content 
and images should be there.


You are welcome to take a look, since we will have to make a final 
synchronization in a few days as Infra needs to switch off the old server.


I can reproduce, but I am not addressing at the moment, the following 3 
issues that apply to the old MWiki too (so they can be fixed after 
migration):


1. Reported by Aleksey Evgenievich Harlamenkov: 
https://wikitest.openoffice.org/wiki/Documentation/Dashboard/Wiki_Editing_Policy 
image is missing in the "To place the image on a page" section.


2. Reported by Pedro Lino: the link in the "Account creation for Apache 
OpenOffice Wiki" email points to
<">https://wiki.openoffice.org/wiki/Main_Page> 
https://wiki.openoffice.org/wiki/Main_Page

where the ending "greater than" character is included in the link.

3. Reported by Matthias: new graphics to implement:
https://home.apache.org/~mseidel/header.png
(to replace /w/skins/aoo/header.png)
https://home.apache.org/~mseidel/asf_logo_simple.png
(to replace /w/ASFLogo/asf_logo_simple.png)
https://home.apache.org/~mseidel/favicon.ico
(to replace /favicon.png)

These 3 will be fixed after we are on the new server.

Regards,
  Andrea.

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

Re: Please test the new MWiki: https://wikitest.openoffice.org

2018-11-25 Thread Andrea Pescetti 

On 15/07/2018 Алексей Евгеньевич Харламенков wrote:

Andrea! good afternoon.


Sorry, it's been a while, but we had the MWiki update in the pipeline 
after the 4.1.6 release. https://wikitest.openoffice.org/ has been 
refreshed today and I'll answer to pending issues below and in separate 
messages.


It is still safe to edit content on the Wiki normally; we'll put a 
prominent notice there while we do the final migration, probably at some 
point next week.



My profile is missing graphics.
https://wikitest.openoffice.org/wiki/User:Sancho


This was https://bz.apache.org/ooo/show_bug.cgi?id=127943 and it is now 
fixed.



On the wiki home page, links "in other languages" lead to the old wiki.


This is due to hard-coded links. The new server will use the same URL as 
the old one, so this won't be a problem after migration (but thanks for 
reporting).


Regards,
  Andrea.

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

Re: svn commit: r1847342 - in /openoffice/trunk/main: ./ postprocess/packcomponents/ solenv/ant/ solenv/gbuild/ xmerge/ xmerge/java/ xmerge/java/XMergeBridge/ xmerge/java/XMergeBridge/java/ xmerge/jav

2018-11-25 Thread Matthias Seidel 
Hi Damjan,

Am 25.11.18 um 14:45 schrieb Damjan Jovanovic:
> One problem was that GNU make 3.8.1, which we use on the Linux buildbots,
> doesn't have the:
> $(file < ...)
> function. I've now changed it to use:
> $(shell cat ...)
> instead. This doesn't however explain why the Windows buildbot also failed
> in xmerge, as its GNU make is recent enough.

Thank you for the explanation!

As it also failed on CentOS 7 (our build environment for 4.2.0) this fix
is highly appreciated.

>
> Another problem was that Windows fail to build in main/bean due to missing
> symbols. Some are clearly from USER32.DLL, which I've added now, but one is
> from Java's AWT library which is stored in $(AWTLIB) as "-lawt" which seems
> to be in the wrong format for Microsoft's linker...

I have forced build on all buildbots incl. Windows.

Regards,

   Matthias

>
>
> On Sun, Nov 25, 2018 at 12:20 AM Matthias Seidel 
> wrote:
>
>> Linux-32 and Windows builds also fail in xmerge.
>>
>> Matthias
>>
>> Am 24.11.18 um 16:08 schrieb Matthias Seidel:
>>> Hi Damjan,
>>>
>>> This commit breaks at least our Linux-64 builds:
>>>
>>>
>> https://ci.apache.org/projects/openoffice/buildlogs/linux64/main/xmerge/unxlngx6.pro/misc/logs/prj.txt
>>> Regards,
>>>
>>>Matthias
>>>
>>> Am 24.11.18 um 08:58 schrieb dam...@apache.org:
 Author: damjan
 Date: Sat Nov 24 07:58:57 2018
 New Revision: 1847342

 URL: http://svn.apache.org/viewvc?rev=1847342&view=rev
 Log:
 Add a "dependencies" target for Ant to allow extracting the JARs that
 a Java module depends on. Use this to make Ant targets depends on
 their dependencies in gbuild, so that Java submodules within a
 main/ module build in the correct order.

 Port main/xmerge to gbuild/Ant using this approach.

 Patch by: me


 Added:
 openoffice/trunk/main/xmerge/Ant_XMergeBridge.mk
 openoffice/trunk/main/xmerge/Ant_aportisdoc.mk
 openoffice/trunk/main/xmerge/Ant_htmlsoff.mk
 openoffice/trunk/main/xmerge/Ant_pexcel.mk
 openoffice/trunk/main/xmerge/Ant_pocketword.mk
 openoffice/trunk/main/xmerge/Ant_xmerge-javadoc.mk
 openoffice/trunk/main/xmerge/Ant_xmerge.mk
 openoffice/trunk/main/xmerge/Makefile   (with props)
 openoffice/trunk/main/xmerge/Module_xmerge.mk
 openoffice/trunk/main/xmerge/Package_xmergesync.mk
 openoffice/trunk/main/xmerge/java/
 openoffice/trunk/main/xmerge/java/XMergeBridge/
   - copied from r1847341,
>> openoffice/trunk/main/xmerge/source/bridge/
 openoffice/trunk/main/xmerge/java/XMergeBridge/src/
 openoffice/trunk/main/xmerge/java/XMergeBridge/src/main/
 openoffice/trunk/main/xmerge/java/XMergeBridge/src/main/java/
   - copied from r1847335,
>> openoffice/trunk/main/xmerge/source/bridge/java/
 openoffice/trunk/main/xmerge/java/aportisdoc/
   - copied from r1847341,
>> openoffice/trunk/main/xmerge/source/aportisdoc/
 openoffice/trunk/main/xmerge/java/aportisdoc/src/
 openoffice/trunk/main/xmerge/java/aportisdoc/src/main/
 openoffice/trunk/main/xmerge/java/aportisdoc/src/main/java/
   - copied from r1847335,
>> openoffice/trunk/main/xmerge/source/aportisdoc/java/
 openoffice/trunk/main/xmerge/java/aportisdoc/src/main/resources/

>>  openoffice/trunk/main/xmerge/java/aportisdoc/src/main/resources/META-INF/
>>  
>> openoffice/trunk/main/xmerge/java/aportisdoc/src/main/resources/META-INF/converter.xml
   - copied unchanged from r1847335,
>> openoffice/trunk/main/xmerge/source/aportisdoc/converter.xml
 openoffice/trunk/main/xmerge/java/htmlsoff/
   - copied from r1847341,
>> openoffice/trunk/main/xmerge/source/htmlsoff/
 openoffice/trunk/main/xmerge/java/htmlsoff/src/
 openoffice/trunk/main/xmerge/java/htmlsoff/src/main/
 openoffice/trunk/main/xmerge/java/htmlsoff/src/main/java/

>>  openoffice/trunk/main/xmerge/java/htmlsoff/src/main/java/package.html
   - copied unchanged from r1847335,
>> openoffice/trunk/main/xmerge/source/htmlsoff/package.html
 openoffice/trunk/main/xmerge/java/htmlsoff/src/main/resources/

>>  openoffice/trunk/main/xmerge/java/htmlsoff/src/main/resources/META-INF/
>>  
>> openoffice/trunk/main/xmerge/java/htmlsoff/src/main/resources/META-INF/converter.xml
   - copied unchanged from r1847335,
>> openoffice/trunk/main/xmerge/source/htmlsoff/converter.xml
>>  openoffice/trunk/main/xmerge/java/htmlsoff/src/main/resources/htmltosoff.xsl
   - copied unchanged from r1847335,
>> openoffice/trunk/main/xmerge/source/htmlsoff/htmltosoff.xsl
>>  openoffice/trunk/main/xmerge/java/htmlsoff/src/main/resources/sofftohtml.xsl
   - copied unchanged from r1847335,
>> openoffice/trunk/main/xmerge/source/htmlsoff/sofftohtml.xsl
 openoffice/trunk/main/xmerge/java/pexcel/
   - copied from r1847341,
>> openoffice/trunk/

Re: svn commit: r1847342 - in /openoffice/trunk/main: ./ postprocess/packcomponents/ solenv/ant/ solenv/gbuild/ xmerge/ xmerge/java/ xmerge/java/XMergeBridge/ xmerge/java/XMergeBridge/java/ xmerge/jav

2018-11-25 Thread Damjan Jovanovic 
One problem was that GNU make 3.8.1, which we use on the Linux buildbots,
doesn't have the:
$(file < ...)
function. I've now changed it to use:
$(shell cat ...)
instead. This doesn't however explain why the Windows buildbot also failed
in xmerge, as its GNU make is recent enough.

Another problem was that Windows fail to build in main/bean due to missing
symbols. Some are clearly from USER32.DLL, which I've added now, but one is
from Java's AWT library which is stored in $(AWTLIB) as "-lawt" which seems
to be in the wrong format for Microsoft's linker...


On Sun, Nov 25, 2018 at 12:20 AM Matthias Seidel 
wrote:

> Linux-32 and Windows builds also fail in xmerge.
>
> Matthias
>
> Am 24.11.18 um 16:08 schrieb Matthias Seidel:
> > Hi Damjan,
> >
> > This commit breaks at least our Linux-64 builds:
> >
> >
> https://ci.apache.org/projects/openoffice/buildlogs/linux64/main/xmerge/unxlngx6.pro/misc/logs/prj.txt
> >
> > Regards,
> >
> >Matthias
> >
> > Am 24.11.18 um 08:58 schrieb dam...@apache.org:
> >> Author: damjan
> >> Date: Sat Nov 24 07:58:57 2018
> >> New Revision: 1847342
> >>
> >> URL: http://svn.apache.org/viewvc?rev=1847342&view=rev
> >> Log:
> >> Add a "dependencies" target for Ant to allow extracting the JARs that
> >> a Java module depends on. Use this to make Ant targets depends on
> >> their dependencies in gbuild, so that Java submodules within a
> >> main/ module build in the correct order.
> >>
> >> Port main/xmerge to gbuild/Ant using this approach.
> >>
> >> Patch by: me
> >>
> >>
> >> Added:
> >> openoffice/trunk/main/xmerge/Ant_XMergeBridge.mk
> >> openoffice/trunk/main/xmerge/Ant_aportisdoc.mk
> >> openoffice/trunk/main/xmerge/Ant_htmlsoff.mk
> >> openoffice/trunk/main/xmerge/Ant_pexcel.mk
> >> openoffice/trunk/main/xmerge/Ant_pocketword.mk
> >> openoffice/trunk/main/xmerge/Ant_xmerge-javadoc.mk
> >> openoffice/trunk/main/xmerge/Ant_xmerge.mk
> >> openoffice/trunk/main/xmerge/Makefile   (with props)
> >> openoffice/trunk/main/xmerge/Module_xmerge.mk
> >> openoffice/trunk/main/xmerge/Package_xmergesync.mk
> >> openoffice/trunk/main/xmerge/java/
> >> openoffice/trunk/main/xmerge/java/XMergeBridge/
> >>   - copied from r1847341,
> openoffice/trunk/main/xmerge/source/bridge/
> >> openoffice/trunk/main/xmerge/java/XMergeBridge/src/
> >> openoffice/trunk/main/xmerge/java/XMergeBridge/src/main/
> >> openoffice/trunk/main/xmerge/java/XMergeBridge/src/main/java/
> >>   - copied from r1847335,
> openoffice/trunk/main/xmerge/source/bridge/java/
> >> openoffice/trunk/main/xmerge/java/aportisdoc/
> >>   - copied from r1847341,
> openoffice/trunk/main/xmerge/source/aportisdoc/
> >> openoffice/trunk/main/xmerge/java/aportisdoc/src/
> >> openoffice/trunk/main/xmerge/java/aportisdoc/src/main/
> >> openoffice/trunk/main/xmerge/java/aportisdoc/src/main/java/
> >>   - copied from r1847335,
> openoffice/trunk/main/xmerge/source/aportisdoc/java/
> >> openoffice/trunk/main/xmerge/java/aportisdoc/src/main/resources/
> >>
>  openoffice/trunk/main/xmerge/java/aportisdoc/src/main/resources/META-INF/
> >>
>  
> openoffice/trunk/main/xmerge/java/aportisdoc/src/main/resources/META-INF/converter.xml
> >>   - copied unchanged from r1847335,
> openoffice/trunk/main/xmerge/source/aportisdoc/converter.xml
> >> openoffice/trunk/main/xmerge/java/htmlsoff/
> >>   - copied from r1847341,
> openoffice/trunk/main/xmerge/source/htmlsoff/
> >> openoffice/trunk/main/xmerge/java/htmlsoff/src/
> >> openoffice/trunk/main/xmerge/java/htmlsoff/src/main/
> >> openoffice/trunk/main/xmerge/java/htmlsoff/src/main/java/
> >>
>  openoffice/trunk/main/xmerge/java/htmlsoff/src/main/java/package.html
> >>   - copied unchanged from r1847335,
> openoffice/trunk/main/xmerge/source/htmlsoff/package.html
> >> openoffice/trunk/main/xmerge/java/htmlsoff/src/main/resources/
> >>
>  openoffice/trunk/main/xmerge/java/htmlsoff/src/main/resources/META-INF/
> >>
>  
> openoffice/trunk/main/xmerge/java/htmlsoff/src/main/resources/META-INF/converter.xml
> >>   - copied unchanged from r1847335,
> openoffice/trunk/main/xmerge/source/htmlsoff/converter.xml
> >>
>  openoffice/trunk/main/xmerge/java/htmlsoff/src/main/resources/htmltosoff.xsl
> >>   - copied unchanged from r1847335,
> openoffice/trunk/main/xmerge/source/htmlsoff/htmltosoff.xsl
> >>
>  openoffice/trunk/main/xmerge/java/htmlsoff/src/main/resources/sofftohtml.xsl
> >>   - copied unchanged from r1847335,
> openoffice/trunk/main/xmerge/source/htmlsoff/sofftohtml.xsl
> >> openoffice/trunk/main/xmerge/java/pexcel/
> >>   - copied from r1847341,
> openoffice/trunk/main/xmerge/source/pexcel/
> >> openoffice/trunk/main/xmerge/java/pexcel/src/
> >> openoffice/trunk/main/xmerge/java/pexcel/src/main/
> >> openoffice/trunk/main/xmerge/java/pexcel/src/main/java/
> >>   - copied from r1847335,
> openoffice/trunk/main/xmerge/source/pexcel/java/
> >>

Re: Check for Updates broken?

2018-11-25 Thread Pedro Lino 

> On November 25, 2018 at 12:13 PM Matthias Seidel < 
> matthias.sei...@hamburg.de mailto:matthias.sei...@hamburg.de > wrote:
> 

> No need to download it again as it is already in your profile. Just add
> it by using "Add..."
> 

That doesn't work unless you have the oxt file
There is also an error in detection of the local version (could be related to 
the failed communication)


> 
> > > Another fix that requires developer time...
> > 
> > > If you can find the time? ;-)
> 

As I mentioned before I'm not a developer

Regards,
Pedro

Re: Check for Updates broken?

2018-11-25 Thread Matthias Seidel 
Am 25.11.18 um 13:09 schrieb Pedro Lino:
> Hi Matthias
>
>
>> > > This means that the program is getting version 
>> information from the server so some communication is passing through...
>>> > You did a reinstall without deleting the profile? Probably you 
>>> updated
>> some dictionary before and AOO just finds them locally...
>>
> You are right. There goes the theory about some communication working :)
>
> The message (and action required) does not make sense then. If AOO finds a 
> newer version locally then it should use the newer version or at least ask if 
> you want to use the newer version... It doesn't make sense to download it 
> again from the server if it is already installed.
No need to download it again as it is already in your profile. Just add
it by using "Add..."
>
> Another fix that requires developer time...

If you can find the time? ;-)

Regards,

   Matthias

>
> Regards,
> Pedro
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Check for Updates broken?

2018-11-25 Thread Pedro Lino 
Hi Matthias


> 
> > > This means that the program is getting version 
> information from the server so some communication is passing through...
> > 
> > > You did a reinstall without deleting the profile? Probably you 
> > updated
> some dictionary before and AOO just finds them locally...
> 

You are right. There goes the theory about some communication working :)

The message (and action required) does not make sense then. If AOO finds a 
newer version locally then it should use the newer version or at least ask if 
you want to use the newer version... It doesn't make sense to download it again 
from the server if it is already installed.

Another fix that requires developer time...

Regards,
Pedro

Re: Check for Updates broken?

2018-11-25 Thread Matthias Seidel 
Am 25.11.18 um 11:58 schrieb Pedro Lino:
> Hi Dave, Andrea, all
>
>> Let’s do our required migrations this week and then we can play with this TLS
>> issue. This may be more complex. My concern is whether or not older AOO is
>> even using TLS. Since legacy forums and wiki must be cut over by Nov 30th we
>> must prioritize.
> Agreed. 
> Keep in mind that previous versions worked until 2-3 weeks ago
> This problem also occurs on version 4.1.5 running on Windows XP (where no 
> updates to the OS occur) so any modification is on the server side.
>
> An interesting detail: I reinstalled version 4.1.5 on a Windows XP netbook 
> and I do get the "New Updates for Extensions" icon and warning but clicking 
> on it returns the same error mentioned before.
>
> This means that the program is getting version information from the server so 
> some communication is passing through...

You did a reinstall without deleting the profile? Probably you updated
some dictionary before and AOO just finds them locally...

Regards,

   Matthias

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



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Small website refresh

2018-11-25 Thread George Karalis 
Hello Francis,

Keep in mind that this is just a prototype to see if you like the overall look 
and feel
that I designed. I just wanted to illustrate my idea and what’s better than a 
fully
functional prototype.

As for the three download buttons, well there's one at the header which will be 
visible on all pages that will serve as a call to action button for users to 
download
OpenOffice(which will lead at the downloads page). The homepage’s hero download
button will serve as a quick download button, so the user downloads the correct 
OpenOffice for his/hers system immediately without having to go to the 
downloads 
page(this is not yet fully implemented, so you only see the download for 
windows,
which for the purpose of the prototype leads again to the downloads page). The 
other releases button serves the purpose, that if a user for example is on a 
windows
machine and wants to download a linux flavour of OpenOffice, to install later on
another linux computer, goes to a page that lists all OpenOffices builds. As i 
couldn't find such a page, in the original website I again redirected to the 
downloads
page(could also lead to the sourceforge page for now). As for the wrong choice 
you've been offered that is true a different thing that affects the current 
downloads 
page.

All I am asking now is if I could have access to a staging environment(maybe in
another url, as I don't want to mess with your current staging site, as  you 
may want 
to make changes there), so I can make those changes and having a fully working 
and
tested homepage within this week, that we can move live.

Thanks in advance,
George


> On 24 Nov 2018, at 06:25, F C. Costero  wrote:
> 
> I like the update. I am puzzled by the three different Download
> buttons/links. The one at the top right says Download, there is a central
> one for Download For Windows, and a small link under that that says Other
> Platforms. All three lead to the standard download page where the OS is
> detected automatically. On this Linux Mint system I am using, the Download
> For Windows button results in me being offered the Linux 64 bit RPM (RPM is
> the wrong choice, but that is a different problem). Why is the button
> labeled as a Windows download?
> Please keep this effort going!
> Francis
> 
> On Fri, Nov 23, 2018 at 2:46 AM George Karalis  wrote:
> 
>> https://thorbust.github.io/openoffice-website/ <
>> https://thorbust.github.io/openoffice-website/>
>> 
>> This is the updated homepage. I ‘d love to hear your feedback and if you
>> feel like it
>> we can move it to production.
>> 
>> As for the MSVC I will send sometime next week the work I have done in
>> the MSVC thread.
>> 
>> Regards,
>> George
>> 
>> 
>> 
>>> On 22 Nov 2018, at 11:52, Peter Kovacs  wrote:
>>> 
>>> Nice job.
>>> 
>>> I am not sure if I am fully remeber the Page.
>>> 
>>> We used to use a CMS system from Apache that is unmaintained. Infra
>>> recommended that we move away from it.
>>> 
>>> This seems a good point to switch the workflow we use? Maybe trying to
>>> move towards static Pages created with Hugo?
>>> 
>>> This would be worth a look.
>>> 
>>> 
>>> About MSVC, where can I see your work?- Is it maybe possible to create a
>>> github repository where you upload your changes?
>>> 
>>> I am curious on the nature of changes needed to be done.
>>> 
>>> 
>>> Please keep up your engagement. This is appreciated.
>>> 
>>> 
>>> All the best
>>> 
>>> Peter
>>> 
>>> 
>>> On 20.11.18 17:59, George Karalis wrote:
 Hello,
 
 I have redesigned and implemented the new homepage in code. I have also
>> setup the
 local web development environment and integrated the code. If anyone
>> likes to view
 the redesigned homepage I can provide a static html, that you can view
>> in your browser,
 to be reviewed etc.
 
 If you are up for a refresh, I want to know how could i send the
>> updated repository,
 or if I could have commit access to the user end portal.
 
 Also, having worked with the website's build process, it’s a little bit
>> counterintuitive,
 especially for modern web development, so I propose to build
>> openoffice.org using
 a static site generator. I recommend Hugo . I can
>> take this as a long project, as in a
 few weeks I am probably finishing with the MSVC update.
 
 Thanks,
 George
 
 
> On 19 Nov 2018, at 14:30, Pedro Lino  wrote:
> 
> As a user, a Big +1
> 
> Very nice layout!
> 
> Best,
> Pedro
>> On November 19, 2018 at 12:04 PM George Karalis 
>> wrote:
>> 
>> 
>> Hello everyone,
>> 
>> Since the 4.1.6 release is out, I was thinking for a small update at
>> the openoffice.org  homepage
>> to make the end users onboarding a little bit easier. I ‘ve coded a
>> little sample that you can see
>> bellow, so if you are ok with a refresh on the homepage I can
>> integrate the code within the
>> c

Re: Check for Updates broken?

2018-11-25 Thread Pedro Lino 
Hi Dave, Andrea, all

> Let’s do our required migrations this week and then we can play with this TLS
> issue. This may be more complex. My concern is whether or not older AOO is
> even using TLS. Since legacy forums and wiki must be cut over by Nov 30th we
> must prioritize.

Agreed. 
Keep in mind that previous versions worked until 2-3 weeks ago
This problem also occurs on version 4.1.5 running on Windows XP (where no 
updates to the OS occur) so any modification is on the server side.

An interesting detail: I reinstalled version 4.1.5 on a Windows XP netbook and 
I do get the "New Updates for Extensions" icon and warning but clicking on it 
returns the same error mentioned before.

This means that the program is getting version information from the server so 
some communication is passing through...

Regards,
Pedro

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