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