package pools - why *does* this work?

[Brian May <bam@debian.org>]

>From this report:

     * heimdal 0.3d-5 (currently 0.2l-7) (low)
          + Maintainer: Brian May <bam@debian.org>
          + heimdal uploaded 11 days ago, out of date by 1 days!
          + out of date on m68k: heimdal-clients, heimdal-clients-x,
            heimdal-dev, heimdal-kdc, heimdal-lib, heimdal-servers,
            heimdal-servers-x (from 0.3d-2)
          + there are up to date bins in m68k also
          + out of date on sparc: heimdal-clients, heimdal-clients-x,
            heimdal-dev, heimdal-kdc, heimdal-lib, heimdal-servers,
            heimdal-servers-x (from 0.3c-4)
          + there are up to date bins in sparc also
          + not considered

I would conclude that the latest version of heimdal-dev available
for m68k is version 0.3d-2. True or False?

Now, looking at another package: libpam-heimdal
It has the following build-depends header:

Build-Depends: debhelper, heimdal-dev (>= 0.3d-5), libpam0g-dev, libdb2-dev, libssl096-dev

My understanding is that this means version 0.3d-5 or latter is
required. True or False?

Now look at this:

     * libpam-heimdal 1.0-8 (new) (low)
          + Maintainer: Brian May <bam@debian.org>
          + only 9/10 days old
          + out of date on alpha: libpam-heimdal (from 1.0-6)
          + not considered


Which implies that an up-to-date version has been compiled by m68k,
even though the build-dependencies can't been satisfied.

Why is going on here?
-- 
Brian May <bam@debian.org>