On Sunday 07 June 2009 20:11:47 3BUIb3S50i 3BUIb3S50i wrote:
From FMS:
fala...@ixvqeqm0lyydtmyaf5z49sjzuxr7ntqkoqvyg0hvitw wrote :
I tried to update to #1215 and now I find this message, and I am still on
#1214:
Your node has found the auto-updater's revocation key on the network. It
From FMS:
fala...@ixvqeqm0lyydtmyaf5z49sjzuxr7ntqkoqvyg0hvitw wrote :
I tried to update to #1215 and now I find this message, and I am still on
#1214:
Your node has found the auto-updater's revocation key on the network. It
means that our auto-updating system is likely to have been
Is this fixed now? Does your node update itself satisfactorily?
On Wed, 2006-07-05 at 19:26 -0400, Joel Salomon wrote:
> My node (build #858 r9464) has been telling me, since early this
> morning, that it "is currently doing a final check to verify the
> security of the update." What can be
Mine does. :)
On 5/19/07, Matthew Toseland wrote:
> Is this fixed now? Does your node update itself satisfactorily?
>
> On Wed, 2006-07-05 at 19:26 -0400, Joel Salomon wrote:
> > My node (build #858 r9464) has been telling me, since early this
> > morning, that it "is currently doing a final
Is this fixed now? Does your node update itself satisfactorily?
On Wed, 2006-07-05 at 19:26 -0400, Joel Salomon wrote:
My node (build #858 r9464) has been telling me, since early this
morning, that it is currently doing a final check to verify the
security of the update. What can be
Mine does. :)
On 5/19/07, Matthew Toseland [EMAIL PROTECTED] wrote:
Is this fixed now? Does your node update itself satisfactorily?
On Wed, 2006-07-05 at 19:26 -0400, Joel Salomon wrote:
My node (build #858 r9464) has been telling me, since early this
morning, that it is currently doing a
On Tue, Jun 20, 2006 at 05:37:17PM -0400, Juiceman wrote:
> Couldn't we have the node immediately check for the revocation key
> when it finds a new update and wait for the revocation key check to
> return before displaying the update button? Admittedly there would be
> a tiny chance that the key
Couldn't we have the node immediately check for the revocation key
when it finds a new update and wait for the revocation key check to
return before displaying the update button? Admittedly there would be
a tiny chance that the key could be blown in between when the
revocation was checked for and
On Sun, Jun 18, 2006 at 08:13:44PM -0400, Joel Salomon wrote:
> How is auto-updating supposed to work? I have auto-update
> notification enabled, updating disabled; should I be able to click
> "update" on the local node web-page and have the node update? (It
> claims to be doing so...)
Yes, but
On Sun, Jun 18, 2006 at 08:13:44PM -0400, Joel Salomon wrote:
How is auto-updating supposed to work? I have auto-update
notification enabled, updating disabled; should I be able to click
update on the local node web-page and have the node update? (It
claims to be doing so...)
Yes, but it
Couldn't we have the node immediately check for the revocation key
when it finds a new update and wait for the revocation key check to
return before displaying the update button? Admittedly there would be
a tiny chance that the key could be blown in between when the
revocation was checked for
On Tue, Jun 20, 2006 at 05:37:17PM -0400, Juiceman wrote:
Couldn't we have the node immediately check for the revocation key
when it finds a new update and wait for the revocation key check to
return before displaying the update button? Admittedly there would be
a tiny chance that the key
How is auto-updating supposed to work? I have auto-update
notification enabled, updating disabled; should I be able to click
"update" on the local node web-page and have the node update? (It
claims to be doing so...)
Thanks,
--Joel
How is auto-updating supposed to work? I have auto-update
notification enabled, updating disabled; should I be able to click
update on the local node web-page and have the node update? (It
claims to be doing so...)
Thanks,
--Joel
___
Support mailing
14 matches
Mail list logo
