Bug#1046055: mpfr4: Fails to build source after successful build

[Vincent Lefevre]

On 2023-08-28 11:51:17 +0200, Vincent Lefevre wrote:
> On 2023-08-28 11:15:15 +0200, Matthias Klose wrote:
> > the package is built in a separate build dir. shouldn't the upstream
> > makefile also build the info file in the build tree?
> 
> I'm not sure. The issue is that the info file may already be available
> in the source tree (this is always the case for tarballs), so that
> there could be some confusion. We're using
> 
> info_TEXINFOS = mpfr.texi
> 
> and the Makeinfo manual says:
> 
>It is worth noting that, contrary to what happens with the other
> formats, the generated ‘.info’ files are by default placed in ‘srcdir’
> rather than in the ‘builddir’.  This can be changed with the
> ‘info-in-builddir’ option.
> 
> So the question is whether we should use this option. Is it common
> among other software?

According to https://debbugs.gnu.org/cgi/bugreport.cgi?bug=11034#65
we must not use info-in-builddir if we distribute info files
(in tarballs). Since distributing them is recommended (as not
everyone has the necessary tools to rebuild them), we will not
be able to use info-in-builddir.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1046055: mpfr4: Fails to build source after successful build

[Vincent Lefevre]

On 2023-08-28 11:15:15 +0200, Matthias Klose wrote:
> > Apparently this is due to the fact that the upstream mpfr.info file
> > is rebuilt.
> 
> the package is built in a separate build dir. shouldn't the upstream
> makefile also build the info file in the build tree?

I'm not sure. The issue is that the info file may already be available
in the source tree (this is always the case for tarballs), so that
there could be some confusion. We're using

info_TEXINFOS = mpfr.texi

and the Makeinfo manual says:

   It is worth noting that, contrary to what happens with the other
formats, the generated ‘.info’ files are by default placed in ‘srcdir’
rather than in the ‘builddir’.  This can be changed with the
‘info-in-builddir’ option.

So the question is whether we should use this option. Is it common
among other software?

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

mpfr4_4.2.1-1_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 28 Aug 2023 11:05:20 +0200
Source: mpfr4
Architecture: source
Version: 4.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 1036606 1046055
Changes:
 mpfr4 (4.2.1-1) unstable; urgency=medium
 .
   * New upstream version. Closes: #1036606.
   * d/rules: Call dh_dwz.
   * d/rules: Clean doc/mpfr.info. Closes: #1046055.
Checksums-Sha1:
 963f01b7c0b5ad30fa78f2317dd2aa4a562d3d2d 1959 mpfr4_4.2.1-1.dsc
 31ffb4244cb469e2b4937cce1f50150300971dfb 1493608 mpfr4_4.2.1.orig.tar.xz
 127ddd425508a0e57e6ce35c8d8fdd4ccb480419 12556 mpfr4_4.2.1-1.debian.tar.xz
 7d07025cc63190003e82e1ab06f41fcbcbb249ec 6511 mpfr4_4.2.1-1_source.buildinfo
Checksums-Sha256:
 2fb0ea6c37591f03c7f3445fc6a298a10dbd9d7662ccb441f7da0e514d71986a 1959 
mpfr4_4.2.1-1.dsc
 277807353a6726978996945af13e52829e3abd7a9a5b7fb2793894e18f1fcbb2 1493608 
mpfr4_4.2.1.orig.tar.xz
 06c6c90efe3653d44527bcd6cfd66563d62409bbb348eb32f33b480e30ad9993 12556 
mpfr4_4.2.1-1.debian.tar.xz
 c98081fb1905b04ea8a4150ce7c5c765478dccd821c91ea88249a07573ad4a47 6511 
mpfr4_4.2.1-1_source.buildinfo
Files:
 e096db2c2a20ed0edcf40fea83f1cc11 1959 math optional mpfr4_4.2.1-1.dsc
 523c50c6318dde6f9dc523bc0244690a 1493608 math optional mpfr4_4.2.1.orig.tar.xz
 bfb00e02f86bc4f932ab3d40f4edf830 12556 math optional 
mpfr4_4.2.1-1.debian.tar.xz
 673ce5b531eb492b5454f3e68d1129ff 6511 math optional 
mpfr4_4.2.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmTsZ0AQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9YMeEADT1GGcT9N9CzvSf56i3HMmnaDQfyztnHr0
OrhrxDQOmlEbwH3r9UvuHa7V0+80xYBedqJ0AyFNTAfXpSHehLzBEUvC0BFrVFwW
z7HhX6rD7bFCg8Gp1tAzREUM7G9fkp62PFWVqNZesMbPVPK4mr6bht1L8DRZ9ZKk
QBMUCIa7Cwz+J3STcARjazbowdkkSlS7BLwEfHX+kiiv0S4Beb95TUn6TsNLnya1
aDsjaPhowp920u2PCiIYnU4+Nfg9BU+Nbm22JeHvGt8tVQdMR3l3QWEYMvfz5Am9
3moR2+PIUipva7RhWbOM/ADaNbiyntfGtNRm7x0LQnzTd2BpLBNJd7XONXJQiIHr
bNK8VkUIa8wej6uee+9dTSng7M8EYthVkIMYGHSytWWlI2rEj8Q4zP8khbs9joz4
FvpbSRM8kXvRs8c3stfdAJ7EfH8XTeOe0nhZ4A5HOObR5vjHf5SFBaioGR9FRbA7
/JwhDd8sNXbZNBNgL7e0T/HC1FI6WfRcjNlenndV7RA+5KLTmqAK+ggmt43OwkSf
x/6Yc1B24vPO7oBCplAilHV761ktlfb519YPQcEcX60S6B63NvGkkxMTMAKaDOxf
1Tkr7ECLLsaCcD1XJsB8vD37SWb1XAlQCBqzt2TcHReZeR+mUFcbNRENMkCkloBT
WbBpCrSFaw==
=a61K
-END PGP SIGNATURE-

