Your message dated Thu, 9 Jan 2020 17:07:22 +0200
with message-id <[email protected]>
and subject line Re: Bug#932143: mariadb-10.3.16 migration excuses indicate
need for manual cleanup?
has caused the Debian Bug report #932143,
regarding mariadb-10.3.16 migration excuses indicate need for manual cleanup?
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.)
--
932143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932143
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
Currently the excuses at
https://qa.debian.org/excuses.php?package=mariadb-10.3 state:
old binaries left on amd64: libmariadbclient18 (from 1:10.3.13-1) (but
ignoring cruft, so nevermind)
old binaries left on arm64: libmariadbclient18 (from 1:10.3.13-1) (but
ignoring cruft, so nevermind)
old binaries left on armel: libmariadbclient18 (from 1:10.3.13-1) (but
ignoring cruft, so nevermind)
old binaries left on armhf: libmariadbclient18 (from 1:10.3.13-1) (but
ignoring cruft, so nevermind)
old binaries left on i386: libmariadbclient18 (from 1:10.3.13-1) (but
ignoring cruft, so nevermind)
old binaries left on mips: libmariadbclient18 (from 1:10.3.13-1) (but
ignoring cruft, so nevermind)
old binaries left on mips64el: libmariadbclient18 (from 1:10.3.13-1)
(but ignoring cruft, so nevermind)
old binaries left on mipsel: libmariadbclient18 (from 1:10.3.13-1)
(but ignoring cruft, so nevermind)
old binaries left on ppc64el: libmariadbclient18 (from 1:10.3.13-1)
(but ignoring cruft, so nevermind)
old binaries left on s390x: libmariadbclient18 (from 1:10.3.13-1) (but
ignoring cruft, so nevermind)
This has been there for many months now and does not seem to clean up
the cruft automatically (or remove the error message).
Could the ftp-masters please take a look and manually resolve it?
Thanks,
- Otto
--- End Message ---
--- Begin Message ---
On Tue, 16 Jul 2019 17:57:58 +0200 Mattia Rizzolo <[email protected]> wrote:
> On Mon, Jul 15, 2019 at 11:18:27PM +0300, Otto Kekäläinen wrote:
> > Currently the excuses at
> > https://qa.debian.org/excuses.php?package=mariadb-10.3 state:
> >
> > old binaries left on amd64: libmariadbclient18 (from 1:10.3.13-1) (but
> > ignoring cruft, so nevermind)
>
> > This has been there for many months now and does not seem to clean up
> > the cruft automatically (or remove the error message).
> >
> > Could the ftp-masters please take a look and manually resolve it?
>
> No, it's not something for ftp-master to manually kick.
>
> You can check with `dak rm` how there are still reverse dependencies
> using it. Fix them and the package will be removed completely.
>
> Checking reverse dependencies...
> # Broken Depends:
> amarok: amarok
> dballe: libdballe7
> mosquitto-auth-plugin: mosquitto-auth-plugin
> mysql++: libmysql++3v5
> mysql-workbench: mysql-workbench
> opensips: opensips-lua-module
> opensips-mysql-module
> quickfix: libquickfix16 [i386]
> stardict: stardict-tools
>
> Dependency problem found.
>
>
> (yes, they are all broken packages not in testing.)
Those were apparently taken care of as multiple successful migrations are now
listed at https://tracker.debian.org/pkg/mariadb-10.3. I think this bug can
be closed.
--- End Message ---
