Your message dated Thu, 1 May 2003 02:30:43 +0200
with message-id <[EMAIL PROTECTED]>
and subject line fixed
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 now your responsibility to reopen the
Your message dated Thu, 1 May 2003 02:17:22 +0200
with message-id <[EMAIL PROTECTED]>
and subject line fixed
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 now your responsibility to reopen the
LAST_UPDATED: Tue Apr 29 23:59:54 UTC 2003
Native configuration is s390-ibm-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/eh/forced1.C execution test
FAIL: g++.dg/eh/forced2.C execution test
FAIL: g++.dg/parse/crash2.C (test for errors, line 5)
FAIL: g++.dg/parse
LAST_UPDATED: Tue Apr 29 23:59:54 UTC 2003
Native configuration is powerpc-unknown-linux-gnu
=== g++ tests ===
Running target unix
XPASS: g++.dg/other/packed1.C execution test
FAIL: g++.dg/parse/crash2.C (test for errors, line 5)
FAIL: g++.dg/parse/crash2.C (test for excess err
LAST_UPDATED: Tue Apr 29 23:59:54 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
LAST_UPDATED: Tue Apr 29 23:59:54 UTC 2003
Native configuration is hppa-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/compat/break/bitfield7 x_tst.o compile
UNRESOLVED: g++.dg/compat/break/bitfield7 x_tst.o-y_tst.o link
UNRESOLVED: g++.dg/compat/break/bit
LAST_UPDATED: Tue Apr 29 23:59:54 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
LAST_UPDATED: Tue Apr 29 23:59:54 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
Package: libstdc++5
Version: 3.3-0pre6
Severity: grave
when tryinig to install various programs such as guile, gnucash, emacs etc
the following appears:
dpkg -i guile-1.6_1.6.4-1_i386.deb
(Reading database ... 109846 files and directories currently installed.)
Preparing to replace guile-1.6 1.6.3
Processing commands for [EMAIL PROTECTED]:
> close 191432
Bug#191432: mtr: Install broken.
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to Viral Shah <[EMAIL PROTECTED]>
> merge 191432 191145
Bug#191145: update-menus: relocatio
> Forwarding to the gpc maintainers.
>
> Joel Baker writes:
> > Package: gcc-3.3
> > Version: 1:3.3ds5-0pre5
> > Severity: normal
> >
> > The following is taken from an attempt to build gcc-3.3 on a netbsd-i386
> > box; gcc-3.2 did not fail at this point, and thus, this should probably be
> > con
Processing commands for [EMAIL PROTECTED]:
> reassign 191432 libstdc++5
Bug#191432: mtr: Install broken.
Bug reassigned from package `mtr' to `libstdc++5'.
> severity 191432 grave
Bug#191432: mtr: Install broken.
Severity set to `grave'.
> merge 191432 191145
Bug#191145: update-menus: relocation
J.H.M. Dassen (Ray) writes:
> Package: gcc-3.2
> Version: unclear, perhaps 1:3.2.3-0pre9 ?
> Severity: important
> Tags: upstream
>
> Severity motivation: ice-on-legal-code when building a package that's not
> supposed to percolate to testing (#180052).
>
> Buildd builds of gnumeric 1.1.x on m68k
Adam Warner writes:
> package: treelang-3.3
> version: 3.3-0pre5
>
> Dear GCC developers,
>
> I got lost finding the treelang documentation after also looking through
> /usr/share/doc/treelang-3.3 until I remembered to try "info treelang"
> instead of "man treelang". At least a man page pointing
Michel Dänzer writes:
> Package: gcc-3.2
> Version: 1:3.2.3-0pre9
> Severity: important
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> This version of gcc-3.2 fails randomly, like
>
> {standard input}: Assembler messages:
> {standard input}:20570: Error: value of 7f3ffab00deb1268 too
Ole Laursen writes:
> Matthias Klose <[EMAIL PROTECTED]> writes:
>
> > > Some people have spent quite a lot of time translating GCC messages
> > > into other languages (yeah, I happen to be one of them). But these
> > > translation .mo files don't seem to be included in any of the Debian
> > > pac
Forwarding to the gpc maintainers.
Joel Baker writes:
> Package: gcc-3.3
> Version: 1:3.3ds5-0pre5
> Severity: normal
>
> The following is taken from an attempt to build gcc-3.3 on a netbsd-i386
> box; gcc-3.2 did not fail at this point, and thus, this should probably be
> considered a regression
Package: libstdc++5
Version: 1:3.3-0pre6
Followup-For: Bug #191393
See also debian bug #191387, filed against the 'menu' package, which seems to
stem from the same problem in libstdc++5.
--scott
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux skiffserv 2
Accepted:
cpp-3.3_3.3-0pre7_hppa.deb
to pool/main/g/gcc-3.3/cpp-3.3_3.3-0pre7_hppa.deb
fastjar_3.3-0pre7_hppa.deb
to pool/main/g/gcc-3.3/fastjar_3.3-0pre7_hppa.deb
fixincludes_3.3-0pre7_hppa.deb
to pool/main/g/gcc-3.3/fixincludes_3.3-0pre7_hppa.deb
g++-3.3_3.3-0pre7_hppa.deb
to pool/main/g
Package: libstdc++5
Version: 1:3.3-0pre6
Followup-For: Bug #191393
The packages emacs21 and lilo are also uninstalables in the system
because of a problem with libstdc++.so.5
Preparando para reemplazar lilo 1:22.5.1-2 (usando
.../lilo_1%3a22.5.1-3_i386.deb) ...
Desempaquetando el reemplazo de lil
Package: gcc-3.3
Version: 1:3.3ds5-0pre5
Severity: normal
The following is taken from an attempt to build gcc-3.3 on a netbsd-i386
box; gcc-3.2 did not fail at this point, and thus, this should probably be
considered a regression (as well as a build failure). It is possible to get
an otherwise wor
Processing commands for [EMAIL PROTECTED]:
> reassign 191393 libstdc++5
Bug#191393: lbreakout2 package problem with libstdc++.so.5
Bug reassigned from package `lbreakout2' to `libstdc++5'.
> merge 191393 191145
Bug#191145: update-menus: relocation error: update-menus: error when upgrading
to gai
I just installed epiphany-browser and I got the same error:
epiphany: relocation error: /usr/lib/libclanCore.so.2: symbol
_ZNSt9basicIcSt11char_traitsIcEE4initEPSt15basic_streambufIcS1_E, version
GLIBCPP_3.2 not defined in file libstdc++.so.5 with link time reference
Bcc: Edward Matteucci <[EMAI
Processing commands for [EMAIL PROTECTED]:
> reassign 191390 libstdc++5
Bug#191390: wmweather: update-menus error while setting up wmweather
Bug reassigned from package `wmweather' to `libstdc++5'.
> severity 191390 grave
Bug#191390: wmweather: update-menus error while setting up wmweather
Severi
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#189851: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Your message dated Wed, 30 Apr 2003 03:02:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#191145: fixed in gcc-3.3 1:3.3ds7-0pre7
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
Accepted:
cpp-3.3-doc_3.3-0pre7_all.deb
to pool/main/g/gcc-3.3/cpp-3.3-doc_3.3-0pre7_all.deb
cpp-3.3_3.3-0pre7_i386.deb
to pool/main/g/gcc-3.3/cpp-3.3_3.3-0pre7_i386.deb
fastjar_3.3-0pre7_i386.deb
to pool/main/g/gcc-3.3/fastjar_3.3-0pre7_i386.deb
fixincludes_3.3-0pre7_i386.deb
to pool/main
There are disparities between your recently accepted upload and the
override file for the following file(s):
gcc-3.3-base_3.3-0pre7_i386.deb: package says priority is important, override
says optional.
g++-3.3_3.3-0pre7_i386.deb: package says priority is standard, override says
optional.
gcc-3.3
Processing commands for [EMAIL PROTECTED]:
> reassign 191314 libstdc++5
Bug#191314: abiword no longer runs
Bug reassigned from package `abiword-common' to `libstdc++5'.
> merge 191314 191319
Bug#191314: abiword no longer runs
Bug#191319: menu: relocation error after gcc-3.2 upgrade
Bug#191145: up
Package: libstdc++5-3.3-doc
Version: N/A
Severity: grave
Preparing to replace libstdc++5-3.3-doc 1:3.3-0pre5 (using
.../libstdc++5-3.3-doc_1%3a3.3-0pre6_all.deb) ...
/usr/bin/update-menus: relocation error: /usr/bin/update-menus: symbol
_ZNSt9basic_iosIcSt11char_traitsIcEE4initEPSt15basic_stream
60 matches
Mail list logo
