Bug#774149: fixing the stable package
[CCs to suitable-seeming people. If you are getting this email via the BTS too, sorry about the noise, but the BTS really should say who is subscribed.] Hi, The patch by Christian Weinberger fixes the problem for me, though I don't really understand it. It seems this bug breaks usbmount in stable, at least for me, and (it seems) others too. Is this a candidate for a stable fix? I'm willing to make a fix and do an upload if there is someone out there who will sponsor me. Or should I submit a pull request? And if so, where? Oh, but first, could we get come concensus that the Christian patch is the correct way to go? It looks good to me, but I don't understand the context well enough to say. Regard, Faheem Mitha
Bug#774149: fixing the stable package
On Fri, 4 Dec 2015, Jürgen Braun wrote: Hi all, the Patch from Christian works for me as well with one exception. I had to remove the file /lib/udev/rules.d/usbmount.rules after creating /etc/udev/rules.d/usbmount.rules. If I do not remove the original file, usbmount is called twice which leads to a double mount of the usb flash drive: $mount|grep sdd1 /dev/sdd1 on /media/usb1 type ext2 (rw,nosuid,nodev,noatime,nodiratime,errors=continue,user_xattr,acl) /dev/sdd1 on /media/usb2 type ext2 (rw,nosuid,nodev,noatime,nodiratime,errors=continue,user_xattr,acl) I've successfully tested ext2, vfat and ntfs based usb flash drives so far using this patch. I guess this is the systemd way to get this done. As far as I understood Christians patch, this adds a dependency to systemd (since it is using systemd-escape). I am not sure if this is the *best* way to do. How to deal with systems using sysvinit or upstart? I forgot to say that I replaced the old usbmount.rules with the old ones. Having two didn't make sense to me. So usbmount.rules went into /lib/udev/rules.d. Also, I put usbmount@.service in /lib/systemd/system. This was what lintian seemed to think was correct. anyway. I didn't check any documentation about this. I've no idea whether how or if this works for systems not using systemd. Regards, Faheem
Bug#774149: fixing the stable package
Hi all, the Patch from Christian works for me as well with one exception. I had to remove the file /lib/udev/rules.d/usbmount.rules after creating /etc/udev/rules.d/usbmount.rules. If I do not remove the original file, usbmount is called twice which leads to a double mount of the usb flash drive: $mount|grep sdd1 /dev/sdd1 on /media/usb1 type ext2 (rw,nosuid,nodev,noatime,nodiratime,errors=continue,user_xattr,acl) /dev/sdd1 on /media/usb2 type ext2 (rw,nosuid,nodev,noatime,nodiratime,errors=continue,user_xattr,acl) I've successfully tested ext2, vfat and ntfs based usb flash drives so far using this patch. I guess this is the systemd way to get this done. As far as I understood Christians patch, this adds a dependency to systemd (since it is using systemd-escape). I am not sure if this is the *best* way to do. How to deal with systems using sysvinit or upstart? best regards, Jürgen Am 04.12.2015 um 17:41 schrieb Faheem Mitha: > > [CCs to suitable-seeming people. If you are getting this email via the > BTS too, sorry about the noise, but the BTS really should say who is > subscribed.] > > Hi, > > The patch by Christian Weinberger fixes the problem for me, though I > don't really understand it. > > It seems this bug breaks usbmount in stable, at least for me, and (it > seems) others too. Is this a candidate for a stable fix? I'm willing to > make a fix and do an upload if there is someone out there who will > sponsor me. Or should I submit a pull request? And if so, where? > > Oh, but first, could we get come concensus that the Christian patch is > the correct way to go? It looks good to me, but I don't understand the > context well enough to say. > > Regard, Faheem Mitha >
