libffi_3.3~rc0-5_source.changes ACCEPTED into experimental

2018-05-03 Thread Debian FTP Masters


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 02 May 2018 17:27:56 +0200
Source: libffi
Binary: libffi-dev libffi7 libffi7-udeb
Architecture: source
Version: 3.3~rc0-5
Distribution: experimental
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Description:
 libffi-dev - Foreign Function Interface library (development files)
 libffi7- Foreign Function Interface library runtime
 libffi7-udeb - Foreign Function Interface library runtime (udeb)
Changes:
 libffi (3.3~rc0-5) experimental; urgency=medium
 .
   * Updates from the trunk 20180502.
Checksums-Sha1:
 0ab4f18cf789d59ff0efd7fbf559d868b64e886b 1963 libffi_3.3~rc0-5.dsc
 968593efdacd8b3513cc18b5b334d97a7c63f105 20992 libffi_3.3~rc0-5.debian.tar.xz
 3a8f35480788bb3f6486a7d66df34038cc9a96e4 6133 libffi_3.3~rc0-5_source.buildinfo
Checksums-Sha256:
 3ad4258eb6047a8149c83e7af688f68cb2a490974e0f04ba71d256f78e67e621 1963 
libffi_3.3~rc0-5.dsc
 e320412f0f3cf7c61795651d20ab2559c7c9453a913577757f44f9d050528847 20992 
libffi_3.3~rc0-5.debian.tar.xz
 cd0c1fa1400f78a8dc9b69e10ca117a78a9ee88002da7a8ec5137b9e5064e1ce 6133 
libffi_3.3~rc0-5_source.buildinfo
Files:
 4e6296b2ab0cfa3773f2f88551847bfa 1963 libs optional libffi_3.3~rc0-5.dsc
 c4fd4f0d952fcaf9816b776c37d40795 20992 libs optional 
libffi_3.3~rc0-5.debian.tar.xz
 4c044d475ab20159929db5dc570e2d87 6133 libs optional 
libffi_3.3~rc0-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlrp2doQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9f+YD/94yQmCToNMHhtPzprZAy7T3pKFr59rAVeT
e8B1HTN2DWGWB2I7vXNlglHF7utjIU4MWg0n5N1HwpaNr9XKXr8t0c5+b3TLgaPR
6EuXbyDvO7XMd3NK2IEyblKVhs9hI7Ve4VUXFEt54RwMR9Mz9WUE0GTJgs3O4qzM
ZSJyOVti0U++wFn4GmxBYOne7QWVM/14BT8Tm3+VPpwA8iM0yOIbKQZhEdvR/REy
aQTHxnLOrzfosyp/OQkZkSo+D35VgEXPm7OhMTW/NQ+nM08Mu2mvbVitiLhATOh5
lpSA+GGACyJH5u+VaWdZmAzcmebebjVrDfBjYMfml8kJ0v12O/6y+ohzmtjPFanI
nqub/Kzj9JOfrKmW9b0VlF6DP5ghmDUdhz6u4og89NLqpyoc5PAHPouBf7cpK0A5
u7PZn7fRTJ/RHM/+lJWx+EGSOBSDizqZGEOV8wbe1SlmW3OWbmwT+d1ED/8Ziilf
tD+yOxsjSxwlyKcXY12zhhS3qOx4yw4X07wLqtMnNQuvrzXfzuNqhtiigp2nL+Qc
SU6K03r9t4LGDyK6G6ptLuwJ6GfioURewqDxW7lCGje6oTZ0yMHX+J7VLN61f3aM
zYJFVltipaXC4yQqwi8HLSIxpjtNb92G9qDh9uww3no8pfr/eCPo/Jf8lPl+EjT5
LCr3XLQTAA==
=Ss/u
-END PGP SIGNATURE-


Thank you for your contribution to Debian.



Processing of libffi_3.3~rc0-5_source.changes

2018-05-03 Thread Debian FTP Masters
libffi_3.3~rc0-5_source.changes uploaded successfully to localhost
along with the files:
  libffi_3.3~rc0-5.dsc
  libffi_3.3~rc0-5.debian.tar.xz
  libffi_3.3~rc0-5_source.buildinfo

