View Single Post
EMAD's Avatar
Posts: 16 | Thanked: 4 times | Joined on Dec 2009 @ Ontario, Canada
#6
Did you check if you spelled fremantle correctly under the Distribution field?

I was unable to connect after installing the repository from http://repository.maemo.org/

However, after adding modifying the catalog field "Distribution" from blank to "Fremantle", the app manager was able to connect.

Hope this helps.



Originally Posted by malaeum View Post
First of all let me say thank you to the community around here, you guys are dealing with an onslaught of issues admirably.

Let me preface my request here by saying that I have had an N800 for over a year and am quite familiar the use of repositories. I have used exclusively debian/ubuntu for over four years now and like to think I understand how this stuff works.

Now that being said, I feel like a total idiot right now having to come here and ask about this. My N900 arrived two hours ago and I've been playing around with it. I'm trying to enable the extras-devel and extras-testing repositories (yes I understand the risks, I've reflashed my N800 a few times due to issues). I went ahead and added them as per the respective wiki pages for each (same as Diablo/Chinook basically). I then took the red pill (perhaps I should have done this before I added them?). Upon trying to refresh the repositories I get the following error:

"http://repository.maemo.org/extras-testing/dists/freemantle/free/binary-armel/Packages 404 Not Found [IP: 64.208.126.83 80]"

And another very similar error for the non-free packages. I've tried deleting and re-adding both testing and devel a few times, been extra careful and triple checked spelling and haven't had any luck. I am able to access the file just fine from my PC however. I did notice that on my desktop, when I ping repository.maemo.org the IP it is pinging does not match that which is found in the error. I am not sure if there is a DNS issue going on here but I doubt it. I am using google's DNS on the N900 and comcasts on the desktop.

Anyone able to think of what could be causing this other than somesort of wonky DNS issues? If I'm missing something obvious please feel free to ridicule me. ;-)