From: newbluemoon <newbluemoon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: po4a: update to 0.65
Date: Thu, 18 Nov 2021 22:02:08 +0100 [thread overview]
Message-ID: <20211118210208.McbAHiQ1E4ZFcTmTjBBcZXLSpMOM6Myzzi6_0frz7nc@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: 1781 bytes --]
New comment by newbluemoon on void-packages repository
https://github.com/void-linux/void-packages/pull/34029#issuecomment-973267880
Comment:
The errors on x86_64-musl like e.g.
```
# FAILED command: PODIFF -I#: cfg/multiple-nopotpo/_multiple.de.po tmp/cfg/multiple-nopotpo-src/multiple.de.po 2>&1 > tmp/cfg/multiple-nopotpo-src/_cmd_output
# Command output:
# | --- cfg/multiple-nopotpo/_multiple.de.po 2021-11-14 12:08:53.000000000 +0000
# | +++ tmp/cfg/multiple-nopotpo-src/multiple.de.po 2021-11-18 19:04:08.059796074 +0000
# | @@ -1,7 +1,8 @@
# | # German translations for po package
# | -# Copyright (C) 2020 Free Software Foundation, Inc.
# | +# German translation for po
# | +# Copyright (C) 2021 Free Software Foundation, Inc.
# | # This file is distributed under the same license as the po package.
# | -# Automatically generated, 2020.
# | +# Automatically generated, 2021.
# | #
# | msgid ""
# | msgstr ""
# (end of output)
```
are caused because musl’s gettext seems to add a translation for the package description while gettext on glibc does not.
So that there is an additional line `# | +# German translation for po` in the example above which doesn’t exist in the original .po file with which the newly generated one is compared. It comes from `/usr/share/locale/*/LC_MESSAGES/gettext-tools.mo`. The other differences are excluded via `diff -I` and don’t matter.
No idea how to fix this right now, if it is worth fixing? @ericonr maybe you know something about the differences of gettext on musl and glibc? :)
All other CI errors are like
```
Broken test cfg/split-multimaster: cfg/split-multimaster/_second.man.fr should be the expected content of produced file second.man.fr
```
and I cannot reproduce them locally.
next prev parent reply other threads:[~2021-11-18 21:02 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
2021-11-17 16:20 ` [PR PATCH] [Updated] " 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 [this message]
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=20211118210208.McbAHiQ1E4ZFcTmTjBBcZXLSpMOM6Myzzi6_0frz7nc@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).