|Summary:||textproc/py-markdown: Update to 3.2.1|
|Product:||Ports & Packages||Reporter:||Alexander Sieg <ports>|
|Component:||Individual Port(s)||Assignee:||Kubilay Kocak <koobs>|
|Status:||In Progress ---|
|Severity:||Affects Only Me||CC:||andreas, arved, swills|
|Bug Depends on:|
Description Alexander Sieg 2019-07-09 18:30:36 UTC
Created attachment 205608 [details] patch Update to 3.1.1 portlint OK (looks fine.) poudriere OK (12amd64)
Comment 1 Kubilay Kocak 2020-02-18 01:24:08 UTC
3.2 dropped support for Python 2.x: https://python-markdown.github.io/change_log/release-3.2/ This needs additional QA, in particular for dependents/consumers of Markdown, and potentially a markdown2 port (copied from the current version)
Comment 2 Tilman Keskinoz 2020-05-26 21:25:44 UTC
If updating to 3.2 is too complicated because of python2, maybe updating to 3.1 is possible? A port update of mine depends on markdown > 3.0.
Comment 3 Kubilay Kocak 2020-05-27 01:28:45 UTC
(In reply to Tilman Keskinoz from comment #2) Thanks for the heads-up Tilman What port has your markdown > 3.0 dependency? I'll include it during QA
Comment 4 Andreas Bilke 2020-08-24 17:58:30 UTC
(In reply to Kubilay Kocak from comment #3) www/py-pelican needs officially markdown > 3 (but it's not mentioned correctly within the Makefile).
Comment 5 Kubilay Kocak 2020-09-14 02:50:13 UTC
To clarify QA requirements: markdown ports consumers need to be audited for version compatibility (and *_DEPENDS <version-spec> correctness), to determine whether markdown2 is necessary/warranted I'd appreciate any assistance, but will otherwise seek to run/complete QA and report here
Comment 6 Andreas Bilke 2020-11-22 08:47:29 UTC
(In reply to Kubilay Kocak from comment #5) I am fairly new to this process, but can you help me and tell me how I can be useful in speed up the QA process? Do one need to go through all packages with markdown dependencies and check manually if they rely on markdown3 or markdown2? What happens if changes need to be done on the port? Do we need to post a patch here, or do we need an own bug report and link them with this issue here?