Bug#807885: libstdc++6-6-dbg: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/debug/libstdc++.a

Package: libstdc++6-6-dbg Version: 6-20151211-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because

Bug#807756: gnubg: fails to start. hangs using 100% of one cpu core

Matthias Klose writes: > On 14.12.2015 01:26, Russ Allbery wrote: >> Now reassigning to the correct package. See the earlier messages in >> the bug log for more information. The short version is that gnubg when >> built with any optimization at all exhibits a lot of weird startup >> behavior (s

Bug#807756: gnubg: fails to start. hangs using 100% of one cpu core

Control: severity -1 normal On 14.12.2015 01:26, Russ Allbery wrote: Control: reassign -1 gcc-5 Russ Allbery writes: Hrm. Okay, so the compiler is doing something weird, and this isn't a problem with libtasn1. Thanks for the additional information! I'm going to reassign this to gcc-5, and

Processed: Re: Bug#807756: gnubg: fails to start. hangs using 100% of one cpu core

Processing control commands: > severity -1 normal Bug #807756 [gcc-5] gnubg: fails to start. hangs using 100% of one cpu core Severity set to 'normal' from 'important' -- 807756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807756 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Re: Bug#807756: gnubg: fails to start. hangs using 100% of one cpu core

Control: reassign -1 gcc-5 Russ Allbery writes: > Hrm. Okay, so the compiler is doing something weird, and this isn't a > problem with libtasn1. Thanks for the additional information! I'm > going to reassign this to gcc-5, and might upload a package built > explicitly with gcc-4.9 as a workar

Processed: Re: Bug#807756: gnubg: fails to start. hangs using 100% of one cpu core

Processing control commands: > reassign -1 gcc-5 Bug #807756 [gcc-5.0] gnubg: fails to start. hangs using 100% of one cpu core Warning: Unknown package 'gcc-5.0' Bug reassigned from package 'gcc-5.0' to 'gcc-5'. Ignoring request to alter found versions of bug #807756 to the same values previously

gcc-6_6-20151213-1_ppc64el.changes ACCEPTED into experimental

-dev libgnatprj6 libgnatprj6-dbg gdc-6 gdc-6-multilib fixincludes gcc-6-source Architecture: source ppc64el all Version: 6-20151213-1 Distribution: experimental Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Description: cpp-6 - GNU C preprocessor fixincludes

Processing of gcc-6_6-20151213-1_ppc64el.changes

gcc-6_6-20151213-1_ppc64el.changes uploaded successfully to localhost along with the files: gcc-6_6-20151213-1.dsc gcc-6_6-20151213.orig.tar.gz gcc-6_6-20151213-1.diff.gz cpp-6_6-20151213-1_ppc64el.deb fixincludes_6-20151213-1_ppc64el.deb g++-6_6-20151213-1_ppc64el.deb gcc-6-base_6

gcc-defaults-ports_1.150_amd64.changes is NEW

binary:gccgo-hppa-linux-gnu is NEW. binary:gccgo-m68k-linux-gnu is NEW. binary:gccgo-sh4-linux-gnu is NEW. binary:gdc-sh4-linux-gnu is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP

gcc-4.8_4.8.5-3_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 13 Dec 2015 15:37:55 +0100 Source: gcc-4.8 Binary: gcc-4.8-base libgcc-4.8-dev lib64gcc-4.8-dev lib32gcc-4.8-dev libn32gcc-4.8-dev libx32gcc-4.8-dev gcc-4.8 gcc-4.8-multilib gcc-4.8-plugin-dev gcc-4.8-hppa64 cpp-

Processing of gcc-defaults-ports_1.150_amd64.changes

gcc-defaults-ports_1.150_amd64.changes uploaded successfully to localhost along with the files: gcc-defaults-ports_1.150.dsc gcc-defaults-ports_1.150.tar.gz cpp-alpha-linux-gnu_5.3.1-1_amd64.deb cpp-hppa-linux-gnu_5.3.1-1_amd64.deb cpp-m68k-linux-gnu_5.3.1-1_amd64.deb cpp-mips64-linux-g

Processing of gcc-4.8_4.8.5-3_amd64.changes

gcc-4.8_4.8.5-3_amd64.changes uploaded successfully to localhost along with the files: gcc-4.8_4.8.5-3.dsc gcc-4.8_4.8.5-3.diff.gz cpp-4.8_4.8.5-3_amd64.deb g++-4.8-multilib_4.8.5-3_amd64.deb g++-4.8_4.8.5-3_amd64.deb gcc-4.8-base_4.8.5-3_amd64.deb gcc-4.8-locales_4.8.5-3_all.deb gc

gcc-defaults_1.150_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 13 Dec 2015 16:14:05 +0100 Source: gcc-defaults Binary: cpp gcc gcc-multilib g++ g++-multilib gobjc gobjc-multilib gobjc++ gobjc++-multilib gfortran gfortran-multilib gccgo gccgo-multilib libgcj-common libgcj-bc

Bug#807276: marked as done (gcc-defaults: duplicated word in some package descriptions)

Your message dated Sun, 13 Dec 2015 16:55:02 + with message-id and subject line Bug#807276: fixed in gcc-defaults 1.150 has caused the Debian Bug report #807276, regarding gcc-defaults: duplicated word in some package descriptions to be marked as done. This means that you claim that the probl

Bug#807830: arm: -fstack-protector-strong adds dependency on ld-linux-aarch64.so.1 on arm64

Package: gcc-5 Version: 5.3.1-3 Severity: normal Hello, I'm not sure if gcc is the right package to report this problem for, but not knowing it better I picked gcc, please reassign if needed. In the buildlog of memtool on arm64[1] I found a message: dpkg-shlibdeps: warning: package coul

Processing of gcc-defaults_1.150_amd64.changes

gcc-defaults_1.150_amd64.changes uploaded successfully to localhost along with the files: gcc-defaults_1.150.dsc gcc-defaults_1.150.tar.gz cpp-aarch64-linux-gnu_5.3.1-1_amd64.deb cpp-arm-linux-gnueabi_5.3.1-1_amd64.deb cpp-arm-linux-gnueabihf_5.3.1-1_amd64.deb cpp-mips-linux-gnu_5.3.1-1