Bug#838315: Removed package(s) from unstable

Version: 4.9.4-3+rm Dear submitter, as the package gnat-4.9 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/838315 The

Bug#838315: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: gnat-4.9 |4.9.3-3 | source, kfreebsd-i386 gnat-4.9 |4.9.4-3 | source, amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, mips, mips64el, mipsel, powerpc, ppc64el,

Bug#825621: marked as done (gnat-4.9: empty Build-Depends-Indep field)

Your message dated Tue, 20 Sep 2016 09:54:11 + with message-id and subject line Bug#838315: Removed package(s) from unstable has caused the Debian Bug report #825621, regarding gnat-4.9: empty Build-Depends-Indep field to be marked as done. This means

Bug#780031: marked as done ([Fixed in 5] result attribute fails in postcondition of generic functions)

Your message dated Tue, 20 Sep 2016 09:54:11 + with message-id and subject line Bug#838315: Removed package(s) from unstable has caused the Debian Bug report #780031, regarding [Fixed in 5] result attribute fails in postcondition of generic functions to

Bug#748297: marked as done (the libgnatprj and libgnatvsn patches should be upstreamed or dropped)

Your message dated Tue, 20 Sep 2016 09:54:11 + with message-id and subject line Bug#838315: Removed package(s) from unstable has caused the Debian Bug report #748297, regarding the libgnatprj and libgnatvsn patches should be upstreamed or dropped to be

Bug#830436: marked as done (gnat-4.9: FTBFS: b_gnatb.adb:86: undefined reference to `__gnat_runtime_finalize')

Your message dated Tue, 20 Sep 2016 09:54:11 + with message-id and subject line Bug#838315: Removed package(s) from unstable has caused the Debian Bug report #830436, regarding gnat-4.9: FTBFS: b_gnatb.adb:86: undefined reference to

Bug#833677: marked as done (gnat-4.9: last call to the put procedure incorrectly appends a newline character to the string)

Your message dated Tue, 20 Sep 2016 09:54:11 + with message-id and subject line Bug#838315: Removed package(s) from unstable has caused the Debian Bug report #833677, regarding gnat-4.9: last call to the put procedure incorrectly appends a newline

Bug#783877: marked as done ([Fixed in 5] Bug box on raise in Dynamic_Predicate)

Your message dated Tue, 20 Sep 2016 09:54:11 + with message-id and subject line Bug#838315: Removed package(s) from unstable has caused the Debian Bug report #783877, regarding [Fixed in 5] Bug box on raise in Dynamic_Predicate to be marked as done. This

Bug#748298: marked as done (please drop the sjlj support)

Your message dated Tue, 20 Sep 2016 09:54:11 + with message-id and subject line Bug#838315: Removed package(s) from unstable has caused the Debian Bug report #748298, regarding please drop the sjlj support to be marked as done. This means that you claim

Bug#812587: marked as done (gnat: Fail to reconize types with an unrejected static size attribute as compile time known size type.)

Your message dated Tue, 20 Sep 2016 09:54:11 + with message-id and subject line Bug#838315: Removed package(s) from unstable has caused the Debian Bug report #812587, regarding gnat: Fail to reconize types with an unrejected static size attribute as

Bug#818774: marked as done (gnat-4.9: non-standard gcc/g++ used for build (gcc-4.9))

Your message dated Tue, 20 Sep 2016 09:54:11 + with message-id and subject line Bug#838315: Removed package(s) from unstable has caused the Debian Bug report #818774, regarding gnat-4.9: non-standard gcc/g++ used for build (gcc-4.9) to be marked as done.

Bug#611248: marked as done ([armel] unexpected symbols added for shared library)

Your message dated Tue, 20 Sep 2016 09:54:11 + with message-id and subject line Bug#838315: Removed package(s) from unstable has caused the Debian Bug report #611248, regarding [armel] unexpected symbols added for shared library to be marked as done. This

Bug#569343: marked as done (OpenToken tests fail with AUnit dynamic library, but not with source)

Your message dated Tue, 20 Sep 2016 09:54:11 + with message-id and subject line Bug#838315: Removed package(s) from unstable has caused the Debian Bug report #569343, regarding OpenToken tests fail with AUnit dynamic library, but not with source to be

Bug#559447: marked as done (extends keyword in project files seems to be broken)

Your message dated Tue, 20 Sep 2016 09:54:11 + with message-id and subject line Bug#838315: Removed package(s) from unstable has caused the Debian Bug report #559447, regarding extends keyword in project files seems to be broken to be marked as done. This

Bug#251265: marked as done ([Fixed in 5] Bug box in Case_Statement_to_gnu, at ada/gcc-interface/trans.c:2198, on legal Ada 83 program)

