Your message dated Sat, 03 Mar 2018 22:15:52 +0000
with message-id <[email protected]>
and subject line Bug#891641: Removed package(s) from unstable
has caused the Debian Bug report #891641,
regarding RM: mariadb-10.2 -- ROM, NPOASR; skipping this version, upgrade path
is 10.1 -> 10.3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
891641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891641
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
I am the maintainer of the MariaDB packages in Debian and Ubuntu. The
package mariadb-10.2 was uploaded in November 2017 by another Debian
Developer helping in the effort, but he did not commit to maintain it.
i personally want to focus my efforts on packaging of mariadb-10.3,
which will obsolete mariadb-10.2 very soon. In the mean time I plan to
make (security) updates only for 10.1.
Therefore I request the removal of mariadb-10.2 from unstable at this
point. I do not have enough time to fix issues caused by this -10.2
package, nor provide updates to -10.2.
The source package mariadb-10.2 produces the following binary
packages, which have no replacement from other MariaDB packages:
mariadb-client-10.2
mariadb-client-core-10.2
mariadb-plugin-connect-10.2
mariadb-plugin-cracklib-password-check-10.2
mariadb-plugin-gssapi-client-10.2
mariadb-plugin-gssapi-server-10.2
mariadb-plugin-mroonga-10.2
mariadb-plugin-oqgraph-10.2
mariadb-plugin-rocksdb-10.2
mariadb-plugin-spider-10.2
mariadb-plugin-tokudb-10.2
mariadb-server-10.2
mariadb-server-core-10.2
libmariadbd19
Please make sure these binary packages are removed so there is no
cruft left over. All other binary packages have a replacement from the
other MariaDB server and connector packages.
Thank you!
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
libmariadb-dev | 10.2.7-1 | amd64, mips, mipsel, powerpc, s390x
libmariadb3 | 10.2.7-1 | amd64, mips, mipsel, powerpc, s390x
libmariadbd19 | 10.2.7-1 | amd64, mips, mipsel, powerpc, s390x
mariadb-10.2 | 10.2.7-1 | source
mariadb-client-10.2 | 10.2.7-1 | amd64, mips, mipsel, powerpc, s390x
mariadb-client-core-10.2 | 10.2.7-1 | amd64, mips, mipsel, powerpc, s390x
mariadb-common | 10.2.7-1 | all
mariadb-plugin-connect-10.2 | 10.2.7-1 | amd64, mips, mipsel, powerpc, s390x
mariadb-plugin-cracklib-password-check-10.2 | 10.2.7-1 | amd64, mips, mipsel,
powerpc, s390x
mariadb-plugin-gssapi-client-10.2 | 10.2.7-1 | amd64, mips, mipsel, powerpc,
s390x
mariadb-plugin-gssapi-server-10.2 | 10.2.7-1 | amd64, mips, mipsel, powerpc,
s390x
mariadb-plugin-mroonga-10.2 | 10.2.7-1 | amd64, mipsel
mariadb-plugin-oqgraph-10.2 | 10.2.7-1 | amd64, mips, mipsel, powerpc, s390x
mariadb-plugin-rocksdb-10.2 | 10.2.7-1 | amd64
mariadb-plugin-spider-10.2 | 10.2.7-1 | amd64, mips, mipsel, powerpc, s390x
mariadb-plugin-tokudb-10.2 | 10.2.7-1 | amd64
mariadb-server-10.2 | 10.2.7-1 | amd64, mips, mipsel, powerpc, s390x
mariadb-server-core-10.2 | 10.2.7-1 | amd64, mips, mipsel, powerpc, s390x
mariadb-test | 10.2.7-1 | amd64, mips, mipsel, powerpc, s390x
mariadb-test-data | 10.2.7-1 | all
------------------- Reason -------------------
ROM, NPOASR; skipping this version, upgrade path is 10.1 -> 10.3
----------------------------------------------
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 [email protected].
The full log for this bug can be viewed at https://bugs.debian.org/891641
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
