Your message dated Sat, 1 Mar 2025 15:11:57 -0500
with message-id
<CAD+GYvzVFeArhNDu9=62sqtxgjqsxyy5edtm-vwdm11sqr2...@mail.gmail.com>
and subject line Re: mysql-workbench: remove from Debian?
has caused the Debian Bug report #1098649,
regarding mysql-workbench: remove from Debian?
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.)
--
1098649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098649
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: mysql-workbench
Version: 8.0.32+dfsg-2
Severity: serious
mysql-workbench was removed from Testing in 2018. Can we please remove
it from Debian now?
This was asked before in 2021: https://bugs.debian.org/982683
I noticed this package today as I was checking why the old
libpoppler140 was not automatically removed from Debian.
mysql-workbench's presence in Unstable is causing cruft libraries to
not be removed.
mysql-workbench is not installable at least because pcre3 was removed
from Unstable.
Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
I'm closing since there was a new mysql-workbench upload to Debian
Unstable today that fixed many bugs.
Thank you,
Jeremy Bícha
--- End Message ---
