gcc-4.9_4.9.3-4_ppc64el.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 26 Aug 2015 14:52:53 +0200 Source: gcc-4.9 Binary: gcc-4.9-base libgcc-4.9-dev lib64gcc-4.9-dev lib32gcc-4.9-dev libn32gcc-4.9-dev libx32gcc-4.9-dev gcc-4.9 gcc-4.9-multilib gcc-4.9-plugin-dev gcc-4.9-hppa64 cpp-

Bug#796937: marked as done (gcc-4.9: Please stop building the common libraries on m68k, powerpcspe, sh4 and sparc64)

Your message dated Wed, 26 Aug 2015 16:20:17 + with message-id and subject line Bug#796937: fixed in gcc-4.9 4.9.3-4 has caused the Debian Bug report #796937, regarding gcc-4.9: Please stop building the common libraries on m68k, powerpcspe, sh4 and sparc64 to be marked as done. This means th

Processing of gcc-4.9_4.9.3-4_ppc64el.changes

gcc-4.9_4.9.3-4_ppc64el.changes uploaded successfully to localhost along with the files: gcc-4.9_4.9.3-4.dsc gcc-4.9_4.9.3-4.diff.gz cpp-4.9_4.9.3-4_ppc64el.deb g++-4.9_4.9.3-4_ppc64el.deb gcc-4.9-base_4.9.3-4_ppc64el.deb gcc-4.9-locales_4.9.3-4_all.deb gcc-4.9-plugin-dev_4.9.3-4_ppc6

[Bug fortran/42607] add information about how to compile a module

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42607 Gary Howell changed: What|Removed |Added CC||gwhowell at ncsu dot edu --- Comment #14 f

Re: Bug#790756: Packages are not [depending on libstdc++6 >= 5] after rebuild

On Tue, 25 Aug 2015 at 16:50:16 -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > And this is because the packages do not use any of the new symbols, so they > do not get the dependency on the last version. there is nothing packagers > can do about it. I wonder whether g++-5 should artificially