man page for copy_file_range() not up to date with mainstream

Bug #1999625 reported by nitin bhutani
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
manpages (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

The man page for copy_file_range() system call is not up to date with the corresponding mainline kernel release. For example, the contents of the following commit is not there when I run man 2 copy_file_range:

https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=d7ba612d0ab10af2ed4e367306784212cc3f3595

tags: added: manpage
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1999625/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → coreutils (Ubuntu)
affects: coreutils (Ubuntu) → ubuntu-docs (Ubuntu)
Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

That commit is included in the development version (coming Ubuntu 23.04).

$ lsb_release -irs
Ubuntu
23.04
$ dpkg-query -W manpages-dev
manpages-dev 6.01-1
$ man 2 copy_file_range | grep EOPNOTSUPP
       EOPNOTSUPP (since Linux 5.12)

affects: ubuntu-docs (Ubuntu) → manpages (Ubuntu)
Changed in manpages (Ubuntu):
status: New → Fix Released
Revision history for this message
nitin bhutani (bhutaninitin) wrote : Re: [Bug 1999625] Re: man page for copy_file_range() not up to date with mainstream

 Could you please check if the latest changes to the man page went in? Please see https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/man2/copy_file_range.2?id=4cf763f7cf83d1fd713c7467ebbe15ca9b0ca749
May be grep for "backported to earlier stable kernels".

    On Thursday, 15 December, 2022 at 01:30:16 am IST, Gunnar Hjalmarsson <email address hidden> wrote:

 That commit is included in the development version (coming Ubuntu
23.04).

$ lsb_release -irs
Ubuntu
23.04
$ dpkg-query -W manpages-dev
manpages-dev    6.01-1
$ man 2 copy_file_range | grep EOPNOTSUPP
      EOPNOTSUPP (since Linux 5.12)

** Package changed: ubuntu-docs (Ubuntu) => manpages (Ubuntu)

** Changed in: manpages (Ubuntu)
      Status: New => Fix Released

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1999625

Title:
  man page for copy_file_range() not up to date with mainstream

Status in manpages package in Ubuntu:
  Fix Released

Bug description:
  The man page for copy_file_range() system call is not up to date with
  the corresponding mainline kernel release. For example, the contents
  of the following commit is not there when I run man 2 copy_file_range:

  https://git.kernel.org/pub/scm/docs/man-pages/man-
  pages.git/commit/?id=d7ba612d0ab10af2ed4e367306784212cc3f3595

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1999625/+subscriptions

Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

On 2022-12-15 04:13, nitin bhutani wrote:
> Could you please check if the latest changes to the man page went in?

Sorry, but this is a bug tracker, not a "look for my favorite commit" service.

Please understand that those manpages are packaged at Debian in a separate source package named just "manpages", and the changes you originally asked about are there in Lunar, but not in 22.04 and 22.10.

New upstream versions are normally not backported to stable releases. That's true in both Debian and Ubuntu.

If someone want's to cherry pick some important change, and propose that an Ubuntu stable release is updated with it, anybody is free to follow the instructions in this guide:

https://wiki.ubuntu.com/StableReleaseUpdates

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.