From: "Darrick J. Wong" <djwong@kernel.org>
To: Bastian Germann <bastiangermann@fishpost.de>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/3] debian: Drop unused dh-python from Build-Depends
Date: Fri, 5 Feb 2021 10:18:17 -0800 [thread overview]
Message-ID: <20210205181817.GN7193@magnolia> (raw)
In-Reply-To: <ca46724d-dce6-ac8c-65a7-99beb6bfc27c@fishpost.de>
On Fri, Feb 05, 2021 at 07:05:12PM +0100, Bastian Germann wrote:
> Am 05.02.21 um 01:51 schrieb Darrick J. Wong:
> > On Fri, Feb 05, 2021 at 01:31:23AM +0100, Bastian Germann wrote:
> > > xfsprogs participates in dependency loops relevant to architecture
> > > bootstrap. Identifying easily droppable dependencies, it was found
> > > that xfsprogs does not use dh-python in any way.
> >
> > scrub/xfs_scrub_all.in and tools/xfsbuflock.py are the only python
> > scripts in xfsprogs. We ship the first one as-is in the xfsprogs
> > package and we don't ship the second one at all (it's a debugger tool).
> >
> > AFAICT neither of them really use dh-python, right?
>
> That is right. dh-python is generally used at build time to generate
> packages with Python modules, i.e., with files in
> /usr/lib/python3/dist-packages. That is not the case in xfsprogs.
>
> For xfsprogs, python3 is only a runtime dependency and that is defined in
> the control file as well.
<nod> /me finally figures out exactly what dh_python does--I thought it
was required for any package shipping any python anything, but I guess
it's only for building and prepping library code and hence not needed
for our single python script in /usr/sbin, so:
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
>
> > --D
> >
> > >
> > > Reported-by: Helmut Grohne <helmut@subdivi.de>
> > > Signed-off-by: Bastian Germann <bastiangermann@fishpost.de>
next prev parent reply other threads:[~2021-02-05 18:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 0:31 [PATCH 0/3] debian: minor fixes Bastian Germann
2021-02-05 0:31 ` [PATCH 1/3] debian: Drop unused dh-python from Build-Depends Bastian Germann
2021-02-05 0:51 ` Darrick J. Wong
2021-02-05 4:49 ` Eric Sandeen
2021-02-05 18:05 ` Bastian Germann
2021-02-05 18:18 ` Darrick J. Wong [this message]
2021-02-05 0:31 ` [PATCH 2/3] debian: Only build for Linux Bastian Germann
2021-02-05 0:48 ` Darrick J. Wong
2021-02-05 0:31 ` [PATCH 3/3] debian: Prevent installing duplicate changelog Bastian Germann
2021-02-05 0:49 ` Darrick J. Wong
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=20210205181817.GN7193@magnolia \
--to=djwong@kernel.org \
--cc=bastiangermann@fishpost.de \
--cc=linux-xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox