Bug#247312: konqueror: opening of bookmarks is much slower when clicking directly on Bookmarks menu
On Fri, Jan 07, 2005 at 12:49:17AM +0100, Adeodato Simó wrote:
> * Hervé Eychenne [Fri, 07 Jan 2005 00:18:30 +0100]:
> > > This bug is now 2 months old. Has it been tagged upstream and forwarded
> > > to upstream? That does not seem to me...
> > > Can I ask you a simple question: Why?
> > 247 days after, this question remains the same, and is still unanswered... :-(
> can I ask you a simple question: why haven't done it yourself?
Done what? Forwarded it to KDE people and tagged the bug as upstream,
Simply because I'm not a Debian developper myself, just a simple user,
and mostly because the Debian way of doing things (correct me if I'm wrong)
offers the possibility to report bugs to Debian and let the package
maintainers deal with them whether they are Debian-specific or not.
So, if some Debian maintainers should "refuse" to tag and forward
upstream bugs to upstream, let's all get rid of this upstream tag
everywhere, let's inform users explicitely that they have to deal with
upstream directly, and modify the Debian procedures accordingly.
But until that change is decided/done, if some Debian maintainers are
unable to do this tagging and forwarding within a decent amount of time,
they should really be considered as failling to do their maintainer's
job properly, ok?
Especially since doing such a minor thing would require so little
of their time compared with the average Debian user, as they are supposed
to have a much better understanding of the upstream practices, as well
as things like being aware of known bugs, getting in touch with the
upstream team, be subscribed to adequate upstream mailing-lists, etc.
Without even mentionning being responsible for the good work of the
application they proposed to help with.
So, I did fill this bug to Debian because I could, and because I
(naively) thought it would be a so simple and usual thing for them
Does this bitter response answer your question?
What I would like to understand now is why the Debian counterpart failed
to manage such a simple thing til now (more than 7 months of delay for a
few minutes operation, let's face it).
But frankly, I would prefer that, instead of replying to this post,
any responsible Debian person would step up and take these 2 minutes
of his time to do it at last.