Processed: tag l10n related bugs [4/7]

2004-01-14 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tags 137658 + l10n Bug#137658: russian debconf template file for htdig package There were no tags set. Tags added: l10n > tags 225824 + l10n Bug#225824: Japanese po-debconf template translation (ja.po) Tags were: patch Tags added: l10n > tags 207727 +

Re: KDE 3.1.5 Status Update -- 20040113

2004-01-14 Thread Chris Cheney
On Wed, Jan 14, 2004 at 01:39:12PM -0500, Nathanael Nerode wrote: > Chris Cheney wrote: > >kdelibs > >--- > >m68k - failed - needs retry (waiting on qt-x11-free) > >mips - failed - ICE #226727 > > Please try to find a workaround for this ICE (or help find & fix it). > The GCC developers haven'

kdenonbeta/kdedebian/livecd/packagelist

2004-01-14 Thread Eva Brucherseifer
CVS commit by eva: answered some questions, that kurt added to the file M +12 -2 might_be_removed 1.4 --- kdenonbeta/kdedebian/livecd/packagelist/might_be_removed #1.3:1.4 @@ -4,4 +4,6 @@ dirmngr dhcp # WHY? (is there a replacement?) + this is the

Bug#227802: kmix: tray icon displays absurd volume levels (e.g. 24119703%)

2004-01-14 Thread John Stamp
Package: kmix Version: 4:3.1.5-1 Severity: normal Tags: patch Kmix 3.1.4 and 3.1.5 show ridiculous volume levels until the volume is manually adjusted. See KDE bug #64274. This was fixed upstream on 11/24/03 but won't be available until KDE 3.2 It's a very simple fix, so I attached a patch. A

Re: KDE 3.1.5 Status Update -- 20040113

2004-01-14 Thread Nathanael Nerode
Chris Cheney wrote: kdelibs --- m68k- failed - needs retry (waiting on qt-x11-free) mips- failed - ICE #226727 Please try to find a workaround for this ICE (or help find & fix it). The GCC developers haven't tracked it down yet, which means it may well not be fixed by sarge release

Bug#224339: marked as done (kcontrol: crash on selecting SOCKS library.)

2004-01-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Jan 2004 17:15:55 +0100 with message-id <[EMAIL PROTECTED]> and subject line Fixed in kdelibs 3.1.5 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 responsibil

kdenonbeta/kdedebian/kapture

2004-01-14 Thread Peter Rockai
CVS commit by mornfall: - oops, mixed up files a bit - also, move one of the TODO items to a later version Akapture/kaptureview.h 1.1 [no copyright] M +5 -5 TODO 1.6 Rkapture/kaptureiface.h 1.1 --- kdenonbeta/kdedebian/kapture/TODO #1.5:1.6 @@ -62,9 +

kdenonbeta/kdedebian/kapture

