[MacPorts] #60788: oniguruma5 and oniguruma6 conflict (was: sudo port upgrade outdated failed because conflicting ports are active)

[MacPorts]

#60788: oniguruma5 and oniguruma6 conflict
------------------------------------+-------------------------
  Reporter:  delphym                |      Owner:  Schamschula
      Type:  defect                 |     Status:  assigned
  Priority:  Normal                 |  Milestone:
 Component:  ports                  |    Version:  2.6.2
Resolution:                         |   Keywords:
      Port:  oniguruma5 oniguruma6  |
------------------------------------+-------------------------
Changes (by ryandesign):

 * owner:  (none) => Schamschula
 * status:  new => assigned
 * port:  oniguruma5 => oniguruma5 oniguruma6


Comment:

 Replying to [ticket:60788 delphym]:
 > This is just a FYI report, as Macport asked me to report it.

 To clarify: MacPorts is not asking you to report a bug; rather, it's
 letting you know how you can report the problem if you believe it is a
 bug. We could improve the wording of that message to make that clearer.

 Here's what happened. You had jq installed. It depended on oniguruma5. The
 maintainer of jq then [changeset:f26b0b6895faf26a3549dc410989352f21c39881
 /macports-ports updated jq so that it used oniguruma6] instead.

 Normally this would not be a problem. Unfortunately in this case it is
 because the oniguruma5 and oniguruma6 ports are not designed properly:
 they conflict with one another. If it is still necessary for us to have
 multiple oniguruma ports, then they should be fixed so that they do not
 conflict.

 The fact that this change in jq would cause the problem you experienced
 was anticipated and documented by the maintainer of jq but there's nothing
 to do about it other than for someone to fix the oniguruma ports.


 > Perhaps if the failure on upgrade would rather point out to a specific
 place in the documentation what to do in such situations rather than a
 link to report a bug, could be more helpful.

 I agree that it would be good if more of our error messages provided links
 to documentation pages with a more detailed explanation of the problem and
 the user's options for fixing it. But so far we don't have such
 documentation written.

 MacPorts always prints the bug reporting instructions when any error
 occurs. I'm not familiar with the part of MacPorts base that does that so
 I wouldn't know how to modify it to skip that for certain known conditions
 that are not considered bugs.

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