Check for English spelling extension updates broken?

[Pedro Lino-4]

Hi all

I am testing version 4.1.9 RC1 under Windows 7 and I just noticed that the English spelling extension I have installed is from 2020.07.01 but Checking for updates does not report any new version.
This is particularly odd because this extension is updated monthly (including in January 2021).

Installing an older version of another extension does detect new versions so this not a problem with Checking for Extension Updates but seems specific for this extension (and maybe for others too).

Can someone confirm this problem?

Just to be clear: this is not a regression or an obstacle for the release of 4.1.9 RC1, the problem also occurs in 4.1.8

Thanks!
Pedro

[Czesław Wolański]

Hi Pedro,

4.1.9 RC1, Windows 7
English spelling extension:
I can confirm your observation - checking for update of any version
(2020.07.01 - 2020.12.01)
results in a message "No new updates are available.".

Regards,
Czesław

Am Di., 19. Jan. 2021 um 13:04 Uhr schrieb Pedro Lino
<[hidden email]>:

> Hi all
>
> I am testing version 4.1.9 RC1 under Windows 7 and I just noticed that the
> English spelling extension I have installed is from 2020.07.01 but Checking
> for updates does not report any new version.
> This is particularly odd because this extension is updated monthly
> (including in January 2021).
>
> Installing an older version of another extension does detect new versions
> so this not a problem with Checking for Extension Updates but seems
> specific for this extension (and maybe for others too).
>
> Can someone confirm this problem?
>
> Just to be clear: this is not a regression or an obstacle for the release
> of 4.1.9 RC1, the problem also occurs in 4.1.8
>
> Thanks!
> Pedro
>

[Marco A.G. Pinto]

I am the maintainer, but I don't remember making any changes that could be causing this.

All I change are the dictionary files, version number of the extension and the release notes.

Not sure why it happens.

On 19/01/2021 12:04, Pedro Lino wrote:

Hi all

I am testing version 4.1.9 RC1 under Windows 7 and I just noticed that the English spelling extension I have installed is from 2020.07.01 but Checking for updates does not report any new version.
This is particularly odd because this extension is updated monthly (including in January 2021).

Installing an older version of another extension does detect new versions so this not a problem with Checking for Extension Updates but seems specific for this extension (and maybe for others too).

Can someone confirm this problem?

Just to be clear: this is not a regression or an obstacle for the release of 4.1.9 RC1, the problem also occurs in 4.1.8

Thanks!
Pedro

[Pedro Lino-4]

Hi Marco

This may be broken for a long time. Please remember that checking for updates (extensions or program) was broken for years.

It is only since 4.1.8 that it is working again.

But this is only a problem for people who need the English dictionary but do not use the Windows English installer (which is very likely a minority...)

Regards,

Pedro

On 01/19/2021 1:15 PM Marco A.G. Pinto <[hidden email]> wrote:

I am the maintainer, but I don't remember making any changes that could be causing this.

All I change are the dictionary files, version number of the extension and the release notes.

Not sure why it happens.

On 19/01/2021 12:04, Pedro Lino wrote:

Hi all

I am testing version 4.1.9 RC1 under Windows 7 and I just noticed that the English spelling extension I have installed is from 2020.07.01 but Checking for updates does not report any new version.
This is particularly odd because this extension is updated monthly (including in January 2021).

Installing an older version of another extension does detect new versions so this not a problem with Checking for Extension Updates but seems specific for this extension (and maybe for others too).

Can someone confirm this problem?

Just to be clear: this is not a regression or an obstacle for the release of 4.1.9 RC1, the problem also occurs in 4.1.8

Thanks!
Pedro

[Pedro Lino-4]

Hi Czeslaw

> On 01/19/2021 1:14 PM Czesław Wolański <[hidden email]> wrote:

> 4.1.9 RC1, Windows 7
> English spelling extension:
> I can confirm your observation - checking for update of any version
> (2020.07.01 - 2020.12.01)
> results in a message "No new updates are available.".

Thank you for confirming!
There is also no information on new versions available when using AOO version 4.1.8 under Ubuntu 20.04 (which included the English spelling extension from 2020.10.01) which means it is also not a Windows problem, but it is specific to this extension.

Regards,
Pedro

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Matthias Seidel]

Hi,

My understanding is:

AOO is looking for an "update feed", quite similar to the release updates.
(Release update feeds are generated by hand after every release)

