Bug#907915: developers-reference: language in manual
Control: tags -1 patch Is the attached patch acceptable? I verified that OUTOFSYNC_ARCHES is set to null in the latest britney2 source. Thanks, Paul Hardy changes.patches.gz.sig Description: PGP signature changes.patches.gz Description: application/gzip
Bug#907915: developers-reference: language in manual
On 2018-09-04 03:52, Paul Hardy wrote: With Debian presenting itself as a distribution suitable for children in educational environments, please consider removing the "f-bombs" in this package. As a fundamental document in Debian, it is something that should be acceptable for school children to read so adding an "offensive" tag to the package will not be enough to remedy the situation. There are three such occurrences: * Section 5.13.2.1 Out-of-date: please find another term for "architectures that don't keep up", and modify the update_out.py mentioned in that section accordingly. * 5.13.2.4 Influence of packaging in testing: same comment; please use another term for such architectures. For the record, "the update_out.py mentioned" is britney, i.e. the testing migration scripts. The name of the variable mentioned above was changed in production nearly two years ago - see https://salsa.debian.org/release-team/britney2/commit/fe7cc466e18b77493d5b4dade14e5e7a50055680 - so both of these occurences can be resolved by simply updating the documentation to match reality. Regards, Adam
Bug#907915: developers-reference: language in manual
Package: developers-reference Version: 3.4.20 Severity: wishlist With Debian presenting itself as a distribution suitable for children in educational environments, please consider removing the "f-bombs" in this package. As a fundamental document in Debian, it is something that should be acceptable for school children to read so adding an "offensive" tag to the package will not be enough to remedy the situation. There are three such occurrences: * Section 5.13.2.1 Out-of-date: please find another term for "architectures that don't keep up", and modify the update_out.py mentioned in that section accordingly. * 5.13.2.4 Influence of packaging in testing: same comment; please use another term for such architectures. * 6.3.4 Common errors in changelog entries: please remove the fsck joke by finding a different example for "too many acronyms"--or just make up an example to replace that one. It would be nice to make these changes before the buster freeze if possible, so a cleaned-up version gets into stable as soon as possible. Thank you, Paul Hardy
