Bug#741183: pdftotext(1): Some typographical corrections to the manual

Source: poppler Version: 0.24.5-2 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Checking the man page with a script * What was the outcome of this action? Found some typographical mistakes ## Changes: Removed space at the end of a line

Bug#741184: pdfunite(1): Some typographical corrections to the man page

Source: poppler Version: 0.24.5-2 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Checking the man page with a script * What was the outcome of this action? Saw some typographical mistakes ## Changes: Changed .. to ... Reduced two word spaces

Bug#741868: mount(8): Some (typographical) corrections to the manual

Source: util-linux Version: 2.24.1 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Checking the man page with a script * What was the outcome of this action? Some (typing) mistakes ## Changes: Space at end of lines removed -- changed to \-\- if

Bug#741868: mount(8): Some (typographical) corrections to the manual

On Sun, Mar 16, 2014 at 05:21:41PM -0400, Phillip Susi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 03/16/2014 02:03 PM, Bjarni Ingi Gislason wrote: Source: util-linux Version: 2.24.1 There is no 2.24.1 in debian. Did you mean 2.20.1-5.6? No. I used the latest version

Bug#742086: /etc/man(mdoc).local: \- named dash instead of minus (sign)

Package: groff Version: 1.22.2-5 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Reading the files * What was the outcome of this action? Misleading name for the character \- The name minus (sign) is used on page 7 in the Troff User's Manual. Also in

Bug#742289: help2man: Adding missing italic correction

Package: help2man Version: 1.44.1 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Reading a resulting output (man page) * What was the outcome of this action? Noticed that an italic correction was missing before \fI (\,) and before (or after) the change

Bug#679150: Acknowledgement (troffcvt: Macros H*ahref and H*aend not defined in the manuals)

The patch tag should be removed, as I forgot to remove it. -- Bjarni I. Gislason -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#742356: xkbprint(1): Some (typographical) corrections to the manual

Package: x11-xkb-utils Version: 7.7+1 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Reading the man page * What exactly did you do (or not do) that was effective (or ineffective)? Checked the manual with a script * What was the outcome of this

Bug#741179: Improvements to the poppler's man pages

On Thu, Jul 03, 2014 at 09:52:40PM +0200, Pino Toscano wrote: [...] You can open a new bug (just one for all the changes should be enough) at https://bugs.freedesktop.org, poppler product. Feel free to provide the bug number/link, so I can track it. The number is 81761 -- Bjarni I.

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 symptoms

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#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:157844

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 file * What exactly did you do (or not do) that was effective (or ineffective)? Called the script with arguments -a ... * What was the

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#765306: util-linux: whereis with -b -m -M one dir -B one dir 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

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

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

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#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 *

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#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 +, 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 report with Debian. [...] -- 765426: http

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 you do (or

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

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 +, Bjarni Ingi Gislason wrote: On Wed, Oct 15, 2014 at 12:06:06AM +, Debian Bug Tracking System wrote: Thank you

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#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. Revised number

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 errors

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

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 for a

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 are

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 -n -e

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#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

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

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",

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

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

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

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#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

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#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 <bjarn...@rhi.hi.is>, 2015-10-11, 01:52: > > * What outcome did you expect instead? > > > > That the environmental variable "TMPDIR" retains its value. > > Lintian

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

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 <bjarn...@rhi.hi.is>, 2015-10-11, 01:52: > > > * What outcome did you expect instead? > > > > > &g

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

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

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

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#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

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#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#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==

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:

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#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 <bjarn...@rhi.hi.is> 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

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. > > > > >

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

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)?

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

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

Bug#544317: closed by Andreas Henriksson <andr...@fatal.se> (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

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'

On Mon, Dec 12, 2016 at 06:40:21PM -0800, Russ Allbery wrote: > Bjarni Ingi Gislason <bjarn...@rhi.hi.is> 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 > > l

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

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

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 th

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

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

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:

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]:

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#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?

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:

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

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

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

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

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

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

Bug#897946: unrar.1: Make some typographic and formatting changes in the manual

Package: unrar Version: 1:5.5.8-1 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Some warnings from "test-groff" (development version of "groff"): :9 (macro BR): only 1 argument, but more are expected :21 (macro BR): only 1 argument, but more are expected :42

Bug#898675: nn.1: Use the correct macro for a font change of one argument

Package: nn Version: 6.7.3-10+b2 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? chk_manuals: Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z :4039 (macro IR): only 1 argument, but more are expected :4321 (macro BR): only 1 argument, but more

Bug#899341: disdvi.1: Some minor fixes in the manual

Package: texlive-binaries Version: 2018.20180416.47457-3+b1 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Warnings from "groff": Input file is disdvi.1 Test nr. 2: :16 (macro IR): only 1 argument, but more are expected :18 (macro IR): only 1 argument, but

