First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 69185
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: John Mylchreest (RETIRED) <johnm@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Nick Berardi <nberardi@zigamorph.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 69185 depends on: Show dependency tree
Show dependency graph
Bug 69185 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2004-10-27 13:57 0000 
Mirrorselect is selecting all mirrors that time out or won't let me connect. 
Is selecting all mirrors that end in *.de, which is half a world away from
Pennsylvania, USA.  I know that I am not having problems just generally
connecting to mirrors from my location because when I manually configure the
mirrors for make.conf, and choose ones that are in the US and by me I get
connections of up 400Kb/s.

Reproducible: Always
Steps to Reproduce:
1. follow the steps to select mirror in the setup instructions.
2.
3.

Actual Results:  
Gave me invalid mirrors and mirrors that average 30Kb/s.

Expected Results:  
Gave me mirrors that are actually giving good download speeds, not mirrors 
half a world away.  I found mirrors at Notre Dom that give me connections at 
400Kb/s.

------- Comment #1 From Kurt Lieber 2004-10-27 14:13:56 0000 ------- 
Kicking over to johnm, who maintains mirrorselect.

------- Comment #2 From John Mylchreest (RETIRED) 2004-11-07 04:11:55 0000 ------- 
this might be due to a change in the way mirrorselect utilizes wget.
checking...

------- Comment #3 From Cory Cameron 2004-11-14 09:58:50 0000 ------- 
I have the same issue with mirrorselect.  When mirrorselect is used in deep
mode (-D), the url's that are unable to be resolved, are instantly returned. 
So their time is shorter than the fastest download.  Therefore mirrorselect
selects them as the fastest sites.  I believe that is where the issue is.  I
have the issue in 0.84 and 0.86.

------- Comment #4 From John Mylchreest (RETIRED) 2004-11-14 15:37:11 0000 ------- 
I have just comitted 0.87, this should solve the issue.
the problem was pretty simple. $? returned 0 regardless of whether or not wget returned 0.
this has now been solved and should work fine, any problems please let me know.
First Last Prev Next    No search results available      Search page      Enter new bug