Bug#143129: fixed

2002-04-17 Thread Debian Archive Maintenance
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: aktion | 4:2.2.2-4 | source, alpha, hppa, arm, i386, m68k, mips, mipsel, powerpc, sparc, s390, ia64 dcethreads |2.0.2-6 | source dcl | 20010406-2 | source, all eventfolder

Bug#136263: marked as done (nasm undocumented syntax change in 0.98.08)

2002-04-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Apr 2002 07:32:10 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#136263: fixed in nasm 0.98.28bf-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#136525: marked as done (nasm generates incorrect addresses in certain circumstancesw)

2002-04-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Apr 2002 07:32:10 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#136525: fixed in nasm 0.98.28bf-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#142085: FTBFS: Build failure of voberon on i386

2002-04-17 Thread Colin Watson
reassign 142085 imlib-dev thanks On Wed, Apr 10, 2002 at 01:55:57PM +0900, Junichi Uekawa wrote: voberon fails to build from source on i386, when doing a binary-all build. I am just filing this bug to notify you that I failed to build your package from source, using a very simplistic program

Processed: Re: nasm generates incorrect addresses in certain circumstances

2002-04-17 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: reopen #136525 Bug#136525: nasm generates incorrect addresses in certain circumstancesw Bug reopened, originator not changed. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator

quickppp_1.2.1-1_i386.changes ACCEPTED

2002-04-17 Thread Debian Installer
Accepted: quickppp_1.2.1-1.diff.gz to pool/main/q/quickppp/quickppp_1.2.1-1.diff.gz quickppp_1.2.1-1.dsc to pool/main/q/quickppp/quickppp_1.2.1-1.dsc quickppp_1.2.1-1_i386.deb to pool/main/q/quickppp/quickppp_1.2.1-1_i386.deb quickppp_1.2.1.orig.tar.gz to

dome_4.60-3_i386.changes ACCEPTED

2002-04-17 Thread Debian Installer
Accepted: dome_4.60-3.diff.gz to pool/main/d/dome/dome_4.60-3.diff.gz dome_4.60-3.dsc to pool/main/d/dome/dome_4.60-3.dsc dome_4.60-3_i386.deb to pool/main/d/dome/dome_4.60-3_i386.deb Announcing to debian-devel-changes@lists.debian.org Closing bugs: 6345 Thank you for your contribution

Bug#6345: marked as done (dome: no man pages for dome(1) and dxftopov(1))

2002-04-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Apr 2002 17:02:09 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#6345: fixed in dome 4.60-3 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

langdrill_0.2.1-6_i386.changes ACCEPTED

2002-04-17 Thread Debian Installer
Accepted: langdrill_0.2.1-6.dsc to pool/main/l/langdrill/langdrill_0.2.1-6.dsc langdrill_0.2.1-6.tar.gz to pool/main/l/langdrill/langdrill_0.2.1-6.tar.gz langdrill_0.2.1-6_i386.deb to pool/main/l/langdrill/langdrill_0.2.1-6_i386.deb Announcing to debian-devel-changes@lists.debian.org

Bug#138995: libcw: text entry widget duplicates characters during quick typing

2002-04-17 Thread Colin Watson
On Thu, Mar 28, 2002 at 08:49:23PM -0600, Colin Watson wrote: On Tue, Mar 19, 2002 at 03:06:38AM +, xsdg wrote: I usually type between 60 and 80 words per minute. As I use cooledit to edit my LaTeX documents, I use it quite often. Sometimes, when I press a key in the main text edit

Bug#129919: marked as done (langdrill segfaults with default /etc/langdrillrc)

2002-04-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Apr 2002 20:17:17 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#129919: fixed in langdrill 0.2.1-6 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