Your message dated Tue, 20 Sep 2016 09:54:11 + with message-id and subject line Bug#838315: Removed package(s) from unstable has caused the Debian Bug report #251265, regarding [Fixed in 5] Bug box in Case_Statement_to_gnu, at

Bug#247564: marked as done ([Fixed in 5] Bug box on legal program in gnat_to_gnu_entity, at ada/gcc-interface/decl.c)

Your message dated Tue, 20 Sep 2016 09:54:11 + with message-id and subject line Bug#838315: Removed package(s) from unstable has caused the Debian Bug report #247564, regarding [Fixed in 5] Bug box on legal program in gnat_to_gnu_entity, at

Bug#746689: marked as done (libgnatvsn should have a proper configure.ac and Makefile.in)

Your message dated Tue, 20 Sep 2016 09:54:11 + with message-id and subject line Bug#838315: Removed package(s) from unstable has caused the Debian Bug report #746689, regarding libgnatvsn should have a proper configure.ac and Makefile.in to be marked as

Bug#182360: marked as done ([Fixed in 5.2] GNAT.OS_Lib.Close ignores return value)

Your message dated Tue, 20 Sep 2016 09:54:11 + with message-id and subject line Bug#838315: Removed package(s) from unstable has caused the Debian Bug report #182360, regarding [Fixed in 5.2] GNAT.OS_Lib.Close ignores return value to be marked as done.

Bug#810868: marked as done (threads: condition_variable or atomic causes _sometimes_ a deadlock)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #810868, regarding threads: condition_variable or atomic causes _sometimes_ a deadlock to be

Bug#814239: marked as done (gcc-4.9: debian/patches/ada-symbolic-tracebacks.diff use snprintf return value without check)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #814239, regarding gcc-4.9: debian/patches/ada-symbolic-tracebacks.diff use snprintf return value

Bug#799953: marked as done (4.9/5: incorrect double to integer conversion on i386)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #799953, regarding 4.9/5: incorrect double to integer conversion on i386 to be marked as done.

Bug#798029: marked as done (Impossible to keep gcc-4.7 after upgrade to Debian Jessie)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #798029, regarding Impossible to keep gcc-4.7 after upgrade to Debian Jessie to be marked as done.

Bug#786883: marked as done (gcc-4.9: --sysroot=... not properly respected - /usr/lib still stays in library search path)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #786883, regarding gcc-4.9: --sysroot=... not properly respected - /usr/lib still stays in

Bug#816776: marked as done (g++: internal compiler error: Segmentation fault when building qt-everywhere-opensource-src-4.8.7)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #816776, regarding g++: internal compiler error: Segmentation fault when building

Bug#785762: marked as done (gcc-4.9: Segfault on llvm build)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #785762, regarding gcc-4.9: Segfault on llvm build to be marked as done. This means that you

Bug#797426: marked as done (g++: internal compiler error: Getötet (program cc1plus))

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #797426, regarding g++: internal compiler error: Getötet (program cc1plus) to be marked as done.

Bug#823222: marked as done (gcc-4.9: reordering of signed int operations triggers overflow)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #823222, regarding gcc-4.9: reordering of signed int operations triggers overflow to be marked as

Bug#797151: marked as done (gcc-4.9: Spurious warnings about pointer to array -> const pointer to array conversion.)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #797151, regarding gcc-4.9: Spurious warnings about pointer to array -> const pointer to array

Bug#838316: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: cpp-4.9 |4.9.4-2 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x g++-4.9 |4.9.4-2 | amd64,

Bug#838316: Removed package(s) from unstable

Version: 4.9.4-2+rm Dear submitter, as the package gcc-4.9 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/838316 The

Bug#759870: marked as done (gcc-4.9: Compiles zsh endlessly with -fstack-protector-strong on s390x)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #759870, regarding gcc-4.9: Compiles zsh endlessly with -fstack-protector-strong on s390x to be

Bug#764732: marked as done (gcc-4.9: broken -O2 optimizations on armhf)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #764732, regarding gcc-4.9: broken -O2 optimizations on armhf to be marked as done. This means

Bug#772436: marked as done (aarch64 optimization bug)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #772436, regarding aarch64 optimization bug to be marked as done. This means that you claim that

Bug#755295: marked as done (GCC testsuite failures on the Hurd)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #755295, regarding GCC testsuite failures on the Hurd to be marked as done. This means that you

Bug#762640: marked as done (gfortran-4.9: generates buggy assembler at -O2 on armhf)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #762640, regarding gfortran-4.9: generates buggy assembler at -O2 on armhf to be marked as done.

Bug#762238: marked as done (gcc-4.9: guile-2.0 fails to build with offset problem)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #762238, regarding gcc-4.9: guile-2.0 fails to build with offset problem to be marked as done.

