Bug#897208: cdtool.1: Some fixes of the manual

Package: cdtool Version: 2.1.8-release-5 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Warning about only one argument for the two-fonts macro "IR". The patch is in the attachment. Summary: Input file is cdtool.1 Spelling: give -> given Remove spa

Bug#895964: par.1: Minor correction to the manual

Package: par Version: 1.52-3+b2 Severity: minor Tags: patch Dear Maintainer, Let macro "LP" come before macro "RS" Change ".BI" to ".B" for one argument Request ".ps" does not accept any scale indicator Change "." to ".\&" when the period does not end a sentence Change "!" to "!\&

Bug#895963: diffstat.1: Minor corrections to the manual

Package: diffstat Version: 1.61-1+b1 Severity: minor Tags: patch Dear Maintainer, Input file is diffstat.1 Test nr. 2: Enable and fix warnings from 'test-groff'. :82 (macro BI): only 1 argument, but more are expected :89 (macro BI): only 1 argument, but more are expected :185 (macro BI): only

Bug#895652: gnu-standards: New versions are not found

Package: gnu-standards Version: 2010.03.11-1 Severity: important Dear Maintainer, New versions are not found according to "tracker.debian.org/pkg/gnu-standards". The upstream sources are in "www.gnu.org/prep/standards" -- System Information: Debian Release: buster/sid APT prefers stable-

Bug#895389: patch.1: Minor adjustments to the manual

Package: patch Version: 2.7.6-2 Severity: minor Tags: patch Dear Maintainer, Suggested commit message for "git": Change ".BR" with one argument to ".B". Change the argument of ".BR ." into two by separating the punctuation from the first one. Protect the period (with \&) from being interpret

Bug#894530: run-parts.8: Some tidying of the manual

