• Bug#872868: debian-policy: section numbers missing

    From Adam Borowski@21:1/5 to All on Tue Aug 22 02:00:01 2017
    XPost: linux.debian.bugs.dist

    Package: debian-policy
    Version: 4.1.0.0
    Severity: normal

    Hi!
    I'm afraid that the new upload of the policy doesn't include section numbers
    in the text -- neither in the TOC nor in the body. As that's how we usually refer to parts of the Policy, that makes any such references impossible.


    Meow!
    -- System Information:
    Debian Release: buster/sid
    APT prefers unstable-debug
    APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (150, 'experimental')
    Architecture: amd64 (x86_64)
    Foreign Architectures: i386

    Kernel: Linux 4.13.0-rc6-debug-ubsan-00198-gafd58c2be315 (SMP w/6 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8)
    Shell: /bin/sh linked to /bin/dash
    Init: sysvinit (via /sbin/init)

    Versions of packages debian-policy depends on:
    ii libjs-sphinxdoc 1.5.6-2

    debian-policy recommends no packages.

    Versions of packages debian-policy suggests:
    pn doc-base <none>

    -- no debconf information

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sean Whitton@21:1/5 to Adam Borowski on Tue Aug 22 02:40:02 2017
    XPost: linux.debian.bugs.dist

    control: retitle -1 Plain text output format lacks section numbering

    Hello Adam,

    On Tue, Aug 22 2017, Adam Borowski wrote:

    I'm afraid that the new upload of the policy doesn't include section numbers in the text -- neither in the TOC nor in the body. As that's how we usually refer to parts of the Policy, that makes any such references impossible.

    The PDF, HTML, info and ePub output formats have section numbering.

    The plain text format doesn't yet, mainly because it's put together with
    a local hack -- Sphinx generates one plain text file for each chapter,
    but we want a single policy.txt. We are waiting on better upstream
    support.

    In the meantime, you might consider using the info output format.

    --
    Sean Whitton

    --=-=-Content-Type: application/pgp-signature; name="signature.asc"

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAlmbbDsACgkQaVt65L8G YkBAvA/+KMQmDfjeVrdWmYzktc0NemG7YIMIDT7mKepZQ6NdI8/JkuqMgY5JrzVb 7oaeZAimUlFl8V4WFzHg3v6FKSDJaUawIFUEqG19VRWMGlDXaEiROEJGzpI8LlV9 +scZsPAlZpuizUP9v4hduryz1W0YondnhEYXJ8tiDHmRC9kmw1OR2sT+N1jcL8iM CYhQlYzwOV8LOI4k861wqAAUOpzOZoeF1M5cxPCrA0qw0pZFo0t6EWwDZVIURX/f bjXs5dADOvGh1r6AeBkGkI3PsNvzwl7s0Wm3/8GUg3k3/ymvsp8AY8qyUmZnNtn9 37uFfdKeaF4/aG22nA83wBx7CTR3BVW65hPAqaeh3T5UqMC+xIb1qHl7B61XD99H Fhrolo00q9hwQoQ93/vhGjTKGAUB3AYHobF456Lu3+AVBh3TqVkyTQvQBj1MKknj OvFjLHgVgX9KeNHLCPcVxSOSGpop8HvYJKgECEzIDVXqAeb94wkrSDEpwDeTQGpT /s0zX4Oe/LFRzR9F+Li62w9h7LlRj8E7wFJjOTbVIeL18Wayv+eePnula2SvWGZr wVayEcYUcgl+9yBUBExLr72cSmecutapc/Gmoz7In2/q25IZuV98Xq0F0PXwM5wF sOI48pelPn98zrx8xZ3rxcfD+8pikOcbFmIDCfhrhELsqWrL6/c]6T
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to Sean Whitton on Tue Aug 22 03:40:01 2017
    XPost: linux.debian.bugs.dist

    Sean Whitton <spwhitton@spwhitton.name> writes:

    The PDF, HTML, info and ePub output formats have section numbering.

    The plain text format doesn't yet, mainly because it's put together with
    a local hack -- Sphinx generates one plain text file for each chapter,
    but we want a single policy.txt. We are waiting on better upstream
    support.

    Well, it's not just that, but also that Sphinx in general doesn't add
    section numbers to the text output. But yes, it's unfortunately a
    casualty of the reStructuredText conversion.

    If we have to, we'll hack together something that will add section
    numbers at some point, but I'm still hoping that Sphinx upstream will add support for this.

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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)