Hi, On 3/8/06, Filipus Klutiero <[EMAIL PROTECTED]> wrote: > Note : you don't need to post to all merged bugs, only the original will do. i noticed this to, but to late ;)
> Frank Schoolmeesters a écrit : > > >Hi all, > > > >I'm almost shure that this bug is fixed in the new upstream > >release krusader-1.70.0 > >Can someone confirm this? > > > > > > > > > This is probably not an upstream bug, so it would probably not be fixed > by simply uploading the latest upstream version. The original bug report > for this was opened only 3 days after 1.60.0-3.1 entered sid. There have > been 2/3 duplicates opened since. There was no report of this bug during > the > 4 months period when 1.60.0-3 was in unstable. The NMU was done by > someone probably not familiar with the package, sponsoring an > inexperienced contributor, so it's quite certain that the bug was > introduced in the NMU. > The most relevant test to do would be to confirm that the bug is a > regression from 1.60.0-3. The reasons for the NMU can be found here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347126 So the NMU was needed and fall back the the previous package is not a option i guess. afaik a small patch like this, sould not cause an instability like it does now, though i can't test it for the moment, currently i use Sarge and not Sid. > >krusader-1.60.x was never intended (kde3.5 did not exist yet when > >1.60.x was released) > >to work on the current Debian Sid (kde3.5, new qt libs, ...). > >but krusader-1.60.x works great on Debian Sarge (kde 3.3.2) . > >krusader-1.70.0 works great on Debian Sid, > >(it was tested intensively on kde3.3 until kde3.5) > >but there is not yet an official 1.70.0 package available in the > >Debian repository ... > > > > > The use of a newer KDE version shouldn't be a problem, as kdelibs should > be compatible with older versions. Well maybe they are compatible, but sometimes it causes a 100% instability, so you get a 100% unstable/unusable krusader ;) I have seen it in the past on Mandrake, and since Mdk did ask for $ for kde updates, i started to use Debian :-) > >IMHO it's pointless to file bugreports against krusader-1.60.x, > >what we need first is krusader-1.70.0 in the Debian repository. > > > > > > > Of course, it's always ideal to have the latest upstream version in > unstable, but that doesn't happen magically. The maintainer has possibly > been unavailable since about 2 months, but that's not a big problem, i'm afraid it's longer than that, today http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=336169 is 133 days open. > except for this bug which appears to be problematic not being dealt with. > The inofficial krusader-1.70.0 sid deb package is stable, and there is no single unstability issue reported untill now. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=352574 http://krusader.sourceforge.net/phpBB/viewtopic.php?t=1465 http://krusader.sourceforge.net//downloads.php kind regards, Frank Schoolmeesters Krusader Krew http://www.krusader.org
