<html>Hi Duncan,<br /><br />Regarding python3-mistune at 2.0.4 (which caused python-m2r to fail to build):<br /><br />A few months ago, I uploaded python3-mistune at 2.0.4.<br />The reason was because I wanted to update jupyter-nbconvert to versions >= 7.0.0 (which required mistune >= 2.0.3).<br /><br />Previously, there was only 1 package named 'mistune' at SlackBuilds.org.<br />Yth was the maintainer of mistune.<br />I initially requested taking over mistune and updating it to 2.0.4 (and for me to upload mistune1, a legacy package for python-m2r).<br />However, Yth requested me to upload a python3-mistune package at 2.0.4.<br />Yth also renamed mistune to python2-mistune (and kept it at 0.8.4).<br />In other words, Yth suggested splitting the existing mistune package into Python 2 and 3 versions, rather than updating mistune and uploading mistune1.<br /><br />Therefore, since python3-mistune is at 2.0.4, python-m2r does not build in python 3.<br />As you have shown, python-m2r requires python3-mistune at 0.8.4 instead.<br /><br />Would you like me to upload a python3-mistune1 SlackBuild, at 0.8.4?<br />There is only a python2-mistune at 0.8.4, maintained by Yth.<br /><br />That being said, if I upload python3-mistune1, it will conflict with my existing python3-mistune.<br />Therefore, I have to indicate that both python3-mistune1 and python3-mistune cannot be installed in the same system at the same time.<br /><br />- Isaac<br /><br /><br /> </html>