Bug#188230: marked as done (bug in xtrlock)

2004-08-08 Thread Debian Bug Tracking System
Your message dated 07 Aug 2004 22:04:19 -0700 with message-id <[EMAIL PROTECTED]> and subject line bug in xtrlock 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

Processed: can't be replicated

2004-08-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tags 249777 + unreproducible Bug#249777: semi: prevents gnus-bonus-el package from configuring There were no tags set. Tags added: unreproducible > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system

Bug#249777: semi: prevents gnus-bonus-el package from configuring

2004-08-08 Thread Thomas Bushnell BSG
I have just done the following with no problems: # apt-get remove gnus-bonus-el gnus # apt-get install semi wl t-gnus # apt-get install gnus-bonus-el with no errors at all. Perhaps this was fixed in a release after the one you have installed (which appears to be 1.14.6+0.20040). Can you try wi

Bug#246486: Debian roleplaying package

2004-08-08 Thread Thomas Bushnell BSG
Are you still planning to take over maintenance of the Debian "roleplaying" package? On May 25 you said you were planning to start working on it. If you no longer intend to adopt the package, please change its status back to orphaned (I would be happy to do that for you if you like). If you d

Bug#261285: Czech translation for lirc (corrected)

2004-08-08 Thread Miroslav Jezbera
Hi, this version contains corrected czech messages for lirc. Regards Miroslav Jezbera # #Translators, if you are not familiar with the PO format, gettext #documentation is worth reading, especially sec

bblaunch segfault patch

2004-08-08 Thread Ovid
Hi, I've no idea to whom I should send this patch nor the procedure for doing so, but when I compiled bblaunch on Red Hat 8, it ran fine, but on Fedora Core 2, it kept segfaulting (no core dump). I tracked down the problem to a bad cast and, as it turns out, the variable in question wasn't eve

Bug#105554: marked as done ([hurd] doesn't build)

2004-08-08 Thread Debian Bug Tracking System
Your message dated 08 Aug 2004 15:13:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line already 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

Bug#195447: marked as done (libarr: FTBFS with gcc-3.3: Varargs problems)

2004-08-08 Thread Debian Bug Tracking System
Your message dated 08 Aug 2004 15:16:01 -0700 with message-id <[EMAIL PROTECTED]> and subject line was accepted 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 t

Bug#227387: marked as done ([installer@ftp-master.debian.org: libarr override disparity])

2004-08-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Aug 2004 18:32:02 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#227387: fixed in libarr 0.1-52 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

Bug#127923: marked as done (libctk3-dev appears to depend on libctk-dev)

2004-08-08 Thread Debian Bug Tracking System
Your message dated 08 Aug 2004 15:30:48 -0700 with message-id <[EMAIL PROTECTED]> and subject line libctk3-dev appears to depend on libctk-dev 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#150235: marked as done (FTBFS: Build failure of libctk on i386)

2004-08-08 Thread Debian Bug Tracking System
Your message dated 08 Aug 2004 15:43:44 -0700 with message-id <[EMAIL PROTECTED]> and subject line accepted by maintainer already 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 responsi

Bug#264459: bblaunch segfaults under Fedora Core 2 (patch)

2004-08-08 Thread Ovid
Package: bblaunch Version: 0.0.3-5 Any attempt to run bblaunch on Fedora Core 2 under Fluxbox results in "Segmentation fault" with no core file. This behavior is consistent regardless of arguments used. [EMAIL PROTECTED] .backups]# uname -a Linux tomis 2.6.5-1.358.8kstacks #1 Sat May 22 21:46

Bug#128058: guppi-gnumeric crashes

2004-08-08 Thread Thomas Bushnell BSG
> Package: libguppi15 > Version: 0.40.2-7 > Severity: important > > On debian ppc sid, I find that guppi-gnumeric crashes when > I try to do the following. > > 1) run gnumeric > 2) enter two columns of three rows of numbers (1,2,3 and 2,4,6) > 3) select these six cells > 4) click on the graph ic

Processing of libarr_0.1-52_powerpc.changes

2004-08-08 Thread Archive Administrator
libarr_0.1-52_powerpc.changes uploaded successfully to localhost along with the files: libarr_0.1-52.dsc libarr_0.1-52.tar.gz libarr-dev_0.1-52_powerpc.deb libarr0_0.1-52_powerpc.deb Greetings, Your Debian queue daemon

Bug#136506: marked as done (Plugins missing.)

2004-08-08 Thread Debian Bug Tracking System
Your message dated 08 Aug 2004 16:21:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line already 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

Bug#148684: marked as done (xmms-singit: xmms startup failed with xmms-singit-0.1.18)

2004-08-08 Thread Debian Bug Tracking System
Your message dated 08 Aug 2004 16:23:54 -0700 with message-id <[EMAIL PROTECTED]> and subject line fixed long ago 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

Bug#187990: marked as done (xmms-singit: All displayer-plugins fail to load)

2004-08-08 Thread Debian Bug Tracking System
Your message dated 08 Aug 2004 16:24:53 -0700 with message-id <[EMAIL PROTECTED]> and subject line long 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

libarr_0.1-52_powerpc.changes ACCEPTED

2004-08-08 Thread Debian Installer
Accepted: libarr-dev_0.1-52_powerpc.deb to pool/main/liba/libarr/libarr-dev_0.1-52_powerpc.deb libarr0_0.1-52_powerpc.deb to pool/main/liba/libarr/libarr0_0.1-52_powerpc.deb libarr_0.1-52.dsc to pool/main/liba/libarr/libarr_0.1-52.dsc libarr_0.1-52.tar.gz to pool/main/liba/libarr/libarr_0.

Processing of libctk_3.0.24.5_powerpc.changes

2004-08-08 Thread Archive Administrator
libctk_3.0.24.5_powerpc.changes uploaded successfully to localhost along with the files: libctk_3.0.24.5.dsc libctk_3.0.24.5.tar.gz libctk3_3.0.24.5_powerpc.deb libctk3-dev_3.0.24.5_powerpc.deb libctk-dev_3.0.24.5_powerpc.deb Greetings, Your Debian queue daemon

libctk_3.0.24.5_powerpc.changes ACCEPTED

2004-08-08 Thread Debian Installer
Accepted: libctk-dev_3.0.24.5_powerpc.deb to pool/main/libc/libctk/libctk-dev_3.0.24.5_powerpc.deb libctk3-dev_3.0.24.5_powerpc.deb to pool/main/libc/libctk/libctk3-dev_3.0.24.5_powerpc.deb libctk3_3.0.24.5_powerpc.deb to pool/main/libc/libctk/libctk3_3.0.24.5_powerpc.deb libctk_3.0.24.5.dsc

Bug#151319: marked as done (xkbd doesn't work with sawfish)

2004-08-08 Thread Debian Bug Tracking System
Your message dated 08 Aug 2004 16:35:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line [Mail Delivery System <[EMAIL PROTECTED]>] Mail delivery failed: returning message to sender has caused the attached Bug report to be marked as done. This means that you claim that the problem has b

Bug#151319: xkbd doesn't work with sawfish

2004-08-08 Thread Thomas Bushnell BSG
> As an ipaq user, I know that xkbd isn't really intended for normal > window managers, but I actually have a real need for it on a real WM on > x86 architecture so I'm reporting this as a bug. > > xkbd under sawfish-gnome 1.0.1.20020116-4 doesn't do a darn thing. It > puts up its keyboard wind

Bug#259258: gnucash: Crashes on startup - guile problem

2004-08-08 Thread Thomas Bushnell BSG
Does this problem still happen for you? I cannot reproduce it on my system, and before I try to investigate further, can you confirm that it is still a problem? > Package: gnucash > Version: 1.8.9-2 > Severity: grave > Justification: renders package unusable > > Hi all, > > I have checked othe

Bug#264473: filerunner: frcolor and frftp refer to missing wish8.0 binary

2004-08-08 Thread Marc Wilson
Package: filerunner Version: 2.5.1-14 Severity: normal I'd just re-open # 190927, which was my own bug, but you can't re-open an archived bug, apparently. Fooey on me for not paying attention when someone closed it without fixing it. Regarding the comment at the end of that bug... the alternativ

Фитнес шорты-миостимулятор ПОВЕР ДЖИМ

2004-08-08 Thread shuhui
Рады предложить Вам прекрасный и беспроигрышный путь преобразить свое тело, подтянуть мыжцы бедер и ягодиц улучшить форму тела, убрать целлюлит ! Спецпредложение ! Бесплатная доставка всем! Подробности на нашем сайте: http://www.pokupki.net

Processed: your mail

2004-08-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > owner 245635 ! Bug#245635: rdiff-backup can't backup files larger than 2GB incrementally Owner recorded as Alec Berryman <[EMAIL PROTECTED]>. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking sy

Bug#245635: marked as forwarded (rdiff-backup can't backup files larger than 2GB incrementally)

2004-08-08 Thread Debian Bug Tracking System
Your message dated Mon, 09 Aug 2004 00:39:01 -0400 with message-id <[EMAIL PROTECTED]> has caused the Debian Bug report #245635, regarding rdiff-backup can't backup files larger than 2GB incrementally to be marked as having been forwarded to the upstream software author(s) [EMAIL PROTECTED] (NB: I