Processed: raise severity of bug reports filed for libstdc++ allocator changes

2005-11-16 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 339142 serious Bug#339142: library package needs to be renamed (libstdc++ allocator change) Severity set to `serious'. > severity 339143 serious Bug#339143: library package needs to be renamed (libstdc++ allocator change) Severity set to `seri

Bug#339257: library package needs to be renamed (libstdc++ allocator change)

2005-11-16 Thread Matthias Klose
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the archive. The renaming of the library packages can now start. You can upload the packages even before the toolchain is built for all architectures because the packages with the new binary packages will be hold in the NEW queue u

Bug#339229: library package needs to be renamed (libstdc++ allocator change)

2005-11-16 Thread Matthias Klose
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the archive. The renaming of the library packages can now start. You can upload the packages even before the toolchain is built for all architectures because the packages with the new binary packages will be hold in the NEW queue u

libxml-ruby_0.3.4-4_i386.changes ACCEPTED

2005-11-16 Thread Debian Installer
Accepted: libxml-ruby1.8_0.3.4-4_i386.deb to pool/main/libx/libxml-ruby/libxml-ruby1.8_0.3.4-4_i386.deb libxml-ruby_0.3.4-4.diff.gz to pool/main/libx/libxml-ruby/libxml-ruby_0.3.4-4.diff.gz libxml-ruby_0.3.4-4.dsc to pool/main/libx/libxml-ruby/libxml-ruby_0.3.4-4.dsc libxml-ruby_0.3.4-4_all.

Bug#282759: marked as done (libxml-ruby1.8: Why no libxml-ruby package, without a version number?)

2005-11-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Nov 2005 15:42:20 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#282759: fixed in libxml-ruby 0.3.4-4 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 no

Bug#260944: marked as done ([Fwd: libxml-ruby1.8: shouldn't be in section interpreters?])

2005-11-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Nov 2005 15:42:20 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#260944: fixed in libxml-ruby 0.3.4-4 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 no

Bug#336894: marked as done (okle: FTBFS on GNU/kFreeBSD)

2005-11-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Nov 2005 21:02:06 +0100 with message-id <[EMAIL PROTECTED]> and subject line okle: FTBFS on GNU/kFreeBSD 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 respon

Doctors Use This Too IzEj

2005-11-16 Thread Rodolfo Roach
High quality Caiilis available at affordable price. Only $3.99 per tabls which last you 36 hours of e rectiions Try us out today... http://de.geocities.com/Rosalind62381Annissa15276/ f2Gu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAI

Bug#287084: marked as done (New dictionary)

2005-11-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Nov 2005 04:02:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#287084: fixed in skkdic 20051116-1 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