Script 'mail_helper' called by obssrc Hello community, here is the log from the commit of package mpfr for openSUSE:Factory checked in at 2023-02-02 18:06:46 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/mpfr (Old) and /work/SRC/openSUSE:Factory/.mpfr.new.32243 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "mpfr" Thu Feb 2 18:06:46 2023 rev:58 rq:1062392 version:4.2.0 Changes: -------- --- /work/SRC/openSUSE:Factory/mpfr/mpfr.changes 2022-11-27 12:52:46.895120755 +0100 +++ /work/SRC/openSUSE:Factory/.mpfr.new.32243/mpfr.changes 2023-02-02 18:28:46.771610431 +0100 @@ -1,0 +2,27 @@ +Tue Jan 31 15:58:22 UTC 2023 - Andreas Schwab <sch...@suse.de> + +- tests-tsprintf.patch: Avoid testsuite failure with glibc >= 2.37 + +------------------------------------------------------------------- +Mon Jan 9 08:22:17 UTC 2023 - Richard Biener <rguent...@suse.com> + +- Update to mpfr 4.2.0 + * New functions mpfr_cosu, mpfr_sinu, mpfr_tanu, mpfr_acosu, mpfr_asinu, + mpfr_atanu and mpfr_atan2u. + * New functions mpfr_cospi, mpfr_sinpi, mpfr_tanpi, mpfr_acospi, mpfr_asinpi, + mpfr_atanpi and mpfr_atan2pi. + * New functions mpfr_log2p1, mpfr_log10p1, mpfr_exp2m1, mpfr_exp10m1 and + mpfr_compound_si. + * New functions mpfr_fmod_ui, mpfr_powr, mpfr_pown, mpfr_pow_uj, mpfr_pow_sj + and mpfr_rootn_si (mpfr_pown is actually a macro defined as an alias for + mpfr_pow_sj). + * Bug fixes. + In particular, for the formatted output functions (mpfr_printf, etc.), + the case where the precision consists only of a period has been fixed + to be like ".0" as specified in the ISO C standard, and the manual has + been corrected and clarified. + The macros of the custom interface have also been fixed: they now behave + like functions (except a minor limitation for mpfr_custom_init_set). +- Remove mpfr-4.1.1-patch01.patch which is included in the new release. + +------------------------------------------------------------------- Old: ---- mpfr-4.1.1-patch01.patch mpfr-4.1.1.tar.xz mpfr-4.1.1.tar.xz.asc New: ---- mpfr-4.2.0.tar.xz mpfr-4.2.0.tar.xz.asc tests-tsprintf.patch ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ mpfr.spec ++++++ --- /var/tmp/diff_new_pack.6U89y6/_old 2023-02-02 18:28:47.179612930 +0100 +++ /var/tmp/diff_new_pack.6U89y6/_new 2023-02-02 18:28:47.183612954 +0100 @@ -1,7 +1,7 @@ # # spec file for package mpfr # -# Copyright (c) 2022 SUSE LLC +# Copyright (c) 2023 SUSE LLC # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed @@ -17,7 +17,7 @@ Name: mpfr -Version: 4.1.1 +Version: 4.2.0 Release: 0 Summary: The GNU multiple-precision floating-point library License: LGPL-3.0-or-later @@ -27,7 +27,7 @@ Source1: https://www.mpfr.org/mpfr-%{version}/mpfr-%{version}.tar.xz.asc Source2: %{name}.keyring Source3: baselibs.conf -Patch0: mpfr-4.1.1-patch01.patch +Patch0: tests-tsprintf.patch BuildRequires: gmp-devel BuildRequires: pkgconfig ++++++ mpfr-4.1.1.tar.xz -> mpfr-4.2.0.tar.xz ++++++ ++++ 30141 lines of diff (skipped) ++++++ tests-tsprintf.patch ++++++ >From 5172494c09718ffcb7ef1f19b3b211e3bce8781a Mon Sep 17 00:00:00 2001 From: Vincent Lefevre <vinc...@vinc17.net> Date: Tue, 10 Jan 2023 17:05:17 +0100 Subject: [PATCH] [tests/tsprintf.c] Modified a buggy test of the thousands separator. The test check_vsprintf ("+01,234,567 :", "%0+ -'13.10Pd:", (mpfr_prec_t) 1234567); is based on the output from glibc up to 2.36, which is incorrect: https://sourceware.org/bugzilla/show_bug.cgi?id=23432 The GNU C Library has apparently been partially fixed in its Git repository for the future 2.37, since a tsprintf failure has been reported (this is a bug in this test, not in the MPFR library): https://sympa.inria.fr/sympa/arc/mpfr/2023-01/msg00001.html So, modified the test to avoid the particular case of leading zeros due to the precision field larger than the number of digits. This case has already been tested without the thousands separator (where there are no issues with the C libraries), so that we do not miss much testing. Added a comment explaining the issue and a possible solution for future testing of this particular case (if need be). --- tests/tsprintf.c | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/tests/tsprintf.c b/tests/tsprintf.c index c68b2ba71..c0182503b 100644 --- a/tests/tsprintf.c +++ b/tests/tsprintf.c @@ -1719,7 +1719,17 @@ test_locale (void) check_sprintf ("000000001,000", "%'013.4Rg", x); #ifdef PRINTF_GROUPFLAG - check_vsprintf ("+01,234,567 :", "%0+ -'13.10Pd:", (mpfr_prec_t) 1234567); + /* Do not test the thousands separator with a precision field larger + than the number of digits (thus needing leading zeros), such as + "%0+ -'13.10Pd:" (used up to MPFR 4.2.0), since the GNU libc is + buggy: https://sourceware.org/bugzilla/show_bug.cgi?id=23432 + We don't know about the other implementations. + If we wanted to check that and avoid a failure of the test because of + a buggy C library (while MPFR would be consistent with the C library), + we could compare the MPFR output with both the correct output and the + output from the C library (possibly buggy). But to do that in a clean + way, this would require a change in the check_vsprintf() call. */ + check_vsprintf ("+1,234,567 :", "%0+ -'13Pd:", (mpfr_prec_t) 1234567); #endif mpfr_clear (x); -- 2.39.1
