23 Aug
2015
23 Aug
'15
4:11 p.m.
On Sunday 23 of August 2015 15:43:29 Gene Heskett wrote:
On Sunday 23 August 2015 08:21:24 Slávek Banko wrote:
The problem is that the package lists are updated, but the packages themselves
are not yet all on the mirror => apt tries to download packages from the
primary server == download is slow. Unfortunately, this also slows
synchronization to mirror. So it becomes a little vicious circle.
Although you can switch directly to the mirror, but for packages that are not
yet available on the mirror you will receive http error 404. However, yes,
this would reduce the load on line to primary server.
Alternatively, you can temporarily switch to the preliminary stable builds
repository, where are now also R14.0.1 - compiled from identical source
packages as is on the official build farm.
--
Slávek
On Sunday 23 of August 2015 13:53:19 Gene Heskett
wrote:
My apologies Slavec, and excuse my N. A. English keyboard, I have no clue
how to generate tha accent marked a in your name.
I had assumed the mirrors were already updated when it was made visible
yesterday evening. I just canceled it, and will let it sit there till
this evening.
I also do not know if I am using a mirror.
From /etc/apt/sources.list
deb
http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-r14.0.0/debian
wheezy main
deb
http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps-r14.0.
0/debian wheezy main
Do those get redirected to a mirror somehow? Or am I beating on your
server only & I need to edit & correct that list?
Thank you.
Cheers, Gene Heskett On Sunday 23 August 2015 03:23:07 Gene Heskett
wrote:
Publishing r14.0.1 to official mirrors is underway. And because the
line to the primary server has a low bandwith, is again overloaded.
Please give it some time and try again later. Greetings;
It originally was going to update 324 packages, but not all could
be downloaded, so now its back in the download phase, having
updated about 100 that it could get the first time. 214 to go,
but the download screen is confusing because its not being kept up
to date.
At one point I was looking at an estimated time to completion of 1
day + 23 hours, with a download rate of about 2k a second.
Right now is says 2278 B/s for file 13 of 278.
07:50 the next morning, showing about 5k/second, on file 116 of 278.
About 7 hours left by its estimate.
Did we melt the server down?
Cheers, Gene Heskett
Cheers, Gene Heskett