Don Armstrong <[EMAIL PROTECTED]> wrote: > > I did already explain recisely what the problem is. > > I've read the logs, and I still have no idea what you're talking > about. > > > What information do you need? > > Let me spell it out the process even more clearly: > > 1) Send mail explaining precisely what the problem is.
I already did this. > 2) If the maintainer disagrees, appeal to the tech ctte to override > the maintainer. The maintainer does not seem to be interested in the problem. > If you believe you've done #1 then your only recourse is #2. At no > point does this involve reopening bugs. ???? Are you going to tell me that Debian has no way to deal with malicious or unwilling maintainers? Note that this is the only reason for the cdrtools dispute from Debian. > See http://lists.debian.org/debian-devel/2006/12/msg00303.html for a > recent post "ex cathedra." The current problem is related to this piece of text from you: Maintainers, of course, should not capriciously close bugs or tag or block them nonsensically, and should attempt to explain why they are closing bugs or altering states wherever possible, but regardless of whatever inequities the maintainer has committed, using the control interface to argue with them will only result in your exclusion from it. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED] (uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
