Closing bugs in another developer's package
-----BEGIN PGP SIGNED MESSAGE-----
What's protocol on closing bugs in someone else's package when it's
clear that the bugs were actually fixed (in a maintainer release or by
the circumstances around the bug changing) some time ago but stayed open
in the tracking system? So far my default behavior has been to just
drop a note to the maintainer letting him or her know that the bug can
probably be closed, but what does one do if one can't get in touch with
the maintainer, or gets no response? Should this be documented
somewhere?
=============================================================================
Zed Pobre <zcp@po.cwru.edu> | PGP key on servers, fingerprint on finger
=============================================================================
-----BEGIN PGP SIGNATURE-----
Version: 5.0
Charset: noconv
iQEVAwUBNVTeoNwPDK/EqFJbAQGPmQgArTCccz01M4gQJWDpa97UHum8u40pavzi
8VmuLk0yhnXmQMGC4QWEUuk8ztdPjYsF7kFGAqZGvHVA1fGu6O15RbMdzHnDf8eO
teXwMZ7UWC2RJAhuY57MQOnDSUzj5RYCCRKlcjq5kl1GVDBxl4fF5xuUhSUOQsC/
GQ/6V4al9LsKJjv8eH4KnTMHnZ5Q6pPx6Dr+ggQzpphy2+omFN3UbqW+deI3He9M
Y/H/JcWC7simQ8iHA7xl2dQ1I7LXrevtIARYS+MVomXbok0DNkxwTOfNIsSNzni0
dB/aaZcXY0kVmMdceuKry8gomaCFF+lxIQSxVcCMxnhSGFwIOPB3ZA==
=AM47
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to debian-policy-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: