From: mvf <mvf@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] glibc: restore localized messages
Date: Fri, 21 May 2021 19:32:51 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31052@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
There is a new pull request by mvf against master on the void-packages repository
https://github.com/mvf/void-packages pr/glibc
https://github.com/void-linux/void-packages/pull/31052
glibc: restore localized messages
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
This restores the `/usr/share/locale/*/LC_MESSAGES/libc.mo` files that went missing at some point after `glibc-locales-2.30_1`.
Before: App is localized, glibc isn't:
```
$ ls ...
ls: '...' にアクセスできません: No such file or directory
```
After:
```
$ ls ...
ls: '...' にアクセスできません: そのようなファイルやディレクトリはありません
```
A patch file from https://github.com/void-linux/void-packages/pull/31052.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pr/glibc-31052.patch --]
[-- Type: text/x-diff, Size: 915 bytes --]
From b52396f6f05dee557509a68954f7115c6d9aa7db Mon Sep 17 00:00:00 2001
From: Matthias von Faber <mvf@gmx.eu>
Date: Fri, 21 May 2021 19:26:15 +0200
Subject: [PATCH] glibc: restore localized messages
---
srcpkgs/glibc/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/glibc/template b/srcpkgs/glibc/template
index 9202e4145453..b361bb98a1ea 100644
--- a/srcpkgs/glibc/template
+++ b/srcpkgs/glibc/template
@@ -1,7 +1,7 @@
# Template file for 'glibc'
pkgname=glibc
version=2.32
-revision=1
+revision=2
bootstrap=yes
short_desc="GNU C library"
maintainer="Enno Boland <gottox@voidlinux.org>"
@@ -48,7 +48,7 @@ conf_files="
/etc/gai.conf
/etc/ld.so.conf"
if [ "$CHROOT_READY" ]; then
- hostmakedepends="bison perl python3 texinfo"
+ hostmakedepends="bison gettext perl python3 texinfo"
fi
makedepends="kernel-libc-headers"
lib32files="/usr/lib/gconv/gconv-modules"
next reply other threads:[~2021-05-21 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 17:32 mvf [this message]
2021-05-21 18:03 ` [PR PATCH] [Merged]: " ericonr
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31052@inbox.vuxu.org \
--to=mvf@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).