Hello, On Sun 25 Feb 2024 at 02:24pm +01, Holger Wansing wrote:
> Seems there is more than only one issue: > > 1. > In the binary package (debian-policy latest version) the above files and > directories are existing, but the files are all empty (0 B size). > However, in the previous version (4.6.2.0) the javascript .js files > are also empty (0 B), so that's most probably not the issue. > I remember we don't have full javascript functionality in our sphinx-based > manuals on debian.org for a longer time, search is not working for example. > That's #1026446, #872944, #987943. > > In a local build here, they are all fine, and the document is displayed > correctly. But that's build on bookworm, so sphinx version 5.3.0. > The binary packages built by buildd will get build on sphinx 7.2.x > I think, so maybe there is the difference? > Maybe we need some adaption for latest sphinx version? > > > 2. > The first file from above list _static/css/theme.css is likely to be > the point, since the html layout is completely broken. > That file is also empty in latest debian-policy binary package. > Since it is fine in local build here, also an issue with latest sphinx > version maybe ??? > Or do we no longer need _static/css/theme.css, as we now have > _static/debian.css ? > > > 3. > Despite the fact, that the files from above are empty, there seems to be > another issue with debian.org website: > the subdirectories under _static are not existing on debian.org, as well as > the files within of course (like _static/css/theme.css). > Apparently there is some more magic needed in webmaster-team's cron > https://salsa.debian.org/webmaster-team/cron/-/blob/master/parts/7doc?ref_type=heads#L319 > to get such files copied over to debian.org during website build. > > But first, we need to have a working version in the binary package, > since that's the basis for website build. I guess I should have done a debdiff huh? :) Thank you for the analysis. Osamu, Stéphane, could you take a look? Thank you. -- Sean Whitton