Note : you don't need to post to all merged bugs, only the original will do.
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.
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.
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,
except for this bug which appears to be problematic not being dealt with.
