Application manager reports that python cannot be installed, however, looking into what programs I have installed, python is listed, albeit broken. In my case the repositories are not the issue, just installing the file has become very troublesome.

A log would help us fix the problem for you a lot more quickly. There's a log entry in the App Manager menu. Newest stuff is at the bottom.

dpkg: dependency problems prevent configuration of python2.5-runtime:
python2.5-runtime depends on python2.5-cairo (>= 1.4.0-1osso1); however:
Package python2.5-cairo is not installed.
dpkg: error processing python2.5-runtime (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
python2.5-runtime
E: Sub-process /usr/bin/dpkg returned an error code (1)

Thats what is reported in the log.

Ok, The magic day is here and still nothing is installing.

Does anyone have a list of repositories that should be on my device just so I can do a reset and make sure I am trying to connect to the correct ones.

I mean the original Nokia and base repositories?

Thanks,

Under the circumstances shouldn't we expect a formal announcement and clarification by Nokia?

Perhaps I missed an update or something else is wrong in my setup but I am still not getting applications to download.

Are things fixed yet?

I believe, I read a post in the last few days that said the repositories were fixed - if this is the case then you should just disable the 2 Temporary repos and enable the originals.

If that doesn't fix things and you still can't download applications, then we need more details as to what you've tried and what error messages you're getting. There is also a log file in the menu of the applications manager that could shed some light on why you're having problems

You really need to be more specific. If you cannot get any applications to download, you are in serious trouble. If you can't get some certain applications to download, you need to tell us something about them.

By the way, I have car problems -- what should I do?

I just replaced my temp hildon*.list with my backed up original and did a apt-get update; apt-get dist-upgrade. The update ran fine, then the upgrade downloaded/installed the new drop of mplayer w/o errors from repository.maemo.org.

Can anyone point me to an official statement on the state of the Repositories and whether they are now properly fixed?

I have seen hearsay and rumour on the forums that they have been but my experience suggests otherwise.

My Application Manager log is here replicated in case it helps shed some light on both mine and others' issues. It may be helpful to ignore the Tuomas Kulve rep for the time being.


hildon-application-manager 2.0.1

apt-worker[1646]: GLIB CRITICAL ** GLib - g_strsplit_set: assertion `string != NULL' failed

apt-worker[1646]: GLIB CRITICAL ** GLib - g_strsplit_set: assertion `string != NULL' failed

W: GPG error: http://tuomas.kulve.fi chinook Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 94D0694709064463

W: GPG error: http://maemo-hackers.org chinook Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5FD45CD3EA68E29D

E: Failed to fetch http://repository.maemo.org/extras/d...el/Packages.gz

E: Failed to fetch http://repository.maemo.org/dists/ch...el/Packages.gz

W: Duplicate sources.list entry http://repository.maemo.org chinook/free Packages (/var/lib/apt/lists/repository.maemo.org_extras_dists_chinook_free_bin ary-armel_Packages)

W: Duplicate sources.list entry http://repository.maemo.org chinook/non-free Packages (/var/lib/apt/lists/repository.maemo.org_extras_dists_chinook_non-free_binary-armel_Packages)

W: You may want to run apt-get update to correct these problems

W: GPG error: http://maemo-hackers.org chinook Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5FD45CD3EA68E29D

W: GPG error: http://tuomas.kulve.fi chinook Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 94D0694709064463