public inbox for bzip2-devel@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "Santiago Ruano Rincón" <santiago@debian.org>
Cc: bzip2-devel@sourceware.org, bzip2@packages.debian.org
Subject: Re: Some bzip2 manual page patches from Debian
Date: Tue, 01 Jan 2019 00:00:00 -0000	[thread overview]
Message-ID: <20190722233014.GB2494@wildebeest.org> (raw)
In-Reply-To: <20190722174137.GB2379@novelo>

Hi,

On Mon, Jul 22, 2019 at 02:41:37PM -0300, Santiago Ruano Rincón wrote:
> (Replacing uploaders with bzip2@packages.debian.org)

Ah, good trick. Thanks.

> El 21/07/19 a las 22:54, Mark Wielaard escribió:
> > Ideally the bzip2.1 man page itself would be generated from the
> > manual.xml file. But I saw that on Debian even the pdf and html
> > generation of the manual seem to fail.
> 
> Sorry, how do you see they fail? Maybe I am missing something, but those
> files are not generated currently.

They are indeed only generated when making a release.
By running make dist (or make manual).
A distro/packager shouldn't have to regenerate them.
But it would be better if they could be.

make manual works on my RHEL7 setup, but fails as follows on my Debian
setup:

$ make distclean
rm -f *.o libbz2.a bzip2 bzip2recover \
sample1.rb2 sample2.rb2 sample3.rb2 \
sample1.tst sample2.tst sample3.tst
rm -f manual.ps manual.html manual.pdf bzip2.txt bzip2.1.preformatted
$ make manual.pdf
./xmlproc.sh -pdf manual.xml
Creating manual.pdf ...
Making portrait pages on USletter paper (8.5inx11in)
Cleaning up: output manual.fmt manual.aux manual.fo manual.log *.out
  deleting output
  deleting manual.fmt
  deleting manual.aux
  deleting manual.fo
  deleting manual.log
  deleting *.out
rm: cannot remove '*.out': No such file or directory
make: *** [Makefile:220: manual.pdf] Error 1

Some digging into the xmlproc.sh script shows that:
pdfxmltex manual.fo >output </dev/null
fails with:

(/usr/share/texlive/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
! Extra \else.
&...x #$1\@empty \XML@charref $2;\XML@tempa \else 
                                                  \begingroup \utfeight@prot...
l.48 ...e\string`\noexpand ;=\the\catcode\string`;
                                                  
? 
! Emergency stop.
&...x #$1\@empty \XML@charref $2;\XML@tempa \else 
                                                  \begingroup \utfeight@prot...
l.48 ...e\string`\noexpand ;=\the\catcode\string`;
                                                  
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on manual.log.

It might certainly be because I don't have the correct packages
installed.

Cheers,

Mark

      reply	other threads:[~2019-07-22 23:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01  0:00 Mark Wielaard
2019-01-01  0:00 ` [PATCH 2/3] Mention the --help command line option in the documentation Mark Wielaard
2019-01-01  0:00 ` [PATCH 3/3] Add generation of bzip2.txt and bzip2.1.preformatted to Makefile Mark Wielaard
2019-01-01  0:00 ` [PATCH 1/3] bzip2.1: remove blank spaces in man page and drop the .PU macro Mark Wielaard
2019-01-01  0:00 ` Some bzip2 manual page patches from Debian Santiago Ruano Rincón
2019-01-01  0:00   ` Mark Wielaard [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190722233014.GB2494@wildebeest.org \
    --to=mark@klomp.org \
    --cc=bzip2-devel@sourceware.org \
    --cc=bzip2@packages.debian.org \
    --cc=santiago@debian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).