Package: debianutils Version: 4.8.4 Severity: minor Tags: patch Dear Maintainer, Test nr. 12: Change -- in x--y to \(em (em-dash), or, if an option, to \-\- 55:but don't actually run them. This option cannot be used with --test. 95:.B --arg # Test nr. 27: Split lines longer than 80 char

Bug#894480: ps.1: Some tidying of the manual

Package: procps Version: 2:3.3.12-4 Severity: minor Tags: patch Dear Maintainer, the patch is in the attachment. Input file is ps.1 Test nr. 2: Enable and fix warnings from 'test-groff'. :152 (macro BR): only 1 argument, but more are expected chk_manuals: Output is from: test-groff -b -e -

Bug#894454: xz.1: Some tidying of the manual

Package: xz-utils Version: 5.2.2-1.3 Severity: minor Tags: patch Dear Maintainer, the patch is in the attachment. Input file is xz.1 Test nr. 2: Enable and fix warnings from 'test-groff'. Input file is /tmp/xz.1 :408 (macro BR): only 1 argument, but more are expected :1724 (macro BR): only

Bug#893318: grep.1: Some fixes in the manual

On Tue, Mar 27, 2018 at 03:55:58PM +0200, Santiago R.R. wrote: > Hi Bjarni, > > El 17/03/18 a las 23:15, Bjarni Ingi Gislason escribió: > > Package: grep > > Version: 3.1-2 > > Severity: minor > > Tags: patch > > > > Dear Maintainer, > &g

Bug#894399: gzip.1: Some typographic corrections and cleaning of the manual

Package: gzip Version: 1.6-5+b1 Severity: minor Tags: patch Dear Maintainer, The patch is in the attachment. Test nr. 6: Change two HYPHEN-MINUSES (code 0x055, 2D) to an em-dash (\[em]), if one is intended. An en-dash is usually surrounded by a space, while an em-dash is used without spaces.

Bug#893579: cron.8: Some fixes in the manual

Package: cron Version: 3.0pl1-130 Severity: minor Tags: patch Dear Maintainer, (The patch is in the attachment.) Input file is cron.8 mandoc: cron.8:17:4: STYLE: whitespace at end of input line mandoc: cron.8:19:4: STYLE: whitespace at end of input line mandoc: cron.8:48:16: STYLE: whitespace

Bug#893576: crontab.1: Some fixes in the manual

Package: cron Version: 3.0pl1-130 Severity: minor Tags: patch Dear Maintainer, (The patch is in the attachment.) Input file is crontab.1 mandoc: crontab.1:46:35: STYLE: whitespace at end of input line mandoc: crontab.1:50:56: STYLE: whitespace at end of input line mandoc: crontab.1:52:25: STY

Bug#893575: crontab.5: Some fixes in the manual

Package: cron Version: 3.0pl1-130 Severity: minor Tags: patch Dear Maintainer, (The patch is in the attachment) Input file is crontab.5 mandoc: crontab.5:19:4: STYLE: whitespace at end of input line mandoc: crontab.5:59:14: STYLE: whitespace at end of input line mandoc: crontab.5:61:10: STYLE

Bug#893457: skill.1: Some fixes in the manual

Package: procps Version: 2:3.3.12-4 Severity: minor Tags: patch Dear Maintainers (also sent to pro...@freelist.org), Input file is skill.1 mandoc: skill.1:9:13: WARNING: cannot parse date, using it verbatim: October 2011 mandoc: skill.1:120:2: WARNING: empty block: UR ### Test nr. 20: Us

Bug#893452: kill.1: Some fixes in the manual

Package: procps Version: 2:3.3.12-4 Severity: minor Tags: patch Dear Maintainers (also sent to pro...@freelist.org), (the patch is in the attachment) mandoc: kill.1:36:2: ERROR: skipping unknown macro: .TQ mandoc: kill.1:38:2: ERROR: skipping unknown macro: .TQ mandoc: kill.1:53:2: WARNING: line

Bug#893444: mandoc.1: Some fixes in the manual

Package: mandoc Version: 1.14.3-3 Severity: minor Tags: patch Dear Maintainers (also sent to "schwa...@openbsd.org"), A patch is in the attachment. NO PATCH mandoc: mandoc.1:838:4: STYLE: unterminated quoted argument mandoc: mandoc.1:852:4: STYLE: unterminated quoted argument mandoc: mandoc

Bug#893318: grep.1: Some fixes in the manual

Package: grep Version: 3.1-2 Severity: minor Tags: patch Dear Maintainer, Input file is grep.in.1 Test nr. 2: Enable and fix warnings from 'test-groff'. Input file is /tmp/grep.in.1 :550 (macro BR): only 1 argument, but more are expected :576 (macro BR): only 1 argument, but more are expected

Bug#892516: mg.1: Some cleaning of the manual

Package: mg Version: 20171014-1 Severity: minor Tags: patch Dear Maintainer, Input file is mg.1 Test nr. 2: Enable and fix warnings from 'test-groff'. Input file is /tmp/mg.1 git/groff/build/tmac/doc.tmac:705: backtrace git/groff/build/tmac/doc.tmac:77: backtrace: macro 'doc-parse-args' git/gro

Bug#892421: apropos.1: Some cleaning of the manual

Package: man-db Version: 2.8.2-1 Severity: minor Tags: patch Dear Maintainer, Input file is apropos.1 Test nr. 1: Remove space at end of lines to simplify other automatic tests to improve typesetting. Use "git apply ... --whitespace=fix" to fix extra space issues, or use global configuration "co

Bug#892230: man.1: Some minor typographic changes in the manual

Package: man-db Version: 2.8.2-1 Severity: minor Tags: patch Dear Maintainer, Input file is man.1 Test nr. 1: Remove space at end of lines to simplify other automatic tests to improve typesetting. 173:directive in # Test nr. 2: Enable and fix warnings from 'test-groff'. Input file is /

Bug#890952: pdffonts.1: Minor formatting changes

Package: poppler-utils Version: 0.61.1-2 Severity: minor Tags: patch Dear Maintainer, Input file is pdffonts.1 Test nr. 2: Fix warning from man/groff Test nr. 14: Change a two-fonts macro to an one-font macro. 72:.BI \-subst Input file is /tmp/pdffonts.1 :72 (macro BI): only 1 argument, but m

Bug#890842: xpdf.1: Some formatting improvements in the manual

Package: xpdf Version: 3.04-5 Severity: minor Tags: patch Dear Maintainer, Input file is xpdf.1 Test nr. 2: Fix warning from man/groff :221 (macro BI): only 1 argument, but more are expected chk_manuals: Output is from: test-groff -Tutf8 -b -e -mandoc -rF0 -t -w w -z Test nr. 5: Change

Bug#890478: pidof.8: Some corrections to the manual

Package: sysvinit-utils Version: 2.88dsf-59.10 Severity: minor Tags: patch Dear Maintainer, Test nr. 17: Start an empty line with ".sp 1". 84: # Test nr. 25: Find a repeated word ! 56 --> the ! 81 --> that fixes bug #815 839 from 24 February 2016 # Test nr. 27: Wrong distance betw

Bug#890041: init(8): Some corrections to the manual

Package: sysvinit-core Version: 2.88dsf-59.10 Severity: minor Tags: patch Dear Maintainer, Test nr. 1: Remove space at end of lines. 122:it is signaled by \fBtelinit\fP to change the system's runlevel. 177:tell \fBinit\fP to re-execute itself (preserving the state). No re-examining of #

Bug#890044: whiptail(1): Some corrections to the manual

Package: whiptail Version: 0.52.20-2 Severity: minor Tags: patch Dear Maintainer, Test nr. 1: Remove space at end of lines. 67:these types of dialog boxes are implemented: 83:The dialog box will open with the cursor over the 91:Use full buttons. (By default, 93:uses compact buttons). 96:The

Bug#890008: init(8): Some corrections to the manual

Package: init Version: 1.51 Severity: minor Tags: patch Dear Maintainer, Test nr. 1: Remove space at end of lines. 122:it is signaled by \fBtelinit\fP to change the system's runlevel. 177:tell \fBinit\fP to re-execute itself (preserving the state). No re-examining of # Test nr. 2: Fix

Bug#889865: bash(1): Some corrections in the manual

Package: bash Version: 4.4-5 Severity: minor Tags: patch Dear Maintainer (Debian and upstream), The result of some tests. The patch is in the attachment. Test nr. 1: Remove space at end of lines. 413:does not attempt to read any other startup files. 1391:Expands to the current option flags

Bug#883129: ntpdate: Wrong evaluation of an invalid option

Package: ntpdate Version: 1:4.2.8p10+dfsg-5 Severity: minor Dear Maintainer, * What led up to the situation? Strange string "rsion" in the output. * What exactly did you do (or not do) that was effective (or ineffective)? command: ntpdate --version * What was the outcome of this

Bug#880706: Warnings about statements that might fall through

Package: bison++ Version: 1.21.11-4+b1 Severity: minor Dear Maintainer, * What led up to the situation? Compilation of "groff" * What was the outcome of this action? Some warnings from the compiler. This should be fixed, or if correct, an explanation should be added to the correspondi

Bug#871310: gcc.1: Some point size changes are wrong in the manual

Package: gcc-6-doc Version: 6.3.0-1 Severity: normal Tags: patch Dear Maintainer, * What led up to the situation? "man gcc" with MAN_KEEP_STDERR=yes MANOPT=--encoding=latin1 --no-hyphenation --warnings=w --no-justification MANWIDTH=80 * What was the outcome of this action? :3310: warnin

Bug#871225: Man.pm: False point size changes

Package: perl-modules-5.26 Version: 5.26.0-5 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? "man gcc" with MAN_KEEP_STDERR=yes MANOPT=--encoding=latin1 --no-hyphenation --warnings=w --no-justification MANWIDTH=80 * What was the outcome of this action? :3310

Bug#869733: ispell.1X: Fix some formatting and textual matters

Package: ispell Version: 3.4.00-6 Severity: minor Tags: patch Dear Maintainer (Debian and upstream), * What led up to the situation? Saw a word repeted ### Input file is ispell.1X Remove space at end of lines. 521:.I ispell 795:then the line contains a '+', a space, and the root word.

Bug#869252: Xserver.1: Fix two warnings and some textual and formatting issues

Package: xserver-common Version: 2:1.19.3-2 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Warnings from "nroff" (in "man"). ### Fix warnings from "nroff/groff": :540: warning [p 8, 2.8i]: can't break line :586: warning [p 8, 10.3i, div `an-div', 0.0i]: can'

Bug#869248: xterm.1: Fix two warnings and some textual and formatting issues

Package: xterm Version: 330-1 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Warnings from "nroff". ### Changes in the patch: Remove space at end of lines. Fix warning from man/groff :64: warning: number register `.I' not defined :5034: warning: number

Bug#867857: man: Two "--no-..." options destroy information about needed preprocessors

Package: man-db Version: 2.7.6.1-2 Severity: normal Dear Maintainer, * What led up to the situation? man groff_diff * What was the outcome of this action? Saw "delim $$" in the output * What outcome did you expect instead? Correct display of equations. ### The options '--n

Bug#863921: man -mandoc: A missing character is not reported on standard error

The cause of this error is that "man" converts the input to "UTF-8" although the output expects "latin1" (iso-8859-1). So the character \[la] gets the code u27E8, which does not exist in the used font. INPUT FILE: .TH angle-test 1 2017-07-06 .pl 5 .fchar \[la] < Angle test with character \e[la

Bug#865584: Manuals: Remove blanks at the end of lines

Package: e2fsprogs Version: 1.43.4-2 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? "groff" and "man" were given the freedom of speach (-ww, MAN_KEEP_STDERR=yes) and spoke up. One kind of an error suggests that others might be there. * What exactly did you

Bug#863921: man -mandoc: A missing character is not reported on standard error

Package: man-db Version: 2.7.6.1-2 Severity: normal Dear Maintainer, * What led up to the situation? Seeing '?' and '??' around some words * What exactly did you do (or not do) that was effective (or ineffective)? Running "man -mandoc groff_mdoc" * What was the outcome of th

Bug#863920: man -d -l : too many irrelevant lines are output

Package: man-db Version: 2.7.6.1-2 Severity: minor Dear Maintainer, about the output of "man -d -l ". The location of the is already known. There are so many irrelevant lines about where the location of the input file could be, that it makes it more difficult and time consuming to spot r

Bug#863437: grep(1): The string "\*(Dt" is not defined

Package: grep Version: 2.27-2 Severity: minor "[gn]roff" (inside "man") reported: :23: warning: macro `Dt' not defined The 23th line is: .TH GREP 1 \*(Dt "GNU grep 2.27" "User Commands" The parent-line in the source file "grep.1.in" is: .TH GREP 1 @UPDATED@ "GNU grep @VERSION@" "User Co

Bug#847972: man: Eliminate warnings from '*roff' about the undefined register 'F'

On Sat, Dec 17, 2016 at 11:24:57AM -0800, Russ Allbery wrote: > Colin Watson writes: > > > I can see that that is attempting to avoid a warning. However, it is > > not quite correct. It should probably be something like this instead: > > > .if !r F .nr F 0 > > > I think ".if !\nF .nr F 0" i

Bug#847972: man: Eliminate warnings from '*roff' about the undefined register 'F'

On Wed, Dec 14, 2016 at 12:09:37AM +, Colin Watson wrote: > On Tue, Dec 13, 2016 at 11:17:18PM +0000, Bjarni Ingi Gislason wrote: > > On Mon, Dec 12, 2016 at 06:40:21PM -0800, Russ Allbery wrote: > > > Apologies for the regression; this is the confluence of two things that

Bug#847972: man: Eliminate warnings from '*roff' about the undefined register 'F'

On Mon, Dec 12, 2016 at 06:40:21PM -0800, Russ Allbery wrote: > Bjarni Ingi Gislason writes: > > > 1) The comment is wrong, because the code was changed from what it > > originally was (in my patch in the original bug report; see the last > > line of my input in the fir

Bug#847972: man: Eliminate warnings from '*roff' about the undefined register 'F'

On Mon, Dec 12, 2016 at 06:39:58PM +, Colin Watson wrote: > Control: reassign -1 perl-modules > > [CCing Russ as upstream for podlators.] > > On Mon, Dec 12, 2016 at 05:07:29PM +0000, Bjarni Ingi Gislason wrote: > >* What led up to the situation? > >

Bug#847972: man: Eliminate warnings from '*roff' about the undefined register 'F'

Package: man-db Version: 2.7.5-2 Severity: minor Dear Maintainer, * What led up to the situation? A warning was issued. * What exactly did you do (or not do) that was effective (or ineffective)? For example "man perl" with "MAN_KEEP_STDERR=yes" * What was the outcome of this

Bug#544317: closed by Andreas Henriksson (Re: wall: outputs "ÿ" (0xFF) as "\377")

On Sun, Nov 06, 2016 at 09:09:04AM +, Debian Bug Tracking System wrote: [...] > > As just discussed in http://bugs.debian.org/826596 it seems the output > is printed as escaped ascii codes when the locale (on the receiving side) > does not consider a character printable. > Not the locale,

Bug#843447: wall: Too many warnings from the compiler

Source: util-linux Version: 2.28.2-1 Severity: normal Tags: upstream Dear Maintainer, * What led up to the situation? A bug in the output of "wall" as the letter "ÿ" was output as '\377'. * What exactly did you do (or not do) that was effective (or ineffective)? Compiled the sou

Bug#822168: The manual for bash: A long word cannot be adjusted to both margins

More environmental variables are needed: export MANWIDTH=80 export MAN_KEEP_STDERR=y -- Bjarni I. Gislason

Bug#822168: The manual for bash: A long word cannot be adjusted to both margins

Package: bash Version: 4.3-14+b1 Severity: normal Tags: patch Dear Maintainer, * What led up to the situation? MANOPT=--no-hyphenation --warnings=w man bash * What exactly did you do (or not do) that was effective (or ineffective)? gunzip -c /usr/share/man/man1/bash.1.gz | groff -T

Bug#669053: smartd.conf.5.in, version 5.42: Escape before "<" and ">", spaces and orthography in the manual.

On Mon, Feb 01, 2016 at 10:47:23AM +, Jonathan Dowland wrote: > On Sat, Jan 30, 2016 at 09:47:25PM +0000, Bjarni Ingi Gislason wrote: > > On Fri, Jan 29, 2016 at 04:40:19PM +, Jonathan Dowland wrote: > > > Hi, thanks for getting back in touch. > > > > > &g

Bug#669053: smartd.conf.5.in, version 5.42: Escape before "<" and ">", spaces and orthography in the manual.

On Fri, Jan 29, 2016 at 04:40:19PM +, Jonathan Dowland wrote: > Hi, thanks for getting back in touch. > > I'm hoping to carry this patch in the next smartmontools upload. Somebody > needs > to refresh it as ~50% of the hunks no longer apply to the current > smartd.conf.5. > I can make a n

Bug#669053: smartd.conf.5.in, version 5.42: Escape before "<" and ">", spaces and orthography in the manual.

On Mon, Jan 25, 2016 at 11:50:56AM +, Jonathan Dowland wrote: [...] > This is a substantial amount of the patch (in lines-changed terms). > Is there a technical reason for this? Yes. In man-pages the technical issue is to have every sentence begin on a new line or (worse) sentences are separ

Bug#812810: fill-paragraph: Leaves a space at the end of the paragraph

Package: mg Version: 20150323-2+b1 Severity: normal Dear Maintainer, * What led up to the situation? Writing some lines that all started on a new line, following recommendations for writing man-pages. * What exactly did you do (or not do) that was effective (or ineffective)? App

Bug#809758: reportbug: Adding an attachment with it adds an extra line at the top so the mail is rejected

Package: reportbug Version: 6.6.3 Severity: normal Dear Maintainer, * What led up to the situation? "reportbug" puts this in front of my report when it is used to incorporate attachment: This is a multi-part MIME message sent by reportbug. --===0054729797023488166== Content-T

Bug#809754: docbook-xsl: manpages: Misuse of "no-break space" causes overlong lines

Package: docbook-xsl Version: 1.78.1+dfsg-1 Severity: normal Tags: patch This is related to Debian bug #569828, which is number 1120 upstream. Dear Maintainer, * What exactly did you do (or not do) that was effective (or ineffective)? For example "man usb_copy_descriptors". Manual

Bug#809184: "aptitude changelog" aborts with "Illegal instruction"

On Mon, Dec 28, 2015 at 10:25:07AM +0800, Paul Wise wrote: > On Mon, 28 Dec 2015 01:57:25 +0000 Bjarni Ingi Gislason wrote: > > >   aptitude changelog apt ... > > Does this always produce the same outcome? > Yes, at least three times. > >   Output was "Il

Bug#809184: "aptitude changelog" aborts with "Illegal instruction"

Package: aptitude Version: 0.7.5-3 Severity: important Dear Maintainer, * What led up to the situation? aptitude changelog apt ... * What was the outcome of this action? Output was "Illegal instruction" with a return value of 132. -- System Information: Debian Release: stretch/sid

Bug#808999: init.d/bootlogd: Last two lines are missing from the log

Package: bootlogd Version: 2.88dsf-59 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Checking the file /var/log/boot * What exactly did you do (or not do) that was effective (or ineffective)? The usual last line "[] Stopping boot logger: bootlog

Bug#803519: lintian: Search for the string "legal" in every file, as it is gererally misused

On Sat, Oct 31, 2015 at 06:12:53PM -0700, Russ Allbery wrote: > Bjarni Ingi Gislason writes: > > > It is not enough to check just the Debian part of a package. The > > part that comes from upstream should be scrutinized. > > If you want to try to teach various u

Bug#803519: lintian: Search for the string "legal" in every file, as it is gererally misused

On Fri, Oct 30, 2015 at 05:54:35PM -0700, Russ Allbery wrote: > Axel Beckert writes: > > > I'd restrict it to packaging (i.e. the debian/ directory) and explicitly > > exclude the file debian/copyright as any appearance of the word "legal" > > or "illegal" in there is very likely a valid (sic!) u

Bug#803712: man.1: Explain the option "-w" better

Package: man-db Version: 2.7.0.2-5 Severity: wishlist Dear Maintainer, The command "man -w man" shows only one location but there are more. /usr/share/man/man1/man.1.gz The same applies to "groff", "hostname", "locale", and "time". The manual explains the option "-w" thus: Don't actuall

Bug#803519: lintian: Search for the string "legal" in every file, as it is gererally misused

On Sat, Oct 31, 2015 at 01:02:00AM +0100, Axel Beckert wrote: > Him > > Bjarni Ingi Gislason wrote: > > The word "(il)legal" is too often used in a wrong sense, both in > > documentation, diagnostic messages, and in a code as a part of a name > > of an ident

Bug#803607: smbios-utils: Too long lines are in the "copyright" file

Package: smbios-utils Version: 2.2.28-2 Severity: minor Dear Maintainer, Lines longer than 80 characters in the file "/usr/share/doc/smbios-utils/copyright" are: copyright: line 130 length 238 copyright: line 134 length 159 copyright: line 137 length 88 copyright: line 138 leng

Bug#803609: libsmbios2: There are too long lines in the "copyright" file

Package: libsmbios2 Version: 2.2.28-2 Severity: minor Dear Maintainer, In the file "/usr/share/doc/libsmbios2/copyright" the indicated lines are too long (longer than 80 characters): copyright: line 130 length 238 copyright: line 134 length 159 copyright: line 137 length 88 copyrig

Bug#803608: python-libsmbios: There are too long lines in the "copyright" file

Package: python-libsmbios Version: 2.2.28-2 Severity: minor Dear Maintainer, Lines that are longer than 80 characters are in the file "/usr/share/doc/python-libsmbios/copyright": copyright: line 130 length 238 copyright: line 134 length 159 copyright: line 137 length 88 copyright:

Bug#803518: lintian: "(il)legal" is used in a wrong sense in the "checks"-directory

Package: lintian Version: 2.5.30+deb8u4 Severity: minor Dear Maintainer, The general fact is mentioned in the GNU Coding Standard. An appropriate word is (in)valid. Examples from "/usr/share/lintian/": checks/files.desc:Tag: run-parts-cron-filename-contains-illegal-chars checks/fields.d

Bug#803519: lintian: Search for the string "legal" in every file, as it is gererally misused

Package: lintian Version: 2.5.30+deb8u4 Severity: wishlist Dear Maintainer, The word "(il)legal" is too often used in a wrong sense, both in documentation, diagnostic messages, and in a code as a part of a name of an identifier. This should be changed to a correct name, like "(in)valid", whi

Bug#803339: dash: Use "invalid" instead of "illegal"

Package: dash Version: 0.5.7-4+b1 Severity: minor Dear Maintainer, * What led up to the situation? A bug in a script. * What exactly did you do (or not do) that was effective (or ineffective)? Run the script. * What was the outcome of this action? A diagnostic message wit

Bug#801483: The environmental variable 'TMPDIR' is made unset by "lintian"

On Sun, Oct 18, 2015 at 09:42:39PM +, Bjarni Ingi Gislason wrote: > On Wed, Oct 14, 2015 at 03:14:43PM +0200, Jakub Wilk wrote: > > * Bjarni Ingi Gislason , 2015-10-11, 01:52: > > > * What outcome did you expect instead? > > > > > > That the environmental

Bug#801483: The environmental variable 'TMPDIR' is made unset by "lintian"

On Wed, Oct 14, 2015 at 03:14:43PM +0200, Jakub Wilk wrote: > * Bjarni Ingi Gislason , 2015-10-11, 01:52: > > * What outcome did you expect instead? > > > > That the environmental variable "TMPDIR" retains its value. > > Lintian sanitizes environment when

Bug#801483: The environmental variable 'TMPDIR' is made unset by "lintian"

Package: lintian Version: 2.5.30+deb8u4 Severity: important Dear Maintainer, * What led up to the situation? Seeking an error that came when executing "lintian". * What exactly did you do (or not do) that was effective (or ineffective)? The folowing simple script shows the error

Bug#801482: The name of a programme, from which an error message comes, is missing in the lintian's message

Package: lintian Version: 2.5.30+deb8u4 Severity: important Dear Maintainer, * What led up to the situation? Seeking an error that came when executing "lintian" * What exactly did you do (or not do) that was effective (or ineffective)? The folowing simple script shows the error:

Bug#801432: The word "parameter" is used in an error message instead of "variable"

Package: dash Version: 0.5.7-4+b1 Severity: minor Dear Maintainer, * What led up to the situation? Figuring out an error in "lintian". * What exactly did you do (or not do) that was effective (or ineffective)? Issuing the script #!/bin/dash set -u unset TMPDIR echo TMPDIR is $

Bug#801261: man: the return value is zero instead of three, when "groff" exits with a non-zero value

Package: man-db Version: 2.7.0.2-5 Severity: normal Dear Maintainer, * What led up to the situation? Added an ".ab " line to a man-page. * What exactly did you do (or not do) that was effective (or ineffective)? issued "man " or "man -l " * What was the outcome of this actio

Bug#801241: man: The option -Z prevents the output of error messages

Package: man-db Version: 2.7.3-1 Severity: normal Dear Maintainer, * What led up to the situation? On the web-page "lintian.debian.org", tag "manpage-has-errors-from-man" an example with this option is presented * What exactly did you do (or not do) that was effective (or ineffecti

Bug#792297: /proc/cgroup: Columns are not aligned

Package: linux-source-3.16 Version: 3.16.7-ckt11-1 Severity: minor Dear Maintainer, Columns should be aligned Content of /proc/cgroups: #subsys_namehierarchy num_cgroups enabled cpuset 0 1 1 cpu 0 1 1 cpuacct 0 1 1 memory 0 1

Bug#660790: lsb-base: log_warning_msg does not respect leading spaces;

tags patch On Wed, Mar 07, 2012 at 11:21:37AM +0100, Didier 'OdyX' Raboud wrote: > tags 660790 +wontfix > thanks > > Hi Luca, and thanks for your bugreport, > > Le 21.02.2012 22:42, Luca Capello a écrit : > > > > As you can see, the leading space is not respected. I think this is > > because lo

Bug#791511: hwclock.sh: Use 'sed' instead of 'head' and 'tail' (which are in the '/usr/bin/' directory)

Package: util-linux Version: 2.25.2-6 Severity: normal Dear Maintainer, * What led up to the situation? This is an old bug. In the file "/etc/init.d/hwclock.sh" "head" and "tail" are not available if "/usr" is not on the mounted root partition. Use "sed" instead, for example sed

Bug#789219: "man" does not adjust line numbers when it adds lines

Package: man-db Version: 2.7.0.2-5 Severity: normal Tags: upstream Dear Maintainer, * What led up to the situation? Greater line numbers were shown for lines in error when some options were used with "man". ### When "man" adds lines to the input stream, the line numbers of the output ar

Bug#789218: Did not check for the existence of a mount point /sys/fs/selinux

Package: libselinux1 Version: 2.4-1 and 2.3-2 Severity: normal Tags: upstream Dear Maintainer, * What led up to the situation? 1) A panic in the kernel >=4.0 in the booting process 2) An line on the screen that was neither in the "kern.log" nor "boot". # This error could be a cause f

Bug#779885: info: Does not display a info-file from the start, if it contains (some) multibyte characters

Package: info Version: 5.2.0.dfsg.1-6 Severity: normal Dear Maintainer, * What led up to the situation? Issuing command "info coreutils". * What was the outcome of this action? Output from "info coreutils" begins with chapter 2.14. Output from "info wdiff" begins with chapter 2.1.

Bug#779795: debian/tarman: fix warnings from "groff" about escaped "equals sign" (\=)

Package: tar Version: 1.27.1-2+b1 Severity: minor Tags: patch (The bug about empty lines is also mentioned in bugs 711725, 720877, and 766016) Dear Maintainer, * What led up to the situation? Warnings from "man --warnings=w --no-justification tar" with MANOPT=--no-hyphenation --warning

Bug#765426: umount; floppy light and humming still present after "umount" and even after "shutdown"

On Mon, Nov 24, 2014 at 06:41:39PM +, Bjarni Ingi Gislason wrote: > On Sat, Oct 25, 2014 at 03:30:01PM +0100, Ben Hutchings wrote: > > On Fri, 2014-10-17 at 00:02 +0000, Bjarni Ingi Gislason wrote: > > > On Wed, Oct 15, 2014 at 12:06:06AM +, Debian Bug Tracking S

Bug#775144: 50-udev-default.rules: A line for permissions for "/dev/fd[0-9]" is missing

On Sun, Jan 11, 2015 at 10:57:53PM +, Bjarni Ingi Gislason wrote: ... > is removed (except for items "floppy") as this is crazy; adding about > 60700 lines of text which have no obvious relevance for this bug. If The named number actually applies to the number of bytes.

Bug#775144: 50-udev-default.rules: A line for permissions for "/dev/fd[0-9]" is missing

Package: udev Version: 215-8 Severity: normal Tags: patch Dear Maintainer, * What led up to the situation? Reading a floppy in a built-in drive * What was the outcome of this action? Read access was denied for a regular user in group "floppy" * What outcome did you expect instead

Bug#774597: bash(1), insure definition of "FN", "zZ", and "zY", and splitting of long strings

Package: bash Version: 4.3-11+b1 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Issuing "man bash" # "man" is a script. * What was the outcome of this action? Some warnings from "nroff" or "groff". * What outcome did you expect instead? Free of er

Bug#773077: man: symbol lookup error if owned by user "root"

This behaviour was caused by the "LD_LIBRARY_PATH" variable, that contained "/usr/local/lib/". An older version "libpipeline.so.1.2.1" was there, so it has been used until now. -- Bjarni I. Gislason -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "uns

Bug#773077: man: symbol lookup error if owned by user "root"

Package: man-db Version: 2.7.0.2-4 Severity: important Dear Maintainer, * What led up to the situation? I changed the owner of "/usr/bin/man" and /usr/bin/mandb" from "man" to "root" with "dpkg-reconfigure man-db" (answered the question about "setuid man" with no). * What exactly did y

Bug#765426: umount; floppy light and humming still present after "umount" and even after "shutdown"

On Sat, Oct 25, 2014 at 03:30:01PM +0100, Ben Hutchings wrote: > On Fri, 2014-10-17 at 00:02 +0000, Bjarni Ingi Gislason wrote: > > On Wed, Oct 15, 2014 at 12:06:06AM +, Debian Bug Tracking System wrote: > > > Thank you for filing a new Bug

Bug#770100: 'apt-get' sends a question to the standard output instead of '/dev/tty'

Package: apt Version: 1.0.9.3 Severity: normal Dear Maintainer, * What led up to the situation? Sending the output of 'apt-get' to a file instead of using 'script'. * What exactly did you do (or not do) that was effective (or ineffective)? apt-get upgrade > /tmp/upgrade * Wh

Bug#770097: util-linux: "whereis this" should deliver empty output, if "this" is not found

Package: util-linux Version: 2.25.2-2 Severity: minor Dear Maintainer, "whereis something" outputs something: This output contains no (new) information, so it is more informative to have it empty. Empty output is what (a user of) the philosophy of Unix-like operating systems expect. It

Bug#769584: Do not change the format of the subject line when it continues on the next line

Package: reportbug Version: 6.6.0 Severity: minor Dear Maintainer, * What led up to the situation? The header line "Subject" is changed into quoted printable when the line is continued on the second line ('folded'), even if the text is pure US-ASCII. This makes the copy of the mail less

Bug#766562: PCMCIA: A 64 k modem blocks output and the keyboard

Package: linux-source-3.2 Version: 3.2.63-1 Severity: normal This is a multi-part MIME message sent by reportbug. --===1378243998== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Dear Maintainer, * What

Bug#766113: man-db: "man -a" sends a (interactive) message to standard error

Package: man-db Version: 2.7.0.2-1 Severity: normal Dear Maintainer, * What led up to the situation? Using a script that contains "man ... 2> " * What exactly did you do (or not do) that was effective (or ineffective)? Called the script with arguments "-a ..." * What was the

Bug#766076: top: Illogical headings like "KiB Mem" and "%Cpu"

Package: procps Version: 1:3.3.9-7 Severity: minor Dear Maintainer, * What led up to the situation? Looking at the output of "top" * What was the outcome of this action? For example, ... %Cpu(s): 0.2 us, 0.2 sy, 0.0 ni, 99.3 id, 0.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem:15784

Bug#765426: umount; floppy light and humming still present after "umount" and even after "shutdown"

On Wed, Oct 15, 2014 at 12:06:06AM +, Debian Bug Tracking System wrote: > Thank you for filing a new Bug report with Debian. > [...] > > -- > 765426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765426 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems This bug

Bug#763668: fsck started to test /dev/fd0 (/media/floppy) after updating some libraries

On Wed, Oct 01, 2014 at 05:57:07PM +, Debian Bug Tracking System wrote: > Thank you for filing a new Bug report with Debian. > > [...]> > -- > 763668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763668 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems The sym

Bug#765426: umount; floppy light and humming still present after "umount" and even after "shutdown"

Package: mount Version: 2.25.1-4 Severity: normal Dear Maintainer, * What led up to the situation? Case described in Debian bug nr. 763668 * What exactly did you do (or not do) that was effective (or ineffective)? Put a floppy into the drive, mounted, changed to the mounted dire

Bug#765306: util-linux: whereis with -b -m -M -B also shows wrong results

Package: util-linux Version: 2.25.1-4 Severity: normal Dear Maintainer, * What led up to the situation? Using a script containing "whereis -b -m -M ... -B ... -f ..." * What exactly did you do (or not do) that was effective (or ineffective)? Tested as root following command li

Bug#763668: fsck started to test /dev/fd0 (/media/floppy) after updating some libraries

Package: util-linux Version: 2.20.1-5.8 Severity: normal Dear Maintainer, * What led up to the situation? The light of the floppy drive lit up and there was noise two times when booting Following was in the kern.log: Sep 18 20:32:52 jeti kernel: end_request: I/O error, dev fd0, sector 0

<    1   2   3   4   5   6   7   8   9   >