Greetings,

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



Bug#897416: mpfr4: FTBFS on kfreebsd-amd64

2018-05-03 Thread Svante Signell
On Thu, 2018-05-03 at 14:59 +0100, James Clarke wrote:
> On 3 May 2018, at 09:21, Svante Signell 
> wrote:
> > On Wed, 2018-05-02 at 12:51 +0100, James Clarke wrote:
> > > Control: reassign -1 gcc-7
> > > Control: retitle -1 gcc: Decimal float support is not enabled on
> > > kfreebsd-
> > > amd64
> > > 
> > > On 2 May 2018, at 10:38, Svante Signell  > > > wrote:
> > > > 
> > > > Source: mpfr4
> > > > Version: 4.0.1-1
> > > > Severity: important
> > > > Tags: patch
> > > > User: debian-...@lists.debian.org
> > > > Usertags: kfreebsd

> > I think it is unfortunate that you reassigned this bug to gcc-7.
> > That will not
> > solve the mpfr4 build on the buildds.
> > 
> > There are two ways to solve this problem:
> > 1)
> > - reassign this bug back to mpfr4, adding the
> > libfr6.symbols.kfreebsd-amd64 in
> > next version 4.0.1-2.
> 
> Well, if you wanted to do that, it should be by changing the
> (arch=...) restriction lists in the main libfr6.symbols rather than
> forking a copy for kfreebsd-amd64.

Do you mean changing
(arch=any-amd64 any-i386 powerpc ppc64 ppc64el s390x)mpfr_get_decimal64
@Base 4.0.0
to
(arch=any-amd64 !kfreebsd-amd64 any-i386 powerpc ppc64 ppc64el s390x)mp
fr_get_decimal64@Base 4.0.0
if that works. Or list all arch-any architectures except kfreebsd-
amd64. How to find the architecture list for any-amd64?

The result would still be the same: as soon as gcc-7-7.3.0-18 is built
the libfr6.symbols file has to be changed again. Wouldn't it be better
to just remove the libfr6.symbols.kfreebsd-amd64 file for next version
of mpfr4 4.0.1-2?

> > - clone this bug to gcc-7, adding a patch to dfp.m4 so it can be
> > integrated in
> > next release of gcc-7: 7.3.0-18?
> 
> Personally I'd just get gcc patched and give back mpfr4.

How would you be able to build gcc-7 on the buildds with the current
mpfr4-4.0.1-1? It does not build as is on kfreebsd-amd64.



gcc-8-cross-ports_9_source.changes ACCEPTED into unstable

2018-05-03 Thread Debian FTP Masters


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 03 May 2018 15:53:04 +0200
Source: gcc-8-cross-ports
Binary: gcc-8-cross-base-ports gcc-8-alpha-linux-gnu-base libgcc1-alpha-cross 
libgcc-8-dev-alpha-cross gcc-8-alpha-linux-gnu gcc-8-plugin-dev-alpha-linux-gnu 
cpp-8-alpha-linux-gnu g++-8-alpha-linux-gnu libgomp1-alpha-cross 
libitm1-alpha-cross libatomic1-alpha-cross gobjc++-8-alpha-linux-gnu 
gobjc-8-alpha-linux-gnu libobjc4-alpha-cross libobjc-8-dev-alpha-cross 
gfortran-8-alpha-linux-gnu libgfortran5-alpha-cross 
libgfortran-8-dev-alpha-cross gccgo-8-alpha-linux-gnu libgo13-alpha-cross 
libstdc++6-alpha-cross libstdc++-8-dev-alpha-cross libstdc++-8-pic-alpha-cross 
gdc-8-alpha-linux-gnu gnat-8-alpha-linux-gnu gnat-8-sjlj-alpha-linux-gnu 
libgnat-8-alpha-cross gcc-8-hppa-linux-gnu-base libgcc-8-dev-hppa-cross 
libgcc4-hppa-cross gcc-8-hppa-linux-gnu gcc-8-plugin-dev-hppa-linux-gnu 
cpp-8-hppa-linux-gnu g++-8-hppa-linux-gnu libgomp1-hppa-cross 
libatomic1-hppa-cross gobjc++-8-hppa-linux-gnu gobjc-8-hppa-linux-gnu 
libobjc4-hppa-cross libobjc-8-dev-hppa-cross gfortran-8-hppa-linux-gnu
 libgfortran5-hppa-cross libgfortran-8-dev-hppa-cross libstdc++6-hppa-cross 
