From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] texinfo 6.8
Date: Tue, 6 Jul 2021 19:20:27 +0100 [thread overview]
Message-ID: <c4fe6fe5-994b-18fb-7c32-518efc4960e7@dronecode.org.uk> (raw)
In-Reply-To: <8642ddac-24da-b16e-362e-b44a3fe91a6b@cornell.edu>
On 06/07/2021 17:32, Ken Brown via Cygwin wrote:
> On 7/6/2021 7:59 AM, Jon Turney wrote:
>> On 05/07/2021 19:04, Ken Brown via Cygwin-announce via Cygwin wrote:
>>> The following packages have been uploaded to the Cygwin distribution:
>>>
>>> * texinfo-6.8-1
>>> * texinfo-tex-6.8-1
>>> * info-6.8-1
>>>
>>> Texinfo is a documentation system that uses a single source file to
>>> produce output in a number of formats, both online and printed (dvi,
>>> html, info, pdf, xml, etc.).
>>>
>>> This is an update to the latest upstream release. See
>>
>> Hi Ken,
>>
>> Thanks for this update.
>>
>> This seems to break building the cygwin documentation:
>>
>> > [...]
>>> docbook2x-texi --xinclude --info --utf8trans-map=charmap
>>> ../../../../src/winsup/doc/cygwin-api.xml --string-param
>>> output-file=cygwin-api
>>> could not find ParserDetails.ini in
>>> /usr/share/perl5/vendor_perl/5.32/XML/SAX
>>> could not open -: No such file or directory
>>> /usr/bin/db2x_texixml: program in pipeline exited with an error
>>> make: *** [Makefile:729: cygwin-api.info] Error 1
>>
>> Poking around a bit, under the hood this is invoking makeinfo, and it
>> seems that can't read from a pipeline anymore:
>>
>>> $ echo foo | makeinfo
>>> could not open -: No such file or directory
>>
>> Downgrading to 6.7, I can build again, and:
>>
>>> $ echo foo | makeinfo
>>> -: warning: document without nodes
>>
>> Is this an intentional upstream change?
>
> No.
>
> I've applied the upstream fix and am waiting for scallywag to build and
> deploy texinfo-6.8-2. (It seems to be taking forever.)
It seems that something went wrong when processing the build complete
notification, which I need to look into...
> My local test indicates that this fixes the problem, but I'd appreciate
> it if you would confirm that before I "untest" the new release.
Yup, that fixes it. Thanks!
prev parent reply other threads:[~2021-07-06 18:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 18:04 Ken Brown via Cygwin-announce
2021-07-06 11:59 ` Jon Turney
2021-07-06 16:32 ` Ken Brown
2021-07-06 18:20 ` Jon Turney [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=c4fe6fe5-994b-18fb-7c32-518efc4960e7@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
/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).