In this case it looks for the feed on the SourceForge server. My guess is, that these feeds are not generated anymore.
I don't know if this was an automatic or a manual process.

Regards,

   Matthias

Am 19.01.21 um 14:15 schrieb Marco A.G. Pinto:

I am the maintainer, but I don't remember making any changes that could be causing this.

All I change are the dictionary files, version number of the extension and the release notes.

Not sure why it happens.

On 19/01/2021 12:04, Pedro Lino wrote:

Hi all

I am testing version 4.1.9 RC1 under Windows 7 and I just noticed that the English spelling extension I have installed is from 2020.07.01 but Checking for updates does not report any new version.
This is particularly odd because this extension is updated monthly (including in January 2021).

Installing an older version of another extension does detect new versions so this not a problem with Checking for Extension Updates but seems specific for this extension (and maybe for others too).

Can someone confirm this problem?

Just to be clear: this is not a regression or an obstacle for the release of 4.1.9 RC1, the problem also occurs in 4.1.8

Thanks!
Pedro

[Pedro Lino-4]

Hi Matthias, Marco, all


>     On 01/19/2021 5:38 PM Matthias Seidel <[hidden email]> wrote:
>
>     AOO is looking for an "update feed", quite similar to the release updates.
>     (Release update feeds are generated by hand after every release)
>
>     In this case it looks for the feed on the SourceForge server. My guess is, that these feeds are not generated anymore.
>     I don't know if this was an automatic or a manual process.
>

Sourceforge seems to work. If you install the 2017.03.01 version or any older from
https://extensions.openoffice.org/en/project/english-dictionaries-apache-openoffice
you will be notified to update to 2017.05.01 (I noticed this because on my old XP laptop I still had version 2015.10.01 and was notified about updates after installing 4.1.9RC1)

So the last notification is from version 2017.05.01 and nobody noticed because 2017 was probably when the Update function was broken.

I hope this helps fixing the issue ;)

Regards,
Pedro

[Matthias Seidel]

Hi Pedro,

Am 20.01.21 um 00:47 schrieb Pedro Lino:

> Hi Matthias, Marco, all
>
>
>>     On 01/19/2021 5:38 PM Matthias Seidel <[hidden email]> wrote:
>>
>>     AOO is looking for an "update feed", quite similar to the release updates.
>>     (Release update feeds are generated by hand after every release)
>>
>>     In this case it looks for the feed on the SourceForge server. My guess is, that these feeds are not generated anymore.
>>     I don't know if this was an automatic or a manual process.
>>
> Sourceforge seems to work. If you install the 2017.03.01 version or any older from
> https://extensions.openoffice.org/en/project/english-dictionaries-apache-openoffice
> you will be notified to update to 2017.05.01 (I noticed this because on my old XP laptop I still had version 2015.10.01 and was notified about updates after installing 4.1.9RC1)

Yes, requesting the feed itself should work again since AOO 4.1.8.
> So the last notification is from version 2017.05.01 and nobody noticed because 2017 was probably when the Update function was broken.

That's the real issue. The feed (at least for the English dictionary) is
outdated.
I think there was a Drupal update maybe in 2017?

This would be discussed with SourceForge. Personally I have no time to
do so...

Regards,

   Matthias

>
> I hope this helps fixing the issue ;)
>
> Regards,
> Pedro
>

[Andrea Pescetti-2]

On 20/01/2021 Matthias Seidel wrote:
> Am 20.01.21 um 00:47 schrieb Pedro Lino:
>>>      On 01/19/2021 5:38 PM Matthias Seidel wrote:
>>>      In this case it looks for the feed on the SourceForge server. My guess is, that these feeds are not generated anymore.
>>>      I don't know if this was an automatic or a manual process.

Generation is automated, but go-live is manual. And this seems to have
been forgotten...

>> you will be notified to update to 2017.05.01 ...
> That's the real issue. The feed (at least for the English dictionary) is
> outdated.

I think we can fix it. Let me give it a try tomorrow.

The relevant feed is described here:
https://wiki.openoffice.org/wiki/Extensions/website/update_feed
but the URL in our case is slightly different; you find it in your local
versionrc (version.ini on Windows?) file and it should point (after
redirection) to
https://extensions.openoffice.org/ExtensionUpdateService/check.Update

As you can verify by downloading it, the feed is there but it was last
updated in June 2017 indeed.