libstdc++-8-dev-hppa-cross libstdc++-8-pic-hppa-cross gdc-8-hppa-linux-gnu 
gnat-8-hppa-linux-gnu gnat-8-sjlj-hppa-linux-gnu libgnat-8-hppa-cross 
gcc-8-m68k-linux-gnu-base libgcc-8-dev-m68k-cross libgcc2-m68k-cross 
gcc-8-m68k-linux-gnu gcc-8-plugin-dev-m68k-linux-gnu cpp-8-m68k-linux-gnu 
g++-8-m68k-linux-gnu libgomp1-m68k-cross libatomic1-m68k-cross 
gobjc++-8-m68k-linux-gnu gobjc-8-m68k-linux-gnu libobjc4-m68k-cross 
libobjc-8-dev-m68k-cross gfortran-8-m68k-linux-gnu libgfortran5-m68k-cross 
libgfortran-8-dev-m68k-cross libstdc++6-m68k-cross libstdc++-8-dev-m68k-cross 
libstdc++-8-pic-m68k-cross gdc-8-m68k-linux-gnu gnat-8-m68k-linux-gnu 
gnat-8-sjlj-m68k-linux-gnu libgnat-8-m68k-cross 
gcc-8-mips64-linux-gnuabi64-base libgcc1-mips64-cross libgcc-8-dev-mips64-cross 
lib32gcc1-mips64-cross lib32gcc-8-dev-mips64-cross libn32gcc1-mips64-cross 
libn32gcc-8-dev-mips64-cross gcc-8-mips64-linux-gnuabi64
 gcc-8-multilib-mips64-linux-gnuabi64 gcc-8-plugin-dev-mips64-linux-gnuabi64 
cpp-8-mips64-linux-gnuabi64 g++-8-mips64-linux-gnuabi64 
g++-8-multilib-mips64-linux-gnuabi64 libgomp1-mips64-cross 
lib32gomp1-mips64-cross libn32gomp1-mips64-cross libatomic1-mips64-cross 
lib32atomic1-mips64-cross libn32atomic1-mips64-cross 
gobjc++-8-mips64-linux-gnuabi64 gobjc++-8-multilib-mips64-linux-gnuabi64 
gobjc-8-mips64-linux-gnuabi64 gobjc-8-multilib-mips64-linux-gnuabi64 
libobjc4-mips64-cross libobjc-8-dev-mips64-cross lib32objc4-mips64-cross 
lib32objc-8-dev-mips64-cross libn32objc4-mips64-cross 
libn32objc-8-dev-mips64-cross gfortran-8-mips64-linux-gnuabi64 
gfortran-8-multilib-mips64-linux-gnuabi64 libgfortran5-mips64-cross 
libgfortran-8-dev-mips64-cross lib32gfortran5-mips64-cross 
lib32gfortran-8-dev-mips64-cross libn32gfortran5-mips64-cross 
libn32gfortran-8-dev-mips64-cross gccgo-8-mips64-linux-gnuabi64 
gccgo-8-multilib-mips64-linux-gnuabi64 libgo13-mips64-cross
 lib32go13-mips64-cross libn32go13-mips64-cross libstdc++6-mips64-cross 
