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 a
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: Bas
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 variab
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 pr
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(-)
>
>
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
>
> Clear
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 . ar
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 of
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:
> > > From:
> 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/
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 defa
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 messag
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 +-
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
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 ++--
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 pr
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(-)
>
> di
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
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 changed
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(-)
>
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 del
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 a/man7/environ.7
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
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".
B
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; http://www.
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 po
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
--
Mi
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():
>
tags 933000 wontfix
thanks
Upstream maintainer here. As I previously explained, this is not a
valid bug report, and should be closed.
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/
es on another
> 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 1
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 error,
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
tags 947091 fixed-upstream
thanks
tags 947091 fixed-upstream
thanks
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 timerfd_settime
Here's a pointer to the upstream discussion:
https://lore.kernel.org/linux-man/4c557b44-4e4e-a689-a17b-f95e6c5ee...@gmail.com/T/#t
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, how
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‐
>
>>> 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 backe
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
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 shoul
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: In
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
> >
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 are
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:
>
>
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 for
Hello Bastien
On 22 November 2017 at 14:53, Bastien ROUCARIES
wrote:
> On Wed, Nov 22, 2017 at 2:45 PM, Michael Kerrisk (man-pages)
> wrote:
>>> Could you also warn about popen ?
>>
>> I already added a cross reference from popen(3) to the Caveats section
>
> 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 t
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,
>
> thanks for the bug
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
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"
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 happene
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
>> > /tmp/apt-dpkg-install-tduipc/101-libbsd-dev_0.8.3-1_amd64.deb
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&
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 o
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; I a
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.
>>>
>>> Ah
On 15 December 2016 at 14:56, Ian Jackson
wrote:
> Michael Kerrisk (man-pages) writes ("Re: Bug#848231: bugs in scandir example
> program"):
>> tags 848231 fixed-upstream
>> thanks
> ...>
>> On 15 December 2016 at 13:55, Ian Jackson
>> >
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 warnings with -Wall. Here is a
> patch (
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 (5). I would have expected them i
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 already have a man
On 13 December 2016 at 10:56, Thorsten Glaser 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). Obviously, various projects came
>>> 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 div
Hello Thorsten,
On 13 December 2016 at 10:43, 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; I assume the conflicting
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, 13 Dec 2016, Michael B
March 2014 at 08:34, Michael Kerrisk (man-pages)
wrote:
> On Sun, Mar 14, 2010 at 9:24 PM, Joey Schulze wrote:
>> Package: manpages-dev
>> Version: 3.24-1
>>
>> Forwarded mail from Daniel.
>>
>> - Forwarded message from Daniel Baluta -
>>
>&g
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 relea
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
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 thes
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
>
> In
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
>
> In
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
Th
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' to
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
> columns
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 b/man2/quot
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 with
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 than
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.
>>
>> http://pubs.opengro
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
an
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
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
> instead.
So, I think thi
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 report, Jakub. And t
On 12/28/2015 08:39 AM, Mathieu Malaterre wrote:
> On Sat, Dec 26, 2015 at 4:54 PM, Michael Kerrisk (man-pages)
> wrote:
>> (Upstream mainatiner here.)
>>
>> On 09/21/2015 03:08 PM, Mathieu Malaterre wrote:
>>> Package: manpages-dev
>>> Version: 3.65-1
&
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
>
(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
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 floa
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
> "perr
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
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 compatabili
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
wrote:
> Processing commands for cont...@bugs.debian.org:
>
>> reassign 7
tags 787625 fixed-upstream
thanks
Fixed with upstream commit be6b243ae2d6b3ba158684c945076a1fd65a6f2f
On 4 June 2015 at 16:49, Michael Kerrisk (man-pages)
wrote:
> On 06/03/2015 03:17 PM, Uwe Kleine-König wrote:
>> Package: manpages
>> Version: 3.74-1
>> Severity: minor
&g
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) {
> perror("ep
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 erro
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
> Signed-off-by: Ma Shimiao
> ---
> man3/printf.3 | 23 +++
> 1 file change
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 report
Hello Stéphane,
On 10 March 2015 at 00:26, Stéphane Aulery 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 Ker
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
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* keyw
tags 775328 fixed-upstream
thanks
Mathieu,
On 14 January 2015 at 08:57, Mathieu Malaterre 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 as:
>
> [..
1 - 100 of 185 matches
Mail list logo