|
Micha,
Thank you for writing, and you are welcome!
See below.
On Monday, October 27, 2014 03:09:06 PM Micha Lenk wrote: > thank you for sharing your experience with compiling kate for Debian > Wheezy. I believe that this really could be of value to someone else, > even if you did not end up with a proper backport so far. > > On 25.10.2014 17:19, Randy Kramer wrote: > > most things seem to work--in particular, the bug fix that I needed > > (which is incorporated in version 4.11.n) is present and works! > > If this bugfix was the only reason why you tried to backport kate, did > you ever consider to only backport the bugfix?
No, I have no idea how to achieve that, and not sure I want to learn (sorry, I am an old codger ;-) But, if you want to point me to some simple explanation, I'll take a look, even an old dog can learn new tricks. ;-)
> I mean this might be much > easier to achieve. And besides that, Debian backports should rather not > be used to fix bugs if they could also get fixed in Debian stable... > > As we are at it already: What bug is it? Does an upstream bug report > exist? Does a Debian bug report exist?
Yes, bug reports exist (I'll have to look for the number in a minute), and the bug was fixed and incorporated in the official kde releases starting with kde 4.11.n. I was on Debian 5.0 until about two months ago, and finally upgraded to Wheezy on a new computer (Debian 7.6)--I expected to find the bug fixed there but it wasn't as Wheezy is still at kde 4.8.4. I had the option to upgrade to testing or to try to backport (iiuc) or compile 4.11.n or greater.
Although I eventually plan to install testing on a computer, I'm not ready at this time, first I want to make sure I have a stable platform for everyday use. (My Debian 5.0 systems (well, only two, my own and one that was my son's) finally died, one at a time, until there were none left...)
The bug is kde/kate bug 112888, at https://bugs.kde.org/show_bug.cgi?id=112888.
Randy Kramer
|