Bug#992377: manpages-dev

tags 992377 fixed-upstream thanks Upstream maintainer here. The keyutils pages in Section 2 are an unusual case. The wrapper functions are provided in the libkeyutils library (instead of, as is conventional, the C library), as noted in the add_key(2) page. The package that provides that library

Bug#981171: [PATCH 6/6] Use subsection for environment

Hello Bastien, In general, I like this idea, but may I ask you to rework the patch a little. Could you please fix up the pieces below (I'm sorry, you'll also need to rebase, because of other changes that I've made), and resubmit? On 1/30/21 12:29 AM, roucaries.bast...@gmail.com wrote: > From:

Bug#981171: [PATCH 5/6] Create a section ENVIRONMENT

Hello Bastien, On 1/30/21 12:29 AM, roucaries.bast...@gmail.com wrote: > From: Bastien Roucariès > > According to man-page (7): > ENVIRONMENT > A list of all environment variables that affect the program or > function and how they affect it. > > Therefore push the list of

Bug#981171: [PATCH 4/6] Better documentation of the environment mechanism

Hello Bastien, Thanks. This looks better. But still some things to improve, I think. On 1/30/21 12:29 AM, roucaries.bast...@gmail.com wrote: > From: Bastien Roucariès > > Document the purpose of the envirment mechanism, compared to the s/envirment/environment/ > command line argument of a

Bug#981171: [PATCH 3/6] Improve pager section by pointing to more

Hello Bastien, On 1/30/21 12:29 AM, roucaries.bast...@gmail.com wrote: > From: Bastien Roucariès > > More is the default pager according to mailx manual page of POSIX.1-2001 to > POSIX.1-2017. Mention it. > --- > man7/environ.7 | 8 +++- > 1 file changed, 7 insertions(+), 1 deletion(-) >

Bug#981171: [PATCH 1/6] Document that means at login time for HOME, LOGNAME, SHELL, USER

Hello Bastien, Thank you for taking the time to prepare this patch. As already noted, the subject line of a patch should read [PATCH ...] page.n: . I've applied the patch, but made many edits. On 1/30/21 12:29 AM, roucaries.bast...@gmail.com wrote: > From: Bastien Roucariès > >

Bug#981171: [PATCH 2/6] Document PATH resolution

Hello Bastien, For various reasons, I applied a different patch. See below. On 1/30/21 12:29 AM, roucaries.bast...@gmail.com wrote: > From: Bastien Roucariès > > Document PATH resolution, particularly null sequence and empty PATH > > Document also that since POSIX.1-2001 null sequence for .

Bug#981171: [PATCH 0/6][V2] environement (7)

Hello Bastien On 1/30/21 12:29 AM, roucaries.bast...@gmail.com wrote: > Please review and apply > > [PATCH 1/6] Document that means at login time for HOME, LOGNAME, > [PATCH 2/6] Document PATH resolution > [PATCH 3/6] Improve pager section by pointing to more > [PATCH 4/6] Better documentation

Bug#981171: [PATCH 01/13] Do not document mktemp (3)

Hello Bastien, On Fri, 29 Jan 2021 at 10:18, Bastien ROUCARIES wrote: > > Hi, > Le mer. 27 janv. 2021 à 22:28, Michael Kerrisk (man-pages) > a écrit : > > > > Salut Bastien, > > > > On 1/27/21 4:48 PM, roucaries.bast...@gmail.com wrote: > > > Fr

Bug#981171: [PATCH 03/13] Document that means at login time for HOME, LOGNAME, SHELL, USER

> Something like Note that behavior of su could lead to a mixed environment. Yes, that would be fine. -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/

Bug#981171: [PATCH 06/13] Improve pager section by pointing to more

On Fri, 29 Jan 2021 at 12:00, Bastien Roucariès wrote: > > Le jeudi 28 janvier 2021, 09:31:00 UTC Michael Kerrisk (man-pages) a écrit : > > On 1/27/21 4:48 PM, roucaries.bast...@gmail.com wrote: > > > From: Bastien Roucariès > > > > > > More is the d

Bug#981171: Environment 7 improvments

Hello Bastien, On 1/27/21 4:48 PM, roucaries.bast...@gmail.com wrote: > Hi, > > Could you find a serie for better documenting environment Thank you for your efforts, but there's much to fix, I'm sorry. I've applied two of the patches, but most of the others need revision, or better commit

Bug#981171: [PATCH 09/13] Document convention of string in environ

Hello Bastien, On 1/27/21 4:48 PM, roucaries.bast...@gmail.com wrote: > From: Bastien Roucariès > > Document the name=value system and that nul byte is forbidden > > Signed-off-by: Bastien Roucariès I've applied this patch, but please see a note below. > --- > man7/environ.7 | 12

Bug#981171: [PATCH 08/13] Better documentation of the environment mechanism

On 1/27/21 4:48 PM, roucaries.bast...@gmail.com wrote: > From: Bastien Roucariès > > Compare with argc/argv Why? The commit message should explain why you think this change is useful. Thanks, Michael > and describe the purpose of environment > --- > man7/environ.7 | 24

Bug#981171: [PATCH 12/13] Introduce the user custumization section

Hello Bastien. On 1/27/21 4:48 PM, roucaries.bast...@gmail.com wrote: > From: Bastien Roucariès Again, a much better commit message is needed here, to explain what you are doing, and why. > Signed-off-by: Bastien Roucariès > --- > man7/environ.7 | 74

Bug#981171: [PATCH 10/13] Introduce ENVIRONMENT section

Hello Bastien, On 1/27/21 4:48 PM, roucaries.bast...@gmail.com wrote: > From: Bastien Roucariès A commit like this deserves a much more detailed commit message explaining what you are doing and why. I think there's some good stuff below. but I need a better commit message, and also this patch

Bug#981171: [PATCH 05/13] Add see also ld.so (8) for LD_ variables

Hello Bastien, On 1/27/21 4:48 PM, roucaries.bast...@gmail.com wrote: > From: Bastien Roucariès > > Signed-off-by: Bastien Roucariès Thanks. I applied this patch, but had to make some patches. See below. > --- > man7/environ.7 | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > >

Bug#981171: [PATCH 06/13] Improve pager section by pointing to more

On 1/27/21 4:48 PM, roucaries.bast...@gmail.com wrote: > From: Bastien Roucariès > > More is the default pager in a lot of system mention it Really "more" and not "less"? On my system, 'git commit' and 'man' use less(1) when PAGER is not set. Thanks, Michael > --- > man7/environ.7 | 8

Bug#981171: [PATCH 04/13] Document PATH resolution

Hello Bastien, On 1/27/21 4:48 PM, roucaries.bast...@gmail.com wrote: > From: Bastien Roucariès > > Document PATH resolution, particularly null sequence and empty PATH > > Signed-off-by: Bastien Roucariès > --- > man7/environ.7 | 42 ++ > 1 file

Bug#981171: [PATCH 07/13] Better documentation of _GNU_SOURCE for environment

Hello Bastien, On 1/27/21 4:48 PM, roucaries.bast...@gmail.com wrote: > From: Bastien Roucariès > > Use feature_test_macros and document that historically > you should manually declare it. > --- > man7/environ.7 | 24 +--- > 1 file changed, 21 insertions(+), 3 deletions(-)

Bug#981171: [PATCH 13/13] Document LINES and COLUMNS

Hello Bastiern, On 1/27/21 4:48 PM, roucaries.bast...@gmail.com wrote: > From: Bastien Roucariès > > Document the variable LINES and COLUMN > > Signed-off-by: Bastien Roucariès > --- > man7/environ.7 | 45 ++--- > 1 file changed, 42 insertions(+), 3

Bug#981171: [PATCH 02/13] Add a note about portability of environment variable

Hello Bastien, On 1/27/21 4:48 PM, roucaries.bast...@gmail.com wrote: > From: Bastien Roucariès > > Some variables are portable at least under UNIX > > Signed-off-by: Bastien Roucariès > --- > man7/environ.7 | 11 +++ > 1 file changed, 11 insertions(+) > > diff --git

Bug#981171: [PATCH 03/13] Document that means at login time for HOME, LOGNAME, SHELL, USER

Hello Bastien, On 1/27/21 4:48 PM, roucaries.bast...@gmail.com wrote: > From: Bastien Roucariès > > Clearly document that su by default does not change this variables. I'm dubious about this. The place that this should be (and is) properly documented is the manual page for su(1). Why repeat it

Bug#981171: [PATCH 01/13] Do not document mktemp (3)

Salut Bastien, On 1/27/21 4:48 PM, roucaries.bast...@gmail.com wrote: > From: Bastien Roucariès > > Do not use for documentation purposes the unsecure mktemp function This message doesn't correspond to the change below (which removes a reference to "tempnam" and adds a reference to "mktemp".

Bug#656657: manpages: environ(7): Please clarify the usage of $PAGER and $EDITOR with regards to whitespace

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866060 seems to be related, and maybe the changes in the patch for that bug are sufficient to address the concerns in this bug? (That patch as just been taken upstream.) Thanks, Michael -- Michael Kerrisk Linux man-pages maintainer;

Bug#942207: getauxval(3): Clarify that AT_EXECFN and AT_BASE_PLATFORM return pointers.

Hi, This Debian bug was fixed quite some time ago upstream. Is there a reason that the bug is still open? Thanks, Michael On Sat, 12 Oct 2019 at 12:51, Witold Baryluk wrote: > > Package: manpages-dev > Version: 5.02-1 > Severity: normal > > Example: > >AT_PLATFORM > A

Bug#866060: environ(7): please document the valid values of pathnames for SHELL, PAGER and EDITOR/VISUAL

tags 866060 fixed-upstream thanks This patch has been applied upstream. Cheers, Michael On Wed, 13 Jan 2021 at 11:15, Bastien Roucariès wrote: > > Package: manpages > Version: 5.10-1 > Followup-For: Bug #866060 > > Dear Maintainer, > > Please found the included patch > > Please apply --

Bug#976312: modf.3: wrong Feature Test Macro Requirements

tags 976312 fixed-upstream thanks On Thu, 3 Dec 2020 at 10:18, Bill Allombert wrote: > > Package: manpages-dev > Version: 4.16-2 > Severity: normal > > Hello Tobias, > > man modf says: > >Feature Test Macro Requirements for glibc (see feature_test_macros(7)): > >modf(), modfl(): >

Bug#933000: resolv.conf(5): refers to MAXNS in , but it's in res_state.h now

tags 933000 wontfix thanks Upstream maintainer here. As I previously explained, this is not a valid bug report, and should be closed.

Bug#909789: manpages-dev: stat(2) manpage on ENOENT for dangling symbolic links (broken links)

tags 909789 fixed-upstream thanks -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/

Bug#959680: Unclear error handling of hsearch_r in manpage

her > system, that didn't mention errno. > > You are right the current version in Debian does clearly states how > the errors are communicate. > > Please close this bug. > > Sorry for the confusion, and thanks for a quick response. > > On Wed, 6 May 2020 at 10:27, Michael K

Bug#959680: Unclear error handling of hsearch_r in manpage

Hello Witold, > The man page doesn't tell how the error code is returned back to the > caller. > > Looking at the source code of hsearch and hsearch_r it looks to be via > errno, but manpage doesn't mention this at all. I'm a bit lost here. The manual page says: In the event of an

Bug#959680: Unclear error handling of hsearch_r in manpage

On Sun, 3 May 2020 at 20:45, Witold Baryluk wrote: > > Package: manpages-dev > Version: 5.06-1 > Severity: normal > > Reading manual: > > """ > int hsearch_r(ENTRY item, ACTION action, ENTRY **retval, > struct hsearch_data *htab); > > Return Value: > > hsearch_r() returns nonzero on

Bug#947091: manpages-dev: timerfd_settime can fail with ECANCELED

tags 947091 fixed-upstream thanks

Bug#947091: manpages-dev: timerfd_settime can fail with ECANCELED

tags 947091 fixed-upstream thanks

Bug#947091: manpages-dev: timerfd_settime can fail with ECANCELED

tags fixed-upstrream thanks I applied the following patch upstream. diff --git a/man2/timerfd_create.2 b/man2/timerfd_create.2 index ec137fbfe..98225dcad 100644 --- a/man2/timerfd_create.2 +++ b/man2/timerfd_create.2 @@ -477,6 +477,9 @@ is not a valid timerfd file descriptor. .BR

Bug#947091: manpages-dev: timerfd_settime can fail with ECANCELED

Here's a pointer to the upstream discussion: https://lore.kernel.org/linux-man/4c557b44-4e4e-a689-a17b-f95e6c5ee...@gmail.com/T/#t

Bug#947091: manpages-dev: timerfd_settime can fail with ECANCELED

Upstream maintainer here. On 12/20/19 9:32 PM, Marc Lehmann wrote: > Package: manpages-dev > Version: 5.04-1 > Severity: wishlist > > Dear Maintainer, > > the timerfd_create/settime/... manpage documents that reads from a timerfd > configured with TFD_TIMER_CANCEL_ON_SET fail with ECANCELED,

Bug#942207: getauxval(3): Clarify that AT_EXECFN and AT_BASE_PLATFORM return pointers.

tags 942207 fixed-upstream thanks On Sat, 12 Oct 2019 at 12:51, Witold Baryluk wrote: > > Package: manpages-dev > Version: 5.02-1 > Severity: normal > > Example: > >AT_PLATFORM > A pointer to a string that identifies the hardware platform > that the program is run‐ >

Bug#931325: manpages-dev: io_cancel can fail with EINTR

>>> I found that, at least with debians 4.19 kernel, io_cancel can fail with >>> EINTR on signal delivery, which should be documented as per similar calls. >> >> Can you provide some more info on the circumstances where you observed >> this behavior please. > > Well, while developing the aio

Bug#931325: manpages-dev: io_cancel can fail with EINTR

Hello Marc, On 7/1/19 10:34 PM, Marc Lehmann wrote: Package: manpages-dev Version: 4.16-2 Severity: minor Dear Maintainer, I found that, at least with debians 4.19 kernel, io_cancel can fail with EINTR on signal delivery, which should be documented as per similar calls. Can you provide some

Bug#933000: resolv.conf(5): refers to MAXNS in , but it's in res_state.h now

On 7/25/19 7:15 PM, Axel Beckert wrote: > Package: manpages > Version: 5.01-1 > Severity: normal > File: /usr/share/man/man5/resolv.conf.5.gz > > Hi, > > resolv.conf(5); states: > >nameserver Name server IP address > Internet address of a name server that the resolver

Bug#932382: manpages-dev: getutline(3): missing #include in example program

tags 932382 fixed-upstream thanks On 7/18/19 5:19 PM, Thorsten Glaser wrote: > Package: manpages-dev > Version: 5.01-1 > Severity: minor > > I was just trying to compile the example program from the > .Sh EXAMPLE > of the getutline(3) manpage and saw this: > > tglase@tglase:~ $ gcc x.c > x.c:

Bug#926292: manpages-dev: memfd_create needs sys/mman.h, not sys/memfd.h

tags 926292 fixed-upstream thanks On Sun, 14 Apr 2019 at 19:16, Michael Kerrisk (man-pages) wrote: > > tags 926292 fixed-upstream > thanks > > On Wed, 3 Apr 2019 at 04:42, Marc Lehmann wrote: > > > > Package: manpages-dev > > Version: 4.16-1 > >

Bug#926292: manpages-dev: memfd_create needs sys/mman.h, not sys/memfd.h

tags 926292 fixed-upstream thanks On Wed, 3 Apr 2019 at 04:42, Marc Lehmann wrote: > > Package: manpages-dev > Version: 4.16-1 > Severity: minor > > Dear Maintainer, > > the manpage for memfd_create documents: > >#include > > but as far as I can tell, this heade rnever existed and trhere

Bug#926292: manpages-dev: memfd_create needs sys/mman.h, not sys/memfd.h

tags fixed-upstream thanks This error was fixed in the latest upstream version, which was released a few weeks ago. On Wed, 3 Apr 2019 at 04:42, Marc Lehmann wrote: > > Package: manpages-dev > Version: 4.16-1 > Severity: minor > > Dear Maintainer, > > the manpage for memfd_create documents: > >

Bug#915874: rename(1): incorrect note since glibc 2.28

tags fixed-upstream thanks A patch to fix this page has already been applied for the next upstream release. Thanks, Michael (Upstream Maintainer) On 12/7/18 2:43 PM, Johannes 'josch' Schauer wrote: > Package: manpages > Version: 4.16-1 > Severity: normal > > Hi, > > currently, the manpage

Bug#882222: Document security problems with system.3 and popen.3 (argument injection)

Hello Bastien On 22 November 2017 at 14:53, Bastien ROUCARIES <roucaries.bast...@gmail.com> wrote: > On Wed, Nov 22, 2017 at 2:45 PM, Michael Kerrisk (man-pages) > <mtk.manpa...@gmail.com> wrote: >>> Could you also warn about popen ? >> >> I alrea

Bug#882222: Document security problems with system.3 and popen.3 (argument injection)

> Could you also warn about popen ? I already added a cross reference from popen(3) to the Caveats section in system(3). I should have mentioned that before. > And mention that system(sprintf("command %s")) is a security hole That seems obviously dangerous. But don't you think it is covered by

Bug#882222: Document security problems with system.3 and popen.3 (argument injection)

Hello Tobias, and Bastien, On 22 November 2017 at 09:52, Dr. Tobias Quathamer wrote: > control: severity -1 important > > Am 20.11.2017 um 12:29 schrieb Bastien ROUCARIES: >> Please document the implication of system.3 and popen.3, particularly >> argument injection. > Hi, > >

Bug#764449: core.5: please mention security implications of /proc/sys/kernel/core_pattern

After, looking at this for quite a while, I am not convinced there's an issue here. %e is returned as just the basename of the executable path, and %t and %E seem even less problematic. If you think there's an issue, it would be good to show a worked example of how an "innocent" core_pattern pipe

Bug#860559: timex.offset unit ambiguity

On 04/18/2017 06:31 PM, Zefram wrote: > Package: manpages-dev > Version: 3.74-1 > Severity: minor > > adjtimex(2) says: > > # struct timex { > # int modes; /* mode selector */ > # long offset; /* time offset (usec) */ > > In fact the "offset"

Bug#859514: file conflict with keyutils

These manual pages recently (about 3 meeks ago) migrated from the upstream keyutils project to the upstream man-pages project. See http://linux-man-pages.blogspot.de/2017/03/man-pages-410-is-released.html . They have been removed in the upstream keyutils project in its latest release 9which

Bug#859511: libbsd-dev: trying to overwrite '/usr/share/man/man3/explicit_bzero.3.gz', which is also in package manpages-dev 4.10-1

On 5 April 2017 at 11:59, Vincent Lefevre wrote: > On 2017-04-04 18:41:10 +0200, Sven Joachim wrote: >> On 2017-04-04 16:29 +0100, Chris Lamb wrote: >> > Unpacking libbsd-dev:amd64 (0.8.3-1) ... >> > dpkg: error processing archive >> >

Bug#847998: [Pkg-sysvinit-devel] Bug#847998: manpages: file conflicts with initscripts

Hello Thorsten, On 12/16/2016 03:36 PM, Thorsten Glaser wrote: > On Fri, 16 Dec 2016, Michael Kerrisk (man-pages) wrote: > >> On 12/16/2016 02:53 PM, Thorsten Glaser wrote: >>> On Fri, 16 Dec 2016, Michael Kerrisk (man-pages) wrote: >>> >>>> That doesn'

Bug#847998: [Pkg-sysvinit-devel] Bug#847998: manpages: file conflicts with initscripts

On 12/16/2016 02:53 PM, Thorsten Glaser wrote: > On Fri, 16 Dec 2016, Michael Kerrisk (man-pages) wrote: > >> That doesn't document (upstream) reality though. Once upon a time, >> there were one or two Section 9 pages in the man-pages >> project. No one updated them or add

Bug#847998: [Pkg-sysvinit-devel] Bug#847998: manpages: file conflicts with initscripts

On 12/16/2016 02:37 PM, Axel Beckert wrote: > Hi, > > Thorsten Glaser wrote: >> On Tue, 13 Dec 2016, Michael Kerrisk (man-pages) wrote: >>> Upstream man-pages maintainer here; I just added tmpfs(5), unaware >>> that it would create a conflict for Debian;

Bug#847998: [Pkg-sysvinit-devel] Bug#847998: manpages: file conflicts with initscripts

On 12/16/2016 02:40 PM, Thorsten Glaser wrote: > On Fri, 16 Dec 2016, Axel Beckert wrote: > > The manpage about the Linux tmpfs should be tmpfs(9) as it > covers a kernel concept (here: a filesystem). Not sure where this idea originates. There is no Section 9 on Linux. >>> >>>

Bug#848231: bugs in scandir example program

On 15 December 2016 at 14:56, Ian Jackson <ijack...@chiark.greenend.org.uk> wrote: > Michael Kerrisk (man-pages) writes ("Re: Bug#848231: bugs in scandir example > program"): >> tags 848231 fixed-upstream >> thanks > ...> >> On 15 Decemb

Bug#848231: bugs in scandir example program

tags 848231 fixed-upstream thanks On 15 December 2016 at 13:55, Ian Jackson wrote: > Package: manpages-dev > Version: 3.74-1 > Severity: minor > > I cut and pasted the example program from scandir(3) and found that it > had some bugs which caused compiler

Bug#848121: [Pkg-sysvinit-devel] File conflict between manpages and initscripts

On 14 December 2016 at 16:45, Ian Jackson wrote: > Axel Beckert writes ("Bug#848121: [Pkg-sysvinit-devel] File conflict between > manpages and initscripts"): >> I must admit that I never was aware that filesystems are in the same >> manual section as file formats

Bug#848121: [Pkg-sysvinit-devel] Bug#848121: File conflict between manpages and initscripts

Hi, On 14 December 2016 at 14:52, Axel Beckert wrote: > Hi, > > Dr. Tobias Quathamer wrote: >> I think there are a few options: >> >> 1. Rename the manpage in one of the packages >> 3. Move one of the manpages to another section > > Any suggestions for how to rename them? Do we

Bug#847998: manpages: file conflicts with initscripts

On 13 December 2016 at 10:56, Thorsten Glaser <t.gla...@tarent.de> wrote: > On Tue, 13 Dec 2016, Michael Kerrisk (man-pages) wrote: > >> I can't move "them" as they come from diverse projects (nfs-utils, > > OK. > >> e2fsprogs, btrfs-progs). O

Bug#847998: manpages: file conflicts with initscripts

>>> And there's certainly precedent for section 5 pages on filesystems. >>> For example, among others, we have ext4(5), btrfs(5), and nfs(5). >> >> But section 5 is for configuration files. You could move them >> to section 7 (general concepts), though. > > I can't move "them" as they come from

Bug#847998: manpages: file conflicts with initscripts

Hello Thorsten, On 13 December 2016 at 10:43, Thorsten Glaser <t.gla...@tarent.de> wrote: > On Tue, 13 Dec 2016, Michael Kerrisk (man-pages) wrote: > >> Upstream man-pages maintainer here; I just added tmpfs(5), unaware >> that it would create a conflict for Debian;

Bug#847998: manpages: file conflicts with initscripts

Upstream man-pages maintainer here; I just added tmpfs(5), unaware that it would create a conflict for Debian; I assume the conflicting page is Debian-specific(?). (I don't have such a page on my Fedora system.) On 13 December 2016 at 10:00, Thorsten Glaser wrote: > On Tue,

Bug#574041: [daniel.bal...@gmail.com: man 2 write - clarification]

March 2014 at 08:34, Michael Kerrisk (man-pages) <mtk.manpa...@gmail.com> wrote: > On Sun, Mar 14, 2010 at 9:24 PM, Joey Schulze <j...@infodrom.org> wrote: >> Package: manpages-dev >> Version: 3.24-1 >> >> Forwarded mail from Daniel. >> >> ---

Bug#845172: manpages-dev: no function protypes in example from mbstowcs(3)

Upstream maintainer here. I added the missing include. But I am unsure what to do about the other point (regarding gcc -Wconversion). There is an analogous situation with islower() and similar functions, where the solution is described by an update I recently added for the upcoming upstream

Bug#839705: manpages-dev: "initial state" in mbstowcs(3) and wcstombs(3)

On 10/06/2016 10:13 AM, Igor Liferenko wrote: > Dear Maintainer, > > According to definitions of mbstowcs and wcstombs (see below), the phrase > ``The conversion starts in the initial state.'' See my earlier reply. > may be left in mbstowcs(3) and wcstombs(3), but the phrase > ``In this

Bug#839705: manpages-dev: "initial state" in mbstowcs(3) and wcstombs(3)

tags 839705 fixed-upstream thanks On 10/04/2016 09:30 AM, Igor Liferenko wrote: > Package: manpages-dev > Version: 4.07-1 > Severity: normal > > Dear Maintainer, > > In mbstowcs(3) there is this sentence: > > The conversion starts in the initial state. > > And in wcstombs(3) there are

Bug#840499: manpages-dev: Inconsistent symbolic error name for EILSEQ in errno(3)

tags 840499 fixed-upstream thanks On 10/12/2016 11:04 AM, Igor Liferenko wrote: > Package: manpages-dev > Version: 4.07-1 > Severity: normal > > Dear Maintainer, > > According to bug glibc bug 20687 [1], the text > > Illegal byte sequence (POSIX.1, C99) > > should be changed to > >

Bug#840499: manpages-dev: Inconsistent symbolic error name for EILSEQ in errno(3)

tags 840499 fixed-upstream thanks On 10/12/2016 11:04 AM, Igor Liferenko wrote: > Package: manpages-dev > Version: 4.07-1 > Severity: normal > > Dear Maintainer, > > According to bug glibc bug 20687 [1], the text > > Illegal byte sequence (POSIX.1, C99) > > should be changed to > >

Bug#838956: manpages-dev: Inconsistent documentation in NOTES section of "man wcstombs"

tags 838956 fixed-upstream thanks Thanks for this report. I've applied the patch below to the upstream man page. Cheers, Michael diff --git a/man3/wcstombs.3 b/man3/wcstombs.3 index c787250..1f189be 100644 --- a/man3/wcstombs.3 +++ b/man3/wcstombs.3 @@ -112,8 +112,7 @@ current locale. .PP

Bug#838958: Fwd: Bug#838958: linux: mount(2) _silently_ ignores other mountflags when MS_BIND is set

tags 838958 fixed-upstream thanks On 09/27/2016 11:27 AM, Debian Bug Tracking System wrote: > Processing control commands: > >> reassign -1 manpages-dev > Bug #838958 [src:linux] linux: mount(2) _silently_ ignores other mountflags > when MS_BIND is set > Bug reassigned from package 'src:linux'

Bug#741360: statm "share" badly described

tags 741360 fixed-upstream thanks Hello Zefram, On 11 March 2014 at 16:48, Zefram wrote: > Package: manpages > Version: 3.44-1 > Severity: minor > > proc(5) says: > >/proc/[pid]/statm > Provides information about memory usage, measured in pages. The >

Bug#825548: quotactl(2) man page is incorrect

tags 825548 fixed-upstream thanks Hello Jacob Upstream maintainer here. Thanks for the excellently documented report. This error appears to have been injected into glibc when copying some headers from BSD. I've applied the patch below. Cheers, Michael diff --git a/man2/quotactl.2

Bug#825022: man pages for *xattr syscalls are missing from manpages-dev

Note that around May 2015, by mutual agreement between the man-pages and libattr projects (which hitherto had both carried versions of the *xattr(2) pages), man-pages became the canonical home for these pages, and the versions in the libattr project were dropped. Maybe Debian has not caught up

Bug#717629: please document LANG and LC_ALL in locale(1)

tags 717629 fixed-upstream thanks Hello Vincent, On 03/14/2016 07:24 AM, Vincent Lefevre wrote: > On 2016-03-14 06:56:56 +1300, Michael Kerrisk (man-pages) wrote: >> The goal of the upstream locale(1) page is to document the syntax of >> the command. > > It did more t

Bug#717629: please document LANG and LC_ALL in locale(1)

On 14 March 2016 at 03:31, Aurelien Jarno wrote: > control: reassign -1 manpages > > On 2013-07-23 09:16, Harald Dunkel wrote: >> Package: locales >> Version: 2.13-38 >> >> Seems that LANG and LC_ALL have been lost in locale(1). It would >> be nice if they could be added. >>

Bug#743525: symlink permissions misdescribed

tags 715261 fixed-upstream thanks Yes, there are odd exceptions. Under /proc/PID, there are some "magic" symlinks that have other permissions. I"ve added some text to the man page to note this. Thanks for the report. On Linux, the permissions of a symbolic link are not used in

Bug#715261: manpages-dev: readdir_r should be strongly discouraged due to security reasons

tags 715261 fixed-upstream thanks glibc 2.24 marks readdir_r() deprecated, and for the upcoming man-pages-4.05 release, I've significantly reworked the man page to note the problems and indicate that the function is deprecated. Thanks, Michael

Bug#679323: clearenv(3): implies that it's a security tool

On 18 February 2016 at 21:34, Matt Zimmerman wrote: > Thanks for following up. My recommendation is to say something like: > > This function DOES NOT securely erase the contents of the environment. > Security-conscious applications which need to do this should use >

Bug#756599: printf(3) manpage: stray asterisk in "NAN*"

tags 756599 fixed-upsteam thanks On 17 February 2016 at 01:21, Stéphane Aulery wrote: > Hello Michael, > > About Debian Bug #756599 [1], I found this explanation [2][3] confirming > that * is not a selector : I've removed the stray "*" (commit 4a66305922b197) Thanks for the

Bug#799674: Properly document l/ll length modifier for double/long double argument

On 12/28/2015 08:39 AM, Mathieu Malaterre wrote: > On Sat, Dec 26, 2015 at 4:54 PM, Michael Kerrisk (man-pages) > <mtk.manpa...@gmail.com> wrote: >> (Upstream mainatiner here.) >> >> On 09/21/2015 03:08 PM, Mathieu Malaterre wrote: >>> Package: manpag

Bug#804210: Invalid documentation for return value of sscanf

On 11/06/2015 09:45 AM, Mathieu Malaterre wrote: > Package: manpages-dev > Version: 3.74-1 > > Currently `man sscanf`` reads as: > > [...] > RETURN VALUE >These functions return the number of input items successfully > matched and assigned, which can be fewer than provided for, or even >

Bug#799674: Properly document l/ll length modifier for double/long double argument

(Upstream mainatiner here.) On 09/21/2015 03:08 PM, Mathieu Malaterre wrote: > Package: manpages-dev > Version: 3.65-1 > Severity: wishlist > > Currenly the man page for *printf family is difficult to read with > regards to float, double and long double printing. The man page for > *scanf family

Bug#803459: drand48(3): errors on interval bounds

tags 803459 fixed-upstream thanks Hello Vincent On 10/30/2015 11:17 AM, Vincent Lefevre wrote: > Package: manpages-dev > Version: 3.74-1 > Severity: normal > > The drand48(3) man page contains: > >The drand48() and erand48() functions return nonnegative >double-precision

Bug#794876: manpages-dev: Should guide users away from deprecated sys_errlist more

On 08/07/2015 04:24 PM, Dale E. Martin wrote: Package: manpages-dev Version: 3.74-1 Severity: wishlist Tags: patch Dear Maintainer, I recently caused a problem for myself when writing some C-code by making direct use of sys_errlist. I did this after reading the manpage for perror. The

Bug#794217: socketpair: unclear where the SOCK_NONBLOCK and SOCK_CLOEXEC flags go

tags 794217 fixed-upstream thanks Hello Goswin, On 07/31/2015 12:41 PM, Goswin von Brederlow wrote: Package: manpages-dev Version: 3.74-1 Severity: minor File: socketpair Hi, reading 'man 2 socketpair' it is unclear where the new SOCK_NONBLOCK and SOCK_CLOEXEC flags go in the function

Bug#794559: ld.so(8) LD_LIBRARY_PATH also treats ';' as a seperator

tags 794559 fixed-upstream thanks On 08/04/2015 02:05 PM, Jonathan David Amery wrote: Package: manpages Version: 3.44-1 Severity: normal The documentation for LD_LIBRARY_PATH notes that the list is colon-seperated; however ld.so also treats ';' as a seperator (possibly for compatability

Bug#788870: Processed: Bug#788870: [base-files] 'LANG=C man 8 resolv+': (fwd)

tags 788870 fixed-upstream thanks This reference was removed in upstream man-pages in May 2014, with commit 0921ce4ab089dca648a4d25f8e7dad8942b84567. Thanks, Michael On 16 June 2015 at 12:36, Debian Bug Tracking System ow...@bugs.debian.org wrote: Processing commands for

Bug#787625: /usr/share/man/man7/epoll.7.gz: epoll(7): wrong string provided to perror in example code

tags 787625 fixed-upstream thanks Fixed with upstream commit be6b243ae2d6b3ba158684c945076a1fd65a6f2f On 4 June 2015 at 16:49, Michael Kerrisk (man-pages) mtk.manpa...@gmail.com wrote: On 06/03/2015 03:17 PM, Uwe Kleine-König wrote: Package: manpages Version: 3.74-1 Severity: minor File

Bug#787625: /usr/share/man/man7/epoll.7.gz: epoll(7): wrong string provided to perror in example code

On 06/03/2015 03:17 PM, Uwe Kleine-König wrote: Package: manpages Version: 3.74-1 Severity: minor File: /usr/share/man/man7/epoll.7.gz The example code in epoll(7) includes: nfds = epoll_wait(epollfd, events, MAX_EVENTS, -1); if (nfds == -1) {

Bug#630029: Processed: retitle 630029 to read/write/readv/writev/sendfile.2: undocumented cap on number of bytes read/written

tags 630029 fixed-upstream thanks And here's the documentation fix. Thanks, Michael diff --git a/man2/pread.2 b/man2/pread.2 index de1e951..c7a7fdd 100644 --- a/man2/pread.2 +++ b/man2/pread.2 @@ -85,6 +85,12 @@ and .BR pwrite () returns the number of bytes written. +Note that is not an

Bug#621057: printf.3: ATTRIBUTES: Note functions those are thread-safe

On 03/23/2015 04:24 AM, Zeng Linggang wrote: The markings match glibc markings. Hello Zeng Linggang, This patch seems to have been sent twice... Cheers, Michael Signed-off-by: Zeng Linggang zenglg...@cn.fujitsu.com Signed-off-by: Ma Shimiao mashimiao.f...@cn.fujitsu.com ---

Bug#773443: host.conf.5: spoof deprecated ?

Hello Stéphane, On 10 March 2015 at 00:26, Stéphane Aulery saul...@free.fr wrote: Hello Michael, Le lundi 09 mars 2015 à 10:03:09, Michael Kerrisk (man-pages) a écrit : On 03/09/2015 08:59 AM, Stéphane Aulery wrote: Le lundi 09 mars 2015 à 08:22:01, Michael Kerrisk (man-pages) a écrit

Bug#773443: [PATCH] host.conf.5: keywords and env. var. nospoof, spoofalert, spoof and RESOLV_SPOOF_CHECK were added to glibc 2.0.7 but never implemented

On 03/10/2015 12:27 AM, Stéphane Aulery wrote: Move descriptions to historical section and reorder it for clarity Thanks, Stéphane. Applied. But please make patch titles shorter (72 chars) --move text to the body of the commit message as needed. Thanks, Michael Debian Bug #773443 reported

Bug#773443: host.conf.5: spoof deprecated ?

On 03/09/2015 08:59 AM, Stéphane Aulery wrote: Le lundi 09 mars 2015 à 08:22:01, Michael Kerrisk (man-pages) a écrit : Hello Stéphane On 03/08/2015 02:05 PM, Stéphane Aulery wrote: ** COPY OF GLIBC BUGZILLA #18091 FOR INFORMATION ** https://sourceware.org/bugzilla/show_bug.cgi?id=18091

Bug#773443: host.conf.5: spoof deprecated ?

Hello Stéphane On 03/08/2015 02:05 PM, Stéphane Aulery wrote: ** COPY OF GLIBC BUGZILLA #18091 FOR INFORMATION ** https://sourceware.org/bugzilla/show_bug.cgi?id=18091 - Hello, A Debian user reported that [1]: spoof* keywords

Bug#775328: manpages: urandom manpage is misleading

tags 775328 fixed-upstream thanks Mathieu, On 14 January 2015 at 08:57, Mathieu Malaterre ma...@debian.org wrote: Package: manpages Version: 3.74-1 Severity: normal Dear Maintainer, The manpage for `urandom` is misleading, at least with recent linux kernel. The current man page reads

  1   2   >