lib32stdc++6-mips64-cross libn32stdc++6-mips64-cross 
libstdc++-8-dev-mips64-cross libstdc++-8-pic-mips64-cross 
lib32stdc++-8-dev-mips64-cross libn32stdc++-8-dev-mips64-cross 
gdc-8-mips64-linux-gnuabi64 gdc-8-multilib-mips64-linux-gnuabi64 
gnat-8-mips64-linux-gnuabi64 gnat-8-sjlj-mips64-linux-gnuabi64 
libgnat-8-mips64-cross gcc-8-powerpc-linux-gnuspe-base libgcc1-powerpcspe-cross 
libgcc-8-dev-powerpcspe-cross gcc-8-powerpc-linux-gnuspe 
gcc-8-plugin-dev-powerpc-linux-gnuspe cpp-8-powerpc-linux-gnuspe 
g++-8-powerpc-linux-gnuspe libgomp1-powerpcspe-cross 
libatomic1-powerpcspe-cross gobjc++-8-powerpc-linux-gnuspe 
gobjc-8-powerpc-linux-gnuspe libobjc4-powerpcspe-cross 
libobjc-8-dev-powerpcspe-cross gfortran-8-powerpc-linux-gnuspe 
libgfortran5-powerpcspe-cross libgfortran-8-dev-powerpcspe-cross 
gccgo-8-powerpc-linux-gnuspe libgo13-powerpcspe-cross 
libstdc++6-powerpcspe-cross
 libstdc++-8-dev-powerpcspe-cross libstdc++-8-pic-powerpcspe-cross 
gdc-8-powerpc-linux-gnuspe gnat-8-powerpc-linux-gnuspe 
gnat-8-sjlj-powerpc-linux-gnuspe libgnat-8-powerpcspe-cross 
gcc-8-powerpc64-linux-gnu-base libgcc1-ppc64-cross libgcc-8-dev-ppc64-cross 
lib32gcc1-ppc64-cross lib32gcc-8-dev-ppc64-cross gcc-8-powerpc64-linux-gnu 
gcc-8-multilib-powerpc64-linux-gnu gcc-8-plugin-dev-powerpc64-linux-gnu 
cpp-8-powerpc64-linux-gnu g++-8-powerpc64-linux-gnu 
g++-8-multilib-powerpc64-linux-gnu libgomp1-ppc64-cross lib32gomp1-ppc64-cross 
libitm1-ppc64-cross lib32itm1-ppc64-cross libatomic1-ppc64-cross 
lib32atomic1-ppc64-cross libasan5-ppc64-cross lib32asan5-ppc64-cross 
libtsan0-ppc64-cross liblsan0-ppc64-cross lib32lsan0-ppc64-cross 
libubsan1-ppc64-cross lib32ubsan1-ppc64-cross gobjc++-8-powerpc64-linux-gnu 
gobjc++-8-multilib-powerpc64-linux-gnu gobjc-8-powerpc64-linux-gnu 

gcc-8-cross_12_source.changes ACCEPTED into unstable

2018-05-03 Thread Debian FTP Masters


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 03 May 2018 15:46:13 +0200
Source: gcc-8-cross
Binary: gcc-8-cross-base gcc-8-x86-64-linux-gnu-base libgcc1-amd64-cross 
libgcc-8-dev-amd64-cross lib32gcc1-amd64-cross lib32gcc-8-dev-amd64-cross 
libx32gcc1-amd64-cross libx32gcc-8-dev-amd64-cross gcc-8-x86-64-linux-gnu 
gcc-8-multilib-x86-64-linux-gnu gcc-8-plugin-dev-x86-64-linux-gnu 
cpp-8-x86-64-linux-gnu g++-8-x86-64-linux-gnu g++-8-multilib-x86-64-linux-gnu 
libgomp1-amd64-cross lib32gomp1-amd64-cross libx32gomp1-amd64-cross 
libitm1-amd64-cross lib32itm1-amd64-cross libx32itm1-amd64-cross 
libatomic1-amd64-cross lib32atomic1-amd64-cross libx32atomic1-amd64-cross 
libasan5-amd64-cross lib32asan5-amd64-cross libx32asan5-amd64-cross 
libtsan0-amd64-cross liblsan0-amd64-cross lib32lsan0-amd64-cross 
libx32lsan0-amd64-cross libubsan1-amd64-cross lib32ubsan1-amd64-cross 
libx32ubsan1-amd64-cross libquadmath0-amd64-cross lib32quadmath0-amd64-cross 
libx32quadmath0-amd64-cross gobjc++-8-x86-64-linux-gnu 
gobjc++-8-multilib-x86-64-linux-gnu gobjc-8-x86-64-linux-gnu
 gobjc-8-multilib-x86-64-linux-gnu libobjc4-amd64-cross 
