[sr #110501] Plese convert all po/*.po fiels to UTF-8

2021-06-01 Thread Tomasz Kłoczko 
URL:
  

 Summary: Plese convert all po/*.po fiels to UTF-8
 Project: GNU M4
Submitted by: kloczek
Submitted on: Tue 01 Jun 2021 09:40:36 AM UTC
Category: None
Priority: 5 - Normal
Severity: 3 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
Originator Email: 
 Open/Closed: Open
 Discussion Lock: Any
Operating System: None

___

Details:

Currently most of the systems are using UTF-8 based locale settings.
Whhen .po file is in non UTF-8 encoding it causes that generated .mo file is
in teh esame encoding. This is causing that when actually .mo file is used
(g)glibc must on the fly convert it to UTF-8.

[tkloczko@barrel po]$ grep charset= *po
bg.po:"Content-Type: text/plain; charset=UTF-8\n"
cs.po:"Content-Type: text/plain; charset=ISO-8859-2\n"
da.po:"Content-Type: text/plain; charset=ISO-8859-1\n"
de.po:"Content-Type: text/plain; charset=ISO-8859-1\n"
el.po:"Content-Type: text/plain; charset=iso-8859-7\n"
eo.po:"Content-Type: text/plain; charset=utf-8\n"
es.po:"Content-Type: text/plain; charset=UTF-8\n"
fi.po:"Content-Type: text/plain; charset=UTF-8\n"
fr.po:"Content-Type: text/plain; charset=UTF-8\n"
ga.po:"Content-Type: text/plain; charset=ISO-8859-1\n"
gl.po:"Content-Type: text/plain; charset=UTF-8\n"
hr.po:"Content-Type: text/plain; charset=UTF-8\n"
id.po:"Content-Type: text/plain; charset=ISO-8859-1\n"
ja.po:"Content-Type: text/plain; charset=UTF-8\n"
ko.po:"Content-Type: text/plain; charset=UTF-8\n"
nl.po:"Content-Type: text/plain; charset=UTF-8\n"
pl.po:"Content-Type: text/plain; charset=UTF-8\n"
pt_BR.po:"Content-Type: text/plain; charset=UTF-8\n"
ro.po:"Content-Type: text/plain; charset=ISO-8859-2\n"
ru.po:"Content-Type: text/plain; charset=KOI8-R\n"
sr.po:"Content-Type: text/plain; charset=UTF-8\n"
sv.po:"Content-Type: text/plain; charset=ISO-8859-1\n"
uk.po:"Content-Type: text/plain; charset=UTF-8\n"
vi.po:"Content-Type: text/plain; charset=utf-8\n"
zh_CN.po:"Content-Type: text/plain; charset=UTF-8\n"
zh_TW.po:"Content-Type: text/plain; charset=UTF-8\n"







___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[sr #110502] 1.4.19: test suite is failing

2021-06-01 Thread Tomasz Kłoczko 
URL:
  

 Summary: 1.4.19: test suite is failing
 Project: GNU M4
Submitted by: kloczek
Submitted on: Tue 01 Jun 2021 10:06:12 AM UTC
Category: None
Priority: 5 - Normal
Severity: 3 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
Originator Email: 
 Open/Closed: Open
 Discussion Lock: Any
Operating System: None

___

Details:

Liooks like some files are missing in dist tar ball.

Please next time generate that tar ball using "distchec" target instead just
"dist".


[tkloczko@barrel tests]$ cat test-suite.log
=
   GNU M4 1.4.19: tests/test-suite.log
=

# TOTAL: 267
# PASS:  245
# SKIP:  20
# XFAIL: 0
# FAIL:  2
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

SKIP: test-asyncsafe-spin2
==

Skipping test: multithreading not enabled
SKIP test-asyncsafe-spin2 (exit status: 77)

SKIP: test-mbrtowc-w32-1.sh
===

Skipping test: not a native Windows system
SKIP test-mbrtowc-w32-1.sh (exit status: 77)

SKIP: test-mbrtowc-w32-2.sh
===

Skipping test: not a native Windows system
SKIP test-mbrtowc-w32-2.sh (exit status: 77)

SKIP: test-mbrtowc-w32-3.sh
===

Skipping test: not a native Windows system
SKIP test-mbrtowc-w32-3.sh (exit status: 77)

SKIP: test-mbrtowc-w32-4.sh
===

Skipping test: not a native Windows system
SKIP test-mbrtowc-w32-4.sh (exit status: 77)

SKIP: test-mbrtowc-w32-5.sh
===

Skipping test: not a native Windows system
SKIP test-mbrtowc-w32-5.sh (exit status: 77)

SKIP: test-mbrtowc-w32-6.sh
===

Skipping test: not a native Windows system
SKIP test-mbrtowc-w32-6.sh (exit status: 77)

SKIP: test-mbrtowc-w32-7.sh
===

Skipping test: not a native Windows system
SKIP test-mbrtowc-w32-7.sh (exit status: 77)

SKIP: test-nl_langinfo-mt
=

Skipping test: multithreading not enabled
SKIP test-nl_langinfo-mt (exit status: 77)

FAIL: test-posix_spawn-dup2-stdout
==

subprocess failed: No such file or directory
FAIL test-posix_spawn-dup2-stdout (exit status: 1)

FAIL: test-posix_spawn-dup2-stdin
=

subprocess failed: No such file or directory
FAIL test-posix_spawn-dup2-stdin (exit status: 1)

SKIP: test-pthread_sigmask2
===

Skipping test: POSIX threads not enabled
SKIP test-pthread_sigmask2 (exit status: 77)

SKIP: test-setlocale_null-mt-one


Skipping test: multithreading not enabled
SKIP test-setlocale_null-mt-one (exit status: 77)

SKIP: test-setlocale_null-mt-all


Skipping test: multithreading not enabled
SKIP test-setlocale_null-mt-all (exit status: 77)

SKIP: test-thread_create


Skipping test: multithreading not enabled
SKIP test-thread_create (exit status: 77)

SKIP: test-wcrtomb-w32-1.sh
===

Skipping test: not a native Windows system
SKIP test-wcrtomb-w32-1.sh (exit status: 77)

SKIP: test-wcrtomb-w32-2.sh
===

Skipping test: not a native Windows system
SKIP test-wcrtomb-w32-2.sh (exit status: 77)

SKIP: test-wcrtomb-w32-3.sh
===

Skipping test: not a native Windows system
SKIP test-wcrtomb-w32-3.sh (exit status: 77)

SKIP: test-wcrtomb-w32-4.sh
===

Skipping test: not a native Windows system
SKIP test-wcrtomb-w32-4.sh (exit status: 77)

SKIP: test-wcrtomb-w32-5.sh
===

Skipping test: not a native Windows system
SKIP test-wcrtomb-w32-5.sh (exit status: 77)

SKIP: test-wcrtomb-w32-6.sh
===

Skipping test: not a native Windows system
SKIP test-wcrtomb-w32-6.sh (exit status: 77)

SKIP: test-wcrtomb-w32-7.sh
===

Skipping test: not a native Windows system
SKIP test-wcrtomb-w32-7.sh (exit status: 77)






___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[sr #110502] 1.4.19: test suite is failing

2021-06-01 Thread Tomasz Kłoczko 
Additional Item Attachment, sr #110502 (project m4):

File name: m4-po_to_utf-8.patch   Size:222 KB




___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[sr #110501] Plese convert all po/*.po fiels to UTF-8

2021-06-01 Thread Tomasz Kłoczko 
Additional Item Attachment, sr #110501 (project m4):

File name: m4-po_to_utf-8.patch   Size:222 KB




___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

Re: m4 1.4.19 check always fails (198.sysval)

2021-06-01 Thread Eric Blake 
On Mon, May 31, 2021 at 09:02:59PM +0200, Ferdinand Thiessen wrote:
> Hello,
> I try to build m4 version 1.4.19, but when running make check it always
> fails.
> I can reproduce it with different systems, tested it on openSUSE
> Tumbleweed, Leap 15.2 and 15.3.
> 
> 
> > Checking ./198.sysval
> > @ ../doc/m4.texi:6751: Origin of test
> > ./198.sysval: stderr mismatch
> > --- m4-tmp.8164/m4-xerr 2021-05-31 17:09:06.248513843 +
> > +++ m4-tmp.8164/m4-err  2021-05-31 17:09:06.232513843 > +
> > @@ -0,0 +1 @@
> > +sh: line 1: 10151 Killed  /bin/sh -c 'kill -9 $$'
> > Checking ./199.mkstemp

Known issue, and due to a bug in the testsuite and not in m4 itself.
It will be fixed for 1.4.20.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.   +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

[sr #110502] 1.4.19: test suite is failing

2021-06-01 Thread Eric Blake 
Follow-up Comment #1, sr #110502 (project m4):

comment #0 original submission:]
> Liooks like some files are missing in dist tar ball.
> 
> Please next time generate that tar ball using "distchec" target instead just
"dist".

The tarball WAS generated with 'make distcheck', and passed on my machine. 
There are no missing files in the tarball itself; however, skipped tests
within the gnulib unit tests are normal based on what your system has
available.


> FAIL: test-posix_spawn-dup2-stdout
> ==
> 
> subprocess failed: No such file or directory
> FAIL test-posix_spawn-dup2-stdout (exit status: 1)
> 
> FAIL: test-posix_spawn-dup2-stdin
> =
> 
> subprocess failed: No such file or directory
> FAIL test-posix_spawn-dup2-stdin (exit status: 1)

These are gnulib unit test failures; I'll forward your report there.  They do
not affect the operation of m4 itself.


___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[sr #110501] Plese convert all po/*.po fiels to UTF-8

2021-06-01 Thread Eric Blake 
Update of sr #110501 (project m4):

  Status:None => Confirmed  
 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

Thanks for the report.  I am forwarding this request to the translation
project, since they are the source of these files.  Nothing that m4.git can do
about it, although the release project automatically picks up any changes made
by the translation project.  As such, I'm closing this, not because the
conversion is complete, but because the translation project does not use this
bug tracker.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

Re: [sr #110502] 1.4.19: test suite is failing

2021-06-01 Thread Eric Blake 
On Tue, Jun 01, 2021 at 06:06:13AM -0400, Tomasz Kłoczko wrote:
> URL:
>   

> Operating System: None
> 
> FAIL: test-posix_spawn-dup2-stdout
> ==
> 
> subprocess failed: No such file or directory
> FAIL test-posix_spawn-dup2-stdout (exit status: 1)
> 
> FAIL: test-posix_spawn-dup2-stdin
> =
> 
> subprocess failed: No such file or directory
> FAIL test-posix_spawn-dup2-stdin (exit status: 1)

Thanks for the report; however, you failed to tell us which operating
system.  The fix will need to be in gnulib's unit tests, so I'm adding
bug-gnulib in the distribution.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.   +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

Re: [sr #110501] Plese convert all po/*.po fiels to UTF-8

2021-06-01 Thread Eric Blake 
Forwarding this to the translation project.

On Tue, Jun 01, 2021 at 05:40:38AM -0400, Tomasz Kłoczko wrote:
> URL:
>   
> 
>  Summary: Plese convert all po/*.po fiels to UTF-8
>  Project: GNU M4

> Currently most of the systems are using UTF-8 based locale settings.
> Whhen .po file is in non UTF-8 encoding it causes that generated .mo file is
> in teh esame encoding. This is causing that when actually .mo file is used
> (g)glibc must on the fly convert it to UTF-8.
> 
> [tkloczko@barrel po]$ grep charset= *po
> bg.po:"Content-Type: text/plain; charset=UTF-8\n"
> cs.po:"Content-Type: text/plain; charset=ISO-8859-2\n"
> da.po:"Content-Type: text/plain; charset=ISO-8859-1\n"
> de.po:"Content-Type: text/plain; charset=ISO-8859-1\n"
> el.po:"Content-Type: text/plain; charset=iso-8859-7\n"
> eo.po:"Content-Type: text/plain; charset=utf-8\n"
> es.po:"Content-Type: text/plain; charset=UTF-8\n"
> fi.po:"Content-Type: text/plain; charset=UTF-8\n"
> fr.po:"Content-Type: text/plain; charset=UTF-8\n"
> ga.po:"Content-Type: text/plain; charset=ISO-8859-1\n"
> gl.po:"Content-Type: text/plain; charset=UTF-8\n"
> hr.po:"Content-Type: text/plain; charset=UTF-8\n"
> id.po:"Content-Type: text/plain; charset=ISO-8859-1\n"
> ja.po:"Content-Type: text/plain; charset=UTF-8\n"
> ko.po:"Content-Type: text/plain; charset=UTF-8\n"
> nl.po:"Content-Type: text/plain; charset=UTF-8\n"
> pl.po:"Content-Type: text/plain; charset=UTF-8\n"
> pt_BR.po:"Content-Type: text/plain; charset=UTF-8\n"
> ro.po:"Content-Type: text/plain; charset=ISO-8859-2\n"
> ru.po:"Content-Type: text/plain; charset=KOI8-R\n"
> sr.po:"Content-Type: text/plain; charset=UTF-8\n"
> sv.po:"Content-Type: text/plain; charset=ISO-8859-1\n"
> uk.po:"Content-Type: text/plain; charset=UTF-8\n"
> vi.po:"Content-Type: text/plain; charset=utf-8\n"
> zh_CN.po:"Content-Type: text/plain; charset=UTF-8\n"
> zh_TW.po:"Content-Type: text/plain; charset=UTF-8\n"

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.   +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

[PATCH] tests: Fix 198.sysval

2021-06-01 Thread Eric Blake 
In my attempt to avoid test failures on Haiku, I caused test failures
on platforms where sh is noisy when reporting a killed sub-process.

* doc/m4.texi (Sysval): Avoid stderr noise during test.
Fixes: 17011ea76a (tests: Skip signal detection on Haiku)
Fixes: https://lists.gnu.org/archive/html/bug-m4/2021-05/msg00029.html
---
 doc/m4.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/m4.texi b/doc/m4.texi
index 247f2be5..3b833b2a 100644
--- a/doc/m4.texi
+++ b/doc/m4.texi
@@ -6756,7 +6756,7 @@ Sysval
 ')m4exit(`77')')dnl
 changequote(`[', `]')
 @result{}
-syscmd([/bin/sh -c 'kill -9 $$'; st=$?;
+syscmd([@{ /bin/sh -c 'kill -9 $$'; @} 2>/dev/null; st=$?;
 test $st = 137 || test $st = 265])
 @result{}
 ifelse(sysval, [0], , [errprint([ skipping: shell does not send signal 9
-- 
2.31.1

[sr #110502] 1.4.19: test suite is failing

2021-06-01 Thread Tomasz Kłoczko 
Follow-up Comment #2, sr #110502 (project m4):

> These are gnulib unit test failures; I'll forward your report there.  They
do not affect the operation of m4 itself.

It affects building and testing procedures.

OK. So why m4 executest gnulib test units?


___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

Re: [PATCH] tests: Fix 198.sysval

2021-06-01 Thread rpm 
I can confirm, the patch fixes the bug for me.

Am 01.06.21 um 15:16 schrieb Eric Blake:
> In my attempt to avoid test failures on Haiku, I caused test failures
> on platforms where sh is noisy when reporting a killed sub-process.
>
> * doc/m4.texi (Sysval): Avoid stderr noise during test.
> Fixes: 17011ea76a (tests: Skip signal detection on Haiku)
> Fixes: https://lists.gnu.org/archive/html/bug-m4/2021-05/msg00029.html

[sr #110502] 1.4.19: test suite is failing

2021-06-01 Thread Eric Blake 
Follow-up Comment #3, sr #110502 (project m4):

[comment #2 comment #2:]
> > These are gnulib unit test failures; I'll forward your report there.  They
do not affect the operation of m4 itself.
> 
> It affects building and testing procedures.
> 
> OK. So why m4 executest gnulib test units?

Because m4 uses gnulib.  Sometimes a gnulib unit test failure DOES indicate a
problem that will be observable through m4 as well; and even if a gnulib unit
test failure does not indicate a problem for m4, it may indicate a problem for
other gnulib clients.

As it is, m4 only runs the gnulib unit tests for the actual gnulib modules in
use by m4, and not all possible gnulib unit tests.


___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/