As one of the Co-Maintainers of KVIrc, I'd like to give you a short outlook on what is planned for KVIrc in Debian in the near future or at least in the Wheezy release cycle.

• Upload of a 4.0.3 bug fix release to stable-proposed-updates as soon as upstream releases it.
• Packaging a new 4.1.1 snapshot every ten days (that is always after the previous one migrated to Testing) and make ready for 4.1.1 (maybe even 4.2?) in Wheezy.
• Rework the CMake build script of KVIrc to ensure minimal linking. At the moment KVIrc has CMake gather all B-Ds in the global CMakeLists.txt and adds those to all compiler/linker invocations. By pushing the include_directories() calls down to the respective modules and adding just the required variables to the target_link_libraries() invocations, we can improve the situation significantly.
• KVIrc uses a lot of reinvented-the-wheel code, some of this is due to its age (I think KVIrc is around since Qt2 and a lot of stuff wasn't available as an easy-to-use library then). But to be maintainable, KVIrc must move to leaner code base, which can be achieved by replacing such fragments of code with library calls. This is a big task and might not be completed in time for Wheezy, but the effort should be taken nonetheless.

Apart from what is listed above, we, the Debian Maintainers of KVIrc, strive to improve its packaging constantly.

Raúl (another maintainer of KVIrc) asked me to add a request to our users to my previous entry about KVIrc in Debian. So here it is: please report any bugs you find!

Please note, that most of the bugs you find are most likely upstream bugs. If you're sure of this, you can help us by tagging your bug accordingly. This is done by adding Tags: upstream to the pseudo-headers of your e-mail. If you really want to help us, you can also check, if upstream already knows about this bug and add a Forwarded: pseudo header to your e-mail (if you want to report a new bug upstream, you can do so at https://svn.kvirc.de/kvirc/newticket).

For the users of Debian Squeeze we, the KVIrc maintainers, plan to upload the soon-to-be-released upstream bug fix release 4.0.4, packages of RC2 are available. RC2 is most likely going to be identical to the final 4.0.4 release.

The update will be, if the SRMs agree (still need to ask them, but I wanted to wait for the final version before I do that), uploaded to stable-proposed-updates, maybe squeeze-updates and fix a few nasty bugs, which some users might experience, including graphical glitches when used under Gnome (upstream bug #1010), some crashes (e.g. upstream bugs #878, #879, #1093, #1098 and some without bug numbers like r4796), a regression in the Perl scripting support and a lot of translation updates (btw: if you use KVIrc and the translation for your mothertounge is lacking, consider to help! Coordinate your efforts on IRC.)

Apart from that I just uploaded a new SVN snapshot of 4.1 into Sid, the next will follow in about ten days unless you report bugs, which make an earlier upload necessary. ;-)

I've just uploaded a new KVIrc SVN snapshot (r5829) to Unstable. This one took a little longer than the "normal" ten days because the transition of the previous version waited for some other packages to migrate first. This transition might also take longer than we hope for, due to #625607 in EGLIBC, which leads to a segfault in CMake on SPARC.

The stable update to (more or less) upstream's 4.0.4 is also almost ready. We hope for an upload soon.