Processing of mpfr4_4.2.1-1_source.changes

[Debian FTP Masters]

mpfr4_4.2.1-1_source.changes uploaded successfully to localhost
along with the files:
  mpfr4_4.2.1-1.dsc
  mpfr4_4.2.1.orig.tar.xz
  mpfr4_4.2.1-1.debian.tar.xz
  mpfr4_4.2.1-1_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#1046055: marked as done (mpfr4: Fails to build source after successful build)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2023 09:34:34 +
with message-id 
and subject line Bug#1046055: fixed in mpfr4 4.2.1-1
has caused the Debian Bug report #1046055,
regarding mpfr4: Fails to build source after successful build
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1046055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1046055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpfr4
Version: 4.2.0-1
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian...@lists.debian.org
Usertags: qa-doublebuild

Hi,

This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).

This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.

More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild

Relevant part of the build log:
> cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env 
> -us -uc -rfakeroot -S
> -
> 
> dpkg-buildpackage: info: source package mpfr4
> dpkg-buildpackage: info: source version 4.2.0-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Matthias Klose 
>  dpkg-source --before-build .
>  fakeroot debian/rules clean
> rm -f doc/texinfo.tex
> dh_autoreconf_clean
> rm -rf stamps
> dh_testdir
> dh_testroot
> rm -rf build
> dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building mpfr4 using existing ./mpfr4_4.2.0.orig.tar.xz
> dpkg-source: warning: ignoring deletion of file INSTALL, use 
> --include-removal to override
> dpkg-source: warning: ignoring deletion of file ltmain.sh, use 
> --include-removal to override
> dpkg-source: warning: ignoring deletion of file configure, use 
> --include-removal to override
> dpkg-source: warning: ignoring deletion of file doc/texinfo.tex, use 
> --include-removal to override
> dpkg-source: info: local changes detected, the modified files are:
>  mpfr4-4.2.0/doc/mpfr.info
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/mpfr4_4.2.0-1.diff.v1TRvW
> dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage 
> --sanitize-env -us -uc -rfakeroot -S' failed to run.


The full build log is available from:
http://qa-logs.debian.net/2023/08/13/mpfr4_4.2.0-1_unstable.log

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: mpfr4
Source-Version: 4.2.1-1
Done: Matthias Klose 

We believe that the bug you reported is fixed in the latest version of
mpfr4, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1046...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated mpfr4 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 28 Aug 2023 11:05:20 +0200
Source: mpfr4
Architecture: source
Version: 4.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 1036606 1046055
Changes:
 mpfr4 (4.2.1-1) unstable; urgency=medium
 .
   * New upstream version. Closes: #1036606.
   * d/rules: Call dh_dwz.
   * d/rules: Clean doc/mpfr.info. Closes: 

Bug#1036606: marked as done (libmpfr6: multiple bugs in GNU MPFR 4.2.0, patches available)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2023 09:34:34 +
with message-id 
and subject line Bug#1036606: fixed in mpfr4 4.2.1-1
has caused the Debian Bug report #1036606,
regarding libmpfr6: multiple bugs in GNU MPFR 4.2.0, patches available
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1036606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmpfr6
Version: 4.2.0-1
Severity: important
Tags: upstream

There are multiple bugs, more or less important, in GNU MPFR 4.2.0.
Patches are available at
  https://www.mpfr.org/mpfr-4.2.0/#bugs

In particular:
* For the mpfr_ui_pow_ui function, infinite loop in case of overflow.
* The mpfr_rec_sqrt function may yield a stack overflow due to many
  small allocations in the stack, based on alloca(). This occurs on
  cases that are very hard to round. In practice, to build such cases,
  the precision of the input needs to be large enough (e.g. around
  10 bits).
* MPFR can crash when a formatted output function is called with
  %.2147483648Rg in the format string (2147483648 = 2^31).

See attached files for simple testcases (but the patches provide
testcases for the testsuite).

