From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <bzip2-devel-return-79-listarch-bzip2-devel=sourceware.org@sourceware.org>
Received: (qmail 12656 invoked by alias); 22 Jul 2019 23:40:57 -0000
Mailing-List: contact bzip2-devel-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:bzip2-devel@sourceware.org>
List-Help: <mailto:bzip2-devel-help@sourceware.org>
List-Subscribe: <mailto:bzip2-devel-subscribe@sourceware.org>
List-Id: <bzip2-devel.sourceware.org>
Sender: bzip2-devel-owner@sourceware.org
Received: (qmail 12647 invoked by uid 89); 22 Jul 2019 23:40:56 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Checked: by ClamAV 0.100.3 on sourceware.org
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-14.2 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=PDF, emergency, Emergency, Transcript
X-Spam-Status: No, score=-14.2 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on sourceware.org
X-Spam-Level: 
X-HELO: gnu.wildebeest.org
Date: Tue, 01 Jan 2019 00:00:00 -0000
From: Mark Wielaard <mark@klomp.org>
To: Santiago Ruano =?iso-8859-1?Q?Rinc=F3n?= <santiago@debian.org>
Cc: bzip2-devel@sourceware.org, bzip2@packages.debian.org
Subject: Re: Some bzip2 manual page patches from Debian
Message-ID: <20190722233014.GB2494@wildebeest.org>
References: <20190721205419.2904-1-mark@klomp.org>
 <20190722174137.GB2379@novelo>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20190722174137.GB2379@novelo>
User-Agent: Mutt/1.10.1 (2018-07-13)
X-Spam-Flag: NO
X-SW-Source: 2019-q3/txt/msg00042.txt.bz2

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