gcc-5_5-20150314-1_ppc64el.changes ACCEPTED into experimental, experimental

libstdc++-5-dev libstdc++-5-pic libstdc++6-5-dbg lib32stdc++-5-dev lib32stdc++6-5-dbg lib64stdc++-5-dev lib64stdc++6-5-dbg libn32stdc++-5-dev libn32stdc++6-5-dbg libx32stdc++-5-dev libx32stdc++6-5-dbg libstdc++-5-doc fixincludes gcc-5-source Architecture: source all ppc64el Version: 5-20150314

Bug#780468: marked as done (fails to build cross compiler for m68k: error during patch application)

Your message dated Sat, 14 Mar 2015 23:00:26 + with message-id and subject line Bug#780468: fixed in gcc-5 5-20150314-1 has caused the Debian Bug report #780468, regarding fails to build cross compiler for m68k: error during patch application to be marked as done. This means that you claim

Bug#778163: marked as done (vim: ftbfs with GCC-5)

Your message dated Sat, 14 Mar 2015 23:00:26 + with message-id and subject line Bug#778163: fixed in gcc-5 5-20150314-1 has caused the Debian Bug report #778163, regarding vim: ftbfs with GCC-5 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#780271: marked as done (gcc-5: fix mips64el build)

Your message dated Sat, 14 Mar 2015 23:00:26 + with message-id and subject line Bug#780271: fixed in gcc-5 5-20150314-1 has caused the Debian Bug report #780271, regarding gcc-5: fix mips64el build to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#776402: marked as done (gcc-5 dropped a mips* chunk in the config-ml patch)

Your message dated Sat, 14 Mar 2015 23:00:25 + with message-id and subject line Bug#776402: fixed in gcc-5 5-20150314-1 has caused the Debian Bug report #776402, regarding gcc-5 dropped a mips* chunk in the config-ml patch to be marked as done. This means that you claim that the problem has

Bug#778073: marked as done (ppl: ftbfs with GCC-5)

Your message dated Sat, 14 Mar 2015 23:00:26 + with message-id and subject line Bug#778073: fixed in gcc-5 5-20150314-1 has caused the Debian Bug report #778073, regarding ppl: ftbfs with GCC-5 to be marked as done. This means that you claim that the problem has been dealt with. If this is

gcc-5_5-20150314-1_ppc64el.changes is NEW

binary:lib32mpx0 is NEW. binary:lib32mpx0-dbg is NEW. binary:lib64mpx0 is NEW. binary:lib64mpx0-dbg is NEW. binary:libmpx0 is NEW. binary:libmpx0-dbg 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 h

Processing of gcc-5_5-20150314-1_ppc64el.changes

gcc-5_5-20150314-1_ppc64el.changes uploaded successfully to localhost along with the files: gcc-5_5-20150314-1.dsc gcc-5_5-20150314.orig.tar.gz gcc-5_5-20150314-1.diff.gz gcc-5-source_5-20150314-1_all.deb gcj-5-jre-lib_5-20150314-1_all.deb gcj-5-source_5-20150314-1_all.deb libgcj

Bug#780468: fails to build cross compiler for m68k: error during patch application

Helmut Grohne writes: > +++ gcc-5-5-20150307/debian/patches/pr52306.diff PR52306 is FIXED in gcc5. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To UNSUBSCRIBE, ema

Bug#780468: fails to build cross compiler for m68k: error during patch application

Source: gcc-5 Version: 5-20150307-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap I noticed that building a cross compiler for m68k fails during patch application. It seems very likely that this also affects native m68k builds, but it appears stuck in BD-Uninstallable at the moment, s