Bug in update_excuses?

[Andreas Metzler <ametzler@logic.univie.ac.at>]

Quoting http://ftp-master.debian.org/testing/update_excuses.html.gz#glibc
-----------------------------
# glibc (2.3.1-16 to 2.3.2-5)

    * Maintainer: GNU Libc Maintainers
    * Too young, only 3 of 10 days old
    * locales/hppa unsatisfiable Depends: glibc-2.3.2-5
    * out of date on hppa: libc6, libc6-dbg, libc6-dev, libc6-pic, libc6-prof, nscd (from 2.3.1-17.0.3)
    * libc6.1 (alpha, ia64) is buggy! (1 > 0)
    * libc6 (arm, hppa, i386, m68k, mips, mipsel, powerpc, s390, sparc) is buggy! (2 > 0)
    * libc6-dev (arm, hppa, i386, m68k, mips, mipsel, powerpc, s390, sparc) is buggy! (3 > 1)
    * glibc (source) is (less) buggy! (1 <= 2)
    * Not considered 
-----------------------------
# db3/s390 (3.2.9-19 to 3.2.9-19)

    * Maintainer: Matthew Wilcox
    * Ignoring db3-doc 3.2.9-19 (from 3.2.9-19) as it is arch: all
    * Updated binary: libdb3 (3.2.9-19 to 3.2.9-19.0.1)
    * Updated binary: libdb3++-dev (3.2.9-19 to 3.2.9-19.0.1)
    * Updated binary: libdb3++c102 (3.2.9-19 to 3.2.9-19.0.1)
    * Updated binary: libdb3-dev (3.2.9-19 to 3.2.9-19.0.1)
    * Updated binary: libdb3-tcl (3.2.9-19 to 3.2.9-19.0.1)
    * Updated binary: libdb3-util (3.2.9-19 to 3.2.9-19.0.1)
    * Ignoring removal of db3-doc as it is arch: all
    * Valid candidate 
-----------------------------

But:
----------
dpkg --info libdb3_3.2.9-19.0.1_s390.deb  | grep '^ Dep'
 Depends: libc6 (>= 2.3.2-1)
----------

So the db3-update predepends on a glibc-update, which cannot happen and
should stop db3 3.2.9-19.0.1 from becoming "Valid candidate",
shouldn't it?
                  cu andreas