libobjc-8-dev-amd64-cross lib32objc4-amd64-cross lib32objc-8-dev-amd64-cross 
libx32objc4-amd64-cross libx32objc-8-dev-amd64-cross 
gfortran-8-x86-64-linux-gnu gfortran-8-multilib-x86-64-linux-gnu 
libgfortran5-amd64-cross libgfortran-8-dev-amd64-cross 
lib32gfortran5-amd64-cross lib32gfortran-8-dev-amd64-cross 
libx32gfortran5-amd64-cross libx32gfortran-8-dev-amd64-cross 
gccgo-8-x86-64-linux-gnu gccgo-8-multilib-x86-64-linux-gnu libgo13-amd64-cross 
lib32go13-amd64-cross libx32go13-amd64-cross libstdc++6-amd64-cross 
lib32stdc++6-amd64-cross libx32stdc++6-amd64-cross libstdc++-8-dev-amd64-cross 
libstdc++-8-pic-amd64-cross lib32stdc++-8-dev-amd64-cross 
libx32stdc++-8-dev-amd64-cross gdc-8-x86-64-linux-gnu 
gdc-8-multilib-x86-64-linux-gnu libgphobos-8-dev-amd64-cross 
libgphobos76-amd64-cross lib32gphobos-8-dev-amd64-cross 
lib32gphobos76-amd64-cross libx32gphobos-8-dev-amd64-cross 
libx32gphobos76-amd64-cross
 gnat-8-x86-64-linux-gnu gnat-8-sjlj-x86-64-linux-gnu libgnat-8-amd64-cross 
gccbrig-8-x86-64-linux-gnu libhsail-rt-8-dev-amd64-cross 
libhsail-rt0-amd64-cross libmpx2-amd64-cross lib32mpx2-amd64-cross 
gcc-8-s390x-linux-gnu-base libgcc1-s390x-cross libgcc-8-dev-s390x-cross 
lib32gcc1-s390x-cross lib32gcc-8-dev-s390x-cross gcc-8-s390x-linux-gnu 
gcc-8-multilib-s390x-linux-gnu gcc-8-plugin-dev-s390x-linux-gnu 
cpp-8-s390x-linux-gnu g++-8-s390x-linux-gnu g++-8-multilib-s390x-linux-gnu 
libgomp1-s390x-cross lib32gomp1-s390x-cross libitm1-s390x-cross 
lib32itm1-s390x-cross libatomic1-s390x-cross lib32atomic1-s390x-cross 
libasan5-s390x-cross lib32asan5-s390x-cross libubsan1-s390x-cross 
lib32ubsan1-s390x-cross gobjc++-8-s390x-linux-gnu 
gobjc++-8-multilib-s390x-linux-gnu gobjc-8-s390x-linux-gnu 
gobjc-8-multilib-s390x-linux-gnu libobjc4-s390x-cross libobjc-8-dev-s390x-cross 
lib32objc4-s390x-cross lib32objc-8-dev-s390x-cross gfortran-8-s390x-linux-gnu
 gfortran-8-multilib-s390x-linux-gnu libgfortran5-s390x-cross 
libgfortran-8-dev-s390x-cross lib32gfortran5-s390x-cross 
lib32gfortran-8-dev-s390x-cross gccgo-8-s390x-linux-gnu 
gccgo-8-multilib-s390x-linux-gnu libgo13-s390x-cross lib32go13-s390x-cross 
libstdc++6-s390x-cross lib32stdc++6-s390x-cross libstdc++-8-dev-s390x-cross 
libstdc++-8-pic-s390x-cross lib32stdc++-8-dev-s390x-cross gdc-8-s390x-linux-gnu 
gdc-8-multilib-s390x-linux-gnu gnat-8-s390x-linux-gnu 
gnat-8-sjlj-s390x-linux-gnu libgnat-8-s390x-cross 
gcc-8-powerpc64le-linux-gnu-base libgcc1-ppc64el-cross 
libgcc-8-dev-ppc64el-cross gcc-8-powerpc64le-linux-gnu 
gcc-8-plugin-dev-powerpc64le-linux-gnu cpp-8-powerpc64le-linux-gnu 
g++-8-powerpc64le-linux-gnu libgomp1-ppc64el-cross libitm1-ppc64el-cross 
libatomic1-ppc64el-cross libasan5-ppc64el-cross libtsan0-ppc64el-cross 
liblsan0-ppc64el-cross libubsan1-ppc64el-cross libquadmath0-ppc64el-cross 
gobjc++-8-powerpc64le-linux-gnu gobjc-8-powerpc64le-linux-gnu
 libobjc4-ppc64el-cross libobjc-8-dev-ppc64el-cross 
