|
2011-02-22
, 04:50
|
|
Posts: 3,811 |
Thanked: 1,151 times |
Joined on Oct 2007
@ East Lansing, MI
|
#2
|
The Following User Says Thank You to Addison For This Useful Post: | ||
|
2011-02-22
, 10:35
|
Posts: 2,802 |
Thanked: 4,491 times |
Joined on Nov 2007
|
#3
|
The Following User Says Thank You to lma For This Useful Post: | ||
|
2011-02-22
, 14:50
|
Posts: 146 |
Thanked: 15 times |
Joined on Oct 2008
|
#4
|
You are not doing anything wrong, for some strange reason the repository started getting signed (and incorrectly at that) with the Fremantle key a while ago. See bug 11384 and feel free to vote for it.
|
2011-02-22
, 14:54
|
Posts: 146 |
Thanked: 15 times |
Joined on Oct 2008
|
#5
|
I think you have the wrong repositories.
Double check that they are all for Diablo and none for Fremantle.
I am trying since a long time to download/update .deb packages with aptget, and it fails badly:
W: GPG error: http://repository.maemo.org diablo Release: The following signatures were invalid: BADSIG E40DC434616730BD maemo.org Extras repositories (Fremantle Extras) <repositories@maemo.org>
W: GPG error: http://repository.maemo.org diablo Release: The following signatures were invalid: BADSIG E40DC434616730BD maemo.org Extras repositories (Fremantle Extras) <repositories@maemo.org>
W: You may want to run apt-get update to correct these problems
So:
1) Why it is taking forever to fix such a trivial issue as signatures? I googled for this error, and seems a very old one.
2) Why apt-get is complaining about "Fremantle Extras" if I use Diablo, and no reference to Fremantle exists on my apt source files?
3) How can I overcome this problem?
Thanks!!
Cheers,
L.