-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-security'), (500, 
'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 
'testing'), (500, 'stable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libmpfr6 depends on:
ii  libc6 2.36-9
ii  libgmp10  2:6.2.1+dfsg1-1.1

libmpfr6 recommends no packages.

libmpfr6 suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
#include 
#include 
#include 

int main (void)
{
  mpfr_exp_t emax_max;
  mpfr_t x;

  emax_max = mpfr_get_emax_max ();

  if (mpfr_set_emax (emax_max))
{
  fprintf (stderr, "ui_pow_ui-overflow error: mpfr_set_emax failed\n");
  return 1;
}

  mpfr_init2 (x, 8);

  /* The purpose of this test is more to check that mpfr_ui_pow_ui
 terminates (without taking much memory) rather than checking
 the value of x. On 2023-02-13, the +Inf case was not handled
 in the Ziv iteration, yielding an infinite loop, affecting
 mpfr_log10 in particular. See
   commit 90de094f0d9c309daca707aa227470d810866616
  */
  mpfr_ui_pow_ui (x, 5, ULONG_MAX, MPFR_RNDN);
  if (emax_max <= ULONG_MAX  /* true with default _MPFR_EXP_FORMAT */
  && ! mpfr_inf_p (x))
{
  fprintf (stderr, "ui_pow_ui-overflow error");
  printf ("ui_pow_ui-overflow: expected +Inf, got ");
  mpfr_dump (x);
  return 1;
}

  mpfr_clear (x);

  return 0;
}
#include 
#include 

int main (void)
{
  mpfr_t x, y;
  int inex;

  mpfr_init2 (x, 123456);
  mpfr_init2 (y, 4);
  mpfr_set_ui (y, 9, MPFR_RNDN);
  mpfr_ui_div (x, 1, y, MPFR_RNDN);
  inex = mpfr_rec_sqrt (y, x, MPFR_RNDN);
  /* Let's also check the result, though this is not the real purpose
 of this test (a stack overflow just makes the program crash).
 1/9 = 0.111000111000111000111000111000111000...E-3 and since the
 precision 123456 is divisible by 6, x > 1/9. Thus 1/sqrt(x) < 3. */
  if (mpfr_nan_p (y) || mpfr_cmp_ui (y, 3) != 0 || inex <= 0)
{
  printf ("mpfr_rec_sqrt error: expected 3 with inex > 0, got ");
  mpfr_out_str (stdout, 10, 0, y, MPFR_RNDN);
  printf (" with inex=%d\n", inex);
  return 1;
}
  mpfr_clear (x);
  mpfr_clear (y);

  return 0;
}
#include 
#include 

int main (void)
{
  mpfr_t x;
  char buf1[3] = "xxx", buf2[3] = "xxx";
  int r;

  mpfr_init2 (x, 128);
  mpfr_set_ui (x, 1, MPFR_RNDN);

  r = mpfr_snprintf (NULL, 0, "%.2147483648Rg\n", x);
  if (r != 2 && r >= 0)
return 1;

  r = mpfr_snprintf (buf1, sizeof(buf1), "%.2147483648Rg\n", x);
  if (r != 2 && r >= 0)
return 2;
  if (r >= 0 && (buf1[0] != '1' || buf1[1] != '\n' || buf1[2] != 0))
return 3;

  r = mpfr_sprintf (buf2, "%.2147483648Rg\n", x);
  if (r != 2 && r >= 0)
return 4;
  if (r >= 0 && (buf2[0] != '1' || buf2[1] != '\n' 

Bug#950647: src:mpfr4, add lib64 for i386 x32 mipsel etc

[Matthias Klose]

closing this as won't fix.

Bug#950647: marked as done (src:mpfr4, add lib64 for i386 x32 mipsel etc)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2023 11:09:01 +0200
with message-id <2caac606-0f9b-013b-81b1-e1d0dfaac...@debian.org>
and subject line Re: src:mpfr4, add lib64 for i386 x32 mipsel etc
has caused the Debian Bug report #950647,
regarding src:mpfr4, add lib64 for i386 x32 mipsel etc
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
950647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mpfr4
Version: 4.0.2-1
Control: block -1 by 950645

Since binutils/gcc meet some problem due to 2GB/3GB memory limitation
on 32bit system.
Now one solution is to have host64-target32 toolchains if the arch
have compatible 64bit arch,
just like x86, mips, powerpc.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950527

-- 
YunQiang Su
--- End Message ---
--- Begin Message ---

closing this as won't fix.--- End Message ---

Bug#1040991: marked as done (gcc-13: consider stripping lto1 / cc1 / cc1plus)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2023 11:01:10 +0200
with message-id <23fb484f-5dcc-821f-6b1c-1b059506c...@debian.org>
and subject line binaries now stripped again
has caused the Debian Bug report #1040991,
regarding gcc-13: consider stripping lto1 / cc1 / cc1plus
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1040991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: gcc-13
Version: 13.1.0-8
Severity: minor


Dear Maintainer,

Like it was before in #783876 #894014 #1015185 gcc-13 package in contain 
unstripped debug
info.

--
.''`.  Mateusz Łukasik
: :' :  l0calh0st.pl
`. `'   Debian Member -mat...@linuxmint.pl
  `-GPG: D93B 0C12 C8D0 4D7A AFBC  FA27 CCD9 1D61 11A0 6851
--- End Message ---
--- Begin Message ---

binaries now stripped again--- End Message ---