gfortran-8-powerpc64le-linux-gnu libgfortran5-ppc64el-cross 
libgfortran-8-dev-ppc64el-cross gccgo-8-powerpc64le-linux-gnu 
libgo13-ppc64el-cross libstdc++6-ppc64el-cross libstdc++-8-dev-ppc64el-cross 
libstdc++-8-pic-ppc64el-cross gdc-8-powerpc64le-linux-gnu 
gnat-8-powerpc64le-linux-gnu gnat-8-sjlj-powerpc64le-linux-gnu 
libgnat-8-ppc64el-cross gcc-8-aarch64-linux-gnu-base libgcc1-arm64-cross 
libgcc-8-dev-arm64-cross gcc-8-aarch64-linux-gnu 
gcc-8-plugin-dev-aarch64-linux-gnu cpp-8-aarch64-linux-gnu 
g++-8-aarch64-linux-gnu libgomp1-arm64-cross libitm1-arm64-cross 
libatomic1-arm64-cross libasan5-arm64-cross libtsan0-arm64-cross 
liblsan0-arm64-cross libubsan1-arm64-cross gobjc++-8-aarch64-linux-gnu 
gobjc-8-aarch64-linux-gnu libobjc4-arm64-cross libobjc-8-dev-arm64-cross 
gfortran-8-aarch64-linux-gnu libgfortran5-arm64-cross 
libgfortran-8-dev-arm64-cross gccgo-8-aarch64-linux-gnu 

Bug#897416: mpfr4: FTBFS on kfreebsd-amd64

2018-05-03 Thread James Clarke
On 3 May 2018, at 09:21, Svante Signell  wrote:
> On Wed, 2018-05-02 at 12:51 +0100, James Clarke wrote:
>> Control: reassign -1 gcc-7
>> Control: retitle -1 gcc: Decimal float support is not enabled on kfreebsd-
>> amd64
>> 
>> On 2 May 2018, at 10:38, Svante Signell  wrote:
>>> 
>>> Source: mpfr4
>>> Version: 4.0.1-1
>>> Severity: important
>>> Tags: patch
>>> User: debian-...@lists.debian.org
>>> Usertags: kfreebsd
>>> 
>>> Hi,
>>> 
>>> mpfr4 FTBFS on kFreebsd-amd64 due to mismatches in the
>>> debian/libmpfr6.symbols
>>> file. Attached is a file with the symbols generated from the build:
>>> libmpfr6.symbols.kfreebsd-amd64.
>>> 
>>> Thanks!
>> 
>> You're right that the symbols file is currently wrong, but IMO gcc should 
>> have
>> decimal float support enabled for kfreebsd-amd64. It's enabled for
>> kfreebsd-i386 by virtue of the fact that i?86*-*-gnu* (for Hurd) matches
>> kfreebsd-i386's tuple, but there's no corresponding x86_64*-*-gnu* for a
>> future
>> 64-bit Hurd, and thus kfreebsd-amd64's tuple is not matched[0].
>> 
>> James
>> 
>> [0] https://github.com/gcc-mirror/gcc/blob/trunk/config/dfp.m4#L23-L26
> 
> Hi James,
> 
> I think it is unfortunate that you reassigned this bug to gcc-7. That will not
> solve the mpfr4 build on the buildds.
> 
> There are two ways to solve this problem:
> 1)
> - reassign this bug back to mpfr4, adding the libfr6.symbols.kfreebsd-amd64 in
> next version 4.0.1-2.

Well, if you wanted to do that, it should be by changing the (arch=...)
restriction lists in the main libfr6.symbols rather than forking a copy for
kfreebsd-amd64.

> - clone this bug to gcc-7, adding a patch to dfp.m4 so it can be integrated in
> next release of gcc-7: 7.3.0-18?

