On Tue, 12 May 2015 16:06:37 +0200 Michael Biebl <bi...@debian.org> wrote:
> Am 12.05.2015 um 15:57 schrieb IgnorantGuru: > > Are there human beings responding to this bug, or just bots? > > "Michael Biebl" doesn't seem to be reading anything said to him? > > Are emails being received? > > No, if you want to contact me, Michael Biebl, you need to CC me. > If you only email the bug number, only the bug tracking system (and > the maintainer of the package) will receive email. > Thank you for your response. Because my message appeared in your bug here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750510#35 I erroneously thought you were aware of it. > > Trying again, here is the explanation for why every statement made > > in this bug report about SpaceFM and udisks is incorrect (from over > > 2 months ago, message #35): > > Well, I clarified that in [1], so I don't think it's correct to say > that every statement in this bug report is incorrect. > > That said, can you elaborate on the usage of the "udisks" mount > option, which is udisks v1 only. > I don't see a similar code for uhelper=udisks2. It this an omission or > deliberately left out? > > Michael > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750510#63 > There is no 'udisks' mount option passed by SpaceFM. As I said, SpaceFM does still support the (optional) use of udisks v1, in addition to udisk v2 (and other solutions), so there is still active code that pertains to udisks v1. But the dbus interface is not used, and udisks v1 is not required. In 1.0.1, you can see how SpaceFM constructs a default mount command using discovery, for example, here (udisksctl is udisks v2): https://github.com/IgnorantGuru/spacefm/blob/07be3fd40da4c619cbc1af5461c00d385cadd69a/src/vfs/vfs-volume-nohal.c#L3692 In 1.0.1, device handlers are configured by the user which can use any combination of mount solutions (udisks v2, udisks v1, udevil, pmount, etc.) You can see the users manual on this here, which mentions udisks2: http://ignorantguru.github.io/spacefm/spacefm-manual-en.html#handlers-dev SpaceFM has been working fine with udisks2 (and without udisks1) for several versions dating back over a year. So I think this report can safely be closed (and was never a genuine issue, except maybe for the udisks package dependency). If you have any other questions on the specifics feel free to ask. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
