We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: hyperestraier | 1.4.13-14 | source hyperestraier | 1.4.13-14+b4 | hurd-i386 hyperestraier | 1.4.13-14+b6 | kfreebsd-amd64, kfreebsd-i386 hyperestraier | 1.4.13-15 | source, amd64, arm64, armel, armhf, i386, mips64el, powerpc, ppc64el hyperestraier | 1.4.13-15+b1 | mips, mipsel, s390x libestraier-dev | 1.4.13-14+b4 | hurd-i386 libestraier-dev | 1.4.13-14+b6 | kfreebsd-amd64, kfreebsd-i386 libestraier-dev | 1.4.13-15 | amd64, arm64, armel, armhf, i386, mips64el, powerpc, ppc64el libestraier-dev | 1.4.13-15+b1 | mips, mipsel, s390x libestraier-java | 1.4.13-15 | amd64, arm64, armel, armhf, i386, mips64el, powerpc, ppc64el libestraier-java | 1.4.13-15+b1 | mips, mipsel, s390x libestraier-perl | 1.4.13-14+b4 | hurd-i386 libestraier-perl | 1.4.13-14+b6 | kfreebsd-amd64, kfreebsd-i386 libestraier-perl | 1.4.13-15 | amd64, arm64, armel, armhf, i386, mips64el, powerpc, ppc64el libestraier-perl | 1.4.13-15+b1 | mips, mipsel, s390x libestraier8 | 1.4.13-14+b4 | hurd-i386 libestraier8 | 1.4.13-14+b6 | kfreebsd-amd64, kfreebsd-i386 libestraier8 | 1.4.13-15 | amd64, arm64, armel, armhf, i386, mips64el, powerpc, ppc64el libestraier8 | 1.4.13-15+b1 | mips, mipsel, s390x ruby-hyperestraier | 1.4.13-14+b4 | hurd-i386 ruby-hyperestraier | 1.4.13-14+b6 | kfreebsd-amd64, kfreebsd-i386 ruby-hyperestraier | 1.4.13-15 | amd64, arm64, armel, armhf, i386, mips64el, powerpc, ppc64el ruby-hyperestraier | 1.4.13-15+b1 | mips, mipsel, s390x ruby-hyperestraier-doc | 1.4.13-14 | all ruby-hyperestraier-doc | 1.4.13-15 | all ------------------- Reason ------------------- RoQA; FTBFS+wontfix ---------------------------------------------- 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 and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not 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. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 894527@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/894527 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
