Bug#742462: kde-workspace-bin: ksystraycmd has no man page
> The bug is reported to stable,
Of course, because that's what I use because I use my computer for
real work and have important data stored. Debian itself recommends:
"If you want to have a secure (and stable) server you are strongly
encouraged to stay with stable."
(https://www.debian.org/security/faq.en.html)
Maybe that's the core of the problem why so many bugs reported to
Debian seem to get ignored. You can't really recommend users to use
stable and report bugs against testing (or unstable?), can't you?
Just for reference, I'm just now upgrading from squeeze to wheezy!
(I planned to do this last year, but I was too lazy, turns out it
was a good decision.) Even now, at 7.4(!), I keep finding new
regressions on a daily basis. (This one, of course, is a minor one,
and probably not a regression, but you asked for it. You can search
for my other reports in the BTS if you want to know. And there are
further issues that I found were already reported and more I'm just
investigating.) All in all, it's been almost a disaster to me, few
bugs (that concern me) were fixed and many new regressions. To think
of trying testing in these circumstances seems absurd to me. (I'm a
developer, but I also need a stable system to use and work on.) At
most, I'll try a few selected packages from testing later this year,
but of course not before I've actually finished upgrading to stable.
> A manpage written in docbook would be welcome,
Well, you know, the reason I was looking for the man page was that I
wanted to find out how to use the program. That hardly puts me in a
position to write one. FWIW, for my particular use case I found what
I needed on the net and using the "--help" output, but that still
doesn't qualify me to document the whole program, don't you think?
Maybe the "--help" output is sufficient. In this case, there's a
useful little too called "help2man". (It even has a Debian package!)
I use it myself for many of my programs since I'm too lazy to write
and maintain separate man pages. Maybe you can use it here too.
> Feel free to forward the bug upstream [1],
Sorry, but isn't this your job as the Debian maintainer? I thought
the workflow was:
* user finds a bug using Debian
* user reports it to the Debian BTS
* Debian maintainer checks whether the bug is due to Debian's
modifications (this happens, not only in ssh ;)
* If so, they fix their patches
* If not, they forward it to upstream
If I'm supposed to forward it to upstream myself why should I use
the DBTS in the first place?
Reply to: