[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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



Sean Whitton <spwhitton@spwhitton.name> 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
> /usr/share/doc/debian-policy/policy.html/.  So I think this is a problem
> on your end rather than ours.  Please do reassign this bug if I'm wrong
> about that, and thanks in advance for your help.

> [1]  https://anonscm.debian.org/cgit/debwww/cron.git/tree/parts/7doc

Hi debian-www folks,

Just a heads-up that we're fixing some more stuff and Policy 4.1.1.0 will
be a bit different again (it's not yet uploaded).  Here's what I currently
have staged for the next version:

* usr/share/doc/debian-policy/policy.html/ in the package will have the
  multi-file HTML version.  This is a directory with a couple of
  subdirectories, and all the internal HTML links should be relative.
  However, please note that some of the Javascript is symlinks to files
  that are shipped in the libjs-sphinxdoc package, so you may need a bit
  of machinery to turn those symlinks into real files.

* usr/share/doc/debian-policy/policy-1.html will be the single-file HTML
  version.  However, the Sphinix single-file version still requires static
  assets in usr/share/doc/debian-policy/{_images,_static} that will need
  to be in the right position relative to policy-1.html.  These have the
  same symlinks to libjs-sphinxdoc.

The current state in the archive right now only has the single-file
version, and it is in the policy.html subdirectory.  But we got feedback
after this release that people really wanted both versions available.

Unfortunately things might be just a touch chaotic for a bit as we work
through finishing this reStructuredText conversion.  Apologies for the
extra work!  We think the long-term result will be worth it both in terms
of better output and in terms of a more maintainable Policy document.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>


Reply to: