Bug#376975: marked as done (libbluetooth{1,2} transition, please rebuild)

2006-07-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Jul 2006 03:47:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376884: fixed in kdebluetooth 0.99+1.0beta1-12 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 cas

Bug#376884: marked as done (Uninstallable due to libbluetooth transition)

2006-07-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Jul 2006 03:47:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376975: fixed in kdebluetooth 0.99+1.0beta1-12 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 cas

Bug#376884: marked as done (Uninstallable due to libbluetooth transition)

2006-07-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Jul 2006 03:47:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376884: fixed in kdebluetooth 0.99+1.0beta1-12 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 cas

Bug#376429: marked as done (xbuffy: FTBFS: rm: cannot remove `debian/xbuffy/usr/man': No such file or directory)

2006-07-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Jul 2006 03:47:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376429: fixed in xbuffy 3.3.bl.3.dfsg-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

Bug#376975: marked as done (libbluetooth{1,2} transition, please rebuild)

2006-07-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Jul 2006 03:47:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376975: fixed in kdebluetooth 0.99+1.0beta1-12 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 cas

Bug#376900: marked as done (Uninstallable due to libbluetooth transition)

2006-07-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Jul 2006 03:17:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376900: fixed in libopenobex 1.3-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 is now

Bug#350739: #350739: cdrecord status?

2006-07-08 Thread Joerg Schilling
Andreas Barth <[EMAIL PROTECTED]> wrote: > Please see Don's reply. It contains all useful information. Even though > you behave like a Kindergarte would be the right place for you, I'm not > doing total mouthfeeding for you now. As you continue to send irrelevent rants, you are obviously not able

Bug#376973: marked as done (libbluetooth{1,2} transition, please rebuild)

2006-07-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Jul 2006 03:17:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376900: fixed in libopenobex 1.3-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 is now

Bug#377109: Bug#350739: #350739: cdrecord status?

2006-07-08 Thread Joerg Schilling
Don Armstrong <[EMAIL PROTECTED]> wrote: > On Fri, 07 Jul 2006, Joerg Schilling wrote: > > Andreas Barth <[EMAIL PROTECTED]> wrote: > > > Also, as usual, you are ignoring the vital fact that the > > > combination of CDDL and GPL is something between legally dubious > > > and illegal. Of course, yo

Bug#350739: #350739: cdrecord status?

2006-07-08 Thread Andreas Barth
* Joerg Schilling ([EMAIL PROTECTED]) [060708 11:19]: > As you are unable to prove your claims by quoting related parts of written > down rules, you are obviously not trustworthy. Please see Don's reply. It contains all useful information. Even though you behave like a Kindergarte would be the rig

Bug#377295: exim: db_upgrade error during configuration

2006-07-08 Thread Mark Baker
severity 377295 normal thanks Marc Haber wrote: On Fri, Jul 07, 2006 at 02:32:04PM -1000, Ryo Furue wrote: bash# dpkg-reconfigure exim db_upgrade: /var/spool/exim/db/retry.lockfile: unrecognized file type db_upgrade: DB->upgrade: /var/spool/exim/db/retry.lockfile: Invalid argument ba

Processed: Re: Bug#377295: exim: db_upgrade error during configuration

2006-07-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 377295 normal Bug#377295: exim: db_upgrade error during configuration Severity set to `normal' from `grave' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator,

Bug#377295: exim: db_upgrade error during configuration

2006-07-08 Thread Marc Haber
On Fri, Jul 07, 2006 at 02:32:04PM -1000, Ryo Furue wrote: > > bash# dpkg-reconfigure exim > db_upgrade: /var/spool/exim/db/retry.lockfile: unrecognized file type > db_upgrade: DB->upgrade: /var/spool/exim/db/retry.lockfile: Invalid argument > bash# > > I marked this bug as "grave" but I

Bug#350739: #350739: cdrecord status?

2006-07-08 Thread Joerg Schilling
Andreas Barth <[EMAIL PROTECTED]> wrote: > * Joerg Schilling ([EMAIL PROTECTED]) [060707 17:50]: > > You seem not to understand how a constitution works > > > > If you do not follow written rules, you end up in arbitraryness. > > Actually, I'm a debian officer while you are not. It seems that

Bug#350739: #350739: cdrecord status?

2006-07-08 Thread Andreas Barth
* Joerg Schilling ([EMAIL PROTECTED]) [060707 17:50]: > You seem not to understand how a constitution works > > If you do not follow written rules, you end up in arbitraryness. Actually, I'm a debian officer while you are not. It seems that my peer developers actually have some trust in me th

Bug#377286: Mitre ID

2006-07-08 Thread Neil McGovern
Hi there, This has been given a Mitre ID CVE-2006-3458. Please mention this in changelogs. Cheers, Neil -- A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? gpg key - http://www.halon.org.uk/pubkey.txt ; the.earth.li B345BDD3 -- To UNSUBSCRIBE, email to [EMAI

Bug#377300: libxul0d: symbol lookup error: /usr/lib/libxul.so.0d: undefined symbol: JS_SetGCParameter

2006-07-08 Thread Mike Hommey
severity 377300 normal reassign 377300 libmozjs0d merge 377300 376374 tag 376374 pending thanks On Fri, Jul 07, 2006 at 11:19:03PM -0400, Akira Yamanita <[EMAIL PROTECTED]> wrote: > Package: libxul0d > Version: 1.8.0.4-1 > Severity: grave > Justification: renders package unusable > > Epiphany an

Processed: Re: Bug#377300: libxul0d: symbol lookup error: /usr/lib/libxul.so.0d: undefined symbol: JS_SetGCParameter

2006-07-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 377300 normal Bug#377300: libxul0d: symbol lookup error: /usr/lib/libxul.so.0d: undefined symbol: JS_SetGCParameter Severity set to `normal' from `grave' > reassign 377300 libmozjs0d Bug#377300: libxul0d: symbol lookup error: /usr/lib/libxul.

<    1   2