infozip-6.0-i486-1.txz not available from slackware.cs.utah.edu

[B_ISC]

I don't know if they are down temporarily or being hit hard, but the v5 to v6 upgrade script tries to download infozip from slackware.cs.utah.edu and it is just retrying over and over...even attempting to go directly to http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/a/infozip-6.0-i486-1.txz or

http://slackware.cs.utah.edu/pub/slackware/slackware-13.37/slackware/a/infozip-6.0-i486-1.txz

gives me a download that stalls to a standstill.

 

I can't find any other location for this file, so I'm guessing manual upgrade (windows flash extraction of 6.0.1 zip file) will be my only method...I will try again tomorrow in case they are just down for maint.

 

Terminal Message:

 

--2015-08-02 23:13:06--  (try:16)  http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/a/infozip-6.0-i486-1.txz

Connecting to slackware.cs.utah.edu (slackware.cs.utah.edu)|155.98.64.87|:80... failed: Connection timed out.

Resolving slackware.cs.utah.edu (slackware.cs.utah.edu)... 155.98.64.87

Connecting to slackware.cs.utah.edu (slackware.cs.utah.edu)|155.98.64.87|:80... failed: Connection timed out.

Retrying.

 

[saarg]

I had no problem downloading the file here. Migth be your internet provider have some problems?

[NAS]

try just opening  http://slackware.cs.utah.edu in a browser.

 

 

[Squid]

I had the same issue with Perl downloading from http://slackware.cs.utah.edu.  Wound up downloading it from a mirror instead.

[B_ISC]

Yes, the www site shows the listing, but the download still stalled and died, any download from the utah site dies. I found a meta4 file that had a list of mirrors for the download. i downloaded the infozip, moved it to where the install script was saving it to, installed the package, installed the unraid package and everything went through flawlessly. The script should find a way to access the mirrors instead of relying on one server.

[BRiT]

It might be wise for LimeTech to host the file themselves for the purpose of updating.

[B_ISC]

I wouldn't do that, that would take the package out of the update chain through the mirrors. Just link to the mirror list or list multiple locations in the package request.