On Wed, Nov 27, 2013 at 7:17 AM, Pedro wrote:
>
> Can someone please fix this AND create a mechanism so that in the future the
> Build ID of every official RC and Final version is automatically added to
> such a check list? IMO trusting that "someone" will remember to manually add
> it, is not a r
Hi Robinson, all
Robinson Tryon wrote
Version 3.6.7.1 is also the official RC1 from TDF
>>> Build ID for that one?
>>
>> Version 3.6.7.1 (Build ID: 9418c72)
>
> Here's what we have listed for 3.6.7 builds:
>
> # 3.6.7 versions
> 'a61ad19-949f691-349cf55-3bea8d1-2c85eb' => '3.6
On Tue, Nov 26, 2013 at 7:24 AM, Pedro wrote:
> Robinson Tryon wrote
>>> Version: 4.1.0.1
>>> Build ID: 1b3956717a60d6ac35b133d7b0a0f5eb55e9155
>>
>> The Updater only knows about the following 4.1.0.1 builds:
>> '43286d64e6126b0915ae60d89d3177018fe63b9' => '4.1.0.1', # rc1
>> (buildfix1)
>>
Hi Robinson, all
Robinson Tryon wrote
>> Version: 4.1.0.1
>> Build ID: 1b3956717a60d6ac35b133d7b0a0f5eb55e9155
>
> The Updater only knows about the following 4.1.0.1 builds:
> '43286d64e6126b0915ae60d89d3177018fe63b9' => '4.1.0.1', # rc1
> (buildfix1)
> 'a7d538950185d02a6b950cd1cb2dfd794
Good morning Robinson, *,
On Dienstag, 26. November 2013 00:08 Robinson Tryon wrote:
> On Mon, Nov 25, 2013 at 5:57 PM, Pedro wrote:
[AutoUpdater does not work on Win]
> The Updater only knows about the following 4.1.0.1 builds:
> '43286d64e6126b0915ae60d89d3177018fe63b9' => '4.1.0.1', # rc1
>
On Mon, Nov 25, 2013 at 5:57 PM, Pedro wrote:
> Hi Christian, Robinson, all
>
>> Can you tell what version those report as? I.e. what git-hash they have?
>
> Version: 4.1.0.1
> Build ID: 1b3956717a60d6ac35b133d7b0a0f5eb55e9155
The Updater only knows about the following 4.1.0.1 builds:
'43286d
Hi Christian, Robinson, all
Christian Lohmaier-3 wrote
>> Version 4.1.0.1 still reports that "LibreOffice 4.1 is up to date." and
>> version 3.6.7.1 still reports "LibreOffice 3.6 is up to date."
>
> Can you tell what version those report as? I.e. what git-hash they have?
Version: 4.1.0.1
Build
Hi Pedro, *,
On Mon, Nov 25, 2013 at 5:45 PM, Pedro wrote:
> Christian Lohmaier-3 wrote
>> Anyway, I did reset it back to the version that's in the repo=the
>> version that should get you the update.
>
> Thank you for the fix. I didn't quite understand the git part...
There is a git repository a
On Mon, Nov 25, 2013 at 11:45 AM, Pedro wrote:
> Hi Christian, all
>
>
> Christian Lohmaier-3 wrote
>> Anyway, I did reset it back to the version that's in the repo=the
>> version that should get you the update.
Great!
> Apparently the version check algorithm only works correctly for the final
>
Hi Christian, all
Christian Lohmaier-3 wrote
> Anyway, I did reset it back to the version that's in the repo=the
> version that should get you the update.
Thank you for the fix. I didn't quite understand the git part... Does this
mean that you updated the version information manually or that you
Hi Christian, *,
Am 25.11.2013 14:32, schrieb Christian Lohmaier:
Hi Pedro, *,
On Mon, Nov 25, 2013 at 1:34 PM, Pedro wrote:
Based on my understanding of the updating mechanism (see the section
"Upgrade Logic"), your 4.1.0.1 install should give you an offer to
upgrade to 4.1.3 now. Could you p
Hi Pedro, *,
On Mon, Nov 25, 2013 at 1:34 PM, Pedro wrote:
>> Based on my understanding of the updating mechanism (see the section
>> "Upgrade Logic"), your 4.1.0.1 install should give you an offer to
>> upgrade to 4.1.3 now. Could you please check that out?
>
> Yes, it should. But it doesn't.
H
Hi qubit
Robinson Tryon wrote
> Based on my understanding of the updating mechanism (see the section
> "Upgrade Logic"), your 4.1.0.1 install should give you an offer to
> upgrade to 4.1.3 now. Could you please check that out?
Yes, it should. But it doesn't.
On another laptop with version 3.6.
On Mon, Nov 18, 2013 at 11:45 AM, Pedro wrote:
>
> I just checked for updates on a laptop I haven't used for a while. The
> installed version is 4.1.0.1 but Check for Updates returned "LibreOffice 4.1
> is up to date." Interesting... :)
Some notes on the updater are available here:
https://wiki.d
Ping! Any news?
Did anyone read
http://nabble.documentfoundation.org/How-long-before-a-released-build-is-notified-by-Update-tp4082780p4083805.html
?
Regards,
Pedro
--
View this message in context:
http://nabble.documentfoundation.org/How-long-before-a-released-build-is-notified-by-Update-tp40
Hi qubit
Robinson Tryon wrote
> It doesn't sound to absurd to me. I really don't know too much about
> the mechanisms of the updater, so let me get some info on the current
> state of things, and then I can see the feasibility of particular
> improvements.
I just checked for updates on a laptop
On Tue, Nov 12, 2013 at 12:09 PM, Pedro wrote:
> Hi Robinson (Rob? qubit?)
>
Well 'Rob' -> Rob Snelders, in the QA namespace, but the other two are
collision-free, AFAIK :-)
> Wouldn't it be possible to have a script checking on
> http://download.documentfoundation.org/libreoffice/stable/
> and
Hi Robinson (Rob? qubit?)
Robinson Tryon wrote
> AFAIK the update system is (still) handled manually. I think Cloph is
> the one in charge of it right now. I'm not sure exactly how we could
> automate the process, but I think it's worth our investigation.
As you know I'm not a Developer so you c
On Tue, Nov 12, 2013 at 11:19 AM, Pedro wrote:
> Hi all
>
> Does any one know what is the rule for a released build to be detected by
> Auto-update (or manual update) check?
>
> Version 4.1.3 was released on November 1st but my LO 4.1.2.3 still reports
> "LibreOffice 4.1 is up to date."
>
> Is the
Hi all
Does any one know what is the rule for a released build to be detected by
Auto-update (or manual update) check?
Version 4.1.3 was released on November 1st but my LO 4.1.2.3 still reports
"LibreOffice 4.1 is up to date."
Is there a problem with version 4.1.3? Or is simply the version on th
20 matches
Mail list logo
