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

2012-02-26 Thread Samuel Thibault
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:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.4 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gcc-4.6 depends on:
ii  binutils  2.22-5
ii  cpp-4.6   4.6.2-12
ii  gcc-4.6-base  4.6.2-12
ii  libc6 2.13-26
ii  libgcc1   1:4.7-20120129-1
ii  libgmp10  2:5.0.4+dfsg-1
ii  libgomp1  4.7-20120129-1
ii  libmpc2   0.9-4
ii  libmpfr4  3.1.0-3
ii  libquadmath0  4.7-20120129-1
ii  zlib1g1:1.2.6.dfsg-1

Versions of packages gcc-4.6 recommends:
ii  libc6-dev  2.13-26

Versions of packages gcc-4.6 suggests:
pn  binutils-gold
pn  gcc-4.6-doc  
pn  gcc-4.6-locales  
pn  gcc-4.6-multilib 4.6.2-12
pn  libgcc1-dbg  1:4.7-20120129-1
pn  libgomp1-dbg 
pn  libmudflap0-4.6-dev  
pn  libmudflap0-dbg  
pn  libquadmath0-dbg 

-- no debconf information

-- 
Samuel Thibault 
 RR> Ce que je cherche à démontrer, c'est qu'il est injuste de faire
 RR> l'amalgame entre du bulk mail et du courrier non-solicité très ciblé
 un suppositoire non reclamé, meme tres bien ciblé, reste un suppositoire.
 -+-OS in : Guide du Neuneu d'Usenet - Plein le cul de la pub à neuneu -+-
Index: debian/patches/hurd-fixes.diff
===
--- debian/patches/hurd-fixes.diff  (révision 0)
+++ debian/patches/hurd-fixes.diff  (révision 0)
@@ -0,0 +1,11 @@
+--- a/src/libgcc/generic-morestack.c.orig  2011-12-19 21:14:52.0 
+0100
 b/src/libgcc/generic-morestack.c   2011-12-19 21:15:35.0 +0100
+@@ -507,7 +507,7 @@
+   sigemptyset (&__morestack_initial_sp.mask);
+ 
+   sigfillset (&__morestack_fullmask);
+-#ifdef __GLIBC__
++#if defined(__GLIBC__) && defined(__SIGRTMIN)
+   /* In glibc, the first two real time signals are used by the NPTL
+  threading library.  By taking them out of the set of signals, we
+  avoiding copying the signal mask in pthread_sigmask.  More
Index: debian/rules.patch
===
--- debian/rules.patch  (révision 5865)
+++ debian/rules.patch  (copie de travail)
@@ -239,7 +239,7 @@
 endif
 
 ifeq ($(DEB_TARGET_ARCH_OS),hurd)
-  debian_patches += hurd-changes
+  debian_patches += hurd-changes hurd-fixes
 endif
 
 debian_patches += gcc-ice-hack gcc-ice-apport


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

2012-02-26 Thread Debian Bug Tracking System
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 compiling git
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
655518: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.6
Version: 4.6.2-11
Severity: important
User: debian-al...@lists.debian.org
Usertags: alpha
X-Debbugs-CC: debian-al...@lists.debian.org

git_1:1.7.8.3-1 FTBFS because of incorrect code generation by gcc-4.6.
The test suite of git fails with a segmentation violation as revealed by
running it under gdb:


Program terminated with signal 11, Segmentation fault.
#0  0x0001200a44b4 in git_config_rename_section (
old_name=0x11fa8392d "branch.vier", new_name=0x11fa83939 "branch.zwei")
at config.c:1533
1533output[0] = '\t';
(gdb) list
1528 * a declaration to put on the
1529 * next line; indent with a
1530 * tab
1531 */
1532output -= 1;
1533output[0] = '\t';
1534}
1535}
1536remove = 0;
1537}
(gdb) print output
$1 = 0x11fa83000 "z = 1\n"
(gdb) print output[0]
$2 = 122 'z'
(gdb) print offset
$3 = 16
(gdb) print i
$4 = 

A test higher up in the code ensures at this point that output points
into a char array so it is safe to decrement it and deference as the
code above does.  Also the print statements above reveal that output
points to valid characters within a bigger char array as expected,
nevertheless a segmentation violation is encountered when writing to
string[0].

The generated object code is:

