From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 221712] New: README.d/deps implies that there is a Debian package named checkpatch, but there isn’t
Date: Wed, 01 Jul 2026 17:36:24 +0000 [thread overview]
Message-ID: <bug-221712-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=221712
Bug ID: 221712
Summary: README.d/deps implies that there is a Debian package
named checkpatch, but there isn’t
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: man-pages
Assignee: documentation_man-pages@kernel-bugs.osdl.org
Reporter: jason@jasonyundt.email
Regression: No
README.d/deps says:
> Description
> There are different kinds of software dependencies on which this
> project depends. For maintaining the health of this project,
> the health of those dependencies is also essential. The
> following lists dependencies as <debian-package>/<binary>.
That same file goes on to say:
> Build
> To build the project, there are many dependencies, some
> of which are strictly necessary, and others which
> improve the quality (such as linters).
>
> This list can be generated by the build system itself.
> Run the following command to print this list:
>
> $ make -R help-list-build-depends
When I run “make -R help-list-build-depends”, all of the items on the list do
indeed appear be written as <debian-package>/<binary> except for one. One of
the items on the list is “checkpatch/checkpatch”. There is no Debian package
that’s named checkpatch (see <https://packages.debian.org/trixie/checkpatch>).
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2026-07-01 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 17:36 bugzilla-daemon [this message]
2026-07-01 19:20 ` [Bug 221712] README.d/deps implies that there is a Debian package named checkpatch, but there isn’t bugzilla-daemon
2026-07-01 21:52 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-221712-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.