Public bug reported:
As was seen in LP: #2089288, dmesg will show systemd logging about
mounting a mysql snap. (This may be from https://snapcraft.io/mysql-
workbench-community, which I'm gathering is a snap packaging of the deb
package that MySQL upstream maintains at
https://dev.mysql.com/downloads/.)
This is an interesting situation because if the upstream deb was
installed, we'd be able to ensure proper conflicts in the d/control to
prevent co-installation and allow one to replace the other via pinning
and so on, but AFAICT no such mechanisms are available to manage
deb<->snap conflicts.
One approach may be solving LP: #2085571, which focuses on the problem
of the TCP/IP port conflict. That symptom is seen with the snap
installations, so if a means of checking the port for foreign mysql's is
developed it might be good enough for this bug. But I don't know if
having the snap installed might cause other conflicts besides the
port...
Also, this is perhaps a larger issue than just mysql, as in theory any
of our server software that exists as both a deb and snap could assume
they own the standard port number for that service and get into
contention.
** Affects: mysql-8.0 (Ubuntu)
Importance: Undecided
Status: New
** Tags: snap
** Summary changed:
- Apport hook needs to detect if snap-mysql is installed
+ Apport hook needs to detect if snap-mysql is installed and inform user
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2090881
Title:
Apport hook needs to detect if snap-mysql is installed and inform user
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/2090881/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