Bug#753134: marked as done (lto1: fatal error: LTO_tags out of range: Range is 0 to 368, value is 756)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #753134, regarding lto1: fatal error: LTO_tags out of range: Range is 0 to 368, value is 756 to

Bug#764280: marked as done (g++-4.9: g++-4.9 ignore "pragma GCC diagnostic ..." directives)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #764280, regarding g++-4.9: g++-4.9 ignore "pragma GCC diagnostic ..." directives to be marked as

Bug#762005: marked as done (gcc-4.9: prototype subroutine (non-static) != functional subroutine (static))

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #762005, regarding gcc-4.9: prototype subroutine (non-static) != functional subroutine (static)

Bug#748024: marked as done (gcc-4.9-plugin-dev: gcc plugins can not build)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #748024, regarding gcc-4.9-plugin-dev: gcc plugins can not build to be marked as done. This means

Bug#751812: marked as done (Incorrect fortify warning with -flto)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #751812, regarding Incorrect fortify warning with -flto to be marked as done. This means that you

Bug#727621: marked as done (armel: std::future appears to be broken?)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #727621, regarding armel: std::future appears to be broken? to be marked as done. This means that

Bug#734973: marked as done (libcilkrts for kfreebsd and the Hurd fails to build)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #734973, regarding libcilkrts for kfreebsd and the Hurd fails to build to be marked as done. This

Bug#450746: marked as done (gcc: Generates extnernal references for static variable.)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #450746, regarding gcc: Generates extnernal references for static variable. to be marked as done.

Bug#764195: marked as done (gcc-4.9: problems with precompiled headers on arm64)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #764195, regarding gcc-4.9: problems with precompiled headers on arm64 to be marked as done. This

Bug#768265: marked as done (gcc-4.9: Please support i386 compilation on amd64 through multiarch)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #768265, regarding gcc-4.9: Please support i386 compilation on amd64 through multiarch to be

Bug#766840: marked as done ([armhf] Illegal assembler code generated with -O2)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #766840, regarding [armhf] Illegal assembler code generated with -O2 to be marked as done. This

Bug#773065: marked as done (selecting target via dpkg-buildpackage --target-arch)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #773065, regarding selecting target via dpkg-buildpackage --target-arch to be marked as done.

Bug#774543: marked as done (gcc-4.9: add DEB_CROSS_NO_BIARCH support)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #774543, regarding gcc-4.9: add DEB_CROSS_NO_BIARCH support to be marked as done. This means that

Bug#774541: marked as done (gcc-4.9: remove override with_deps_on_target_arch_pkgs)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #774541, regarding gcc-4.9: remove override with_deps_on_target_arch_pkgs to be marked as done.

Bug#777169: marked as done (FTBFS on sparc64: symbol errors)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #777169, regarding FTBFS on sparc64: symbol errors to be marked as done. This means that you

Bug#781060: marked as done (g++-4.9: Broken optimization when move-constructing from virtual subclass)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #781060, regarding g++-4.9: Broken optimization when move-constructing from virtual subclass to

Bug#777275: marked as done (php5-cli: Odd compiled assembly causing mmap detection to sometimes fail)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #777275, regarding php5-cli: Odd compiled assembly causing mmap detection to sometimes fail to be

Bug#774548: marked as done (gcc-4.9: add with_deps_on_target_arch_pkgs back and rename packages)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #774548, regarding gcc-4.9: add with_deps_on_target_arch_pkgs back and rename packages to be

Bug#785249: marked as done (gcc-4.9: test suite errors when memory overcommitting is turned off)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #785249, regarding gcc-4.9: test suite errors when memory overcommitting is turned off to be

Bug#784544: marked as done (gcc-4.9: 'cc --version' fails to identify cc as GCC)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #784544, regarding gcc-4.9: 'cc --version' fails to identify cc as GCC to be marked as done. This

Bug#782391: marked as done (g++-4.9: false-positive -Warray-bounds apprently due to wrong integer-range inference)

Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #782391, regarding g++-4.9: false-positive -Warray-bounds apprently due to wrong integer-range

Bug#773065: closed by Debian FTP Masters <ftpmas...@ftp-master.debian.org> (Bug#838316: Removed package(s) from unstable)

Control: reopen -1 Control: reassign -1 src:gcc-6 On Tue, Sep 20, 2016 at 10:19:12PM +, Debian Bug Tracking System wrote: > Please allow selecting the target architecture using "dpkg-buildpackage > --target-arch" again. This ability was removed in 4.9.2-7 when #768167 > was fixed. > > I am

Processed: Re: Bug#773065 closed by Debian FTP Masters <ftpmas...@ftp-master.debian.org> (Bug#838316: Removed package(s) from unstable)

Processing control commands: > reopen -1 Bug #773065 {Done: Debian FTP Masters } [src:gcc-4.9] selecting target via dpkg-buildpackage --target-arch 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and