Bug#899344: dotlocfile.1: Some minor fixes in the manual

Package: liblockfile-bin Version: 1.14-1.1 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Warnings from "groff": :6 (macro RB): only 1 argument, but more are expected :13 (macro RB): only 1 argument, but more are expected Output is from: test-groff -b -e

Bug#899339: calendar.1: Some minor fixes in the manual

Package: bsdmainutils Version: 11.1.2+b1 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Warning from "troff": troff: :310: warning: macro 'FL' not defined Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z ["test-groff" is a developmental

Bug#900043: dt2dv.1: Some formatting fixes in the manual

On Fri, May 25, 2018 at 09:51:06AM +0200, Hilmar Preuße wrote: > Am 25.05.2018 um 04:36 teilte Bjarni Ingi Gislason mit: > > Hi, > > >Dear Maintainer, > > > >* What led up to the situation? > > > > Warning from "groff": > > > T

Bug#900040: dpkg-trigger.1: Some formatting fixes in the manual

Package: dpkg Version: 1.19.0.5+b1 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Warnings from "groff": :44 (macro BR): only 1 argument, but more are expected :62 (macro BR): only 1 argument, but more are expected :68 (macro BR): only 1 argument, but more

Bug#900043: dt2dv.1: Some formatting fixes in the manual

Package: texlive-binaries Version: 2018.20180416.47457-3+b1 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Warning from "groff": :60 (macro IR): only 1 argument, but more are expected Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z

Bug#900035: dpkg-split.1: Some formatting fixes in the manual

Package: dpkg Version: 1.19.0.5+b1 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Warning from "groff": :148 (macro BR): only 1 argument, but more are expected :181 (macro BR): only 1 argument, but more are expected Output is from: test-groff -b -e -mandoc

Bug#900033: dpkg-deb.1: Some fixes in the manual

Package: dpkg Version: 1.19.0.5+b1 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Warnings from "groff": :133 (macro IR): only 1 argument, but more are expected :210 (macro BR): only 1 argument, but more are expected :279 (macro BR): only 1 argument, but more

Bug#901188: utils.py: Make the line "Dear Maintainer" more specific

Package: reportbug Version: 7.1.10 Severity: minor Make the line "Dear Maintainer" more specific and mention what distribution is meant, for example by using "Dear Debian maintainer". This line is in the file "/usr/lib/python3/dist-packages/reportbug/utils.py". See an answer to the bug

Bug#901636: mandoc: "mandoc -mdoc -T man" causes memory dump

Package: mandoc Version: 1.14.3-4 Severity: important Output from "mandoc -mdoc -T man groff_mdoc.7": mandoc: mdoc_man.c:678: print_node: Assertion `n->tok >= MDOC_Dd && n->tok < MDOC_MAX' failed. Aborted (core dumped) -- System Information: Debian Release: buster/sid APT prefers

Bug#520414: bash: --verbose is not documented in manpage

On Thu, Mar 19, 2009 at 11:40:06AM -0300, Marco Túlio Gontijo e Silva wrote: > Package: bash > Version: 3.2-5 > Severity: normal > > Option --verbose is not documented in manpage. It says only that it's the > same > of -v. > Why has this report not been closed. It reports no error or a

Bug#900446: hdparm.8: Change a two-fonts macro to an one-font macro for a single argument

Package: hdparm Version: 9.56+ds-2 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? A warning from "groff": :9 (macro BI): only 1 argument, but more are expected Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z [ "test-groff" is a

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

On Thu, May 31, 2018 at 09:24:52PM +1000, Craig Small wrote: > Hello Bjarni, > Thankyou for your three bug reports. I have applied two, but the ps one > was not the patch, just a text file showing the problems again. > So, most of the changes have been applied to the upstream procps >

Bug#900857: hostname.1: Minor fixes is the manual

Package: hostname Version: 3.20 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Warnings from "groff": :65 (macro BR): only 1 argument, but more are expected :69 (macro BR): only 1 argument, but more are expected :71 (macro BR): only 1 argument, but more are

Bug#900247: gpg-check-pattern.1: Some formatting changes in the manual

Package: gpg-agent Version: 2.2.5-1 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Warning from "groff": :19 (macro BR): only 1 argument, but more are expected Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z [ "test-groff" is a

Bug#900033: dpkg-deb.1: Some fixes in the manual

r further fixes, or > this might get a bit out of control. :) ] > I usually only test for warnings from "groff". If there are some, I run the whole testing script on the man pages, if there are not too many. Otherwise just patches to eliminate the warnings. > On Thu, 2018-05-24 at 22

<    1   2   3   4   5   6   7   8   >