https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267188
--- Comment #1 from John W. O'Brien <j...@saltant.com> --- Thank you for the report. A corresponding bug reported upstream [0] blames breaking changes in mistune 2.x for this error. I see that neither textproc/py-mistune0 nor textproc/py-mistune mention the other in CONFLICTS. textproc/py-mistune0 installs as a module in site-packages/mistune.py while textproc/py-mistune installs as a package in site-packages/mistune/. Consequently, pkgng detects no conflict when both are installed. The Python import logic seems to prefer packages over modules. If py39-mistune-2.0.4 is installed on your build system, m2r will use it instead of its stated dependency, py39-mistune0-0.8.4. In the short-term it will be necessary for sunpoet to update the two mistune ports to conflict with each other. Longer term, m2r would have to add support mistune 2.x. Unfortunately, m2r may now be abandonware. The last release was four years ago, almost to the day (2018-10-11 [1]), and the last commit in the canonical repository was over three years ago (2019-06-04 [2]). Unless something changes upstream, the fate of textproc/py-m2r is inseparable from the fate of textproc/py-mistune0. [0] https://github.com/miyakogi/m2r/issues/66 [1] https://github.com/miyakogi/m2r/releases/tag/v0.2.1 [2] https://github.com/miyakogi/m2r/commit/66f4a5a500cdd9fc59085106bff082c9cadafaf3 -- You are receiving this mail because: You are on the CC list for the bug.
