Date: Wed, 2 Sep 2020 19:41:46 +0200 From: Stefan Esser <se@freebsd.org> To: "Julian H. Stacey" <jhs@berklix.com> Cc: current@freebsd.org, Gavin Howard <gavin.d.howard@gmail.com> Subject: Re: /usr/src/usr.bin/gh-bc don't know how to make /usr/src/contrib/bc/locales/en_US.UTF-8.msg Message-ID: <a584510b-c26d-e21c-5a04-624e0bf4e9d3@freebsd.org> In-Reply-To: <202009012342.081NgURH013325@fire.js.berklix.net> References: <202009012342.081NgURH013325@fire.js.berklix.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--xUYjhE8QUBM1qYSNZ8PiXyewEF6PCOab5
Content-Type: multipart/mixed; boundary="nxEl86qplHrEbWq26EoHxvMKJvSHqR8lj";
protected-headers="v1"
From: Stefan Esser <se@freebsd.org>
To: "Julian H. Stacey" <jhs@berklix.com>
Cc: current@freebsd.org, Gavin Howard <gavin.d.howard@gmail.com>
Message-ID: <a584510b-c26d-e21c-5a04-624e0bf4e9d3@freebsd.org>
Subject: Re: /usr/src/usr.bin/gh-bc don't know how to make
/usr/src/contrib/bc/locales/en_US.UTF-8.msg
References: <202009012342.081NgURH013325@fire.js.berklix.net>
In-Reply-To: <202009012342.081NgURH013325@fire.js.berklix.net>
--nxEl86qplHrEbWq26EoHxvMKJvSHqR8lj
Content-Type: multipart/mixed;
boundary="------------F2194693E52E17CBF5D02FDF"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------F2194693E52E17CBF5D02FDF
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
Am 02.09.20 um 01:42 schrieb Julian H. Stacey:
> Hi current@freebsd.org,
>=20
> /usr/src/usr.bin/gh-bc don't know how to make /usr/src/contrib/bc/local=
es/en_US.UTF-8.msg
> With .ctm_status src-cur 14656 .svn_revision 364986 /usr/src/usr.bin/gh=
-bc
Hi Julian,
since I'm building -CURRENT at least once a day with this bc
and there have been no other reports, this does appear to be
a local problem on your system (or a problem with CTM).
> Avoided for now with /etc/src.conf WITHOUT_GH_BC=3DYES
Yes, but the correct fix is to provide the missing file, which
is a symbolic link to en_US.msg. In fact, most of the message
catalogs are provided by symlinks (71 of 96 files in the locales
directory).
My assumption is, that CTM does not correctly encode and create
symbolic links, so you miss them ... (but I did not check the
CTM sources to verify that assumption).
This ought to be fixed in CTM and then a delta should be created
that provides these missing symlinks - since you are one of very
few CTM users left, you may want to create a patch ...
Since the mail list strips binary attachments, I'm including a
compresssed and uuencoded TAR file with these symlinks below.
Extract from within src/contrib/bc/locales to generate them:
begin 644 gh-bc-locales.tar.bz2
M0EIH.3%!6293618`G<P`#W!_D-"``)!``W_@/_?^D*?77I`$0``(4`/^TQ#A
M4(J+#)3TTTU(]0!#0Q-`:9`#09,14_T1E0&3(`!H:```9-`DU$%)#:@`````
M-#0!@````-``````4I*::@D_5/:IZGJ&)ZC(:`>IIH`'ZI[JAY5#VJAUJ'0S
MB5)<^7/.[OVC><;E,R%I@YC!.4$C!%0&\T"DP#,3(KT4RW8;8ZL<=3D^PJ'\5#
MMBEQ*ABH=3DRH=3D50RH94.NH<ZAM1`'("`>DD@:R,W/GV>3:MKS5-J$-83WJDS.
M)1%%A['191"3G$0\(S*S-#O-:6214=3DJ+2@HJ,CILM%IM\<((&8``>!/:`2:D
M`UNUOI<D)5NO>K>%^6W9OX=3DW/T^/CPUIGHWXYQ\=3DI4-M:%0\]0^BH8J'XK\#
MO8SO8QF,X3FF939;&8.-0ZE0RH>JH>;DJ'ON,DNYPY9FOK!SW<\J'94-;]CL
M6M^I%DP@060$<&-XODQ>V8=3D20"BM(8:NE8B<)(!>+T9O4D`:<5G*7:#R20#-
MX2Y(!CAAV:S,Z0V--71:%+%-XN5>7>I(!F2`60,2JD1@+-54NJ)C#AQJ&HVV
MTWXU#THM];M^IOIIEF\-(+*24PU)`*M+=3D:<7JRV2`54-.&<=3D=3D=3D0X94.VH]TG
M:B\D76B^^G&>V7DL@]%87K];RF:UIIFK6M9K@>-1E'6G"M+5>2+3Y3U9GG1<
M65M3M1?DTG"H[?8,9,U)P>M?4J"P(OHDY2!**Z,5&+4D"H>1>,-@`P(<($XD
MY3WP^Y/=3D\8ASA=3D*BJX555YBB'.%PF`G,;A1$V!^BP`_)=3D0Z=3D'LPS,F99VU#^
MR<JARJ&PRP6"P6"D2$57<(,I!05EF&;JAT=3D*AMMO4/,.CP5#@JMN.8S,S)EF
M6<ZA]I7#AL?=3D4.BH=3D]0["Y5#4G@_1^K&,SH9AF&8"@L&E$1$11B(BSC"'^D@
0"M>@D$#B+N2*<*$@+`$[F```
`
end
But since further symlinks will occur if more locales are added,
the problem will re-appear for CTM users, unless symlinks are
supported by CTM.
Regards, STefan
--------------F2194693E52E17CBF5D02FDF--
--nxEl86qplHrEbWq26EoHxvMKJvSHqR8lj--
--xUYjhE8QUBM1qYSNZ8PiXyewEF6PCOab5
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature"
-----BEGIN PGP SIGNATURE-----
wsB5BAABCAAjFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAl9P2VoFAwAAAAAACgkQR+u171r99UTO
Ugf/S50c47sBXWsKLF8DXGT6e3o1bAIhKlPesuadD1JGz8EL7gVI7JczcOyLWHnKU6DfMfVgzJSG
EYav2PtSMCcteL0+clpTRKFKlirQjm0Qlr3WGKFSeLkEF6XE3Gt7HH/QeNO1fDpLQNsBC/8CgCkN
hqtrye1C9tOaiOsz4gKLXT+Qeg22KzwWgfKV1dPknihBF4SD2mYjBXRTtNKAGH/wgI4CJE5UXeeO
g384KYy+0ghha5wcff9tXcvJU6TrCkvRV/M3U8Y67MTE/ntQiK8bNkn9ZZSvnGeZuE8j3q7ZF87D
zr/UprnbK9kHU9sxB6kPu4JAEwDyJCTxeotbyHN61w==
=ULsv
-----END PGP SIGNATURE-----
--xUYjhE8QUBM1qYSNZ8PiXyewEF6PCOab5--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a584510b-c26d-e21c-5a04-624e0bf4e9d3>