Bug#551496: RM: tork/0.31-2
On Sunday 18 October 2009 17:44:01 Patrick Matthäi wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: rm
>
> Hello,
>
> please remove tork from testing/squeeze.
>
> Reasons:
> 2) Upstream is not very reponsive
Hi - I'm the upstream developer. Guilty as charged. Patrick has been very
supportive of Tork and has put a lot of work into improving it over the
last year or two. I'm afraid I've let him down with his last couple of bug-
reports. It's the usual story of getting sidetracked to other projects.
> 1) It still lacks a Qt4 port
Correct, and this is likely to remain the case for some time. I honestly
don't see myself taking on this task at all in the next year at least.
> and is not very compatible with KDE4
When running KDE 4.2 I would have agreed with this statement. However, I
recently upgraded to KDE 4.3.2 and, lo and behold, Tork works fine with it.
Tork's interaction with Konqueror was completely broken in 4.2, but in
4.3.2 now seems more or less on a par with 3.5 - the KDE series it was
originally written for.
I'm using the KDE 4.3.2 supplied by:
deb http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu jaunty main
So if there are any niggles left I could fix those to maintain complete
interoperability with KDE 4.
> 3) Bug #529908 has become critical, it is a showstopper for inclusion in
> Squeeze. It has to be fixed, before tork may enter squeeze again.
I just responded to that bug - there has been a fix in CVS for a while but
Patrick reported that it did not work for him. It works for me, but my
autofoo is very weak, many levels beneath the know-how that comes with
maintaining packages. So my hope here is that someone can take a look at
that patch and advise on what I'm doing wrong.
http://sourceforge.net/mailarchive/message.php?msg_name=E1MLhzT-0000aQ-7A@ddv4jf1.ch3.sourceforge.com
So in summary:
There won't be a Qt4 based Tork for a long time, if ever. However, Tork
does seem to interoperate with KDE 4.3.2 - so if someone can help with
#529908 and point out any remaining interoperability niggles for me to fix,
Tork could remain a viable debian package.
>
> Upstream CCed.
>
> -- System Information:
> Debian Release: squeeze/sid
> APT prefers unstable
> APT policy: (500, 'unstable'), (200, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 2.6.30-2-amd64 (SMP w/2 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
>
Reply to: