We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: bakery-gnomeui2.0 | 2.0.0-3 | source bakery2.0 | 2.0.0-4 | source gconfmm2.0 | 2.0.2-1.1 | source gnome-vfsmm1.3 | 1.3.5-2 | source libbakery-gnomeui2.0-1 | 2.0.0-3 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc libbakery-gnomeui2.0-dev | 2.0.0-3 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc libbakery2.0-1 | 2.0.0-4 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc libbakery2.0-dev | 2.0.0-4 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc libgconfmm-2.0-1 | 2.0.2-1.1 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc libgconfmm2.0-dev | 2.0.2-1.1 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc libglademm2.0 | 2.2.0-1.1 | source libglademm2.0-1c102 | 2.2.0-1.1 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc libglademm2.0-dev | 2.2.0-1.1 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc libgnomecanvasmm2.0 | 2.0.1-5 | source libgnomecanvasmm2.0-1c102 | 2.0.1-5 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc libgnomecanvasmm2.0-dev | 2.0.1-5 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc libgnomemm2.0 | 2.0.1-2.1 | source libgnomemm2.0-1c2 | 2.0.1-2.1 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc libgnomemm2.0-dev | 2.0.1-2.1 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc libgnomeuimm2.0 | 2.0.0-5 | source libgnomeuimm2.0-1 | 2.0.0-5 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc libgnomeuimm2.0-dev | 2.0.0-5 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc libgnomevfsmm1.3-6 | 1.3.5-2 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc libgnomevfsmm1.3-dev | 1.3.5-2 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive (ftp-master.debian.org) and will not propagate to any mirrors (ftp.debian.org included) until the next cron.daily run at the earliest. Packages are never removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 325216@bugs.debian.org. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@debian.org. Debian distribution maintenance software pp. Ryan Murray (the ftpmaster behind the curtain)