Personally I'd just get gcc patched and give back mpfr4.

> 2) (not preferred)
> - Build an NMUed version of mpfr4, 4.0.1-1.1, and install it at debian-ports. 

Indeed, unreleased uploads are best avoided when possible.

> For GNU/Hurd the entry in sources.list is
> deb http://ftp.ports.debian.org/debian-ports unreleased main
> 
> What about creating
> http://ftp.ports.debian.org/debian-ports/pool-kfreebsd-{amd64,i386} and 
> populate
> the mpfr4 packages there at pool-kfreebsd-amd64/m/. Additionally the buildds
> need to use these packages. Unfortunately I don't know how to do that.

We could, and may well eventually need an unreleased suite, but not now.
Getting the buildds to see the suite would be simple; wanna-build would need a
copy of the hurd code to tell it that unreleased exists, and our buildd setup
scripts would need tweaking to add it to apt's sources in the chroots.

> Then when gcc-7-7.3.0-18 is released, an updated version of mpfr4 is hopefully
> available (if not, what to do, how to get back to using the old version?)

In such a situation, the updated version of mpfr4 in unstable would be picked
by `apt upgrade` as unstable and unreleased get the same priority by default,
just like how you automatically get security updates from stretch/updates for
packages installed from the stretch archive on ftp-master.

James



Processing of gcc-8-cross-ports_9_source.changes

2018-05-03 Thread Debian FTP Masters
gcc-8-cross-ports_9_source.changes uploaded successfully to localhost
along with the files:
  gcc-8-cross-ports_9.dsc
  gcc-8-cross-ports_9.tar.xz
  gcc-8-cross-ports_9_source.buildinfo

Greetings,

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



Processing of gcc-8-cross_12_source.changes

2018-05-03 Thread Debian FTP Masters
gcc-8-cross_12_source.changes uploaded successfully to localhost
along with the files:
  gcc-8-cross_12.dsc
  gcc-8-cross_12.tar.xz
  gcc-8-cross_12_source.buildinfo

Greetings,

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



Re: filing bug reports for GCC 8 build failures

2018-05-03 Thread Alastair McKinstry


On 03/05/2018 09:51, Matthias Klose wrote:
> On 03.05.2018 09:03, Alastair McKinstry wrote:
>> On 03/05/2018 08:43, Matthias Klose wrote:
>>
>>> On 03.05.2018 07:29, Alastair McKinstry wrote:
 Hi,

 FTBFS bugs haveveen filed for packages that fail under gcc8.
>>> I didn't file any, and I didn't see any being filed. Which ones do you mean?
>> They were filed by Lucas Nussbaum,  e.g. #897518, #897507,
>> these use grib_api.mod from libeccodes-dev.
>> These fail because they need eccodes-dev to be built with gfortran8.
>>
>> Others will use netcdf.mod , etc.
> I can't see any gfortran-8 involvement for these issues.

My error, sorry (but we still need to plan the gfortran-8 transition).

What happened here is that I moved the .mod file in libeccodes-dev to
/usr/include/$ARCH, to make the package multi-arch capable. While gcc
looks there for header files, gfortran does _not_, which is inconsistent
and a challenge.

Is this deliberate, or will a patch to multiarch-enable gfortran be
accepted ?

-- 
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered. 




Bug#896057: gcc-7: doesn't look for "as" in dir specified by -B

2018-05-03 Thread Bob McChesney

On Fri, 20 Apr 2018 00:20:33 +0200 Jakub Wilk  wrote:
> * Helmut Grohne , 2018-04-19, 06:36:
> >>perhaphs gcc-7 should ship an appropriate symlink in
> >>/usr/lib/gcc//7/, instead of hardcoding path to "as" at
> >>configure time?
> --
> Jakub Wilk

Please could assist with what you believe the best workaround is to get 
this working again? I've tried the latest build (7.3.0-17) and it's 
still not working. Adding a symlink didn't seem to help.


Thanks,
Bob McChesney



Bug#897416: mpfr4: FTBFS on kfreebsd-amd64

