It sounds like this is/was a valid regression report. It's something
that was considered:
> e.g. 4.2 may be selected instead of 4.0 used previously. This could
have an impact on workloads if there are any regressions in switching to
4.2 from 4.0 etc.
...but on balance we chose to proceed anyway. That's not necessarily a
wrong decision - we have to choose between fixing a valid bug and
risking regressing some users - but it's still a regression from the
perspective of this class of users.
Therefore, I think regression-update is correct, and I'd like to leave
that tag there for future analysis please. And I think the bug is valid,
albeit "Won't Fix" since at least for now we think that the original fix
is preferable even if some users are regressed (without applying a
workaround) from the protocol upgrade.
** Tags added: regression-update
** Changed in: nfs-utils (Ubuntu Focal)
Status: Invalid => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056549
Title:
Problems with nfs-common after upgrade to 3.6
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2056549/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
