|
2011-04-26
, 15:57
|
|
Posts: 47 |
Thanked: 78 times |
Joined on Dec 2010
@ New Delhi, India
|
#2
|
|
2011-04-26
, 16:03
|
|
Posts: 129 |
Thanked: 11 times |
Joined on Feb 2010
@ Bangalore, India
|
#3
|
|
2011-04-26
, 16:03
|
Posts: 5,795 |
Thanked: 3,151 times |
Joined on Feb 2007
@ Agoura Hills Calif
|
#4
|
|
2011-04-26
, 16:07
|
|
Posts: 129 |
Thanked: 11 times |
Joined on Feb 2010
@ Bangalore, India
|
#5
|
|
2011-04-26
, 16:12
|
Posts: 63 |
Thanked: 26 times |
Joined on Jul 2010
@ Canada
|
#6
|
I am not sure what the issue is in that case. I have been trying to update since the evening. Was working fine until last night!
The Following User Says Thank You to jprobichaud For This Useful Post: | ||
|
2011-04-26
, 16:18
|
Posts: 5,795 |
Thanked: 3,151 times |
Joined on Feb 2007
@ Agoura Hills Calif
|
#7
|
|
2011-04-26
, 16:24
|
|
Posts: 129 |
Thanked: 11 times |
Joined on Feb 2010
@ Bangalore, India
|
#8
|
It is possible that the mirror you're trying to reach is down (that happens to me frequently these days)
1) open an x-term
2) get root privileges (type "root" on the command prompt)
3) run the following command: echo "63.84.95.11 repository.maemo.org" >> /etc/hosts
Make sure you put 2 ">" signs or you'll get into troubles...
If you want to check first if that's the issue, try "ping repository.maemo.org" as root in an x-term session.
|
2011-04-26
, 16:26
|
|
Posts: 129 |
Thanked: 11 times |
Joined on Feb 2010
@ Bangalore, India
|
#9
|
Just to make sure, I reran apt-get update at 9:07 california time with no sign of problems.
I think the problem has to do with your setup. I have no idea what, however. Make sure you are not accidentally using the wrong router -- I caught myself doing that a few hours ago.
|
2011-04-26
, 16:40
|
Posts: 154 |
Thanked: 33 times |
Joined on Oct 2009
@ Lima-Perú
|
#10
|
Tags |
n900=crap |
Thread Tools | |
|
From what i got on searching the forum and bugzilla, this generally happens when either the servers are down or the repositories are being moved to different servers. I am attaching the logs that I captured while refreshing my repositories. The one captured at 1800 hours is the one I tried fetching over the 3G network and the other at 2047 hours is the one I tried fetching over the wifi network. This clearly rules out the issue of my ISP blocking the server pings.