Author Topic: Help! Todays updated deleted miranda. How do I continue  (Read 3529 times)

0 Members and 1 Guest are viewing this topic.

Offline thosrtanner

  • Jr. Member
  • **
  • Posts: 56
Seriously. My miranda NG folders contains no  miranda executable. If I try to install it tells me the directory already exists. How on earth am I meant to continue?
 

Offline Wishmaster

Re: Help! Todays updated deleted miranda. How do I continue
« Reply #1 on: 14 06 2016, 21:51:11 »
Just download and extract binary from here (*.zip-Version).

I know why it did it, I'll fix it right now.

Done!
« Last Edit: 14 06 2016, 21:59:30 by Wishmaster »
 

Offline borut

  • Newbie
  • *
  • Posts: 32
  • Country: pl
Re: Help! Todays updated deleted miranda. How do I continue
« Reply #2 on: 15 06 2016, 07:00:32 »
For me the same thing. After restoring from an archive, I update error.
 

Offline Vulpix

Re: Help! Todays updated deleted miranda. How do I continue
« Reply #3 on: 15 06 2016, 07:31:26 »
It happened to me yesterday and I spoke to wishmaster, I thought it was only affecting the debug symbols version. Seems it affected all of them.

I did try updating just now however and it seems that the 32bit (nightly, no debug symbols) version doesn't wanna update. The other ones (stable and nightly with debug symbols) are working just fine.

The error seems to be a missing file with hashes:

[09:30:11 11D4] [PluginUpdater] (1536) Connected to miranda-ng.org:80

[09:30:11 11D4] [PluginUpdater] (04EE1278:1536) Data sent
GET /distr/x32/hashes.zip HTTP/1.1
User-Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; Trident/6.0)
Cache-Control: no-cache
Pragma: no-cache
Accept-Encoding: deflate, gzip
Host: miranda-ng.org
Connection: Keep-Alive
Proxy-Connection: Keep-Alive


[09:30:11 11D4] [PluginUpdater] (04EE1278:1536) Data received
HTTP/1.1 404 Not Found

[09:30:11 11D4] [PluginUpdater] (04EE1278:1536) Data received
Server: nginx/1.8.0
Date: Wed, 15 Jun 2016 07:30:10 GMT
Content-Type: text/html
Content-Length: 570
Connection: keep-alive
Keep-Alive: timeout=20
Set-Cookie: _ga_cid=0.000267.1465975810.87264510404; path=/; domain=.miranda-ng.org

<html>
<head><title>404 Not Found</title></head>
<body bgcolor="white">
<center><h1>404 Not Found</h1></center>
<hr><center>nginx/1.8.0</center>
</body>
</html>
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
 

Offline Wishmaster

Re: Help! Todays updated deleted miranda. How do I continue
« Reply #4 on: 15 06 2016, 07:36:16 »
For me the same thing. After restoring from an archive, I update error.
Yes, same problem as in the post above yours.
 

Offline Wishmaster

Re: Help! Todays updated deleted miranda. How do I continue
« Reply #5 on: 15 06 2016, 07:37:27 »
It happened to me yesterday and I spoke to wishmaster, I thought it was only affecting the debug symbols version. Seems it affected all of them.

I did try updating just now however and it seems that the 32bit (nightly, no debug symbols) version doesn't wanna update. The other ones (stable and nightly with debug symbols) are working just fine.

The error seems to be a missing file with hashes:
You mean watcher, not me? :)

And yes, hashes.zip seem to be  missing.
 

Offline Vulpix

Re: Help! Todays updated deleted miranda. How do I continue
« Reply #6 on: 15 06 2016, 07:49:26 »
Yess sorry sorry :< sleepy in the morning. I meant Watcher.
 

Offline thosrtanner

  • Jr. Member
  • **
  • Posts: 56
Re: Help! Todays updated deleted miranda. How do I continue
« Reply #7 on: 15 06 2016, 19:30:38 »
So I should refrain from updating for a while?
 

Offline Wishmaster

Re: Help! Todays updated deleted miranda. How do I continue
« Reply #8 on: 15 06 2016, 20:33:45 »
So I should refrain from updating for a while?
It's fixed the next build