Enable the nfs backend

Just got here when trying to migrate a user from Solaris to Ubuntu (16.04).

It would be nice to get at least some statement why it isn't included/when it might be included.

From what I can see 16.04.1 has gvfs 1.28.2 (e.g. >1.23.90) and libnfs 1.9.8 (e.g. >1.9.7).
That suggests that all prerequisites are covered based on the nfs support announcment post https://mail.gnome.org/archives/gvfs-list/2015-March/msg00000.html .

The fact that the requirements are met is exactly what made me file the bug in the first place. It's a huge usability failure, and dismissing it as "wishlist" without any further explanation is quite perplexing. :/

Ok, according to the changelog at http://changelogs.ubuntu.com/changelogs/pool/main/g/gvfs/gvfs_1.30.3-1ubuntu1/changelog, the problem is libnfs being in universe. Why is it not available in main?

Status changed to 'Confirmed' because the bug affects multiple users.

Still issue with 17.10

I have filed a Main Inclusion request for libnfs at LP: #1746598. When that is approved, we can enable the NFS backend in gvfs.

Still an issue with 18.04. FWIW, it is included in the Arch version of Gnome and gvfs-nfs works in Arch. Both in Nautilus and in DejaDup. NFS should also be a possible means of a backup with deja-dup, but because this module is not included in gvfs, it does not work. Waiting for this regression to be remedied.

Can't a libgvfs-nfs package be created separate from libgvfs-backends, the way Fedora does it? (https://apps.fedoraproject.org/packages/gvfs-nfs) That way it could stay in universe also. (I do think it should be included by default, but libnfs11 is still stuck in universe as of 18.10).

Guys, really? It's simple to resolve but there is still in backlog.

This has been fixed in Ubuntu 19.04 which will be released in April.

Can this please be backported to 18.04, give it's 10 year LTS status

Updating the bug for cosmic/bionics SRUs

Hello Rui, or anyone else affected,

Accepted gvfs into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gvfs/1.38.1-0ubuntu1.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Actually... so I poked the MIR team and they said the security team still needs to ACK the promotion of the packages for the stable series. Can we get security looking at this? I already accepted (a bit too hastily) the cosmic upload, for which I apologize. Guess formally we should make sure the libnfs package is in main before that happens.

Let me poke the MIR and security teams for feedback.

Hi, Łukasz

I will gladly help testing it when the packages hit cosmic-proposed. By the way, I'm not using nautilus anymore (I migrated to MATE), but I'm assuming caja will work just fine.

Thanks,
Rui

Hi again, Łukasz

I dist-upgraded the cosmic-proposed packages, tried browsing a couple of nfs shares and it worked perfectly on caja. I suppose nautilus will work fine too.

Thanks,
Rui

Hello Rui, or anyone else affected,

Accepted gvfs into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gvfs/1.36.1-0ubuntu1.3.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Why has this SRU been pushed against the current 2.0 version of libnfs in bionic and cosmic, when the Security Team has identified outstanding concerns with 2.0 in the MIR bug (LP:# 1746598; https://bugs.launchpad.net/ubuntu/+source/libnfs/+bug/1746598/comments/23)?

This does not look releasable as an SRU in its current state.

Marking verification-failed to block promotion, until the MIR concerns for the earlier libnfs version are resolved.

Also, note that this currently breaks daily image builds in bionic now that gvfs-backends in -proposed depends on libnfs11 from universe.

I'm deleting this SRU from bionic-proposed to unbreak image builds. It can always be copied back in over itself if we decide to go ahead with it after the MIR is completed.

The dependency libnfs is still in universe for Cosmic and the MIR bug was marked Won't Fix so I'm setting the verification to failed.

(removed the cosmic-proposed one as well now)

Following a discussion on December 17th in #ubuntu-desktop by the desktop team we have determine this issue won't be resolved in 18.04.