gcc-4.6 override disparity

There are disparities between your recently accepted upload and the override file for the following file(s): libstdc++6_4.6.2-16_amd64.deb: package says priority is important, override says required. Please note that a list of new sections were recently added to the archive: cli-mono, database,

gcc-4.6_4.6.2-16_amd64.changes ACCEPTED into unstable

Accepted: cpp-4.6_4.6.2-16_amd64.deb to main/g/gcc-4.6/cpp-4.6_4.6.2-16_amd64.deb fixincludes_4.6.2-16_amd64.deb to main/g/gcc-4.6/fixincludes_4.6.2-16_amd64.deb g++-4.6-multilib_4.6.2-16_amd64.deb to main/g/gcc-4.6/g++-4.6-multilib_4.6.2-16_amd64.deb g++-4.6_4.6.2-16_amd64.deb to main/g

Processing of gcc-4.6_4.6.2-16_amd64.changes

gcc-4.6_4.6.2-16_amd64.changes uploaded successfully to localhost along with the files: gcc-4.6_4.6.2-16.dsc gcc-4.6_4.6.2-16.diff.gz gcc-4.6-source_4.6.2-16_all.deb libstdc++6-4.6-doc_4.6.2-16_all.deb gcc-4.6-locales_4.6.2-16_all.deb gcc-4.6-base_4.6.2-16_amd64.deb libgcc1_4.6.2-16_a

Bug#661385: marked as done (libstdc++6-4.6-dbg: libstdcxx Python package installed in the wrong place)

Your message dated Sun, 26 Feb 2012 23:04:04 + with message-id and subject line Bug#661385: fixed in gcc-4.6 4.6.2-16 has caused the Debian Bug report #661385, regarding libstdc++6-4.6-dbg: libstdcxx Python package installed in the wrong place to be marked as done. This means that you claim

Bug#661362: marked as done (gcc-4.6: FTBFS on hurd-i386)

Your message dated Sun, 26 Feb 2012 23:04:03 + with message-id and subject line Bug#661362: fixed in gcc-4.6 4.6.2-16 has caused the Debian Bug report #661362, regarding gcc-4.6: FTBFS on hurd-i386 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#661118: marked as done (libstdc++6: is "Priority: required" but not pseudo-essential)

Your message dated Sun, 26 Feb 2012 23:04:03 + with message-id and subject line Bug#661118: fixed in gcc-4.6 4.6.2-16 has caused the Debian Bug report #661118, regarding libstdc++6: is "Priority: required" but not pseudo-essential to be marked as done. This means that you claim that the probl

Bug#651550: marked as done (libstdc++6 4.6.1-4 breaks libstdc++6-4.4-dev 4.4.5-8 but doesn't "conflict" with it)

Your message dated Sun, 26 Feb 2012 23:04:03 + with message-id and subject line Bug#651550: fixed in gcc-4.6 4.6.2-16 has caused the Debian Bug report #651550, regarding libstdc++6 4.6.1-4 breaks libstdc++6-4.4-dev 4.4.5-8 but doesn't "conflict" with it to be marked as done. This means that

Bug#623280: marked as done (/usr/lib/libstdc++.so.6: undefined symbol: _ZNSt8messagesIcE2idE, version GLIBCXX_3.4)

Your message dated Sun, 26 Feb 2012 23:04:03 + with message-id and subject line Bug#584572: fixed in gcc-4.6 4.6.2-16 has caused the Debian Bug report #584572, regarding /usr/lib/libstdc++.so.6: undefined symbol: _ZNSt8messagesIcE2idE, version GLIBCXX_3.4 to be marked as done. This means tha

Bug#584572: marked as done (symbol lookup error: undefined symbol)

Your message dated Sun, 26 Feb 2012 23:04:03 + with message-id and subject line Bug#584572: fixed in gcc-4.6 4.6.2-16 has caused the Debian Bug report #584572, regarding symbol lookup error: undefined symbol to be marked as done. This means that you claim that the problem has been dealt with.

Bug#661385: libstdc++6-4.6-dbg: libstdcxx Python package installed in the wrong place

On 26.02.2012 21:44, Zack Weinberg wrote: Package: libstdc++6-4.6-dbg Version: 4.6.2-15 Severity: normal gdb wants Python extensions installed under /usr/share/gdb/python, but libstdc++6-4.6-dbg is putting them under /usr/share/gcc-4.6/python instead. Thus, you get an obnoxious error message eve

Re: libreoffice, mingw-w64, gcc-mingw-w64 and gnat-4.6 on armhf

Hi, On Sat, Feb 25, 2012 at 02:16:09PM +, Luke Kenneth Casson Leighton wrote: > > # file /usr/share/libreoffice/sdk/classes/win/unowinreg.dll > > /usr/share/libreoffice/sdk/classes/win/unowinreg.dll: PE32 executable (DLL) > > (console) Intel 80386 (stripped to external PDB), for MS Windows >

Bug#661385: libstdc++6-4.6-dbg: libstdcxx Python package installed in the wrong place

Package: libstdc++6-4.6-dbg Version: 4.6.2-15 Severity: normal gdb wants Python extensions installed under /usr/share/gdb/python, but libstdc++6-4.6-dbg is putting them under /usr/share/gcc-4.6/python instead. Thus, you get an obnoxious error message every time you debug a C++ program: from l

Results for 4.7.0 20120223 (experimental) [trunk revision 184508] (Debian 4.7-20120224-1) testsuite on arm-unknown-linux-gnueabi

LAST_UPDATED: Thu Feb 23 14:51:05 UTC 2012 (revision 184508) Native configuration is arm-unknown-linux-gnueabi === boehm-gc tests === Running target unix FAIL: boehm-gc.c/thread_leak_test.c -O2 (test for excess errors) === boehm-gc Summary === # of expected pas

Bug#655518: marked as done (gcc-4.6 on Alpha: incorrect code generation when compiling git)

Your message dated Sun, 26 Feb 2012 18:31:14 +0100 with message-id <4f4a6c62.7010...@debian.org> and subject line Re: Bug#655518: gcc-4.6 on Alpha: incorrect code generation when, compiling git has caused the Debian Bug report #655518, regarding gcc-4.6 on Alpha: incorrect code generation when com

Bug#661362: gcc-4.6: FTBFS on hurd-i386

Package: gcc-4.6 Version: 4.6.2-15 Severity: important Tags: patch Hello, The #652693 bug of gcc-4.7 was introduced in gcc-4.6 too, making it FTBFS on hurd-i386. Could you backport the hurd-fixes.diff patch to the 4.6 branch as the attached patch does? Thanks, Samuel -- System Information: Debi