2018-05-03 Thread Svante Signell
On Wed, 2018-05-02 at 12:51 +0100, James Clarke wrote:
> Control: reassign -1 gcc-7
> Control: retitle -1 gcc: Decimal float support is not enabled on kfreebsd-
> amd64
> 
> On 2 May 2018, at 10:38, Svante Signell  wrote:
> > 
> > Source: mpfr4
> > Version: 4.0.1-1
> > Severity: important
> > Tags: patch
> > User: debian-...@lists.debian.org
> > Usertags: kfreebsd
> > 
> > Hi,
> > 
> > mpfr4 FTBFS on kFreebsd-amd64 due to mismatches in the
> > debian/libmpfr6.symbols
> > file. Attached is a file with the symbols generated from the build:
> > libmpfr6.symbols.kfreebsd-amd64.
> > 
> > Thanks!
> 
> You're right that the symbols file is currently wrong, but IMO gcc should have
> decimal float support enabled for kfreebsd-amd64. It's enabled for
> kfreebsd-i386 by virtue of the fact that i?86*-*-gnu* (for Hurd) matches
> kfreebsd-i386's tuple, but there's no corresponding x86_64*-*-gnu* for a
> future
> 64-bit Hurd, and thus kfreebsd-amd64's tuple is not matched[0].
> 
> James
> 
> [0] https://github.com/gcc-mirror/gcc/blob/trunk/config/dfp.m4#L23-L26

Hi James,

I think it is unfortunate that you reassigned this bug to gcc-7. That will not
solve the mpfr4 build on the buildds.

There are two ways to solve this problem:
1)
- reassign this bug back to mpfr4, adding the libfr6.symbols.kfreebsd-amd64 in
next version 4.0.1-2.
- clone this bug to gcc-7, adding a patch to dfp.m4 so it can be integrated in
next release of gcc-7: 7.3.0-18?

2) (not preferred)
- Build an NMUed version of mpfr4, 4.0.1-1.1, and install it at debian-ports. 

For GNU/Hurd the entry in sources.list is
deb http://ftp.ports.debian.org/debian-ports unreleased main

What about creating
http://ftp.ports.debian.org/debian-ports/pool-kfreebsd-{amd64,i386} and populate
 the mpfr4 packages there at pool-kfreebsd-amd64/m/. Additionally the buildds
need to use these packages. Unfortunately I don't know how to do that.

Then when gcc-7-7.3.0-18 is released, an updated version of mpfr4 is hopefully
available (if not, what to do, how to get back to using the old version?)



Re: filing bug reports for GCC 8 build failures

2018-05-03 Thread Matthias Klose
On 03.05.2018 09:03, Alastair McKinstry wrote:
> On 03/05/2018 08:43, Matthias Klose wrote:
> 
>> On 03.05.2018 07:29, Alastair McKinstry wrote:
>>> Hi,
>>>
>>> FTBFS bugs haveveen filed for packages that fail under gcc8.
>> I didn't file any, and I didn't see any being filed. Which ones do you mean?
> They were filed by Lucas Nussbaum,  e.g. #897518, #897507,
> these use grib_api.mod from libeccodes-dev.
> These fail because they need eccodes-dev to be built with gfortran8.
> 
> Others will use netcdf.mod , etc.

I can't see any gfortran-8 involvement for these issues.



Re: filing bug reports for GCC 8 build failures

2018-05-03 Thread Alastair McKinstry
On 03/05/2018 08:43, Matthias Klose wrote:

> On 03.05.2018 07:29, Alastair McKinstry wrote:
>> Hi,
>>
>> FTBFS bugs haveveen filed for packages that fail under gcc8.
> I didn't file any, and I didn't see any being filed. Which ones do you mean?
They were filed by Lucas Nussbaum,  e.g. #897518, #897507,
these use grib_api.mod from libeccodes-dev.
These fail because they need eccodes-dev to be built with gfortran8.

Others will use netcdf.mod , etc.
   

-- 
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered. 



Re: filing bug reports for GCC 8 build failures

2018-05-03 Thread Matthias Klose
On 03.05.2018 07:29, Alastair McKinstry wrote:
> Hi,
> 
> FTBFS bugs haveveen filed for packages that fail under gcc8.

I didn't file any, and I didn't see any being filed. Which ones do you mean?