From: Salvatore Bonaccorso <carnil@debian.org>
To: Benjamin Coddington <bcodding@redhat.com>,
Andreas Hasenack <andreas@canonical.com>
Cc: Steve Dickson <steved@redhat.com>,
Scott Mayhew <smayhew@redhat.com>,
Ben Hutchings <benh@debian.org>,
linux-nfs@vger.kernel.org
Subject: Re: Always run rpc-pipefs-generator generator (was: Re: Why keep var-lib-nfs-rpc_pipefs.mount around?)
Date: Mon, 24 Jul 2023 11:12:28 +0200 [thread overview]
Message-ID: <ZL5AfARR1rrlPEdz@eldamar.lan> (raw)
In-Reply-To: <A172CCB3-973D-4A26-A8AF-3D654F4D444F@redhat.com>
Hi,
On Mon, Jul 10, 2023 at 10:39:43AM -0400, Benjamin Coddington wrote:
> On 9 Jul 2023, at 3:38, Salvatore Bonaccorso wrote:
>
> > Hi Steve,
>
> ...
>
> > FWIW, in Debian we have applied the respective change. The idea would
> > be to only depend on a single mechanism for setting up the mounts
> > rather than a combination of the two (the generator and the static
> > mount unit). For this reason we have applied the attached patch, and
> > are not installing the units that we will let the generator produce,
> > that is var-lib-nfs-rpc_pipefs.mount and rpc_pipefs.target
> >
> > We in Debian for long have diverged too much from you upstream,
> > causing that we lacked behind several new upstream version and stuck
> > with old versions in stable releases. We want to avoid running into
> > that again in future. So if this make sense to you, would you apply
> > the same (or as you prefer similar) change to you upstream?
> >
> > On one side so you could apply Andreas Hasenack patch, secondly
> > installing the var-lib-nfs-rpc_pipefs.mount and rpc_pipefs.target
> > could be dropped (note no changes to the other units needed as the
> > repsective needed dependencies are generated by the systemd
> > generator).
> >
> > Ben, Andreas, please add what else is needed from your point of view
> > please!
>
> I don't think I've seen the PATCH land on the list addressed to nfs-utils
> maintainer yet, but I could have missed it.
>
> Otherwise it looks sane to me, but I could be missing some upstream case.
>
> > Thanks a lot for considering this. If you have any suggestion further
> > how we can unify the Debian downstream to you upstream, let us know
> > please.
>
> At Red Hat, we use "upstream first" as a leading principle. If this change
> makes sense for upstream, send Adreas' patch along and I am sure Steve D will
> consider it or let us know why its not acceptible for upstream.
Andreas, could you sent a proper patchset please, so upstream can have
a look at it for inclusion?
Regards,
Salvatore
next prev parent reply other threads:[~2023-07-24 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 16:50 Why keep var-lib-nfs-rpc_pipefs.mount around? Andreas Hasenack
2022-07-11 13:13 ` Benjamin Coddington
2022-07-23 17:29 ` Steve Dickson
2022-07-25 12:38 ` Andreas Hasenack
2023-07-09 7:38 ` Always run rpc-pipefs-generator generator (was: Re: Why keep var-lib-nfs-rpc_pipefs.mount around?) Salvatore Bonaccorso
2023-07-10 14:39 ` Benjamin Coddington
2023-07-24 9:12 ` Salvatore Bonaccorso [this message]
2023-07-24 13:13 ` Andreas Hasenack
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=ZL5AfARR1rrlPEdz@eldamar.lan \
--to=carnil@debian.org \
--cc=andreas@canonical.com \
--cc=bcodding@redhat.com \
--cc=benh@debian.org \
--cc=linux-nfs@vger.kernel.org \
--cc=smayhew@redhat.com \
--cc=steved@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).