Bug#872944: www.debian.org: Debian Policy Manual not fully published

Russ Allbery writes: > That said, introducing Javascript for the first time does feel like a > large-ish step, and the reluctance also makes sense. I'm not sure the > search functionality really adds much. (I haven't checked to confirm that > is the only thing in the Sphinx output that uses

Bug#872944: www.debian.org: Debian Policy Manual not fully published

Sean Whitton writes: > On Fri, Aug 25 2017, Laura Arjona Reina wrote: >> My concern is about doing the right thing... making our web visitors >> run javascript code from sid in their browsers does not sound right for >> me. It's fairly unlikely that this would cause a

Bug#872944: www.debian.org: Debian Policy Manual not fully published

On Fri, Aug 25 2017, Laura Arjona Reina wrote: > My concern is about doing the right thing... making our web visitors > run javascript code from sid in their browsers does not sound right > for me. > > Would you (Debian Policy Team) consider acceptable to leave the website > version > of the

Bug#872944: www.debian.org: Debian Policy Manual not fully published

El 24/08/17 a las 23:05, Sean Whitton escribió: > Hello Laura, > > On Thu, Aug 24 2017, Laura Arjona Reina wrote: > >> >> * If we should use the packages from "sid" as we use for the >> documentation packages, or stable, or backports... > > If it's easy, we'd prefer you to use them from sid,

Bug#872944: www.debian.org: Debian Policy Manual not fully published

On 08/24/2017 09:01 AM, Laura Arjona Reina wrote: > I'm not sure about the points below: > > * If we should copy those javascript files to "live" under > www.debian.org/doc/policy-manual or in another place in the > www.debian.org site (or in cgi.debian.org?). For now, policy-manual is > the only

Bug#872944: www.debian.org: Debian Policy Manual not fully published

Hello Russ, Sean and website team Thanks for your mail. El 23/08/17 a las 06:01, Russ Allbery escribió: > Sean Whitton writes: > >> The Debian Policy Manual just changed its HTML output and while the HTML >> has published, the CSS and included images have not. > >>

Bug#872944: www.debian.org: Debian Policy Manual not fully published

Hello again El 23/08/17 a las 09:43, Laura Arjona Reina escribió: > > See commit: > > https://anonscm.debian.org/cgit/debwww/cron.git/commit/?id=64faa5504f980c377ed6e44d0a61f1943336b102 > Well, that didn't work but it was because the fix was incomplete (I was not creating the correct _images

Bug#872944: www.debian.org: Debian Policy Manual not fully published

Hello I've been reading the 7doc script and I think the problem is that currently the sphinx-based policy manual stores the css files in a subfolder called _static and our cron script does not contemplate that. The called function is mvhtml() that uses pagepattern="$basedir/*.css" for moving the

Bug#872944: www.debian.org: Debian Policy Manual not fully published

Sean Whitton writes: > The Debian Policy Manual just changed its HTML output and while the HTML > has published, the CSS and included images have not. > Looking at [1], the CSS and included images should have been published > because they're still installed to >

Bug#872944: www.debian.org: Debian Policy Manual not fully published

Package: www.debian.org Severity: important Hello webmasters, The Debian Policy Manual just changed its HTML output and while the HTML has published, the CSS and included images have not. Looking at [1], the CSS and included images should have been published because they're still installed to