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. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-failed verification-failed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1637988 Title: Enable the nfs backend Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Fix Committed Status in gvfs source package in Cosmic: Fix Committed Bug description: * Impact The gio/nautilus nfs:// locations handling is missing * Test case Try to connect to/browse a nfs server from nautilus by using a nfs:// location * Regression potential It's a new backend being enabled, it shouldn't have an impact on the existing ones Note that the backend relies on libnfs which got promoted in disco and would need to be promoted in cosmic/bionic as well then To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1637988/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
