Github messages for voidlinux
 help / color / mirror / Atom feed
From: newbluemoon <newbluemoon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: po4a: update to 0.65
Date: Tue, 16 Nov 2021 09:01:39 +0100	[thread overview]
Message-ID: <20211116080139._KsX-olibRQwRG35F_DkWdHKfmhx3IT83oub6AMPPbE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34029@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 817 bytes --]

New comment by newbluemoon on void-packages repository

https://github.com/void-linux/void-packages/pull/34029#issuecomment-969980443

Comment:
Added an upstream patch which removes piping into `onsgmls`, reading the file as a paramater instead. This seems to have been a residual from a long time ago and fixes half of the problem.

The test still fails because `docbook` ships a declaration which has `OMITTAG NO`. When set to `YES` the test passes. Debian for example completely patches out all `docbook` declarations and ships its own.

This seems to happen because the test sgml files are not valid according to the original docbook declaration and the way to go should be to fix the test sgml files. I will give it a shot, but until then, I think this PR is good to go as it is the test that’s broken. :)

  parent reply	other threads:[~2021-11-16  8:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11 13:44 [PR PATCH] po4a: update to 0.64 newbluemoon
2021-11-12 22:53 ` ericonr
2021-11-13  7:24 ` newbluemoon
2021-11-15 13:20 ` [PR PATCH] [Updated] " newbluemoon
2021-11-16  7:18 ` [PR PATCH] [Updated] po4a: update to 0.65 newbluemoon
2021-11-16  8:01 ` newbluemoon [this message]
2021-11-17 16:20 ` newbluemoon
2021-11-17 16:22 ` newbluemoon
2021-11-18  5:10 ` [PR PATCH] [Updated] " newbluemoon
2021-11-18 18:59 ` newbluemoon
2021-11-18 19:04 ` newbluemoon
2021-11-18 21:02 ` newbluemoon
2021-11-21 19:35 ` ericonr
2021-11-21 21:49 ` [PR PATCH] [Updated] " newbluemoon
2021-11-21 22:06 ` newbluemoon
2022-02-25 18:42 ` [PR PATCH] [Updated] " newbluemoon
2022-03-13 19:29 ` [PR PATCH] [Updated] po4a: update to 0.66 newbluemoon
2022-03-28 18:57 ` newbluemoon
2022-05-07 18:32 ` newbluemoon
2022-05-13 14:47 ` ericonr
2022-05-13 14:47 ` [PR PATCH] [Merged]: " ericonr
2022-05-13 15:06 ` newbluemoon

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=20211116080139._KsX-olibRQwRG35F_DkWdHKfmhx3IT83oub6AMPPbE@z \
    --to=newbluemoon@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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 NNTP newsgroup(s).