2004-01-14 Thread Peter Rockai
CVS commit by mornfall: - update TODO (domi: please read, maybe adjust) - fix qextmdi.diff (you'll need to reapply) - create initial kmdi interface - implemented PkgGrouperChain: this encapsulates a chain of PkgGrouperFactory's, or of PkgGrouperChain's. This allows for building trees of PkgGr

kdeutils_3.1.5-1_i386.changes is NEW

2004-01-14 Thread Debian Installer
ark_3.1.5-1_i386.deb to pool/main/k/kdeutils/ark_3.1.5-1_i386.deb kcalc_3.1.5-1_i386.deb to pool/main/k/kdeutils/kcalc_3.1.5-1_i386.deb kcharselect_3.1.5-1_i386.deb to pool/main/k/kdeutils/kcharselect_3.1.5-1_i386.deb kdepasswd_3.1.5-1_i386.deb to pool/main/k/kdeutils/kdepasswd_3.1.5-1_i386

Processing of kdeutils_3.1.5-1_i386.changes

2004-01-14 Thread Archive Administrator
kdeutils_3.1.5-1_i386.changes uploaded successfully to localhost along with the files: kdeutils_3.1.5-1.dsc kdeutils_3.1.5.orig.tar.gz kdeutils_3.1.5-1.diff.gz ark_3.1.5-1_i386.deb kcalc_3.1.5-1_i386.deb kcharselect_3.1.5-1_i386.deb kdepasswd_3.1.5-1_i386.deb kdessh_3.1.5-1_i386.deb

Bug#227677: kate: change to Recommends: kregexpeditor

2004-01-14 Thread Christopher L Cheney
Package: kate Version: 4:3.1.5-1 Severity: important Don't forget to change the Recommends: libkregexpeditor to kregexpeditor. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux calc 2.6.0-mm1 #1 SMP Thu Dec 25 17:43:51 CST 2003 i686 Locale: LANG=en_US.UTF-8,

kdepim_3.1.5-1_i386.changes ACCEPTED

2004-01-14 Thread Debian Installer
Accepted: kaddressbook_3.1.5-1_i386.deb to pool/main/k/kdepim/kaddressbook_3.1.5-1_i386.deb kalarm_3.1.5-1_i386.deb to pool/main/k/kdepim/kalarm_3.1.5-1_i386.deb kandy_3.1.5-1_i386.deb to pool/main/k/kdepim/kandy_3.1.5-1_i386.deb karm_3.1.5-1_i386.deb to pool/main/k/kdepim/karm_3.1.5-1_i38

Processing of kdepim_3.1.5-1_i386.changes

2004-01-14 Thread Archive Administrator
kdepim_3.1.5-1_i386.changes uploaded successfully to localhost along with the files: kdepim_3.1.5-1.dsc kdepim_3.1.5.orig.tar.gz kdepim_3.1.5-1.diff.gz kdepim-dev_3.1.5-1_i386.deb kaddressbook_3.1.5-1_i386.deb kalarm_3.1.5-1_i386.deb kandy_3.1.5-1_i386.deb karm_3.1.5-1_i386.deb kd

kdenonbeta/kdedebian/kalternatives

2004-01-14 Thread Juanjo Alvarez
CVS commit by juanjux: TODO M +2 -2 TODO 1.4 --- kdenonbeta/kdedebian/kalternatives/TODO #1.3:1.4 @@ -1,5 +1,5 @@ -* KDE Support (KUniqueApp, Exit confirm dialog, etc) +* KDE Support (KUniqueApp, Exit confirm dialog, .desktop file, etc) * Buttons with icons, where configured -* Abo

kdenonbeta/kdedebian/kalternatives

2004-01-14 Thread Juanjo Alvarez
CVS commit by juanjux: More TODO modification M +1 -1 TODO 1.3 --- kdenonbeta/kdedebian/kalternatives/TODO #1.2:1.3 @@ -1,5 +1,5 @@ * KDE Support (KUniqueApp, Exit confirm dialog, etc) * Buttons with icons, where configured -* About, Help and tooltips +* About, Help and tooltips (

kdenonbeta/kdedebian/kalternatives

2004-01-14 Thread Juanjo Alvarez
CVS commit by juanjux: Changed the TODO (the sys.exit problem is already fixed) M +0 -1 TODO 1.2 --- kdenonbeta/kdedebian/kalternatives/TODO #1.1.1.1:1.2 @@ -1,3 +1,2 @@ -* sys.exit(0) doesn't seems to work here, change it * KDE Support (KUniqueApp, Exit confirm dialog, etc) * But

Bug#209624: marked as done (The package description does not follow Debian policy)

2004-01-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Jan 2004 01:18:26 -0600 with message-id <[EMAIL PROTECTED]> and subject line The package description does not follow Debian policy 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

Bug#209767: marked as done (The package description does not follow Debian policy)

2004-01-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Jan 2004 01:18:26 -0600 with message-id <[EMAIL PROTECTED]> and subject line The package description does not follow Debian policy 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

Bug#209788: marked as done (The package description does not follow Debian policy)

2004-01-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Jan 2004 01:18:26 -0600 with message-id <[EMAIL PROTECTED]> and subject line The package description does not follow Debian policy 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

Bug#209842: marked as done (The package description does not follow Debian policy)

2004-01-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Jan 2004 01:18:26 -0600 with message-id <[EMAIL PROTECTED]> and subject line The package description does not follow Debian policy 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

Bug#210186: marked as done (The package description does not follow Debian policy)

2004-01-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Jan 2004 01:18:26 -0600 with message-id <[EMAIL PROTECTED]> and subject line The package description does not follow Debian policy 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

Bug#209966: marked as done (The package description does not follow Debian policy)

2004-01-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Jan 2004 01:18:26 -0600 with message-id <[EMAIL PROTECTED]> and subject line The package description does not follow Debian policy 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

Bug#209918: marked as done (The package description does not follow Debian policy)

2004-01-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Jan 2004 01:18:26 -0600 with message-id <[EMAIL PROTECTED]> and subject line The package description does not follow Debian policy 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

Bug#210025: marked as done (The package description does not follow Debian policy)

2004-01-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Jan 2004 01:18:26 -0600 with message-id <[EMAIL PROTECTED]> and subject line The package description does not follow Debian policy 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

Bug#209677: marked as done (The package description does not follow Debian policy)

2004-01-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Jan 2004 01:18:26 -0600 with message-id <[EMAIL PROTECTED]> and subject line The package description does not follow Debian policy 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

Bug#209654: marked as done (The package description does not follow Debian policy)

2004-01-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Jan 2004 01:18:26 -0600 with message-id <[EMAIL PROTECTED]> and subject line The package description does not follow Debian policy 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

Bug#209444: marked as done (The package description does not follow Debian policy)

2004-01-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Jan 2004 01:18:26 -0600 with message-id <[EMAIL PROTECTED]> and subject line The package description does not follow Debian policy 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

Bug#209819: marked as done (The package description does not follow Debian policy)

2004-01-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Jan 2004 01:18:26 -0600 with message-id <[EMAIL PROTECTED]> and subject line The package description does not follow Debian policy 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

Bug#209768: marked as done (The package description does not follow Debian policy)

2004-01-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Jan 2004 01:18:26 -0600 with message-id <[EMAIL PROTECTED]> and subject line The package description does not follow Debian policy 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

Bug#209828: marked as done (The package description does not follow Debian policy)

2004-01-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Jan 2004 01:18:26 -0600 with message-id <[EMAIL PROTECTED]> and subject line The package description does not follow Debian policy 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

Bug#209553: marked as done (The package description does not follow Debian policy)

2004-01-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Jan 2004 01:18:26 -0600 with message-id <[EMAIL PROTECTED]> and subject line The package description does not follow Debian policy 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

KDE 3.1.5 Status Update - 20040113

2004-01-14 Thread Chris Cheney
It appears m68k will be holding up KDE as usual. It still has not built qt-x11-free even though it was uploaded on Jan 6. Which means it can't build the rest of KDE until it does. Thanks, Chris arts m68k- failed - needs retry (waiting on qt-x11-free) kdeaddons - not uploaded ye