1525if (strlen(output) > 0) {
   0x0001200a448c <+956>:   lda t1,1(a1)
   0x0001200a4490 <+960>:   ldq_u   t2,0(a1)
   0x0001200a4494 <+964>:   extqh   t2,t1,t1
   0x0001200a4498 <+968>:   sra t1,0x38,t1
   0x0001200a449c <+972>:   beq t1,0x1200a4228


1526/*
1527 * More content means there's
1528 * a declaration to put on the
1529 * next line; indent with a
---Type  to continue, or q  to quit---
1530 * tab
1531 */
1532output -= 1;
   0x0001200a44bc <+1004>:  lda a1,-1(a1)

1533output[0] = '\t';
   0x0001200a44a0 <+976>:   lda t1,1
   0x0001200a44a4 <+980>:   sll t1,0x3d,t1
   0x0001200a44a8 <+984>:   addqa1,t1,t0
   0x0001200a44ac <+988>:   lda t3,-1(t0)
   0x0001200a44b0 <+992>:   lda t1,9
=> 0x0001200a44b4 <+996>:   ldq_u   t2,-1(t0)
   0x0001200a44b8 <+1000>:  insbl   t1,t3,t1
   0x0001200a44c0 <+1008>:  mskbl   t2,t3,t2
   0x0001200a44c4 <+1012>:  or  t1,t2,t1
   0x0001200a44c8 <+1016>:  stq_u   t1,-1(t0)
   0x0001200a44cc <+1020>:  br  0x1200a4228


At line 1532 it decrements register a1 and saves back to a1, but does
not use that result when saving '\t" to output[0]!  Instead it sets the
high bit of a1 (the lda t1,1; sll t1,0x3d,t1; addq a1,t1,t0
instructions) and then uses that as the memory address for storing the
'\t'.  But that is no longer in user memory space!

If I compile with the -mcpu=ev67 compiler option (mainly to allow
compilation with the byte-word extension) then the generated code is:

   output -= 1;
output[0] = '\t';
 22c:   09 00 3f 20 lda t0,9
 * More content means there's
 * a declaration to put on the
 * next line; indent with a
 * tab
 */
output -= 1;
 230:   ff ff 

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

2012-02-26 Thread Matthias Klose
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 passes11
# of unexpected failures1
# of unsupported tests  1
=== libgomp tests ===


Running target unix
FAIL: libgomp.c/atomic-1.c execution test
FAIL: libgomp.c/atomic-10.c execution test
FAIL: libgomp.c/atomic-13.c execution test
FAIL: libgomp.c/atomic-2.c execution test
FAIL: libgomp.c/atomic-3.c execution test
FAIL: libgomp.c/atomic-4.c execution test
FAIL: libgomp.c/atomic-5.c execution test
FAIL: libgomp.c/atomic-6.c execution test
FAIL: libgomp.c/autopar-1.c execution test
FAIL: libgomp.c++/atomic-6.C  -O0  execution test
FAIL: libgomp.c++/atomic-6.C  -O1  execution test
FAIL: libgomp.c++/atomic-6.C  -O2  execution test
FAIL: libgomp.c++/atomic-6.C  -O3 -fomit-frame-pointer  execution test
FAIL: libgomp.c++/atomic-6.C  -O3 -fomit-frame-pointer -funroll-loops  
execution test
FAIL: libgomp.c++/atomic-6.C  -O3 -fomit-frame-pointer -funroll-all-loops 
-finline-functions  execution test
FAIL: libgomp.c++/atomic-6.C  -O3 -g  execution test
FAIL: libgomp.c++/atomic-6.C  -Os  execution test
FAIL: libgomp.c++/atomic-7.C  -O0  execution test
FAIL: libgomp.c++/atomic-7.C  -O1  execution test
FAIL: libgomp.c++/atomic-7.C  -O2  execution test
FAIL: libgomp.c++/atomic-7.C  -O3 -fomit-frame-pointer  execution test
FAIL: libgomp.c++/atomic-7.C  -O3 -fomit-frame-pointer -funroll-loops  
execution test
FAIL: libgomp.c++/atomic-7.C  -O3 -fomit-frame-pointer -funroll-all-loops 
-finline-functions  execution test
FAIL: libgomp.c++/atomic-7.C  -O3 -g  execution test
FAIL: libgomp.c++/atomic-7.C  -Os  execution test
FAIL: libgomp.fortran/jacobi.f  -O0  execution test
FAIL: libgomp.fortran/jacobi.f  -O1  execution test
FAIL: libgomp.fortran/jacobi.f  -O2  execution test
FAIL: libgomp.fortran/jacobi.f  -O3 -fomit-frame-pointer  execution test
FAIL: libgomp.fortran/jacobi.f  -O3 -fomit-frame-pointer -funroll-loops  
execution test
FAIL: libgomp.fortran/jacobi.f  -O3 -fomit-frame-pointer -funroll-all-loops 
-finline-functions  execution test
FAIL: libgomp.fortran/jacobi.f  -O3 -g  execution test
FAIL: libgomp.fortran/jacobi.f  -Os  execution test
FAIL: libgomp.fortran/omp_atomic1.f90  -O0  execution test
FAIL: libgomp.fortran/omp_atomic1.f90  -O1  execution test
FAIL: libgomp.fortran/omp_atomic1.f90  -O2  execution test
FAIL: libgomp.fortran/omp_atomic1.f90  -O3 -fomit-frame-pointer  execution test
FAIL: libgomp.fortran/omp_atomic1.f90  -O3 -fomit-frame-pointer -funroll-loops  
execution test
FAIL: libgomp.fortran/omp_atomic1.f90  -O3 -fomit-frame-pointer 
-funroll-all-loops -finline-functions  execution test
FAIL: libgomp.fortran/omp_atomic1.f90  -O3 -g  execution test
FAIL: libgomp.fortran/omp_atomic1.f90  -Os  execution test
FAIL: libgomp.fortran/omp_atomic3.f90  -O0  execution test
FAIL: libgomp.fortran/omp_atomic3.f90  -O1  execution test
FAIL: libgomp.fortran/omp_atomic3.f90  -O2  execution test
FAIL: libgomp.fortran/omp_atomic3.f90  -O3 -fomit-frame-pointer  execution test
FAIL: libgomp.fortran/omp_atomic3.f90  -O3 -fomit-frame-pointer -funroll-loops  
execution test
FAIL: libgomp.fortran/omp_atomic3.f90  -O3 -fomit-frame-pointer 
-funroll-all-loops -finline-functions  execution test
FAIL: libgomp.fortran/omp_atomic3.f90  -O3 -g  execution test
FAIL: libgomp.fortran/omp_atomic3.f90  -Os  execution test
FAIL: libgomp.fortran/omp_atomic4.f90  -O0  execution test
FAIL: libgomp.fortran/omp_atomic4.f90  -O1  execution test
FAIL: libgomp.fortran/omp_atomic4.f90  -O2  execution test
FAIL: libgomp.fortran/omp_atomic4.f90  -O3 -fomit-frame-pointer  execution test
FAIL: libgomp.fortran/omp_atomic4.f90  -O3 -fomit-frame-pointer -funroll-loops  
execution test
FAIL: libgomp.fortran/omp_atomic4.f90  -O3 -fomit-frame-pointer 
-funroll-all-loops -finline-functions  execution test
FAIL: libgomp.fortran/omp_atomic4.f90  -O3 -g  execution test
FAIL: libgomp.fortran/omp_atomic4.f90  -Os  execution test
FAIL: libgomp.fortran/omp_orphan.f  -O  execution test
FAIL: libgomp.fortran/pr48894.f90  -O0  execution test
FAIL: libgomp.fortran/pr48894.f90  -O1  execution test
FAIL: libgomp.fortran/pr48894.f90  -O2  execution test
FAIL: libgomp.fortran/pr48894.f90  -O3 -fomit-frame-pointer  execution test
FAIL: libgomp.fortran/pr48894.f90  -O3 -fomit-frame-pointer -funroll-loops  
execution test
FAIL: libgomp.fortran/pr48894.f90  -O3 -fomit-frame-pointer -funroll-all-loops 
-finline-functions  execution test
FAIL: libgomp.fortran/pr48894.f90  -O3 -g  execution test
FAIL: libgomp.fortran/pr48894.f90  -Os  execution test
WARNING: program timed out.
FAIL: libgomp.fortran/strassen.f90  -O  execution test

=== libgomp Summary ===

# of expected passes2927
# of unexpected failures67
# 

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

2012-02-26 Thread Zack Weinberg
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 libstdcxx.v6.printers import register_libstdcxx_printers
Traceback (most recent call last):
  File "", line 1, in 
ImportError: No module named libstdcxx.v6.printers

and, more seriously, the STL pretty-printing feature does not work.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (501, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libstdc++6-4.6-dbg depends on:
ii  gcc-4.6-base  4.6.2-15
ii  libc6 2.13-26
ii  libgcc1   1:4.6.2-15
ii  libgcc1-dbg   1:4.6.2-15
ii  libstdc++64.6.2-15

Versions of packages libstdc++6-4.6-dbg recommends:
ii  libstdc++6-4.6-dev  4.6.2-15

libstdc++6-4.6-dbg suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/2012022620.9792.85108.reportbug@moxana.local



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

2012-02-26 Thread Rene Engelhard
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
> >
> > i686-w64-mingw32-g++ is called.
> 
>  that's different from mingw-w64, then.

Wrong. that is mingw-64. peter already said that, though.

> >> simply wouldn't even run on an ARM processor anyway seems to have
> >> entirely escaped everyone's attention.
> >
> > No. In contast, Stephen said it correctly.
> 
>  actually, he didn't: in the public post he didn't mention that it was
> purely for shipping with the *windows* version of libreoffice, so that

That's wrong anyway. The windows version of libreoffice doesn't even ship
it either.

It's the *SDK* shipping this. On all archs.

For being ale to create cross-platform Java stuff there (which also then
runs on windows as intended)

> people who perform development on gnu/linux of libreoffice
> applications can ship the libreoffice application with that DLL *such
> that* the *windows* version of libreoffice will actually work and have
> access to the windows dll.

He said that, sorry.

--- snip ---
[...] is supposed to be bundled with plugins which need to access the
registry, and therefore to be able to correctly build "shippable"
plugins [...]
--- snip ---

>  your bullying and lack of forgiveness is duly noted.

And you do have one? I didn't see it formulated in your unpolite mail at least.

Regards,

Rene


-- 
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120226202859.gj17...@rene-engelhard.de



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

2012-02-26 Thread Matthias Klose

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 every time you debug a C++ program:

 from libstdcxx.v6.printers import register_libstdcxx_printers
 Traceback (most recent call last):
   File "", line 1, in
 ImportError: No module named libstdcxx.v6.printers


correct place, but the back-path is wrongly calculated for the multiarch 
location.



--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f4aa542.9030...@debian.org



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

2012-02-26 Thread Debian Bug Tracking System
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.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
584572: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libstdc++6
Version: 4.5.0-5
Severity: critical
Tags: experimental

After upgrading libstdc++6 this morning, various C++ software began
failing. The original version upgraded from was 4.5.0-4 so the problem
appears to be introduced in this specific version.

Following is a transcript of reproducing the problem.
=
# apt-cache policy libstdc++6
libstdc++6:
  Installed: 4.4.4-1
  Candidate: 4.4.4-1
  Version table:
 4.5.0-5 0
700 http://dpkg.teamgleim.com rc-buggy/main Packages
 4.4.4-4 0
800 http://dpkg.teamgleim.com sid/main Packages
 *** 4.4.4-1 0
900 http://dpkg.teamgleim.com squeeze/main Packages
100 /var/lib/dpkg/status
# aptitude install libstdc++6/experimental
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Reading extended state information... Done
Initializing package states... Done   
The following packages will be upgraded:
  libstdc++6 
1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 345kB of archives. After unpacking 16.4kB will be freed.
Do you want to continue? [Y/n/?] 
Writing extended state information... Done
Get:1 http://dpkg.teamgleim.com rc-buggy/main libstdc++6 4.5.0-5 [345kB]
Fetched 345kB in 0s (8,694kB/s)
Reading changelogs... Done
(Reading database ... 137430 files and directories currently installed.)
Preparing to replace libstdc++6 4.4.4-1 (using .../libstdc++6_4.5.0-5_i386.deb) 
...
Unpacking replacement libstdc++6 ...
Setting up libstdc++6 (4.5.0-5) ...
Reading package lists... Done 
Building dependency tree   
Reading state information... Done
Reading extended state information... Done
Initializing package states... Done   
Writing extended state information... Done

Current status: 0 updates [-1].
# apt-cache policy libstdc++6
apt-cache: symbol lookup error: /usr/lib/libstdc++.so.6: undefined symbol: 
_ZNSt7num_getIcSt19istreambuf_iteratorIcSt11char_traitsIcEEE2idE, version 
GLIBCXX_3.4
# 
=

I'm going to downgrade to the version in squeeze now, but I can
reupgrade any time if more details are needed.

-- System Information:
Debian Release: squeeze/sid
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libstdc++6 depends on:
ii  gcc-4.5-base  4.5.0-5The GNU Compiler Collection (base 
ii  libc6 2.10.2-9   Embedded GNU C Library: Shared lib
ii  libgcc1   1:4.5.0-5  GCC support library

libstdc++6 recommends no packages.

libstdc++6 suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: gcc-4.6
Source-Version: 4.6.2-16

We believe that the bug you reported is fixed in the latest version of
gcc-4.6, which is due to be installed in the Debian FTP archive:

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/gcc-4.6/g++-4.6_4.6.2-16_amd64.deb
gcc-4.6-base_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-base_4.6.2-16_amd64.deb
gcc-4.6-locales_4.6.2-16_all.deb
  to main/g/gcc-4.6/gcc-4.6-locales_4.6.2-16_all.deb
gcc-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-multilib_4.6.2-16_amd64.deb
gcc-4.6-plugin-dev_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-plugin-dev_4.6.2-16_amd64.deb
gcc-4.6-source_4.6.2-16_all.deb
  to main/g/gcc-4.6/gcc-4.6-source_4.6.2-16_all.deb
gcc-4.6_4.6.2-16.diff.gz
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16.diff.gz
gcc-4.6_4.6.2-16.dsc
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16.dsc
gcc-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16_amd64.deb
gccgo-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gccgo-4.6-multilib_4.6.2-16_amd64.deb
gccgo-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gccgo-4.6_4.6.2-16_amd64.deb
gfortran-4.6-mul

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

2012-02-26 Thread Debian Bug Tracking System
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 that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
584572: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libstdc++6
Version: 4.6.0-2
Severity: normal

update-menus: symbol lookup error: /usr/lib/libstdc++.so.6: undefined symbol: 
_ZNSt8messagesIcE2idE, version GLIBCXX_3.4
dpkg: error processing menu (--unpack):
 subprocess installed post-installation script returned error exit status 127
Errors were encountered while processing:
 /var/cache/apt/archives/qt4-qtconfig_4%3a4.7.2-3_i386.deb
 menu

apt-get: symbol lookup error: /usr/lib/libstdc++.so.6: undefined symbol: 
_ZNSt8messagesIcE2idE, version GLIBCXX_3.4

This system tracks unstable but had been off, and trying to install
something pulled in a new libstdc++6 w/o first upgrading libc6,
which was at version 2.10.2-9.

This bug seems similar to #584572, except with newer versions. I fixed
the problem here my manually upgrading libc6 with dpkg.

So, there must be a badly versioned dependency.

-- 
see shy jo


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: gcc-4.6
Source-Version: 4.6.2-16

We believe that the bug you reported is fixed in the latest version of
gcc-4.6, which is due to be installed in the Debian FTP archive:

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/gcc-4.6/g++-4.6_4.6.2-16_amd64.deb
gcc-4.6-base_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-base_4.6.2-16_amd64.deb
gcc-4.6-locales_4.6.2-16_all.deb
  to main/g/gcc-4.6/gcc-4.6-locales_4.6.2-16_all.deb
gcc-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-multilib_4.6.2-16_amd64.deb
gcc-4.6-plugin-dev_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-plugin-dev_4.6.2-16_amd64.deb
gcc-4.6-source_4.6.2-16_all.deb
  to main/g/gcc-4.6/gcc-4.6-source_4.6.2-16_all.deb
gcc-4.6_4.6.2-16.diff.gz
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16.diff.gz
gcc-4.6_4.6.2-16.dsc
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16.dsc
gcc-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16_amd64.deb
gccgo-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gccgo-4.6-multilib_4.6.2-16_amd64.deb
gccgo-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gccgo-4.6_4.6.2-16_amd64.deb
gfortran-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gfortran-4.6-multilib_4.6.2-16_amd64.deb
gfortran-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gfortran-4.6_4.6.2-16_amd64.deb
gobjc++-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gobjc++-4.6-multilib_4.6.2-16_amd64.deb
gobjc++-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gobjc++-4.6_4.6.2-16_amd64.deb
gobjc-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gobjc-4.6-multilib_4.6.2-16_amd64.deb
gobjc-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gobjc-4.6_4.6.2-16_amd64.deb
lib32gcc1-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gcc1-dbg_4.6.2-16_amd64.deb
lib32gcc1_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gcc1_4.6.2-16_amd64.deb
lib32gfortran3-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gfortran3-dbg_4.6.2-16_amd64.deb
lib32gfortran3_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gfortran3_4.6.2-16_amd64.deb
lib32go0-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32go0-dbg_4.6.2-16_amd64.deb
lib32go0_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32go0_4.6.2-16_amd64.deb
lib32gomp1-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gomp1-dbg_4.6.2-16_amd64.deb
lib32gomp1_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gomp1_4.6.2-16_amd64.deb
lib32mudflap0-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32mudflap0-dbg_4.6.2-16_amd64.deb
lib32mudflap0_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32mudflap0_4.6.2-16_amd64.deb
lib32objc3-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32objc3-dbg_4.6.2-16_amd64.deb
lib32objc3_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32objc3_4.6.2-16_amd64.deb
lib32quadmath0-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32quadmath0-dbg_4.6.2-16_amd64.deb
lib32quadmath0_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32quadmath0_4.6.2-16_amd64.deb
lib32stdc++6-4.6-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32stdc++6-4.6-dbg_4.6.2-16_amd64.deb
lib32stdc

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)

2012-02-26 Thread Debian Bug Tracking System
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 you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
651550: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libstdc++6
Version: 4.6.2-5
Severity: normal

Apparently libstdc++.so.6 used to be in 
/usr/lib  in version 4.4.5, but was moved to 
/usr/lib/x86_64-linux-gnu in version 4.6 (or less)

The symlink /usr/lib/gcc/x86_64-linux-gnu/4.4.5/libstdc++.so, which is
part of libstdc++6-4.4-dev, points to 
/usr/lib in  version 4.4.5-8 and to 
/usr/lib/x86_64-linux-gnu in version 4.4.6-11

That means that the symlink is broken when the following package
versions are installed:
ii  libstdc++64.6.2-5   GNU Standard C++ 
Library v3
ii  libstdc++6-4.4-dev4.4.6-11  GNU Standard C++ 
Library v3 (development files)

This could be fixed by adding a "Conflicts" dependency for 
libstdc++6-4.4-dev to libstdc++6, which prevents the installation of
incompatible versions.

-- System Information:
Debian Release: 6.0.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-core2 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libstdc++6 depends on:
ii  gcc-4.6-base  4.6.2-5GCC, the GNU Compiler Collection (
ii  libc6 2.13-21Embedded GNU C Library: Shared lib
ii  libgcc1   1:4.6.2-5  GCC support library
ii  multiarch-support 2.13-16Transitional package to ensure mul

libstdc++6 recommends no packages.

libstdc++6 suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: gcc-4.6
Source-Version: 4.6.2-16

We believe that the bug you reported is fixed in the latest version of
gcc-4.6, which is due to be installed in the Debian FTP archive:

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/gcc-4.6/g++-4.6_4.6.2-16_amd64.deb
gcc-4.6-base_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-base_4.6.2-16_amd64.deb
gcc-4.6-locales_4.6.2-16_all.deb
  to main/g/gcc-4.6/gcc-4.6-locales_4.6.2-16_all.deb
gcc-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-multilib_4.6.2-16_amd64.deb
gcc-4.6-plugin-dev_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-plugin-dev_4.6.2-16_amd64.deb
gcc-4.6-source_4.6.2-16_all.deb
  to main/g/gcc-4.6/gcc-4.6-source_4.6.2-16_all.deb
gcc-4.6_4.6.2-16.diff.gz
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16.diff.gz
gcc-4.6_4.6.2-16.dsc
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16.dsc
gcc-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16_amd64.deb
gccgo-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gccgo-4.6-multilib_4.6.2-16_amd64.deb
gccgo-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gccgo-4.6_4.6.2-16_amd64.deb
gfortran-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gfortran-4.6-multilib_4.6.2-16_amd64.deb
gfortran-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gfortran-4.6_4.6.2-16_amd64.deb
gobjc++-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gobjc++-4.6-multilib_4.6.2-16_amd64.deb
gobjc++-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gobjc++-4.6_4.6.2-16_amd64.deb
gobjc-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gobjc-4.6-multilib_4.6.2-16_amd64.deb
gobjc-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gobjc-4.6_4.6.2-16_amd64.deb
lib32gcc1-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gcc1-dbg_4.6.2-16_amd64.deb
lib32gcc1_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gcc1_4.6.2-16_amd64.deb
lib32gfortran3-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gfortran3-dbg_4.6.2-16_amd64.deb
lib32gfortran3_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gfortran3_4.6.2-16_amd64.deb
lib32go0-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32go0-dbg_4.6.2-16_amd64.deb
lib32go0_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32go0_4.6.2-16_amd64.deb
lib32gomp1-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gomp1-dbg_4.

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

2012-02-26 Thread Debian Bug Tracking System
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 problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
661118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libstdc++6
Version: 4.7-20120210-1
Severity: wishlist
Tags: patch

Hi,

libstdc++6 has "Priority: required", but no pseudo-essential package
depends on it:

$ grep-dctrl -sPackage \
-FPriority required \
-a -FDepends,Pre-Depends 'libstdc++6' \

= 2.11) for STB_GNU_UNIQUE support
 (Eugene V. Lyubimkin).  Closes: #584572.
+  * libstdc++6: Lower priority from required to important.
 
  -- Jonathan Nieder   Fri, 24 Feb 2012 02:38:01 -0600
 
diff --git i/debian/control.m4 w/debian/control.m4
index cbae8a86..fb8d4d48 100644
--- i/debian/control.m4
+++ w/debian/control.m4
@@ -1826,7 +1826,7 @@ ifenabled(`libcxx',`
 Package: libstdc++CXX_SO`'LS
 Architecture: ifdef(`TARGET',`all',`any')
 Section: ifdef(`TARGET',`devel',`libs')
-Priority: ifdef(`TARGET',`extra',PRI(required))
+Priority: ifdef(`TARGET',`extra',PRI(important))
 Depends: BASEDEP, ${dep:libc}, ${shlibs:Depends}, ${misc:Depends}
 ifdef(`TARGET',`Provides: libstdc++CXX_SO-TARGET-dcv1',
 ifdef(`MULTIARCH', `Multi-Arch: same


--- End Message ---
--- Begin Message ---
Source: gcc-4.6
Source-Version: 4.6.2-16

We believe that the bug you reported is fixed in the latest version of
gcc-4.6, which is due to be installed in the Debian FTP archive:

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/gcc-4.6/g++-4.6_4.6.2-16_amd64.deb
gcc-4.6-base_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-base_4.6.2-16_amd64.deb
gcc-4.6-locales_4.6.2-16_all.deb
  to main/g/gcc-4.6/gcc-4.6-locales_4.6.2-16_all.deb
gcc-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-multilib_4.6.2-16_amd64.deb
gcc-4.6-plugin-dev_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-plugin-dev_4.6.2-16_amd64.deb
gcc-4.6-source_4.6.2-16_all.deb
  to main/g/gcc-4.6/gcc-4.6-source_4.6.2-16_all.deb
gcc-4.6_4.6.2-16.diff.gz
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16.diff.gz
gcc-4.6_4.6.2-16.dsc
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16.dsc
gcc-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16_amd64.deb
gccgo-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gccgo-4.6-multilib_4.6.2-16_amd64.deb
gccgo-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gccgo-4.6_4.6.2-16_amd64.deb
gfortran-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gfortran-4.6-multilib_4.6.2-16_amd64.deb
gfortran-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gfortran-4.6_4.6.2-16_amd64.deb
gobjc++-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gobjc++-4.6-multilib_4.6.2-16_amd64.deb
gobjc++-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gobjc++-4.6_4.6.2-16_amd64.deb
gobjc-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gobjc-4.6-multilib_4.6.2-16_amd64.deb
gobjc-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gobjc-4.6_4.6.2-16_amd64.deb
lib32gcc1-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gcc1-dbg_4.6.2-16_amd64.deb
lib32gcc1_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gcc1_4.6.2-16_amd64.deb
lib32gfortran3-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gfortran3-dbg_4.6.2-16_amd64.deb
lib32gfortran3_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gfortran3_4.6.2-16_amd64.deb
lib32go0-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32go0-dbg_4.6.2-16_amd64.deb
lib32go0_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32go0_4.6.2-16_amd64.deb
lib32gomp1-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gomp1-dbg_4.6.2-16_amd64.deb
lib32gomp1_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gomp1_4.6.2-16_amd64.deb
lib32mudflap0-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32mudflap0-dbg_4.6.2-16_amd64.deb
lib32mudflap0_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32mudflap0_4.6.2-16_amd64.deb
lib32objc3-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32objc3-dbg_4.6.2-16_amd64.deb
lib32objc3_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32objc3_4.6.2-16_amd64.deb
lib32quadmath0-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32quadmath0-dbg_4.6.2-16_amd64.deb
lib32quadmath0_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32quadmath0_4.6.2-16_amd64.de

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

2012-02-26 Thread Debian Bug Tracking System
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 is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
661362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.4 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gcc-4.6 depends on:
ii  binutils  2.22-5
ii  cpp-4.6   4.6.2-12
ii  gcc-4.6-base  4.6.2-12
ii  libc6 2.13-26
ii  libgcc1   1:4.7-20120129-1
ii  libgmp10  2:5.0.4+dfsg-1
ii  libgomp1  4.7-20120129-1
ii  libmpc2   0.9-4
ii  libmpfr4  3.1.0-3
ii  libquadmath0  4.7-20120129-1
ii  zlib1g1:1.2.6.dfsg-1

Versions of packages gcc-4.6 recommends:
ii  libc6-dev  2.13-26

Versions of packages gcc-4.6 suggests:
pn  binutils-gold
pn  gcc-4.6-doc  
pn  gcc-4.6-locales  
pn  gcc-4.6-multilib 4.6.2-12
pn  libgcc1-dbg  1:4.7-20120129-1
pn  libgomp1-dbg 
pn  libmudflap0-4.6-dev  
pn  libmudflap0-dbg  
pn  libquadmath0-dbg 

-- no debconf information

-- 
Samuel Thibault 
 RR> Ce que je cherche à démontrer, c'est qu'il est injuste de faire
 RR> l'amalgame entre du bulk mail et du courrier non-solicité très ciblé
 un suppositoire non reclamé, meme tres bien ciblé, reste un suppositoire.
 -+-OS in : Guide du Neuneu d'Usenet - Plein le cul de la pub à neuneu -+-
Index: debian/patches/hurd-fixes.diff
===
--- debian/patches/hurd-fixes.diff  (révision 0)
+++ debian/patches/hurd-fixes.diff  (révision 0)
@@ -0,0 +1,11 @@
+--- a/src/libgcc/generic-morestack.c.orig  2011-12-19 21:14:52.0 
+0100
 b/src/libgcc/generic-morestack.c   2011-12-19 21:15:35.0 +0100
+@@ -507,7 +507,7 @@
+   sigemptyset (&__morestack_initial_sp.mask);
+ 
+   sigfillset (&__morestack_fullmask);
+-#ifdef __GLIBC__
++#if defined(__GLIBC__) && defined(__SIGRTMIN)
+   /* In glibc, the first two real time signals are used by the NPTL
+  threading library.  By taking them out of the set of signals, we
+  avoiding copying the signal mask in pthread_sigmask.  More
Index: debian/rules.patch
===
--- debian/rules.patch  (révision 5865)
+++ debian/rules.patch  (copie de travail)
@@ -239,7 +239,7 @@
 endif
 
 ifeq ($(DEB_TARGET_ARCH_OS),hurd)
-  debian_patches += hurd-changes
+  debian_patches += hurd-changes hurd-fixes
 endif
 
 debian_patches += gcc-ice-hack gcc-ice-apport
--- End Message ---
--- Begin Message ---
Source: gcc-4.6
Source-Version: 4.6.2-16

We believe that the bug you reported is fixed in the latest version of
gcc-4.6, which is due to be installed in the Debian FTP archive:

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/gcc-4.6/g++-4.6_4.6.2-16_amd64.deb
gcc-4.6-base_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-base_4.6.2-16_amd64.deb
gcc-4.6-locales_4.6.2-16_all.deb
  to main/g/gcc-4.6/gcc-4.6-locales_4.6.2-16_all.deb
gcc-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-multilib_4.6.2-16_amd64.deb
gcc-4.6-plugin-dev_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-plugin-dev_4.6.2-16_amd64.deb
gcc-4.6-source_4.6.2-16_all.deb
  to main/g/gcc-4.6/gcc-4.6-source_4.6.2-16_all.deb
gcc-4.6_4.6.2-16.diff.gz
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16.diff.gz
gcc-4.6_4.6.2-16.dsc
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16.dsc
gcc-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16_amd64.deb
gccgo-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gccgo-4.6-multilib_4.6.2-16_amd64.deb
gccgo-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gccgo-4.6_4.6.2-16_amd64.deb
gfortran-4.6-multil

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

2012-02-26 Thread Debian Bug Tracking System
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 that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
661385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 libstdcxx.v6.printers import register_libstdcxx_printers
Traceback (most recent call last):
  File "", line 1, in 
ImportError: No module named libstdcxx.v6.printers

and, more seriously, the STL pretty-printing feature does not work.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (501, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libstdc++6-4.6-dbg depends on:
ii  gcc-4.6-base  4.6.2-15
ii  libc6 2.13-26
ii  libgcc1   1:4.6.2-15
ii  libgcc1-dbg   1:4.6.2-15
ii  libstdc++64.6.2-15

Versions of packages libstdc++6-4.6-dbg recommends:
ii  libstdc++6-4.6-dev  4.6.2-15

libstdc++6-4.6-dbg suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: gcc-4.6
Source-Version: 4.6.2-16

We believe that the bug you reported is fixed in the latest version of
gcc-4.6, which is due to be installed in the Debian FTP archive:

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/gcc-4.6/g++-4.6_4.6.2-16_amd64.deb
gcc-4.6-base_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-base_4.6.2-16_amd64.deb
gcc-4.6-locales_4.6.2-16_all.deb
  to main/g/gcc-4.6/gcc-4.6-locales_4.6.2-16_all.deb
gcc-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-multilib_4.6.2-16_amd64.deb
gcc-4.6-plugin-dev_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-plugin-dev_4.6.2-16_amd64.deb
gcc-4.6-source_4.6.2-16_all.deb
  to main/g/gcc-4.6/gcc-4.6-source_4.6.2-16_all.deb
gcc-4.6_4.6.2-16.diff.gz
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16.diff.gz
gcc-4.6_4.6.2-16.dsc
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16.dsc
gcc-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16_amd64.deb
gccgo-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gccgo-4.6-multilib_4.6.2-16_amd64.deb
gccgo-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gccgo-4.6_4.6.2-16_amd64.deb
gfortran-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gfortran-4.6-multilib_4.6.2-16_amd64.deb
gfortran-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gfortran-4.6_4.6.2-16_amd64.deb
gobjc++-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gobjc++-4.6-multilib_4.6.2-16_amd64.deb
gobjc++-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gobjc++-4.6_4.6.2-16_amd64.deb
gobjc-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gobjc-4.6-multilib_4.6.2-16_amd64.deb
gobjc-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gobjc-4.6_4.6.2-16_amd64.deb
lib32gcc1-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gcc1-dbg_4.6.2-16_amd64.deb
lib32gcc1_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gcc1_4.6.2-16_amd64.deb
lib32gfortran3-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gfortran3-dbg_4.6.2-16_amd64.deb
lib32gfortran3_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gfortran3_4.6.2-16_amd64.deb
lib32go0-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32go0-dbg_4.6.2-16_amd64.deb
lib32go0_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32go0_4.6.2-16_amd64.deb
lib32gomp1-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gomp1-dbg_4.6.2-16_amd64.deb
lib32gomp1_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gomp1_4.6.2-16_amd64.deb
lib32mudflap0-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32mudflap0-dbg_4.6.2-16_amd64.deb
lib32mudflap0_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32mudflap0_4.6.2-16_amd64.deb
lib32objc3-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32objc3-dbg_4.6.2-16_amd64.deb
lib32objc3_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32objc3_4.6.2-16_amd64.deb
lib32quadmath0-dbg_4.6.2-16_amd64

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

2012-02-26 Thread Debian FTP Masters
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_amd64.deb
  libgcc1-dbg_4.6.2-16_amd64.deb
  lib32gcc1_4.6.2-16_amd64.deb
  lib32gcc1-dbg_4.6.2-16_amd64.deb
  libquadmath0_4.6.2-16_amd64.deb
  libquadmath0-dbg_4.6.2-16_amd64.deb
  lib32quadmath0_4.6.2-16_amd64.deb
  lib32quadmath0-dbg_4.6.2-16_amd64.deb
  libgomp1_4.6.2-16_amd64.deb
  libgomp1-dbg_4.6.2-16_amd64.deb
  lib32gomp1_4.6.2-16_amd64.deb
  lib32gomp1-dbg_4.6.2-16_amd64.deb
  cpp-4.6_4.6.2-16_amd64.deb
  fixincludes_4.6.2-16_amd64.deb
  libmudflap0-4.6-dev_4.6.2-16_amd64.deb
  libmudflap0_4.6.2-16_amd64.deb
  libmudflap0-dbg_4.6.2-16_amd64.deb
  lib32mudflap0_4.6.2-16_amd64.deb
  lib32mudflap0-dbg_4.6.2-16_amd64.deb
  gobjc++-4.6-multilib_4.6.2-16_amd64.deb
  gobjc++-4.6_4.6.2-16_amd64.deb
  gobjc-4.6-multilib_4.6.2-16_amd64.deb
  gobjc-4.6_4.6.2-16_amd64.deb
  libobjc3_4.6.2-16_amd64.deb
  libobjc3-dbg_4.6.2-16_amd64.deb
  lib32objc3_4.6.2-16_amd64.deb
  lib32objc3-dbg_4.6.2-16_amd64.deb
  libgo0_4.6.2-16_amd64.deb
  libgo0-dbg_4.6.2-16_amd64.deb
  lib32go0_4.6.2-16_amd64.deb
  lib32go0-dbg_4.6.2-16_amd64.deb
  gccgo-4.6_4.6.2-16_amd64.deb
  gccgo-4.6-multilib_4.6.2-16_amd64.deb
  g++-4.6-multilib_4.6.2-16_amd64.deb
  g++-4.6_4.6.2-16_amd64.deb
  libstdc++6_4.6.2-16_amd64.deb
  lib32stdc++6_4.6.2-16_amd64.deb
  lib32stdc++6-4.6-dbg_4.6.2-16_amd64.deb
  libstdc++6-4.6-dev_4.6.2-16_amd64.deb
  libstdc++6-4.6-pic_4.6.2-16_amd64.deb
  libstdc++6-4.6-dbg_4.6.2-16_amd64.deb
  libgfortran3_4.6.2-16_amd64.deb
  libgfortran3-dbg_4.6.2-16_amd64.deb
  lib32gfortran3_4.6.2-16_amd64.deb
  lib32gfortran3-dbg_4.6.2-16_amd64.deb
  gfortran-4.6-multilib_4.6.2-16_amd64.deb
  gfortran-4.6_4.6.2-16_amd64.deb
  gcc-4.6-multilib_4.6.2-16_amd64.deb
  gcc-4.6-plugin-dev_4.6.2-16_amd64.deb
  gcc-4.6_4.6.2-16_amd64.deb

Greetings,

Your Debian queue daemon (running on host franck.debian.org)


-- 
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1s1mxa-0006aa...@franck.debian.org



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

2012-02-26 Thread Debian FTP Masters



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/gcc-4.6/g++-4.6_4.6.2-16_amd64.deb
gcc-4.6-base_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-base_4.6.2-16_amd64.deb
gcc-4.6-locales_4.6.2-16_all.deb
  to main/g/gcc-4.6/gcc-4.6-locales_4.6.2-16_all.deb
gcc-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-multilib_4.6.2-16_amd64.deb
gcc-4.6-plugin-dev_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6-plugin-dev_4.6.2-16_amd64.deb
gcc-4.6-source_4.6.2-16_all.deb
  to main/g/gcc-4.6/gcc-4.6-source_4.6.2-16_all.deb
gcc-4.6_4.6.2-16.diff.gz
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16.diff.gz
gcc-4.6_4.6.2-16.dsc
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16.dsc
gcc-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gcc-4.6_4.6.2-16_amd64.deb
gccgo-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gccgo-4.6-multilib_4.6.2-16_amd64.deb
gccgo-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gccgo-4.6_4.6.2-16_amd64.deb
gfortran-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gfortran-4.6-multilib_4.6.2-16_amd64.deb
gfortran-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gfortran-4.6_4.6.2-16_amd64.deb
gobjc++-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gobjc++-4.6-multilib_4.6.2-16_amd64.deb
gobjc++-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gobjc++-4.6_4.6.2-16_amd64.deb
gobjc-4.6-multilib_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gobjc-4.6-multilib_4.6.2-16_amd64.deb
gobjc-4.6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/gobjc-4.6_4.6.2-16_amd64.deb
lib32gcc1-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gcc1-dbg_4.6.2-16_amd64.deb
lib32gcc1_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gcc1_4.6.2-16_amd64.deb
lib32gfortran3-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gfortran3-dbg_4.6.2-16_amd64.deb
lib32gfortran3_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gfortran3_4.6.2-16_amd64.deb
lib32go0-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32go0-dbg_4.6.2-16_amd64.deb
lib32go0_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32go0_4.6.2-16_amd64.deb
lib32gomp1-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gomp1-dbg_4.6.2-16_amd64.deb
lib32gomp1_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32gomp1_4.6.2-16_amd64.deb
lib32mudflap0-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32mudflap0-dbg_4.6.2-16_amd64.deb
lib32mudflap0_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32mudflap0_4.6.2-16_amd64.deb
lib32objc3-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32objc3-dbg_4.6.2-16_amd64.deb
lib32objc3_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32objc3_4.6.2-16_amd64.deb
lib32quadmath0-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32quadmath0-dbg_4.6.2-16_amd64.deb
lib32quadmath0_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32quadmath0_4.6.2-16_amd64.deb
lib32stdc++6-4.6-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32stdc++6-4.6-dbg_4.6.2-16_amd64.deb
lib32stdc++6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/lib32stdc++6_4.6.2-16_amd64.deb
libgcc1-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/libgcc1-dbg_4.6.2-16_amd64.deb
libgcc1_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/libgcc1_4.6.2-16_amd64.deb
libgfortran3-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/libgfortran3-dbg_4.6.2-16_amd64.deb
libgfortran3_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/libgfortran3_4.6.2-16_amd64.deb
libgo0-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/libgo0-dbg_4.6.2-16_amd64.deb
libgo0_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/libgo0_4.6.2-16_amd64.deb
libgomp1-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/libgomp1-dbg_4.6.2-16_amd64.deb
libgomp1_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/libgomp1_4.6.2-16_amd64.deb
libmudflap0-4.6-dev_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/libmudflap0-4.6-dev_4.6.2-16_amd64.deb
libmudflap0-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/libmudflap0-dbg_4.6.2-16_amd64.deb
libmudflap0_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/libmudflap0_4.6.2-16_amd64.deb
libobjc3-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/libobjc3-dbg_4.6.2-16_amd64.deb
libobjc3_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/libobjc3_4.6.2-16_amd64.deb
libquadmath0-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/libquadmath0-dbg_4.6.2-16_amd64.deb
libquadmath0_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/libquadmath0_4.6.2-16_amd64.deb
libstdc++6-4.6-dbg_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/libstdc++6-4.6-dbg_4.6.2-16_amd64.deb
libstdc++6-4.6-dev_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/libstdc++6-4.6-dev_4.6.2-16_amd64.deb
libstdc++6-4.6-doc_4.6.2-16_all.deb
  to main/g/gcc-4.6/libstdc++6-4.6-doc_4.6.2-16_all.deb
libstdc++6-4.6-pic_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/libstdc++6-4.6-pic_4.6.2-16_amd64.deb
libstdc++6_4.6.2-16_amd64.deb
  to main/g/gcc-4.6/libstdc++6_4.6.2-16_amd64.deb


Override entries for your package:
cpp-4.6_4.6.2-16_amd64.deb - optional interpreters
fixincludes_4.6.2-16_amd64.deb - optional devel
g++-4.6-multilib_4.6.2-16_amd64.deb - optional devel
g++-4.6_4

gcc-4.6 override disparity

2012-02-26 Thread Debian FTP Masters
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, debug, fonts, gnu-r, gnustep, haskell,
httpd, java, kernel, lisp, localization, ocaml, php, ruby, vcs, video,
xfce, zope.  At this time a script was used to reclassify packages into
these sections.  If this is the case, please only reply to this email if
the new section is inappropriate, otherwise please update your package
at the next upload.

Either the package or the override file is incorrect.  If you think
the override is correct and the package wrong please fix the package
so that this disparity is fixed in the next upload.  If you feel the
override is incorrect then please file a bug against ftp.debian.org and
explain why. Please INCLUDE the list of packages as seen above, or we
won't be able to deal with your request due to missing information.

Please make sure that the subject of the bug you file follows the
following format:

Subject: override: BINARY1:section/priority, [...], BINARYX:section/priority

Include the justification for the change in the body of the mail please.


[NB: this is an automatically generated mail; if you already filed a bug
and have not received a response yet, please ignore this mail.  Your bug
needs to be processed by a human and will be in due course, but until
then the installer will send these automated mails; sorry.]

--
Debian distribution maintenance software

(This message was generated automatically; if you believe that there
is a problem with it please contact the archive administrators by
mailing ftpmas...@debian.org)


-- 
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1s1n8c-av...@franck.debian.org