debian-archive-keyring installing ubuntu keys?

[Daniel Pocock <daniel@pocock.com.au>]

I have a project that is building in the travis-ci.org environment
(based on Ubuntu)

I added the following to .travis.yml to try and make it use packages
from sid:

 before_install:
  - sudo apt-get update -qq
  - sudo apt-get install -qq debian-archive-keyring
  - sudo add-apt-repository -y "deb http://http.debian.net/debian/ sid main"
  - sudo apt-get update -qq
  - sudo apt-get install -qq gperf libasio-dev libboost-dev
libc-ares-dev libdb++-dev ........



The log shows the following output:

Unpacking debian-archive-keyring (from
.../debian-archive-keyring_2010.08.28_all.deb) ...
Setting up debian-archive-keyring (2010.08.28) ...
gpg: key 437D05B5: "Ubuntu Archive Automatic Signing Key
<ftpmaster@ubuntu.com>" not changed
gpg: key FBB75451: "Ubuntu CD Image Automatic Signing Key
<cdimage@ubuntu.com>" not changed
gpg: Total number processed: 2
gpg:              unchanged: 2

...

$ sudo apt-get update -qq
W: GPG error: http://http.debian.net sid InRelease: The following
signatures couldn't be verified because the public key is not available:
NO_PUBKEY 8B48AD6246925553
...
$ sudo apt-get install -qq gperf libasio-dev libboost-dev libc-ares-dev
libdb++-dev libpopt-dev libssl-dev ......
WARNING: The following packages cannot be authenticated!
  locales libnih-dbus1 libnih1 libc-dev-bin libc6-dev libc6 libdb5.3
perl .....
  .....
  .....


Is this simply because I'm trying to use packages from sid?  Or is this
"debian-archive-keyring" package at fault?  My understanding is that
because the package has debian in the name, it will give me Debian
project keys.


Build log:
https://travis-ci.org/resiprocate/resiprocate/jobs/21572385