[MacPorts] #68009: Improvement to logging for installation of Mariadb server

[MacPorts]

#68009: Improvement to logging for installation of Mariadb server
---------------------------+--------------------
  Reporter:  jasimon9      |      Owner:  (none)
      Type:  enhancement   |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:
Resolution:                |   Keywords:
      Port:  mariadb-10.6  |
---------------------------+--------------------

Comment (by ryandesign):

 I'm not sure what you're talking about:

 Replying to [ticket:68009 jasimon9]:
 > - during the process, macports has to uninstall mariadb-10.6 apparently
 after the mariadb-10.6-server is done

 That doesn't make sense. mariadb-10.6-server depends on mariadb-10.6.
 mariadb-10.6-server requires mariadb-10.6 to be installed. MacPorts won't
 uninstall it.

 > - but because mariadb-10.6 is dependent upon the server, a notice is
 displayed about that, but then it goes ahead to force the uninstall and
 upgrade of mariadb-10.6. The key part is that there is a notice stating to
 the effect that '''the server mariadb-10.6-server has to be
 reinstalled.'''
 > - I did not originally see that. The result was apparently that the
 server install is corrupted such that is has to be redone.
 > - The result is that the commands to unload and reload the server shown
 below appeared to function properly, but mariadb as mysqld was not
 running.
 >   - sudo port unload mariadb-10.6-server
 >   - sudo port load mariadb-10.6-server

 Perhaps you mean that the rev-upgrade process, which runs after every
 install or upgrade, analyzed your installed ports and found mariadb-10.6
 to be broken?

 > I finally got it fixed by realizing that the install of the server had
 to be executed by itself, and then the unload/reload sequence. After that
 all was again good.

 Normally rev-upgrade rebuilds the port for you to work around the
 breakage. If rebuilding fixed the breakage, then the bug may be that
 someone forgot to increase the revision of the port after one of its
 dependencies was updated. Debug output from the rev-upgrade process, run
 when the port was broken, would let us know if that was the case.

 If rebuilding doesn't fix the breakage, rev-upgrade reports that to you.
 In that case, installing it manually shouldn't do anything different and
 shouldn't fix it either.

 So it's very unclear what happened in your situation or what fixed it. We
 can't add any notes to the port or to MacPorts in general to describe
 something we don't understand, and it sounds like an undesirable situation
 that should be fixed rather than adding a note about it. But we would need
 to see the log you don't have to understand what happened and what to do
 about it.

-- 
Ticket URL: <https://trac.macports.org/ticket/68009#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS