Autofs mount fails if it relies on another autofs managed resource on Ubuntu; compile option missing

[Joe Jaeger]

I am trying to access an autofs mounted resource that depends on another autofs managed resource.
I.e. I try to open a truecrypt container that is located on a samba fileshare.
Both are registered with autofs and both are initially not mounted.
When I try to access the truecrypt container it fails. The autofs log says "no such file" for the cifs container and does not
try to mount the cifs resource automatically.
If I manually mount the cifs fileshare (or try to accesss this prior to the truecrypt) it works.

After some research and communication with the autofs maintainer (Ian Kent) I found out that in order for this to work autofs has to be configured with the configure option
--disable-mount-locking is used.

Currently, autofs_5.0.7-3ubuntu1.dsc does not use this option.
I contacted the autofs maintainer and he confirmed that
--disable-mount-locking should be used in the configure.
He believes that using this option causes no side effects and solves the issue I experience.

Additional infos requested:
1)
> lsb_release -rd
Description: Ubuntu 13.04
Release: 13.04

2)
>apt-cache policy autofs
autofs:
  Installed: 5.0.7-3ubuntu1
  Candidate: 5.0.7-3ubuntu1

3)
I would expect that the autofs_5.0.7-3ubuntu1.debian.tar.xz -> rules is adapted and the option
--disable-mount-locking
is added by default, see attachement patch

4)
n/a

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: autofs 5.0.7-3ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
Date: Sun Aug 25 18:51:02 2013
InstallationDate: Installed on 2013-03-30 (148 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: autofs
UpgradeStatus: Upgraded to raring on 2013-04-27 (119 days ago)

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "patch for rules file in utofs_5.0.7-3ubuntu1.debian.tar.xz" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[Brian Murray (brian-murray)]

I think it would be good to check with Debian about this change as the rules file came from them.

[Joe Jaeger (nimjj)]

Filed the bug in debian Bug#721331

[Christian Ehrhardt  (paelzer)]

Fix released for Zesty, added tasks for Xenial/Yakkety to consider backporting as SRU.
The change itself is to build with --disable-mount-locking

https://anonscm.debian.org/cgit/collab-maint/autofs.git/diff/?id=a9caea9