Package Details: autofs 5.1.9-5

Git Clone URL: https://aur.archlinux.org/autofs.git (read-only, click to copy)
Package Base: autofs
Description: A kernel-based automounter for Linux
Upstream URL: https://www.kernel.org/pub/linux/daemons/autofs/
Keywords: autofs,auto mount
Licenses: GPL2
Submitter: arojas
Maintainer: ajacocks
Last Packager: ajacocks
Votes: 43
Popularity: 0.56
First Submitted: 2021-05-08 08:58 (UTC)
Last Updated: 2024-08-16 04:39 (UTC)

Dependencies (10)

Sources (43)

Latest Comments

1 2 3 4 5 6 .. 8 Next › Last »

mok0 commented on 2025-03-21 16:39 (UTC)

After installing autofs using makepkg -si I experienced the very, very weird situation when trying to edit the conf files that they didn't exists! In my many years with Linux I've never seen anything like this. When listing the files in /etc with wildcard auto* they appear to exist, and even have a size, but when trying to list the files individually, the shell claims they don't exist.

I'm not sure if this is caused by the way makepkg -si installs files that are supposed to be owned by root or if my btrfs filesystem is simply corrupted.

[root@archbox etc]# ls -lb auto*
total 36
-rw-r--r-- 1 root root 16216 Mar 21 14:58 autofs.conf
-rw------- 1 root root   232 Mar 21 14:58 autofs_ldap_auth.conf
-rw-r--r-- 1 root root  1317 Mar 21 14:58 auto.master
drwxr-xr-x 1 root root     0 Mar 21 14:58 auto.master.d
-rw-r--r-- 1 root root   519 Mar 21 14:58 auto.misc
-rwxr-xr-x 1 root root   897 Mar 21 14:58 auto.net
-rwxr-xr-x 1 root root  2083 Mar 21 14:58 auto.smb
[root@archbox etc]# ls -lb autofs.conf
ls: cannot access 'autofs.conf': No such file or directory

If I try using auto dot wildcard I get the same:

[root@archbox etc]# ls auto.*
ls: cannot access 'auto.*': No such file or directory

drekbour commented on 2024-10-10 20:37 (UTC)

When it asks Packages to cleanBuild?, choose [A]ll instead of the default ([N]one).

joanmanel commented on 2024-09-16 07:36 (UTC)

How do I delete the old source files? I am using yay

Vasily.Bortnikov commented on 2024-09-06 17:23 (UTC)

You can import it manually: gpg --keyserver keyserver.ubuntu.com --recv-keys E7677380F54FD8A9

hippieben commented on 2024-08-28 04:28 (UTC) (edited on 2024-08-28 04:29 (UTC) by hippieben)

Having trouble building for some reason

gpg: error reading key: No public key

:: PGP keys need importing: -> CD0A6E3CBB6768800B0736A8E7677380F54FD8A9, required by: autofs :: Import? [Y/n] :: Importing keys with gpg... gpg: keyserver receive failed: No keyserver available -> problem importing keys

pvdp commented on 2024-08-17 06:31 (UTC) (edited on 2024-08-17 06:33 (UTC) by pvdp)

Thx grawity, deleting the old source files did the trick!

ajacocks commented on 2024-08-16 14:41 (UTC)

Thanks, grawity. I was just about to suggest that as a possibility. Given the number of patches that are being added upstream, pre-5.2.0, I have been thinking about how I might be able to automate the patch integration process, but haven't come up with anything interesting, yet.

grawity commented on 2024-08-16 06:02 (UTC)

Still an issue after latest update. Looks like more patches.

You're probably verifying old files against new checksums. Delete your previously downloaded source files and let makepkg re-download the updated ones.

ajacocks commented on 2024-08-16 04:42 (UTC)

I'm not sure why you're seeing that. I checked the checksums, and they are correct. To try to improve verification, I have added GPG signature verification of the upstream maintainer's key.

1 2 3 4 5 6 .. 8 Next › Last »