Tags: help Hello Boyuan,
Am Sat, Jun 08, 2024 at 08:01:09PM -0400 schrieb Boyuan Yang: > Source: python-mkdocs > Severity: normal > Version: 1.5.3+dfsg-1 > X-Debbugs-CC: b...@debian.org c.schoen...@t-online.de > > Dear Debian python-mkdocs maintainer, > > A new upstream release of mkdocs is available. Please consider reviewing it > (as well as the compatibility of related packages) and have it packaged in > Debian. I did spend now several days and attempts to work on an updated package mkdocs based on the latest upstream version 1.6.0. I think I did covered so far all the points and actions that were needed to get a newer Debian version prepared. For now I pushed my WIP to my namespace only. https://salsa.debian.org/tijuca/python-mkdocs/ Some "ready" to use packages can be picked up on p.d.o. https://people.debian.org/~tijuca/mkdoc/ The build itself is no problem I guess (the autopkgtest will need further adjustments too), but I see issues if I'm trying to browse through the contents of the installed python-mkdocs-doc package. These issues so far are broken linking, e.g. on the start page file:///usr/share/doc/mkdocs/html/index.html the first a href element with the name 'introductory tutorial' is pointing correctly to file:///usr/share/doc/mkdocs/html/getting-started.html but the button beneath "Getting Started" is linked to file:///usr/share/doc/mkdocs/html/getting-started The same is happen to other buttons but also to a href elements all over the content. Dimitry did added a patch in the past that is adding 'use_directory_urls: false' to the mkdocs.yaml file that should do exactly the trick. https://www.mkdocs.org/user-guide/configuration/#use_directory_urls Currently I've no idea why this is happen, but I think this behavior might happen to all mkdocs based documentation in packages if we would upload the current state to the archive so we need to fix this first bevor a upload can happen. My time and my knowledge it currently to limited o give an hint when a fixed build can happen, I appreciate any help. Might also be that this is an upstream issue. But it might also be we are to strict with the removal of some vendored files. So rebuilding all without any removed upstream files and folder would be the next logical step. I'm happy to look into this while DC in Busan with someone! But I will probably not having time to look into this until DC is starting. Regards Carsten