What I can do tomorrow is: I can check whether our (site moderator)
access is enough to push the updated feed live; and I'll document it
internally in case.

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Pedro Lino-4]

Hi Andrea

> On 01/20/2021 10:23 PM Andrea Pescetti <[hidden email]> wrote:

> I think we can fix it. Let me give it a try tomorrow.

Excellent! Thanks!

> What I can do tomorrow is: I can check whether our (site moderator)
> access is enough to push the updated feed live; and I'll document it
> internally in case.

Thank you again!

Regards,
Pedro

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Andrea Pescetti-2]

On 20/01/2021 Andrea Pescetti wrote:
> I think we can fix it. Let me give it a try tomorrow.

I believe it's fixed now (limited to the specific case of the English
dictionary; I had to find some workarounds so I enabled only that
extension for testing).

Please let me know if it works; if it does, I will then revert it and
republish only after 4.1.9 is out (or users will be confused by the
double update; this is exactly the reason for the update to be manual by
the way).

Before:

$ curl -s
https://extensions.openoffice.org/ExtensionUpdateService/check.Update |
grep -A1 org.openoffice.en.hunspell.dictionaries
     <identifier value="org.openoffice.en.hunspell.dictionaries"/>
     <version value="2017.05.01" />

After:

$ curl -s
https://extensions.openoffice.org/ExtensionUpdateService/check.Update |
grep -A1 org.openoffice.en.hunspell.dictionaries
     <identifier value="org.openoffice.en.hunspell.dictionaries"/>
     <version value="2021.01.01" />

To check: in OpenOffice, check for Extensions Updates (not OpenOffice
updates) and see whether this prompts you with an updated English
dictionary to be downloaded (with a web browser, not within OpenOffice)
and installed.

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Marcus (OOo)]

Am 21.01.21 um 21:04 schrieb Andrea Pescetti:

> On 20/01/2021 Andrea Pescetti wrote:
>> I think we can fix it. Let me give it a try tomorrow.
>
> I believe it's fixed now (limited to the specific case of the English
> dictionary; I had to find some workarounds so I enabled only that
> extension for testing).
>
> Please let me know if it works; if it does, I will then revert it and
> republish only after 4.1.9 is out (or users will be confused by the
> double update; this is exactly the reason for the update to be manual by
> the way).
>
> [...]
>
> To check: in OpenOffice, check for Extensions Updates (not OpenOffice
> updates) and see whether this prompts you with an updated English
> dictionary to be downloaded (with a web browser, not within OpenOffice)
> and installed.

wow \o/ , it's working again. :-)

My English and German dictionaries want to be updated.

A click on the [Install] button opens 2 tabs in my browser to the
extension website for both dictionaries.

Thanks for analysing this old problem.

Marcus


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Pedro Lino-4]

Hi Andrea

> On 01/21/2021 8:04 PM Andrea Pescetti <[hidden email]> wrote:

> I believe it's fixed now (limited to the specific case of the English
> dictionary; I had to find some workarounds so I enabled only that
> extension for testing).
> Please let me know if it works; if it does, I will then revert it and
> republish only after 4.1.9 is out (or users will be confused by the
> double update; this is exactly the reason for the update to be manual by
> the way).

It is fixed indeed (although I get 2 notifications for that extension, but one problem at a time!). Thanks!

It makes sense that it is manually to prevent double notifications but if an extension author submits a new version does s/he have permission to do that manual update or s/he has to request someone to do it? Is that the part that needs to be documented?

Thank you for solving this issue!

Regards,
Pedro

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Andrea Pescetti-2]

On 21/01/2021 Pedro Lino wrote:
>> Please let me know if it works; if it does, I will then revert it and
>> republish only after 4.1.9 is out ...
> It is fixed indeed (although I get 2 notifications for that extension, but one problem at a time!). Thanks!

OK, thank you for checking. I've now reverted the fix and we'll go live
with a more complete version when people will have upgraded to 4.1.9.

> if an extension author submits a new version does s/he have permission to do that manual update or s/he has to request someone to do it?

Extensions authors cannot trigger the update. Site moderators can (and
probably should) do it once in a while as a routine task. The worst
period is for sure when you are close to a release and the few weeks
after a release, since before the release you might be downloading a
newer version than the one coming with the release (like: if a bundled
extension was updated yesterday, 4.1.9 would contain an older extension
version than the one people would download today).

