This one time, at band camp, icelinux@icelinux.net said: > Quoting Neil Williams <codehelp@debian.org>: > > >If you are going to be the Debian Maintainer for this package, you > >should be able to at least understand error reports from the package > >which is very difficult if you don't understand the interpreter output > >in the case of python. > > Consider the following: > I was of the understanding that the purpose of the unstable version > was to determine if there were bugs in a package which needed to be > corrected before release. Yes, that means it's your job to triage and fix those bugs. > If the software goes into the testing distribution and is found to > contain bugs, then it will have no overall negative impact upon the > Debian release is those bugs are not fixed as the software will be > withheld from the release. Yes, but getting a buggy package into testing is worse than useless - you have added to the overall workload of the release team, and you are not bothering to fix bugs in your own packages. > If the software does not have any bugs or problems then it will have > no overall negative impact as there are no problems. Correct. > If the software is found to have a non-security related bug after > release, according to my understanding Debian only releases security > fixes so this will not be addressed. Correct. > If the software does have a security issue then between the security team > and > the author of the software this should be able to be addressed. No, the security team only does the work when the maintainer cannot be bothered to pick up their own slack. I know that for my packages at least I do the security uploads and that sort of thing. Expecting upstream to do your work for you is just laziness and an unrealistic expectation. > Please inform me of any errors in the aforementioned conclusions and > foreseeable issues which would constitute there actually being a > problem with creating a package to go into the unstable distribution > for testing. The main problem is that you appear to not want to do any of the actual work of maintaining packages you want to take responsibility for. We already have plenty of MIA maintainers, and we certainly don't need more. It's pretty simple, really. If you want to maintain packages in Debian, at least pretend to want to understand the package and pretend to want to support them through a stable release. Saying up front that you're too lazy to do even minimal support isn't winning my support, for what little that's worth. -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : sgran@debian.org | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
Attachment:
signature.asc
Description: Digital signature