Processed: merge

2003-04-28 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 191145 grave Bug#191145: update-menus: relocation error: update-menus: error when upgrading to gaim0.61-1 Severity set to `grave'. > reassign 191145 libstdc++5 Bug#191145: update-menus: relocation error: update-menus: error when upgrading to

Processed: merge

2003-04-28 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 191149 grave Bug#191149: libstdc++5: The update of libstdc++5 breaks update-menu Severity set to `grave'. > merge 191149 191148 Bug#191148: libstdc++5: relocation errors from /usr/bin/update-menus Bug#191149: libstdc++5: The update of libstdc+

Processed: Re: Processed: merge

2003-04-28 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 191148 grave Bug#191148: libstdc++5: relocation errors from /usr/bin/update-menus Bug#191147: version GLIBCPP_3.2 not defined Severity set to `grave'. > merge 191150 191148 191149 Bug#191148: libstdc++5: relocation errors from /usr/bin/update-

Processed: merge

2003-04-28 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reassign 191150 libstdc++5 Bug#191150: update-menus: relocation error: prevents it and other packages from installing Bug#191151: menu: broken update-menus Bug reassigned from package `menu' to `libstdc++5'. > merge 191150 191148 191149 Bug#191148: li

Processed: merge

2003-04-28 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > merge 191147 191148 Bug#191147: version GLIBCPP_3.2 not defined Bug#191148: libstdc++5: relocation errors from /usr/bin/update-menus Merged 191147 191148. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug trackin

Bug#191147: version GLIBCPP_3.2 not defined

2003-04-28 Thread Anthony L. Awtrey
It turns out that the version changes from GLIBCPP_3.2 to GLIBCPP_3.3 in the symbols when updating from libstdc++5_3.3-0pre5_i386.deb to libstdc++5_3.3-0pre6_i386.deb. We've been hacking around in the IRC channel and have found that going back and holding the pre5 version works for now. Is this

Bug#191149: libstdc++5: The update of libstdc++5 breaks update-menu

2003-04-28 Thread Yannick Roehlly
Package: libstdc++5 Version: 1:3.3-0pre6 Severity: important Tags: sid Hi ! Today, when I apt-get updated my system, I faced a lot of problems. Among them, there were problems with update-menu. These problems come from the update of libstc++5. Without updating this package, everything worked fin

Bug#191147: version GLIBCPP_3.2 not defined

2003-04-28 Thread Alex Romosan
Package: libstdc++5 Version: 1:3.3-0pre6 Severity: important after upgrading libstdc++5, now i get: symbol _ZNSt9basic_iosIcSt11char_traitsIcEE4initEPSt15basic_streambufIcS1_E, version GLIBCPP_3.2 not defined in file libstdc++.so.5 with link time reference this is for every c++ program. on a re

Bug#191148: libstdc++5: relocation errors from /usr/bin/update-menus

2003-04-28 Thread Dave Rolsky
Package: libstdc++5 Version: 1:3.3-0pre6 Severity: important Tags: sid When running /usr/bin/update-menus with the latest libstdc++5 package, I get: /usr/bin/update-menus: relocation error: /usr/bin/update-menus: symbol _ZNSt9basic_iosIcSt11char_traitsIcEE4initEPSt15basic_streambufIcS1_E, versi

Results for 3.3 20030427 (Debian prerelease) testsuite on powerpc-unknown-linux-gnu

2003-04-28 Thread Matthias Klose
LAST_UPDATED: Sun Apr 27 21:48:44 UTC 2003 Native configuration is powerpc-unknown-linux-gnu === g++ tests === Running target unix FAIL: g++.dg/compat/break/bitfield7 y_tst.o compile UNRESOLVED: g++.dg/compat/break/bitfield7 x_tst.o-y_tst.o link UNRESOLVED: g++.dg/compat/break/

Results for 3.3 20030427 (Debian prerelease) testsuite on s390-ibm-linux-gnu

2003-04-28 Thread Matthias Klose
LAST_UPDATED: Sun Apr 27 21:48:44 UTC 2003 Native configuration is s390-ibm-linux-gnu === g++ tests === Running target unix FAIL: g++.dg/compat/break/bitfield7 y_tst.o compile UNRESOLVED: g++.dg/compat/break/bitfield7 x_tst.o-y_tst.o link UNRESOLVED: g++.dg/compat/break/bitfiel

Results for 3.3 20030427 (Debian prerelease) testsuite on ia64-unknown-linux-gnu

2003-04-28 Thread Matthias Klose
LAST_UPDATED: Sun Apr 27 21:48:44 UTC 2003 Native configuration is ia64-unknown-linux-gnu === g++ tests === Running target unix FAIL: g++.dg/parse/crash2.C (test for errors, line 5) FAIL: g++.dg/parse/crash2.C (test for excess errors) FAIL: g++.dg/tls/init-2.C (test for excess

Results for 3.3 20030427 (Debian prerelease) testsuite on i386-pc-linux-gnu

2003-04-28 Thread Matthias Klose
LAST_UPDATED: Sun Apr 27 21:48:44 UTC 2003 Native configuration is i386-pc-linux-gnu === g++ tests === Running target unix FAIL: g++.dg/parse/crash2.C (test for errors, line 5) FAIL: g++.dg/parse/crash2.C (test for excess errors) FAIL: g++.dg/tls/init-2.C (test for excess error

Results for 3.3 20030427 (Debian prerelease) testsuite on alpha-unknown-linux-gnu

2003-04-28 Thread Matthias Klose
LAST_UPDATED: Sun Apr 27 21:48:44 UTC 2003 Native configuration is alpha-unknown-linux-gnu === libjava tests === Running target unix FAIL: initexc execution - gij test FAIL: initexc execution - gij test === libjava Summary === # of expected passes29

Results for 3.3 20030427 (Debian prerelease) testsuite on hppa-unknown-linux-gnu

2003-04-28 Thread Matthias Klose
LAST_UPDATED: Sun Apr 27 21:48:44 UTC 2003 Native configuration is hppa-unknown-linux-gnu === g++ tests === Running target unix FAIL: g++.dg/compat/break/bitfield7 y_tst.o compile UNRESOLVED: g++.dg/compat/break/bitfield7 x_tst.o-y_tst.o link UNRESOLVED: g++.dg/compat/break/bit

Bug#189983: marked as done (libstdc++5: symbol __gnu_cxx::_Atomic_add_mutex missing)

2003-04-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Apr 2003 02:17:59 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#189983: fixed in gcc-3.3 1:3.3ds6-0pre6 has caused the attached Bug report 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

Bug#189424: marked as done (libstdc++5-3.3-doc: dangling symbolic link)

2003-04-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Apr 2003 02:17:59 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#189424: fixed in gcc-3.3 1:3.3ds6-0pre6 has caused the attached Bug report 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

Processed: gcc reports

2003-04-28 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > retitle 188527 [fixed in 3.3] [PR 10427] [3.2/3.3/3.4 regression] Stack > corruption with variable-length automatic arrays and virtual destructors Bug#188527: [PR 10427] [3.2/3.3/3.4 regression] Stack corruption with variable-length automatic arrays a

gcc-3.3_3.3ds6-0pre6_i386.changes ACCEPTED

2003-04-28 Thread Debian Installer
Accepted: cpp-3.3-doc_3.3-0pre6_all.deb to pool/main/g/gcc-3.3/cpp-3.3-doc_3.3-0pre6_all.deb cpp-3.3_3.3-0pre6_i386.deb to pool/main/g/gcc-3.3/cpp-3.3_3.3-0pre6_i386.deb fastjar_3.3-0pre6_i386.deb to pool/main/g/gcc-3.3/fastjar_3.3-0pre6_i386.deb fixincludes_3.3-0pre6_i386.deb to pool/main

gcc-3.3_3.3ds6-0pre6_hppa.changes ACCEPTED

2003-04-28 Thread Debian Installer
Accepted: cpp-3.3_3.3-0pre6_hppa.deb to pool/main/g/gcc-3.3/cpp-3.3_3.3-0pre6_hppa.deb fastjar_3.3-0pre6_hppa.deb to pool/main/g/gcc-3.3/fastjar_3.3-0pre6_hppa.deb fixincludes_3.3-0pre6_hppa.deb to pool/main/g/gcc-3.3/fixincludes_3.3-0pre6_hppa.deb g++-3.3_3.3-0pre6_hppa.deb to pool/main/g

gcc-3.3 override disparity

2003-04-28 Thread Debian Installer
There are disparities between your recently accepted upload and the override file for the following file(s): gcc-3.3_3.3-0pre6_i386.deb: package says priority is standard, override says optional. cpp-3.3_3.3-0pre6_i386.deb: package says priority is standard, override says optional. gcc-3.3-base_