Hi,
On Thu, Feb 10, 2022 at 08:13:12PM +0800, Tongliang Liao wrote:
> I'm aware of the exp version, but there're 2 concerns:
>
> 1. Deploying from exp repo doesn't sound right for production systems,
> for stability reason of course.
> 2. I'm not familiar of changes in nfs-utils. Given the major version
> update and the fact that both Debian 11/Sid haven't included v2, I
> guess it's either not well-tested on Debian, or has breaking changes that
> most people don't want? That's why I proposed for a simple backport,
> although most non-Debian distros have moved to v2 officially.
Let me explain, because I realize the just closing the bug might be
missinterpreted. This was for version tracking. The issue is fixed in
the repsective experimental version, so we can track it accordingly.
The BTS will show you still affected the unstable, testing and stable
version.
We "might" backport the fix to stable, once it is fixed in the upper
suite that said, and yes the target would then be to cherry-pick the
commit you referenced. Moving to 2.5.4 in stable is not an option.
So far we got only little feedback on the experimental version, so we
were not yet confident to upload it to unstable. But we need to move
this move earlier than too late for bookworm to avoid that we have
another Debian cycle with an ancient nfs-utils version.
There is as well an open question on how to handle the upstream
introduced move to /etc/nfs.conf.
Hope this clarifies your questions.
Regards,
Salvatore