Developer discussion for Creative Commons technology and tools

[Burobjorn <burobjorn AT gmail.com>]

I'm probably an idiot, but I could not get the correct key to work with
the CC repository.

I get:

W: GPG error: http://mirrors.creativecommons.org hardy Release: The
following signatures couldn't be verified because the public key is not
available: NO_PUBKEY 51A2E86C1B01F328
W: You may want to run apt-get update to correct these problems

I used the instructions here:
http://mirrors.creativecommons.org/packages/

All the best,

grtz
BjornW


met vriendelijke groet,
Bjorn Wijers

* b u r o b j o r n .nl *
digitaal vakmanschap | digital craftsmanship

Concordiastraat 68-126
3551 EM Utrecht
The Netherlands

phone: +31 30 2444 101
http://www.burobjorn.nl


Asheesh Laroia wrote:
> On Sun, 22 Jun 2008, Asheesh Laroia wrote:
> 
>> On Monday I'll switch this to using a CC key that I sign.  And then
>> I'll publish instructions. (-:
> 
> Okay, an update for everyone who wants to use the Creative Commons
> Ubuntu packages:
> 
> http://mirrors.creativecommons.org/packages/ has updated instructions,
> and the repository is now signed by a "Creative Commons archive key". 
> In order to have your apt setup trust that key, run these commands:
> 
> $ gpg --keyserver subkeys.pgp.net --recv-key 0x1B01F328
> $ gpg -a --export 0x1B01F328 | sudo apt-key add -
> $ sudo apt-get update
> 
> Then make sure you have the right sources.list entries in, as per
> http://mirrors.creativecommons.org/packages/.
> 
> Then try:
> 
> $ sudo aptitude install liblicense-cli
> 
> Ta-da!
> 
> (Next on the queue is amd64 packages.  (Greg, note that both signing the
> repository and shipping Debian sid packages are impossible with
> Launchpad's Personal Package Archives, so already I'm beating them on
> features.))
> 
> -- Asheesh.
>