We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable:
libkf5messagecomposer-dev | 4:16.04.3-2 | hurd-i386 libkf5messagecomposer-dev | 4:16.04.3-3 | armel, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, powerpc, ppc64el, s390x libkf5messagecomposer5 | 4:16.04.3-2 | hurd-i386 libkf5messagecomposer5 | 4:16.04.3-3 | armel, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, powerpc, ppc64el, s390x libkf5messagecore-dev | 4:16.04.3-2 | hurd-i386 libkf5messagecore-dev | 4:16.04.3-3 | armel, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, powerpc, ppc64el, s390x libkf5messagecore5 | 4:16.04.3-2 | hurd-i386 libkf5messagecore5 | 4:16.04.3-3 | armel, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, powerpc, ppc64el, s390x libkf5messagelist-dev | 4:16.04.3-2 | hurd-i386 libkf5messagelist-dev | 4:16.04.3-3 | armel, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, powerpc, ppc64el, s390x libkf5messagelist5 | 4:16.04.3-2 | hurd-i386 libkf5messagelist5 | 4:16.04.3-3 | armel, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, powerpc, ppc64el, s390x libkf5messageviewer-dev | 4:16.04.3-2 | hurd-i386 libkf5messageviewer-dev | 4:16.04.3-3 | armel, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, powerpc, ppc64el, s390x libkf5messageviewer5 | 4:16.04.3-2 | hurd-i386 libkf5messageviewer5 | 4:16.04.3-3 | armel, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, powerpc, ppc64el, s390x libkf5templateparser-dev | 4:16.04.3-2 | hurd-i386 libkf5templateparser-dev | 4:16.04.3-3 | armel, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, powerpc, ppc64el, s390x libkf5templateparser5 | 4:16.04.3-2 | hurd-i386 libkf5templateparser5 | 4:16.04.3-3 | armel, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, powerpc, ppc64el, s390x ------------------- Reason ------------------- ROM; requires QtWebEngine ---------------------------------------------- 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. 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. The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 885...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/885058 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
