Bug#935024: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
kdepim4 | 4:4.14.10-7 | source
knode | 4:4.14.10-7+b3 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
ktimetracker | 4:4.14.10-7+b3 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
libcalendarsupport4 | 4:4.14.10-7+b3 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
libincidenceeditorsng4 | 4:4.14.10-7+b3 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
libkdepim4 | 4:4.14.10-7+b3 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
libkdepimdbusinterfaces4 | 4:4.14.10-7+b3 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
libkdgantt2-0 | 4:4.14.10-7+b3 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
libkleo4 | 4:4.14.10-7+b3 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
libkpgp4 | 4:4.14.10-7+b3 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
libmessagecomposer4 | 4:4.14.10-7+b3 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
libmessagecore4 | 4:4.14.10-7+b3 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
libmessageviewer4 | 4:4.14.10-7+b3 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
libpimcommon4 | 4:4.14.10-7+b3 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
libsendlater4 | 4:4.14.10-7+b3 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
libtemplateparser4 | 4:4.14.10-7+b3 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
------------------- Reason -------------------
ROM; Obsolete libs - Qt4, no longer needed
----------------------------------------------
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 935024@bugs.debian.org.
The full log for this bug can be viewed at https://bugs.debian.org/935024
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)
Reply to: