Re: Bug#3253: Pine base64 bug
Santiago Vila Doncel <firstname.lastname@example.org> writes:
> > > This "bug" has reached its "final" state: the bug is dead. So
> > > there is nothing more to "track".
> > How do you know that someone won't fix this at some time in the
> > future?
> I am the current maintainer. If you are interested, I will tell you
> if somebody send me a patch. I don't see the point in keeping open
> "just to have something to close" if (by miracle) somebody write a
> patch and send it to me.
I'm sorry you don't see the point. However, you will not be the pine
maintainer for all time, you can not speak for all future pine
maintainers -> you should not close the bug. And as for being a
miracle that somebody would write the patch, I'm sure people would
have said that about #988. The point is you can't know for sure that
no one will fix it -> you should not close the bug.
> Again, we have *much* better things to do. I don't want people
> working on Debian bugs to waste their time on this one and the only
> way to avoid this is closing it.
Why on earth should you be the one to judge if it's wasting someone's
time? If someone wants to spend their time by fixing the bug, that is
*their* prerogative, they do not need to be dictated to by *you*
telling them what they can and can't fix.
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to email@example.com .