Comment 2 for bug 625953

No. This was during a maintenance update of a running Lucid (10.04) system. autofs5 had been running on the affected machines for months. The previous version of autofs was 5.0.4-3.1ubuntu5. (Without the .1 at the end)

There were no magic done prior to the update. Just a normal, apt-get update and apt-get dist-upgrade, to get the latest kernel update.

Then the shit hit the fan when it came to autofs, complaining that /usr/share/autofs5/conffiles did not exist. The update then bailed out prematurely, and I had to do a dpkg --configure -a to be able to continue. I then had to create the before mentioned directory structure by hand and populate them with auto.master and default.autofs5, which I copied from /etc/default/autofs.

I did this on three different systems, just to verify the behavior. Two virtual hosts and one stand-alone system.

Currently autofs works, since default.autofs5 and /etc/default/autofs both point to the auto.master in /etc, so it's not critical.

 -- K