[MacPorts] #64404: mariadb-10.5 @10.5.13 requires rebuild after running reclaim

[MacPorts]

#64404: mariadb-10.5 @10.5.13 requires rebuild after running reclaim
---------------------------+-----------------------
  Reporter:  p-b-west      |      Owner:  michaelld
      Type:  defect        |     Status:  assigned
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:
Resolution:                |   Keywords:
      Port:  mariadb-10.5  |
---------------------------+-----------------------

Comment (by ryandesign):

 Replying to [comment:4 p-b-west]:
 > {{{
 > Could not open /opt/local/lib/libcurl.4.dylib: Error opening or reading
 file (referenced from /opt/local/lib/mariadb-10.5/bin/aria_s3_copy)
 > DEBUG: Marking /opt/local/lib/mariadb-10.5/bin/aria_s3_copy as broken
 > Could not open /opt/local/lib/liblzo2.2.dylib: Error opening or reading
 file (referenced from /opt/local/lib/mariadb-10.5/bin/mariadb-backup)
 > DEBUG: Marking /opt/local/lib/mariadb-10.5/bin/mariadb-backup as broken
 > }}}

 So files installed by mariadb-10.5 link with libraries installed by the
 curl and lzo2 ports but the mariadb-10.5 port does not declare a
 dependency on them. It either needs to do that or ensure that those
 libraries are not used even if those ports are installed.

 Replying to [comment:6 michaelld]:
 > Looks like `curl` was updated

 Nope, curl still provides /opt/local/lib/libcurl.4.dylib.

 > We don't always rev-bump dependent ports ... and in this case `curl`
 would have a ton of ports that depend on it so strongly doubt we'd rev-
 bump them all.

 If the install_name of a library installed by a port X changes (because
 its major version changes or for any other reason) it would be the
 responsibility of whoever updates the port X to that new version to also
 revbump all ports that link with that library.

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