But when we are not in proximity of a release, we can trigger the update
perhaps once a month; fact is, the process I could find is still
cumbersome and requires shell commands to be run, so until we streamline
it it won't be run very frequently. And I would be against fully
automating it as some anti-spam checks might be needed, even though spam
is a problem on the Templates site much more than the Extensions site.

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Pedro Lino-4]

Hi Andrea

> On 01/21/2021 11:39 PM Andrea Pescetti <[hidden email]> wrote:

> OK, thank you for checking. I've now reverted the fix and we'll go live
> with a more complete version when people will have upgraded to 4.1.9.

Agreed. Thank you!
 
> But when we are not in proximity of a release, we can trigger the update
> perhaps once a month; fact is, the process I could find is still
> cumbersome and requires shell commands to be run, so until we streamline
> it it won't be run very frequently. And I would be against fully
> automating it as some anti-spam checks might be needed, even though spam
> is a problem on the Templates site much more than the Extensions site.

If/when the process is streamlined I can volunteer to run it on a monthly/2 months basis (except before and after a new AOO release).
It should be an improvement compared to 3 years :)

Regards,
Pedro

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Matthias Seidel]

Hi Andrea,

When would be the best time for an update?

Regards,

   Matthias

Am 22.01.21 um 00:39 schrieb Andrea Pescetti:

> On 21/01/2021 Pedro Lino wrote:
>>> Please let me know if it works; if it does, I will then revert it and
>>> republish only after 4.1.9 is out ...
>> It is fixed indeed (although I get 2 notifications for that
>> extension, but one problem at a time!). Thanks!
>
> OK, thank you for checking. I've now reverted the fix and we'll go
> live with a more complete version when people will have upgraded to
> 4.1.9.
>
>> if an extension author submits a new version does s/he have
>> permission to do that manual update or s/he has to request someone to
>> do it?
>
> Extensions authors cannot trigger the update. Site moderators can (and
> probably should) do it once in a while as a routine task. The worst
> period is for sure when you are close to a release and the few weeks
> after a release, since before the release you might be downloading a
> newer version than the one coming with the release (like: if a bundled
> extension was updated yesterday, 4.1.9 would contain an older
> extension version than the one people would download today).
>
> But when we are not in proximity of a release, we can trigger the
> update perhaps once a month; fact is, the process I could find is
> still cumbersome and requires shell commands to be run, so until we
> streamline it it won't be run very frequently. And I would be against
> fully automating it as some anti-spam checks might be needed, even
> though spam is a problem on the Templates site much more than the
> Extensions site.
>
> Regards,
>   Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

[Pedro Lino-4]

Hi again Andrea

Marco has released two versions since the one included in AOO 4.1.9

Can you update this or teach us how to do it?

Thanks!

Regards,
Pedro

> On 03/10/2021 4:42 PM Matthias Seidel <[hidden email]> wrote:
>
>  
> Hi Andrea,
>
> When would be the best time for an update?
>
> Regards,
>
>    Matthias
>
> Am 22.01.21 um 00:39 schrieb Andrea Pescetti:
> > On 21/01/2021 Pedro Lino wrote:
> >>> Please let me know if it works; if it does, I will then revert it and
> >>> republish only after 4.1.9 is out ...
> >> It is fixed indeed (although I get 2 notifications for that
> >> extension, but one problem at a time!). Thanks!
> >
> > OK, thank you for checking. I've now reverted the fix and we'll go
> > live with a more complete version when people will have upgraded to
> > 4.1.9.
> >
> >> if an extension author submits a new version does s/he have
> >> permission to do that manual update or s/he has to request someone to
> >> do it?
> >
> > Extensions authors cannot trigger the update. Site moderators can (and
> > probably should) do it once in a while as a routine task. The worst
> > period is for sure when you are close to a release and the few weeks
> > after a release, since before the release you might be downloading a
> > newer version than the one coming with the release (like: if a bundled
> > extension was updated yesterday, 4.1.9 would contain an older
> > extension version than the one people would download today).
> >
> > But when we are not in proximity of a release, we can trigger the
> > update perhaps once a month; fact is, the process I could find is
> > still cumbersome and requires shell commands to be run, so until we
> > streamline it it won't be run very frequently. And I would be against
> > fully automating it as some anti-spam checks might be needed, even
> > though spam is a problem on the Templates site much more than the
> > Extensions site.
> >
> > Regards,
> >   Andrea.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]