Bug#1008829: pysrs-bin: envfrom2srs and srs2envtol fails with ModuleNotFoundError: No module named 'ConfigParser'
Hefee 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
Bug#1008829: pysrs-bin: envfrom2srs and srs2envtol fails with ModuleNotFoundError: No module named 'ConfigParser'
Control: forwarded -1 https://github.com/sdgathman/pysrs/issues/12 Hey, > 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. > 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. > > It is only the two example scripts, that are not properly ported to Python > > 3. > You are installing known broken examples in $PATH? But why! > > Well, whatever. Thanks for not caring about quality 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. I start asking upstream to create a new version in order to get a fixed package in Debian soon. regards hefee signature.asc Description: This is a digitally signed message part.
Bug#1008829: pysrs-bin: envfrom2srs and srs2envtol fails with ModuleNotFoundError: No module named 'ConfigParser'
Hefee writes: > Control: severity -1 normal Why do you insist on keeping broken packages in Debian? >> # envfrom2srs >> Traceback (most recent call last): >> File "/usr/bin/envfrom2srs", line 14, in >> from ConfigParser import ConfigParser, DuplicateSectionError >> ModuleNotFoundError: No module named 'ConfigParser' >> >> # srs2envtol >> Traceback (most recent call last): >> File "/usr/bin/srs2envtol", line 14, in >> from ConfigParser import ConfigParser, DuplicateSectionError >> ModuleNotFoundError: No module named 'ConfigParser' >> >> No need to clutter the archive with broken and untested packages. >> Please remove > > can you please use a less offensive language. Sorry. What's the less offensice way to describe broken and untested? > It is only the two example scripts, that are not properly ported to Python 3. You are installing known broken examples in $PATH? But why! Well, whatever. Thanks for not caring about quality Bjørn
Bug#1008829: pysrs-bin: envfrom2srs and srs2envtol fails with ModuleNotFoundError: No module named 'ConfigParser'
Control: severity -1 normal Hey, > # envfrom2srs > Traceback (most recent call last): > File "/usr/bin/envfrom2srs", line 14, in > from ConfigParser import ConfigParser, DuplicateSectionError > ModuleNotFoundError: No module named 'ConfigParser' > > # srs2envtol > Traceback (most recent call last): > File "/usr/bin/srs2envtol", line 14, in > from ConfigParser import ConfigParser, DuplicateSectionError > ModuleNotFoundError: No module named 'ConfigParser' > > No need to clutter the archive with broken and untested packages. > Please remove can you please use a less offensive language. It is only the two example scripts, that are not properly ported to Python 3. With a big warning in the top of the file: # Use only if absolutely necessary. It is *very* inefficient and # a security risk. This was fixed upstream, but they not have released a new version. Regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#1008829: pysrs-bin: envfrom2srs and srs2envtol fails with ModuleNotFoundError: No module named 'ConfigParser'
Package: pysrs-bin Version: 1.0.3-2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, # envfrom2srs Traceback (most recent call last): File "/usr/bin/envfrom2srs", line 14, in from ConfigParser import ConfigParser, DuplicateSectionError ModuleNotFoundError: No module named 'ConfigParser' # srs2envtol Traceback (most recent call last): File "/usr/bin/srs2envtol", line 14, in from ConfigParser import ConfigParser, DuplicateSectionError ModuleNotFoundError: No module named 'ConfigParser' No need to clutter the archive with broken and untested packages. Please remove - -- System Information: Debian Release: 11.3 APT prefers stable-security APT policy: (700, 'stable-security'), (700, 'stable'), (699, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-13-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pysrs-bin depends on: ii python3 3.9.2-3 ii python3-srs 1.0.3-2 pysrs-bin recommends no packages. pysrs-bin suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iGwEARECACwWIQR3fjfc8EF8nPbC0aDXSuqSjBsiyQUCYkgktA4cYmpvcm5AbW9y ay5ubwAKCRDXSuqSjBsiyUJdAJ4zvzZBL6hIfzScL01SNMcAQDNSEQCfZZJU9yuy jyC6TtdcMxqBEPpi278= =yarJ -END PGP SIGNATURE-
