Re: anyone give me some advice about split scim-bridge

2007-08-09 Thread Zhengpeng Hou
2007/8/10, Brian Nelson <[EMAIL PROTECTED]>: > ZhengPeng Hou <[EMAIL PROTECTED]> writes: > > > hi all, > >I've already splited scim-brodge into scom-brodge-agent > >scim-brodge-client-gtk, scim-bridge-client-qt, and scim-bridge(a > >dumy package for upgrade), but now the upstream has ad

Re: anyone give me some advice about split scim-bridge

2007-08-09 Thread Brian Nelson
ZhengPeng Hou <[EMAIL PROTECTED]> writes: > hi all, >I've already splited scim-brodge into scom-brodge-agent >scim-brodge-client-gtk, scim-bridge-client-qt, and scim-bridge(a >dumy package for upgrade), but now the upstream has added qt4 >support, so shall I split it into five? lik

kde4

2007-08-09 Thread Waqar Malik
I've been trying to install kdelibs-bin_3.92.0.dfsg.1-1_i386.deb but it seems to conflict with the kde3.5.7 Can kde4 be installed along side kde3.5.7 or does it require a chroot environment. Currently, I think what kubuntu does is install kde4 in /usr/lib/kde4 and sets up the required environmen

kde4libs_3.92.0.dfsg.1-1_i386.changes ACCEPTED

2007-08-09 Thread Debian Installer
Accepted: kde4libs_3.92.0.dfsg.1-1.diff.gz to pool/main/k/kde4libs/kde4libs_3.92.0.dfsg.1-1.diff.gz kde4libs_3.92.0.dfsg.1-1.dsc to pool/main/k/kde4libs/kde4libs_3.92.0.dfsg.1-1.dsc kde4libs_3.92.0.dfsg.1.orig.tar.gz to pool/main/k/kde4libs/kde4libs_3.92.0.dfsg.1.orig.tar.gz kdelibs-bin_3.92

anyone give me some advice about split scim-bridge

2007-08-09 Thread ZhengPeng Hou
hi all, I've already splited scim-brodge into scom-brodge-agent scim-brodge-client-gtk, scim-bridge-client-qt, and scim-bridge(a dumy package for upgrade), but now the upstream has added qt4 support, so shall I split it into five? likde -agent, -client-gtk -client-qt3, and -client-qt

Bug#426910: #426910 Crash and data loss after applying filters

2007-08-09 Thread Sheldon Hearn
I don't think this bug should block kdepim-3.5.7's inclusion in testing, because it does not represent a regression from 3.5.5. The original submitter claimed that this problem did not occur in kmail-1.9.5 (kdepin-3.5.4), but upstream confirms that the bug was present as early as kmail-1.9.4 (