On 10/03/22 Pedro Lino wrote:
Thanks to Andrea's clear instructions we now have one more trained "staff" to
do this update ;)
Thank you for taking over! I'll try to get the instructions posted to
some "official" shared space by this weekend.
Regards,
Andrea.
Hi Marcus,
Am 10.03.22 um 21:12 schrieb Marcus:
> Am 10.03.22 um 18:21 schrieb Matthias Seidel:
>> Am 10.03.22 um 17:52 schrieb Pedro Lino:
>>>
>>> Yes, it was updated on March 1st
>>>
>>> Thanks to Andrea's clear instructions we now have one more trained
>>> "staff" to do this update ;)
>>>
>>>
Am 10.03.22 um 18:21 schrieb Matthias Seidel:
Am 10.03.22 um 17:52 schrieb Pedro Lino:
Yes, it was updated on March 1st
Thanks to Andrea's clear instructions we now have one more trained "staff" to
do this update ;)
I can confirm that it also works perfectly under Linux using the 4.1.12
Hi Pedro,
Am 10.03.22 um 17:52 schrieb Pedro Lino:
> Hi Matthias
>
> Yes, it was updated on March 1st
>
> Thanks to Andrea's clear instructions we now have one more trained "staff" to
> do this update ;)
>
> I can confirm that it also works perfectly under Linux using the 4.1.12
> Nightly
Hi Matthias
Yes, it was updated on March 1st
Thanks to Andrea's clear instructions we now have one more trained "staff" to
do this update ;)
I can confirm that it also works perfectly under Linux using the 4.1.12 Nightly
builds
Maybe this is a good enough motive to release 4.1.12 to all?
Hi Pedro, all,
Am 19.02.22 um 17:56 schrieb Pedro Lino:
> Hi Andrea, all
>
>> On 02/13/2022 10:11 PM Andrea Pescetti wrote:
>> I'm assuming lazy consensus on giving you permissions on the Extensions
>> site (not the site itself, actually, but the shell access). You should
>> post here your
On 20.02.22 00:41, Andrea Pescetti wrote:
On 19/02/22 Pedro Lino wrote:
no one opposes that I have permissions on the Extensions shell access?
Done! You have it now.
Who can handle this so you can teach me further steps?
I've written extensive documentation with the aim of adding it to
On 19/02/22 Pedro Lino wrote:
no one opposes that I have permissions on the Extensions shell access?
Done! You have it now.
Who can handle this so you can teach me further steps?
I've written extensive documentation with the aim of adding it to
Hi Andrea, all
> On 02/13/2022 10:11 PM Andrea Pescetti wrote:
> I'm assuming lazy consensus on giving you permissions on the Extensions
> site (not the site itself, actually, but the shell access). You should
> post here your SourceForge username for you to be added.
>
> Once we are ready
Hi Andrea
> On 02/13/2022 10:11 PM Andrea Pescetti wrote:
> I had to try a lot of times since apparently the process changed since
> the last time I checked this, but I was able to login at last and it's
> still weekend!
Thank you for taking some time to do this and for testing first!
>
On 11/02/22 Pedro Lino wrote:
Do you have time for this issue during this weekend?
Hello Pedro,
I had to try a lot of times since apparently the process changed since
the last time I checked this, but I was able to login at last and it's
still weekend!
So, the first steps on your side,
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
Hi Andrea
Thank you for the fast reply!
> On 02/03/2022 11:01 PM Andrea Pescetti wrote:
> 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
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."
Returning to this subject:
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
Hi Matthias
> On 02/03/2022 11:04 AM Matthias Seidel wrote:
> Is it possible to re-activate the update feed for SourceForge?
I'm available to do this if someone helps me. Andrea?
Regards,
Pedro
> Am 15.03.21 um 21:12 schrieb Pedro Lino:
> > Hi again Andrea
> >
> > Marco has released two
Hi Pedro, all,
Bumping this one up:
Is it possible to re-activate the update feed for SourceForge?
Regards,
Matthias
Am 15.03.21 um 21:12 schrieb Pedro Lino:
> 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
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 wrote:
>
>
> Hi Andrea,
>
> When would be the best time for an update?
>
> Regards,
>
>
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
Hi Andrea
> On 01/21/2021 11:39 PM Andrea Pescetti 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
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
Hi Andrea
> On 01/21/2021 8:04 PM Andrea Pescetti 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
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
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
Hi Andrea
> On 01/20/2021 10:23 PM Andrea Pescetti 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
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
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 wrote:
>>
>> AOO is looking for an "update feed", quite similar to the release
>> updates.
>> (Release update feeds are generated by hand after every release)
>>
Hi Matthias, Marco, all
> On 01/19/2021 5:38 PM Matthias Seidel 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
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
Hi Czeslaw
> On 01/19/2021 1:14 PM Czesław Wolański 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!
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
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
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
:
> Hi all
>
> I
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
34 matches
Mail list logo
