Linux Mint Forums

I've been away for a few days, and started to take care of updates. When running apt-get update, I get the following message:
The apparent entry in my sources.list file causing the issue seems to be:
Any advice on what's going on, or how to fix?

Hello all,
I'm a newbie to Linux Mint. If you help me I will be your friend, or give you a piece of candy!
I have this error after I did an update around Feb 18? 2011.
Any help would be appreciated... I don't really know what else to do.

I have the latest version of Mint Debian. There was an error with the last update because the internet shut down.
I never re-started the computer, I just closed the update program and re-started it. It seemed to work fine with the internet on
but now I get an error when I update.

Below this line is my error message:

W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ftp.debian.org testing Release: The following signatures were invalid: BADSIG AED4B06F473041FA Debian Archive Automatic Signing Key (6.0/squeeze) <ftpmaster@debian.org>

W: Failed to fetch http://ftp.debian.org/debian/dists/testing/Release

W: Some index files failed to download, they have been ignored, or old ones used instead.
End of error message

Thanks for the help! I really don't want to switch back to "MS Win-Don'ts"! Great work on this OS everyone! I love it!!!

There seems to be a general problem with this - also reported in IRC and at the Debian forums

I suggest waiting until it gets fixed.

Does this issue appear in Squeeze or only in 'testing' ?

I am using both, Squeeze in one OS, and am currently in my Debian/Mint 'testing' install . . . I recently updated and do not have this problem.

I did notice that this same issue has appeared in the Debian User Forums, as well. Hopefully, a 'fix' will come swiftly.

Disabling testing solves it - so it seems like testing only.

Testing respoitory is working again

Using Testing here. I had 100 updates, they seem to have worked OK. Still getting the error message at this time. Most likely it will get worked out in due time.

I get that too...but it is on and off...somedays it does that and other days it doesn't...so it seems to be a widespread kind of bug...and since it was mentioned it was reported, i would imagine it will eventually get fixed...doesn't seem to affect the updates from coming in (thankfully)

I am also using the default (debian testing of course)...

Seems to be fixed now. I just got a lump of about 14 updates the first time it ran without errors to look for updates.

yeah it's been doing that lately - just keep trying again. one out of three apt-get updates manage to get it here

Yeah, it seems to have sorted itself out OK. Changed to a different error, and then a bit later all was good again. Thank you to all who looked into this.