How to resolve expired GPG key

1,566 views
Skip to first unread message

Scott W

unread,
Dec 19, 2014, 1:24:45 AM12/19/14
to beagl...@googlegroups.com
I've successfully updated two BBB to the latest 2014-12-11 Debian image.  I ran into a small problem trying to upgrade one more.

When executing sudo apt-get update I'm seeing a GPG error that the other two boards didn't have.  Any help resolving this would be appreciated!

debian@beaglebone:~$ uname -a
Linux beaglebone 3.8.13-bone68 #1 SMP Sat Nov 22 02:12:03 UTC 2014 armv7l GNU/Linux
debian@beaglebone:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2014-12-11

debian@beaglebone:~$ sudo apt-get update
Hit http://repos.rcn-ee.net wheezy Release.gpg
Hit http://ftp.us.debian.org wheezy Release.gpg
Get:1 http://debian.beagleboard.org wheezy-bbb Release.gpg [490 B]
Hit http://repos.rcn-ee.net wheezy Release
Hit http://security.debian.org wheezy/updates Release.gpg
Hit http://ftp.us.debian.org wheezy-updates Release.gpg
Hit http://debian.beagleboard.org wheezy-bbb Release
Hit http://security.debian.org wheezy/updates Release
Ign http://debian.beagleboard.org wheezy-bbb Release
Hit http://ftp.us.debian.org wheezy Release
Hit http://repos.rcn-ee.net wheezy/main armhf Packages
Hit http://ftp.us.debian.org wheezy-updates Release
Hit http://debian.beagleboard.org wheezy-bbb/main armhf Packages
Hit http://security.debian.org wheezy/updates/main armhf Packages
Hit http://security.debian.org wheezy/updates/contrib armhf Packages
Hit http://security.debian.org wheezy/updates/non-free armhf Packages
Hit http://ftp.us.debian.org wheezy/main armhf Packages
Hit http://ftp.us.debian.org wheezy/contrib armhf Packages
Hit http://ftp.us.debian.org wheezy/non-free armhf Packages
Hit http://ftp.us.debian.org wheezy-updates/main armhf Packages
Hit http://ftp.us.debian.org wheezy-updates/contrib armhf Packages
Hit http://ftp.us.debian.org wheezy-updates/non-free armhf Packages
Fetched 490 B in 8s (57 B/s)
Reading package lists... Done
W: GPG error: http://debian.beagleboard.org wheezy-bbb Release: The following signatures were invalid: KEYEXPIRED 1418840246 KEYEXPIRED 1418840304 KEYEXPIRED 1418840246 KEYEXPIRED 1418840246 KEYEXPIRED 1418840304

-- Scott

John Syn

unread,
Dec 19, 2014, 1:44:57 AM12/19/14
to beagl...@googlegroups.com

From: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Reply-To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Date: Thursday, December 18, 2014 at 10:24 PM
To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Subject: [beagleboard] How to resolve expired GPG key
My guess is your date/time is wrong. Try "sudo ntpdate-debian” and try again. 

Regards,
John

-- Scott

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Robert Nelson

unread,
Dec 19, 2014, 9:36:48 AM12/19/14
to Beagle Board
So long story short, we can't actually update that repo anymore...

For the factory "2014-05-14" image the procedure is a little more indepth:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#W:_GPG_error:_http:.2F.2Fdebian.beagleboard.org_wheezy-bbb

But for you the first part only applies. (disable the repo in
/etc/apt/sources.list)

I spent yesterday merging the final 50 or so "node-xyz" packages to
repos.rcn-ee.net..

So even thou the key expired, in the end you get all the "jessie" node
backports..

Regards,

--
Robert Nelson
http://www.rcn-ee.com/
Reply all
Reply to author
Forward
0 new messages