On 2023-06-03 20:41:40, Nicholas D. Steeves wrote: > Nicholas D Steeves <s...@debian.org> writes: > >> I also confirmed that both the patched version (in the staging branch) >> and unpatched version (in bookworm) work correctly with >> >> >> https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-36-gitolite-gitweb-retirement.md >> >> when one loads markdown-toc and generates the toc before native comp >> kicks in. > > Sorry for not being clear. What I mean is that I believe that this bug > is triggered by native compilation, and that it's unlikely that I'll > find enough time figure out what the upstream issue is before the > autoremoval. Also, upstream hasn't seen any activity since 2021... > > Feel free to forward this bug and/or adopt this package (I don't use > it).
You seem to have pasted a link to the TPA GitLab wiki here... Did you mean to paste some other bug report or link there? I think I'm okay with the package being removed from bookworm if we can't find a quick fix here. The release date is just too close. We can always fix this in a point release or get a backport going. Interestingly, it's not marked as autoremoval here though: https://tracker.debian.org/pkg/markdown-toc-el Alternatively, I wonder if there's a way to make a simpler module that would defer the TOC generation to an external command... Is there something out there that takes a markdown doc as input and outputs a TOC? Cheers, a. -- Power is always dangerous. Power attracts the worst and corrupts the best. - Edward Abbey
