Hefee <he...@debian.org> writes: >> Why do you insist on keeping broken packages in Debian? > > because pysrs is more than these two scripts - the core part is the python > library supporting handle SRS.
Please read the subject and/or "Package" field before replying. This is what I reported as broken: Package: pysrs-bin Version: 1.0.3-2 Severity: grave Justification: renders package unusable The bug report is against pysrs-bin. This package contains nothing but those two "examples": bjorn@miraculix:~$ apt-file show pysrs-bin pysrs-bin: /usr/bin/envfrom2srs pysrs-bin: /usr/bin/srs2envtol pysrs-bin: /usr/share/doc/pysrs-bin/NEWS.Debian.gz pysrs-bin: /usr/share/doc/pysrs-bin/changelog.Debian.gz pysrs-bin: /usr/share/doc/pysrs-bin/changelog.gz pysrs-bin: /usr/share/doc/pysrs-bin/copyright pysrs-bin: /usr/share/man/man1/envfrom2srs.1.gz pysrs-bin: /usr/share/man/man1/srs2envtol.1.gz >> Sorry. What's the less offensice way to describe broken and untested? > > Just telling it is broken is fine. But saying it is crap and ask directly for > removal is offensive. Sure. Which is one of the reasons I did NOT say that it is crap. I find your usage of such straw-man arguments extremely offensive. "crap" is your description and yours only. Your package is broken. It contains nothing but two broken scripts. This is a simple fact and I don't know how else to express it. "Untested" is my assumption only. and I should probably not have made that. But it's really an assumption of good faith in this context. The only alternative I see is that you're packaging known failing scripts. Removal of a package conaining ONLY broken scripts and nothing else is a no-brainer. It's Debian policy. > I try not to ship broken packages on purpose, but I'm just a human make > mistakes and don't have the time to test everything. Well, that's simple: You do not have to package everything. I do not have time to install, test and then remove broken packages. Assumng that I and other Debian users should do testing for you is arrogant. Your time is not worth more than mine. Reporting this bug wasted even more time. I did that to help other Debian users avoid the same problem. Your package is a policy violation. You have so far not done anything to fix that, which is very disappointing. Bjørn
