From: ailiop-git <ailiop-git@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: util-linux: update to 2.36.
Date: Tue, 28 Jul 2020 14:21:49 +0200 [thread overview]
Message-ID: <20200728122149.97f63xiylUO1IqZUVP8a9ZnHs-fb75mXl_8tzojju1U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23760@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
New comment by ailiop-git on void-packages repository
https://github.com/void-linux/void-packages/pull/23760#issuecomment-665007457
Comment:
Ah ok, so the particular failure on glibc is on `column/invalid-multibyte` test, due to missing locale:
`/bin/sh: warning: setlocale: LC_ALL: cannot change locale (C.UTF-8)`
this was changed in commit `6ef9a9e18471b9 ("tests: (column) use actually invalid multibytes to test encoding")`, which means it has been failing since v2.35.
This can be fixed with:
```
sed -i s/^#C.UTF-8/C.UTF-8/ masterdir/etc/default/libc-locales
xbps-reconfigure -r masterdir/ glibc-locales -f
```
The second issue on musl, is the `getopt/options-posix_correctly `test failing. This is due to the ordering of the options processing, see diff of failing test below:
```
- -a -b '1' -c '2' --a-long --b-long '3' --c-long '' -- 'foo' 'bar' 'xyxxy' '--a-long'
+ -a -b '1' -c '2' --a-long --b-long '3' --c-long '' --a-long -- 'foo' 'bar' 'xyxxy'
```
This happens as musl doesn't implement `POSIXLY_CORRECT` (which influences the ordering). It also means that the particular test has always been failing on musl.
next prev parent reply other threads:[~2020-07-28 12:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 10:39 [PR PATCH] " ailiop-git
2020-07-23 13:41 ` [PR REVIEW] " sgn
2020-07-23 13:53 ` [PR PATCH] [Updated] " ailiop-git
2020-07-28 7:56 ` sgn
2020-07-28 9:16 ` ailiop-git
2020-07-28 10:01 ` sgn
2020-07-28 12:21 ` ailiop-git [this message]
2020-07-28 14:32 ` sgn
2020-07-28 16:22 ` ailiop-git
2020-07-28 17:00 ` ericonr
2020-07-28 17:14 ` ailiop-git
2020-07-29 14:50 ` [PR PATCH] [Closed]: " sgn
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=20200728122149.97f63xiylUO1IqZUVP8a9ZnHs-fb75mXl_8tzojju1U@z \
--to=ailiop-git@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).