Public bug reported: mdit-py-plugins 0.6.1-1 FTBFS because its test suite requires markdown-it-py >= 4.1.0. The likely cause is that when mdit-py-plugins 0.6.1-1 was trying to get built in proposed, markdown-it-py 4.2.0-2 had not yet landed in proposed, so it built and tested against the old version 3.0.0 which is insufficient. This has left three interdependent packages in a collectively broken state in proposed:
- markdown-it-py 4.2.0-2 - in proposed, Breaks myst-parser < 5.0.0-2 - mdit-py-plugins 0.6.1-1 - FTBFS, needs markdown-it-py >= 4.1.0 to build - myst-parser 5.1.0-1 - FTBFS, needs mdit_py_plugins.gfm which is non-functional against markdown-it-py 3.0.0 These three must migrate together in order: markdown-it-py 4.2.0-2 -> mdit-py-plugins 0.6.1-1 -> myst-parser 5.1.0-1. We have verified that building them in the correct order in a PPA produces a working set: https://launchpad.net/~b0b0a/+archive/ubuntu/myst-parser The broken proposed state is blocking all packages from the ROCm set (depending on python3-rocm-docs) from building on Stonking with -proposed enabled, as apt deadlocks on the inconsistent markdown-it- py/myst-parser versions. ** Affects: mdit-py-plugins (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2154286 Title: mdit-py-plugins 0.6.1 FTBFS: uncoordinated proposed migration with markdown-it-py 4.2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdit-py-plugins/+bug/2154286/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
