Bug#364977: manpages-dev: clone.2 needs updating

2006-04-30 Thread Michael Kerrisk
Hi Joey, > Err... could somebody enlighten me if this bug still holds or not? > > It seems that Michael asserted that it's not a bug, correct? Correct. Cheers, Michael -- Michael Kerrisk maintainer of Linux man pages Sections 2, 3, 4, 5, and 7 Want to help with man page maintenance? Grab

Bug#364977: manpages-dev: clone.2 needs updating

2006-04-30 Thread Martin Schulze
Michael Kerrisk wrote: > Hi Justin, > > > > > > Yes. I mean, if you open a report and immedaitely tag it > > > > "upstream" means that the bug is not in the Debian .diff.gz, and the > > > > version indicates what version the bug was found in. > > > > > > Oh -- thanks for the education. I had

Bug#364977: manpages-dev: clone.2 needs updating

2006-04-27 Thread Justin Pryzby
On Fri, Apr 28, 2006 at 01:19:28AM +0200, Michael Kerrisk wrote: > Hi Justin, > > > > > > > Tags: upstream > > > > > > > > > > Any time you open a report like this you better make sure > > > > > that whatever you say holds against the latest upstream release. > > > > Do you mean of manpages? > >

Bug#364977: manpages-dev: clone.2 needs updating

2006-04-27 Thread Michael Kerrisk
Hi Justin, > > > > > Tags: upstream > > > > > > > > Any time you open a report like this you better make sure > > > > that whatever you say holds against the latest upstream release. > > > Do you mean of manpages? > > > > Yes. I mean, if you open a report and immedaitely tag it > "upstream" me

Bug#364977: manpages-dev: clone.2 needs updating

2006-04-27 Thread Michael Kerrisk
Hi Justin, > > > > Yes. I mean, if you open a report and immedaitely tag it > > > "upstream" means that the bug is not in the Debian .diff.gz, and the > > > version indicates what version the bug was found in. > > > > Oh -- thanks for the education. I had guessed it means that the > > report

Bug#364977: manpages-dev: clone.2 needs updating

2006-04-27 Thread Justin Pryzby
On Thu, Apr 27, 2006 at 11:38:17PM +0200, Michael Kerrisk wrote: > Justin, > > > > > Tags: upstream > > > > > > Any time you open a report like this you better make sure > > > that whatever you say holds against the latest upstream release. > > Do you mean of manpages? > > Yes. I mean, if you o

Bug#364977: manpages-dev: clone.2 needs updating

2006-04-27 Thread Michael Kerrisk
Justin, > > > Tags: upstream > > > > Any time you open a report like this you better make sure > > that whatever you say holds against the latest upstream release. > Do you mean of manpages? Yes. I mean, if you open a report and immedaitely tag it upstream like this, my assumption would be tha

Bug#364977: manpages-dev: clone.2 needs updating

2006-04-26 Thread Justin Pryzby
On Thu, Apr 27, 2006 at 04:54:09AM +0200, Michael Kerrisk wrote: > Justin, > > > Tags: upstream > > Any time you open a report like this you better make sure > that whatever you say holds against the latest upstream release. Do you mean of manpages? > > It seems that the clone manpage is out of

Bug#364977: manpages-dev: clone.2 needs updating

2006-04-26 Thread Michael Kerrisk
Justin, > Tags: upstream Any time you open a report like this you better make sure that whatever you say holds against the latest upstream release. > It seems that the clone manpage is out of sync with the libc/kernel > reality. > > In particular, the following succeeds, The preceding is near

Bug#364977: manpages-dev: clone.2 needs updating

2006-04-26 Thread Justin Pryzby
Package: manpages-dev Version: 2.25-3 Severity: normal Tags: upstream It seems that the clone manpage is out of sync with the libc/kernel reality. In particular, the following succeeds, but the annotation says that it should not: CLONE_NEWNS|CLONE_FS CLONE_THREAD (because CLONE_SIGHAND