On Mon, May 23, 2011 at 12:54 AM, Robert Simmons <[email protected]> wrote: > On Sun, May 22, 2011 at 4:18 PM, Harald Sitter <[email protected]> > wrote: >> On Sun, May 22, 2011 at 5:49 PM, Robert Simmons <[email protected]> wrote: >>> Are there plans to update KTorrent and libktorrent to 4.1.1? The >>> version in maverick and natty, 4.0.5, has a crash that leaves a zombie >>> process that prevents KTorrent from being opened again which then >>> requires a reboot to use KTorrent again. Please see >>> https://bugs.kde.org/show_bug.cgi?id=267853 >>> >>> This bug does not appear in 4.1 and the current version is 4.1.1 >> >> Stable release update policies generally disallow that, as there is >> grave regression potential from introducing new feature baring >> versions into a stable release using the regular updates repository. >> >> It could however go into the backports repository, once 4.1 lands in oneiric. >> >> The probably most sensible option would probably be to get an as small >> as possible patch that fixes this particular issue, so that this >> individual bug fix could be deployed via updates to every user. > > Well, I had submitted a bug report to bugs.kde.org about the problem, > and the suggestion was to upgrade to 4.1 because the bug was not > reproducible in that version, which I did and it fixed the problem. I > now have to keep the built-from-source version in /usr/local > > How does something land in oneiric? Is the optimal thing for it to > drop into debian first?
Yes, then we either have to merge it or it will be pulled in automatically (depending on whether we carry ubuntu changes to the debian package, of which I am not sure for ktorrent). > And, once something is there in the dev branch, how does it move into > backports? Someone follows [1] through [1] https://help.ubuntu.com/community/UbuntuBackports#Backport Process -- kubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
